Sorry for the late reply. Actually for our application, I ended up not using the mock reverse geocoder. I ended up just making a webservice call to ws.geonames.org, which provides a decent reverse geocode service that takes a simple http get param list and returns xml describing the nearest address. Of course, I'm sort of screwed if ws.geonames.org is down occasionally.Hope this helps.
On Apr 12, 2:03 pm, marvin <[EMAIL PROTECTED]> wrote: > I've been frustrated for a while by the lack of support for proper > reverse geocoding - or at least, proper mock reverse geocoding. And > we really need it now for our app (left this bit to the last minute). > We didn't want to use the undocumented GML-thing and wanted to stick > to the standard format for the geodb mock, so I whipped up a little > class to do it, after looking at the source code. > We've started a blog where I posted what I think to be the current > problem with the mock geocoder, and I've uploaded the Java source code > for the replacement. > > Look at the last 2 posts on the > blog:http://blog.marvinware.com/2008/04/gee-oh-code.htmlhttp://blog.marvinware.com/2008/04/geocoder-with-working-reverse-geoc... > > Let me know what you all think. > > - Marvin --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
