Replying back to the whole list. On Mon, Dec 12, 2011 at 6:06 PM, Chris Ostler <[email protected]>wrote:
> On Dec 12, 4:37 pm, TreKing <[email protected]> wrote: > > On Mon, Dec 12, 2011 at 2:07 PM, Chris Ostler <[email protected] > >wrote: > > > > > I'm interested in building an alternative backend service for use by > the > > > android.location.Geocoder class. > > > > Are you talking about updating the existing Geocoder class? Because you > > should consult the platform or porting group for that. > > As per the documentation, the Geocoder class requires a separate > backend service that actually does the geocoding. I'm wanting to put > together an implementation of this service *different* than the one > provided in the Maps API package. > It's not in the Maps API package - that's a separate library - Geocoder is in the core platform. "The Geocoder query methods will return an empty list if there no backend service *in the platform*. Use the isPresent() method to determine whether a Geocoder implementation exists." That to me sounds like you'd have to modify the firmware. > My goal is to allow existing apps that currently use the Geocoder > to function correctly when no network access is available (which > is required by the Maps API provided service). > Geocoder is not required by the Maps API. ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
