Template talk:Location/2009

Help with broken instance

I am new to the template, and made some errors using it, at File:Diner on Route 40 Delaware by Rothstein OWI.jpg. (I wanted to use decimal coordinates, and to specify a small mapping scale, as I don't know where on Route 40 the photo was taken. The Google Maps and Google Earth links ended up broken.) Could you guide me in correcting the page, please? --InfantGorilla (talk) 16:09, 16 December 2008 (UTC)

I still need help. --InfantGorilla (talk) 11:03, 26 January 2009 (UTC)

Done. Thanks Para. --InfantGorilla (talk) 14:42, 26 January 2009 (UTC)

Category: Templates generating Geo ‎

{{Editprotected}} Please add Category: Templates generating Geo. Thank you. Andy Mabbett (talk) 15:00, 24 January 2009 (UTC)

Added. --Dschwen (talk) 18:03, 24 January 2009 (UTC)

Thank you. Andy Mabbett (talk) 20:30, 25 January 2009 (UTC)

direction: "heading"

shouldn't we add point of the compass of the image? --W!B: (talk) 22:27, 4 March 2009 (UTC)

We should, and we are. At least people who know that the heading parameter does exist :-). example. --Dschwen (talk) 23:53, 4 March 2009 (UTC)

fine, i added some minor descriptions --W!B: (talk) 20:50, 11 March 2009 (UTC)

Internationalization of {{Location}} template

I created internationalized versions of 4 location templates:

• {{Location}} - at temporary location User:Jarekt/b
• {{Location dec}} - at temporary location User:Jarekt/a
• {{Object location}} - already uploaded
• {{Object location dec}} - already uploaded

Here is test image with those 4 templates: in english and polish version. All 4 templates use the same set of translation phrases and the same layout template. I am seeking comments before asking for upload of the first 2 templates. --Jarekt (talk) 12:56, 10 March 2009 (UTC)

 Done The above 4 templates are now internationalized --Jarekt (talk) 02:23, 17 March 2009 (UTC)

Nice work! --Dschwen (talk) 02:35, 17 March 2009 (UTC)

vcard

Original {{Location}} source code had the following line: <span style="display:none" class="fn org">{{{name|{{PAGENAME}}}}}</span> which was copied to the current Template:Location/layout. Whatever was its intended use it is probably currently not working since {{{name}}} argument is not passes to the template. This can be fixed, but I was wandering what is the purpose of that line. w:HCard mentions "If the hCard is for an organization or venue, the fn and org classes are used on the same element, as in Wikipedia or Wembley Stadium." However this use do not make much sense in relation to {{Location}}. Does anybody know if we need to keep this line?--Jarekt (talk) 13:31, 16 March 2009 (UTC)

The <span style="display:none" class="fn org">{{{name|{{PAGENAME}}}}}</span> line was removed from the template. --Jarekt (talk) 15:32, 18 March 2009 (UTC)

In a microformats aware browser, a page with fn org on it will enable the map button that when pressed would launch an internet map application for the location(s). Multiple locations can be emitted for a single article, and in the most popular implementation, the "fn" (full name) values appear as items in a menu when the map button is pressed. Without the fn org info, no items will appear. Currently, the only browser that I am aware of that handles microformats reliably is Firefox with the en:Operator (extension) installed. Major browsers have made noises about having full support for microformats in their coming version, but though Firefox (and possibly IE) has it implemented in native internal functions so far this has not materialized in the UI. Info on setup of Operator and example use for location as well as dates working on WP may be found here. Do you guys want this functionality back in this template? If so I will create a sandboxed version of location so that it will work again. -J JMesserly (talk) 17:13, 5 April 2009 (UTC)

I would like to see the microformat syntax back, it makes a lot of sense to have a microformat attached to a location. Note that images using the {{Description}} template, already have a vcalendar microformat attached. Adding vcard (with geo) only incresases the usability. --Qyd (talk) 02:26, 7 April 2009 (UTC)

It does make sense, and my personal opinion is to have it back too, but the reality is that all commons visitors can use the Geohack links, whereas the only users that can navigate using the microformat emitted coords are those with firefox with the operator extension installed. Microformats is something that few template writers understand or care about and it keeps getting tripped over. I'd be happy to fix it, but if there are objections, I'd rather not waste time on something that's only going to get ripped out again. -J JMesserly (talk) 17:26, 7 April 2009 (UTC)

