Wikipedia talk:WikiProject Geographical coordinates/Archive 19

Fastcgi error
On Template talk:Coord and Template talk:Infobox nrhp2 there is discussion about Coord returning: This server has encountered an internal error which prevents it from fulfilling your request. The most likely cause is a misconfiguration. Please ask the administrator to look for messages in the server's error log."
 * "Fastcgi Protocol Error

From the couple cases which I looked at, This is apparently due to Coord being supplied with a "template" parameter (display=title, format=dms, name= ...) without a "coordinates" parameter (region:, type:, scale:, source:, ...) resulting in a "malformed" URL ending in "_". For instance: with generated:
 * Wollaston Islands (Nunavut)
 * 73.71667°N, -80.91667°W
 * http://stable.toolserver.org/geohack/geohack.php?pagename=Wollaston_Islands_(Nunavut)&params=73_43_00_N_80_55_00_W_

resulting in: http://stable.toolserver.org/geohack/geohack.php?pagename=Wollaston_Islands_(Nunavut)&params=73_43_0_N_80_55_0_W_region:CA-NU_type:island&title=Wollaston+Islands+%28Nunavut%29 which works.
 * I updated the "offending" coordinates to:
 * 73.71667°N, -80.91667°W

i.e. add a "coordinates" parameter (region, type, scale, source, ...) whenever adding a "template" parameter (display, format, name, ...) LeheckaG (talk) 07:25, 5 August 2008 (UTC)


 * Specifically, the problem appears to be with missing the "region:" coordinates parameter. From my limited tests playing with a "malformed" URL, it appears that when a region: parameter is NOT supplied, then the Fastcgi error occurs.  But when a region: parameter is supplied (even if empty), then the Fastcgi error does not occur.

LeheckaG (talk) 07:47, 5 August 2008 (UTC)


 * Recent Toolserver geohack.php (actually mapsources.php) source code changes appear to have nothing to do with the Fastcgi error:

Specifically 2008-07-30 21:34:38 +0000 Author: magnus, Patch by en:user:SQL and 2008-08-03 21:39:23 +0000 Author: magnus, extended list of scales, by en:user:Docu
 * https://fisheye.toolserver.org/browse/geohack/www
 * https://fisheye.toolserver.org/browse/geohack/www/mapsources.php?r1=1&r2=3
 * https://fisheye.toolserver.org/browse/geohack/www/mapsources.php?r1=3&r2=4

So the "source" of the Fastcgi issue would appear to be something else on ToolServer which changed "recently" and either calls geohack.php or is called by geohack.php LeheckaG (talk) 09:00, 5 August 2008 (UTC)


 * Previous (geohack/mapsources) changes were more than a couple weeks ago. Does anyone know of the earliest reported instance of Fastcgi Protocol Error?

"(But look out for a future post about switchboard, a fast replacement for suphp using FastCGI -- if I ever get around to finishing it.) Posted at 11:44PM Jun 21, 2008 by River in Tech"
 * ToolServer Blog mentions:

I am not sure whether the "glue" between the World Wide Web and ToolServer's .php scripts like geohack.php is? or So, I am not sure what changed "recently" (also not sure what "recently" means - 2 days, 2 weeks, ...)? LeheckaG (talk) 09:20, 5 August 2008 (UTC)
 * Python_WSGI
 * https://fisheye.toolserver.org/browse/~raw,r=37448/wikimedia/trunk/switchboard/


 * The toolservers give that FastCGI error for scripts that are running too long, and interrupts them. GeoHack shouldn't run long of course, but as LeheckaG noticed, it was taking its time when a region hadn't been given. That's because the region lookup functionality is running on another server that was unresponsive at the time, and GeoHack was waiting all eternity for it to answer. A bug report has been submitted. --Para (talk) 10:41, 5 August 2008 (UTC)


 * So the "moral" of the story is to "always" supply a "region:" with an accurate ISO 3166-1 (and 3166-2 region, for instance US-AK for Alaska, or US-OH for Ohio, ...) and some Geobox/Infobox which create a "Coor(d)" should supply the appropriate region (if known) when creating the Coor(d), or at least as much of it as known, for instance I updated Infobox nrhp2 to supply region:US_type:landmark (would be nice if the -XX state was coded/known) since nrhp2 and nrhp are specific to the United States of America. I did not update (yet?) but will check on the Infobox nrhp as well (not sure which other US-specific Geobox/Infobox templates there might be?)  LeheckaG (talk) 10:50, 5 August 2008 (UTC)


 * It's exceptional for the main toolserver to be so busy that it doesn't answer within the 30 second fastcgi timeout, but with the current code always having the region parameter would be a quick workaround, yes. --Para (talk) 11:18, 5 August 2008 (UTC)


 * Infobox nrhp does supply "region:US_type:landmark", which was why nrhp2 (prior to adding region:US) was more susceptible to the Fastcgi timeout error than nhrp. LeheckaG (talk) 12:14, 5 August 2008 (UTC)


 * (From my talkpage) Well, when that happens to me, I check with the toolserver administrators. Having taken a look at the error log for the stable toolserver, I'm not seeing any specific problems from this application. Also, in reloading the same URL 10 times, I get one fastcgi error, and, nine successful pageloads. These two things combined, tell me there is not a problem with the application, but, with the underlying server (specifically Fastcgi... Hence the FastCGI Protocol error most likely, and not a blank page or a 500 internal server error, or a PHP error.). I don't think we use switchboard on stable, all projects there use FastCGI (and, I'm fairly sure there's no way around it). I'll see what I can do as far as bugging people, to get the problem resolved soon. SQL Query me!  14:34, 5 August 2008 (UTC)


 * As the creator of Wollaston Islands (Nunavut), I want to say thanks to all involved for your follow-up on this Fastcgi error issue. --Rosiestep (talk) 21:42, 5 August 2008 (UTC)

