On Thu, Aug 4, 2011 at 9:31 AM, Chris J. Karr wrote:
> The simplest solution would be to ignore Geocoder altogether (and just
> use a custom lookup method), but in the spirit of doing things the
> "Android way", I was wondering if it was possible to override the
> system provider Context.LOCATION_
I have an app where I want to implement a function that takes a
latitude & longitude pair and return a "place" associated with those
coordinates. The android.location.Geocoder interface is exactly what I
need, but the documentation includes the following note: "The Geocoder
class requires a backend
2 matches
Mail list logo
