Last modified: 2014-03-28 10:39:08 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T46870, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 44870 - Reverse geocoding
Reverse geocoding
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Maps (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-11 11:53 UTC by kvolden
Modified: 2014-03-28 10:39 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description kvolden 2013-02-11 11:53:24 UTC
It would be great if the Maps extension could provide reverse geocoding, something at least Google provides. As of now, if you use the #geocoder parser hook with coordinates as a parameter, you simply get a conversion of the coordinates. But if you use the Google geocoder api and send coordinates with the latlng parameter, you get a response formatted as xml or a json structure with addresses ranging from very specific to very general. Being able to pass some coordinates and pick out things like the city and different administrative areas (municipality, county, state, etc) would be very useful.

The method for doing this is basically identical to regular geocoding, with a few minor adjustments, and can be found here:

https://developers.google.com/maps/documentation/geocoding/?hl=en#ReverseGeocoding
https://developers.google.com/maps/documentation/javascript/geocoding?hl=en#ReverseGeocoding

Example: http://maps.googleapis.com/maps/api/geocode/json?latlng=40.714224,-73.961452&sensor=false
Comment 1 Jeroen De Dauw 2014-03-28 10:39:08 UTC
https://github.com/JeroenDeDauw/Maps/issues/22

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links