I removed it because I was cleaning up the location template family and could not find the purpose of this tag, and could not test if it works properly. Also, I merged 6 templates into one and I think only one of them had it. If it does serve a purpose please put it back in and verify that it works properly. Maybe add a note in the documentation about it. This discussion will (hopefully) prevent future removals. --Jarekt (talk) 01:58, 8 April 2009 (UTC)

(undent) Ok, I will take a look at it tomorrow. Is there any objection to adding an optional parameter #10 to all variants? This would be the proper name that corresponds to the geo location, and so there should be minimal internationalization issues (other than non latin transliterations). I cannot implicitly assume PAGENAME, since uploaded file names are usually poor candidates, and may refer not to the location, but the subject matter of the image. The name parameter can be optional because in these instances Operator for example gracefully degrades, displaying just the coordinates in the menu. Not too helpful to the commons user, but better than no text at all. -J JMesserly (talk) 17:52, 8 April 2009 (UTC)

About optional parameter #10 - I do not have objection, but it should be probably named parameter, since each template has different number of parameters, and some are optional. If I understand it correctly it will be a name of the object in the image, is it correct? If so than this tag will not be desired in case of geo-tagging plants, animals, landscapes, intersections, etc. Should this tag be applied only if this optional parameter is provided? Should we have a way to populate this field in old images? I assume that in majority of images it will not be provided since most people do not type the coordinates in directly but use one of the several processes to generate the text of this template. --Jarekt (talk) 13:20, 9 April 2009 (UTC)

More proposed changes to {{Location}} template family

• There is a bunch of templates redirecting to {{Location}} or {{Location dec}}. Those old templates will be replaced by the bot and deleted to cut down the clutter. Some of the templates to delete: {{Geolinks-US-hoodscale}}, {{Location d}}, {{Location dec US}}, {{Location dec min}}, {{Location dms}}, {{Map}} and {{Map-LatLong}}.

 Done --Jarekt (talk) 12:35, 13 April 2009 (UTC)

• I would like to propose unifying the output of {{Location}} and {{Location dec}} so both templates display numbers in degrees-minutes-seconds notation no matter what the input.

 Done --Jarekt (talk) 13:11, 23 March 2009 (UTC)

• I would like to propose to slim down the look of the {{Location}} template to one line:

Camera location	Coordinates	This and other images at their location on: Google Maps - Google Earth	(Info)

 Done --Jarekt (talk) 13:11, 23 March 2009 (UTC)

--Jarekt (talk) 15:53, 18 March 2009 (UTC)

All instances of {{Location dms}} and {{Location d}} are replaced now with {{Location}} and {{Location dec}}. Should we delete those redirects or keep them as is. Deleting would simplify maintenance and cut down on clutter, but some people like (and use) the alternative names. --Jarekt (talk) 16:40, 9 April 2009 (UTC)

Delete them. --Slomox (talk) 11:37, 10 April 2009 (UTC)

Ok, I marked {{Location d}} as a duplicate, but {{Location dms}} is protected so I can not mark it for deletion. An admin will have to do it.--Jarekt (talk) 12:16, 10 April 2009 (UTC)

Done. --Slomox (talk) 14:05, 10 April 2009 (UTC)

Also, for anyone interested in location templates. Please voice your opinion in:

• Commons:Deletion requests/Template:Location deg min
• Commons:Deletion requests/Template:Geolinks-US-hoodscale
• Commons:Deletion requests/Template:Coordinate

--Jarekt (talk) 03:20, 11 April 2009 (UTC)

altitude/depth yet?

Has the status on altitude changed yet? That is, can I add altitude as one of the extended parameters. Eg. so that google earth altitude (absolute mode) will use it? -J JMesserly (talk) 18:17, 4 April 2009 (UTC)

Changed from what? You can add altitude~(the same way you specify heading), and User:DschwenBot does extract it from GPS data. Whether Google uses it is something that someone at Google should answer. --Dschwen (talk) 18:50, 4 April 2009 (UTC)