bad Coor(d)
Maintenance tasks:
 * someone? should scan through the Geobox/Infobox templates to see which do and which do not supply region: with a valid ISO 3166-1 (like US) and or -2 (like US-AK for Alaska) code. (Infobox nrhp and nrhp2 both supply US, would be nice if they supplied US-XX where XX is the state code).
 * likewise a list (sub- Category: ?) of "bad" coordinates should be created with a bot? populating such "list" with those articles containing coordinates which are not "completely/properly" specified. Perhaps a sub- Category: of "Articles needing coordinates" or "Pages requiring geodata verification"?  LeheckaG (talk) 12:14, 5 August 2008 (UTC)

To be included on the Indonesian Wikipedia
I just wondering on how to put this feature on Indonesian Wikipedia? I am one of the contributor there and now we have article around 84,000 more and one of our target is reaching 100,000 by the end 2008. ThanksNaidNdeso (talk) 22:10, 8 August 2008 (UTC)

Response
I am not sure "which" feature? In general: are the primary templates along with their inclusions/sub-templates, and categories. Additionally, you need the appropriate CSS class=/id= like "coordinates" and "geo*" (* meaning all) from common.css and Skins.
 * Coord
 * GeoGroupTemplate
 * GeoTemplate

If you post which feature(s) as well as a suggested use on the Indonesian Wikipedia, then we can probably provide some guidance as what needs to be copied over.

If we know what exactly you are looking for, we can possibly post a "How To" so that other language Wikipedias have a step-by-step "installation guide". LeheckaG (talk) 10:22, 9 August 2008 (UTC)

I forgot to also mention the MiniAtlas (when you click on a "globe" the pop-up map which appears), it depends on some JavaScript, but I am not sure exactly which files or pages are needed.

So post what you are looking for and then we can post the various details. LeheckaG (talk) 10:25, 9 August 2008 (UTC)


 * There is a short FAQ on meta:WikiMiniAtlas. Just put

importScriptURL('importScriptURI( 'http://meta.wikimedia.org/w/index.php?title=MediaWiki:Wikiminiatlas.js' + '&action=raw&ctype=text/javascript&smaxage=21600&maxage=86400' );
 * in your site's MediaWiki:Common.js --Dschwen 14:57, 9 August 2008 (UTC)

Celestial Coordinate clickable template?
Has any thought ever been given to a template that would link a set of celestial coordinates to online sky "charts" (assuming such charts are/will soon be readily available)? This would be similar to how template:coor works. Likewise with selenographic coordinates. &mdash; Eoghanacht  talk 21:44, 14 August 2008 (UTC)


 * For the latter (Moon), there exist:

although Talk suggested United States Geological Survey MapAPlanet.Org:
 * MoonTemplate corresponding to GeoTemplate; currently the map source is Google,
 * Example: http://stable.ts.wikimedia.org/geohack/moonhack.php?params=49_45_24_N_6_38_29_E corresponding to GeoHack
 * which links to: http://www.google.com/moon/#lat=49.756667&lon=6.641389&zoom=8
 * http://www.mapaplanet.org/explorer-bin/explorer.cgi?map=Moon&layers=moon_clementine_multi&west=55.25&south=32.61&east=60.00&north=34.99&center=57.625&defaultcenter=on&grid=none&stretch=none&projection=SIMP&r=5&g=3&b=1&advoption=NO&info=NO&resolution=303.23&scale=0.1185&imageTopX=-85419.456763&imageTopY=1067441.160253.


 * The missing "glue" is an appropriate Geo Microformat:

and corresponding Wikipedia templates (either similar to or modified versions of the Coor(d) templates which emit the Geo microformat (enabling the "clickable link"). The principal thing which is missing is an XML (geo microformat) tag indicating which celestial body the coordinates are on, and then the "glue" - on ToolSever - a modified geohack URL and geohack.php (instead of one for each planet like the moonhack.php, unless separate URLs are a better way to go?) and modified Coor(d) templates which accept an optional parameter to emit the appropriate geo tag.
 * http://microformats.org/wiki/geo-extension-strawman
 * In addition to the Moon, currently Google also has Mars.


 * There are several Astronomical coordinate systems, Google Sky uses the most common? Equatorial coordinate system, not sure which Epoch they use B1950, J2000? (longitude=Right Ascension (24 hours=360 degrees) and latitude=declination), for example:


 * http://www.google.com/sky/#latitude=32.186073305250304&longitude=-96.82525634765625&zoom=11&Spitzer=0.00&ChandraXO=0.00&Galex=0.00&IRAS=0.00&WMAP=0.00&Cassini=0.00&slide=1&mI=-1&oI=-1


 * RA and DEC accept and display Right Ascension and Declination, but do not provide clickable links. See also:.

For example: produces: which links to:
 * EqCoor (or EqCoor-DEC and EqCoor-RA) provides clickable links to WikiSky.Org.
 * http://www.wikisky.org/w/index.php?title=Equatorial_coordinates&astro_params=12+22+54.9++15+49+21+15+M100.

See also. LeheckaG (talk) 07:26, 15 August 2008 (UTC)


 * There is some work going on at de:Portal_Diskussion:Astronomie/Wikisky&Googlesky, with a Skyhack being developed http://toolserver.org/~kolossos/sky/skyhack.php?ra=11.1925&de=-61.3622222222&size=0.05&name=NGC%203576 . --Dschwen 11:40, 15 August 2008 (UTC)