One way is to capture the geocoder responses into a collection (over time) then write an algoritm to determine the which contents of that collection are usable. The geocode throws bad results and nulls all thge time. Most of the good algorithms are propietary (skyhook), but there is room for exploration with your own exciting code.
On Mar 10, 2:34 pm, Jake Colman <col...@ppllc.com> wrote: > At random times my production app will get > > GeoCoder error: java.io.IOException: Unable to parse response from > server > > When I try to get the location name corresponding to a given > latitude/longitude taken from a Location object. > > Is there anything I should be doing differently so that this doesn't > happen? It's random and usually clears itself up next time I try to > update the information. But it's annoying. > > Is it just that Google's sever may have been unavailable at the time of > the request or that my phone's internet connection was temporarily > flaky? > > Thanks. > > ...Jake > > -- > Jake Colman -- Android Tinkerer -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