I'm refering to the geohack code. Your extraction looks great. Changed from what? Well, Geohack from not passing anything. For example, File:Acanthogorgia- Gold coral- noaa.jpg has an alt of -1950 or so meters (deepsea photo). The value is not passed to any of the sites on the geohack page (as far as I can see). I am putting alt:-1950 as the last param. -J JMesserly (talk) 00:17, 5 April 2009 (UTC)

can any of the sites use it? --Dschwen (talk) 00:49, 5 April 2009 (UTC)

I know Google Earth can. Turn on the Ocean layer, click on the google earth link from my gold coral page, and you will be able to dive under the water and view the davidson mount from the side. Click the commons pushpin for the image, and you will see that you can set the altitude- I think its the last tab. I don't know what their parameter is so that it may be passed from geohack page. -J JMesserly (talk) 01:39, 5 April 2009 (UTC)

More Error checking

In order to catch more types of incorrectly formatted input parameters I would like to add and {{#if: {{{10|}}} |0|1}} to {{Location}} to catch templates with too many parameters. Other 3 templates already check for that condition. --Jarekt (talk) 13:23, 21 July 2009 (UTC)

Done. --Slomox (talk) 19:33, 21 July 2009 (UTC)

thanks --Jarekt (talk) 20:04, 21 July 2009 (UTC)

OpenStreetMap

I know this is a totally freetarded comment but...

Should this template be designed to give a little more link-love to the free and open collaborative wiki-style project OpenStreetMap.org, and little less to google.inc?

-- Harry Wood (talk) 00:00, 23 September 2009 (UTC)

+1 Raymond 07:34, 23 September 2009 (UTC)

+2 OSM is in a state where it is starting to make sense to include it. --Dschwen (talk) 23:14, 23 September 2009 (UTC)

+3 I also want to see images in OSM. But who write a tool like para's in OpenLayers? Or could we live with OSM-tiles and GoogleMaps-API in the backround? Than I could provide such a thing fast. --Kolossos (talk) 19:45, 24 September 2009 (UTC)

I assume most people realize that OpenStreetMap is on the long list of sites any geo-taged file can use for visualizing its location (by clicking on coordinates and choosing OpenStreetMap). However it is not on a short list of sites for which more specialized tools are written, like the one by Para. I am all for collaboration with OpenStreetMap.org but this site still have rather limited capabilities. I tried search for my home address - and got an error. I viewed location some of my files, like File:Joshua Tree - Room to Shroom.jpg and the results are quite disappointing due to lack of satellite images. That is one reason I will likely still favor Google Maps or WikiMapia. But may be we can convince OpenStreetMap.org people to directly use images from commons, like Google is using images from Panoramio? this kind of collaboration might help both projects. --Jarekt (talk) 21:07, 24 September 2009 (UTC)

Recent changes

As some of you might have noticed there were several changes to the location template mainly template:location/layout :

1. A link to OpenStreetMap was added, see Template_talk:Location#OpenStreetMap - at the moment it displays only the location of a single image but hopefully we will have in the future support for displaying many Commons images on the same map the way we do it in Google Maps.
2. {{Globe location}} template was added for geotagging other globes than earth, see Commons_talk:Geocoding#Geocodding_mars. {{Globe location}} can take coordinates as 2 numbers {{Location dec}} style and as 8 fields {{Location}} and adds an extra parameter to specify globe. Supported values are: moon, mars, venus, mercury, ganymede, and titan. (see w:Template:Coord#globe:G for details). In addition direct links to google maps are supported for Mars and Moon.
3. Better support for languages other than English with direct links to language specific versions of Google Maps and GeoHack (link behind coordinates)
4. More error checking was added which populates Category:Media with erroneous locations. This time it was range checking on final latitude and longitude.

As a result of addition of {{Globe location}} more text has to be translated and added to all language subtemplates Template:Location/lang. See Template:Location/doc#Translation for details. --Jarekt (talk) 05:01, 8 November 2009 (UTC)

error in translation code

There is an error in the translation code template. The error is in this line:
| globe = {{{globe}}}
It should be
| globe = {{{globe|Earth}}}

compare this: http://commons.wikimedia.org/wiki/File:Ptichnick.jpg?uselang=zh-hans vs http://commons.wikimedia.org/wiki/File:Ptichnick.jpg?uselang=en

-- SKvalen (talk) 20:47, 28 December 2009 (UTC)

Fixed. --Slomox (talk) 21:08, 28 December 2009 (UTC)