Thanks for the info and links! somehow I missed the Location api in my search, so really its the directions service, that can be called via the web services. seems odd that this is not encapsulated into the mapping api.
When I said "state of play" about the rate limiting, I mean does anyone know if this situation is true or even an issue? On Jul 7, 8:27 am, gjs <[email protected]> wrote: > Hi, > > There is other options as well - > > You could use both of google native & web based. > > Other map provider libraries/api eg: > > http://www.openstreetmap.org/http://resources.arcgis.com/content/arcgis-android/api > > plus the online offering from microsoft, ovi > > http://msdn.microsoft.com/en-us/library/dd877180.aspxhttp://api.maps.ovi.com/devguide/overview.html > > usgs -http://store.usgs.gov/ > > etc, etc > > Regards > > On Jul 7, 2:06 pm, TreKing <[email protected]> wrote: > > > > > > > > > On Wed, Jul 6, 2011 at 7:50 AM, David <[email protected]> wrote: > > > 1) Looking at the native map api, there seems to be functionality > > > missing that we would need, such as finding directions between two > > > points and geocoding. > > > You can use the online Google Directions API and the built-in GeoCoder > > class(es). > > > > Has this functionality been intentionality > > > missed out due to Terms of Service restrictions? or is it in the road > > > map for future api releases? > > > That would require insider Google knowledge into the maps library, > > development of which has been fairly stagnant - you're unlikely to get an > > answer to that. > > > 2) We understand that we could make the app as a browser based app and > > > > use the functionality of the javascript v3 libs or even just use the > > > web services to get the data we need to keep the app in line with the > > > desktop version. But reading around the forums, it has been speculated > > > that mobile apps are going to fall into rate limiting problems due to > > > mobile providers ip masking for individual phones (ie lots of phones > > > on one ip, as far as google maps is concerned). Does anyone know what > > > the state of play is here? > > > What "state of play"? > > > > I am a little confused about the recommended direction App developers > > > are meant to take when building Android map based apps. The options > > > seem to be, make a native app with missing functionality / workarounds > > > or make a browser based app that has all the functionality of the > > > desktop version, but the interaction experience and visual quality of > > > the app is poor in the browser compared to the native solution; any > > > suggestions here? > > > Yup, that about sums it up. > > > --------------------------------------------------------------------------- > > ---------------------- > > 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
