| Issue 5935: | Geocoder support | |
| 62 people starred this issue and may be notified of changes. | Back to list |
When are we going to get Geocoder support for the v2 Android mapping API? The built-in Geocoder class in Android requires compiling against the deprecated Google APIs and simply fails to work on many devices with a "Service not available" message (sometimes solved by a reboot): https://code.google.com/p/android/issues/detail?id=38009 http://stackoverflow.com/questions/7109240/service-not-available-geocoder-android http://stackoverflow.com/questions/3619924/android-geocoder-why-do-i-get-the-service-is-not-available http://stackoverflow.com/questions/17483242/how-to-obtain-100-success-geocoding-in-android Are there any plans to add Geocoder support to the Google Play Services library?
Dec 1, 2013
#1
[email protected]
Dec 1, 2013
The solution from Google exists for some time already: https://developers.google.com/maps/documentation/geocoding/
Jan 27, 2014
The Google Geocoding web API is not an appropriate solution to dynamic geocoding on a mobile device: "This service is generally designed for geocoding static (known in advance) addresses for placement of application content on a map; this service is not designed to respond in real time to user input, for example." The default rate limits reflect this.
Jun 30, 2014
Any update on this? Relying on the Google APIs platform target for Android is a real pain.
Jul 29, 2014
Hi Tristan, Are you looking for Geocoding, or Autocomplete, like on this demo page: https://developers.google.com/maps/documentation/javascript/examples/places-autocomplete Chris
Status:
Acknowledged
Jul 29, 2014
Hey Chris, This ticket was specifically for Geocoding. Taking a street address and geocoding to a LatLng and the reverse. However, the Places support in Google Play Services would be fantastic. I see now that you have some example code for integrating with the raw HTTP API in Android here: https://developers.google.com/places/training/autocomplete-android We'll take a look at that for now.
Mar 9, 2016
It is now March 2016, and I have just encountered this issue on many phones when we ran our pre-release trial. I would have expected a fix since this was logged, and there probably has been one, but what can I do for the testers currently experiencing this? Is there something I can recommend them to update on their devices? |
|
| ► Sign in to add a comment |