search

CUTR-at-USF / OpenTripPlanner-for-Android

An Android app for multi-modal trip planning and navigation using any OpenTripPlanner server.
Other
129 stars 91 forks source link

Android geocoder and Google Places data usage limits #364

Open vreixo opened 10 years ago

vreixo commented 10 years ago

Related to #357 we might consider to study the limits of data usage of both providers.

One possible idea will be to only use MapQuest for the internal geocoding, for the otp generated names.

vreixo commented 10 years ago

It's worth to note here that "internal geocoding" has been removed for the moment at least and Android geocoder issue was unrelated to limits.

barbeau commented 10 years ago

@vreixo Good point. Android Geocoder bug is being tracked in https://github.com/CUTR-at-USF/OpenTripPlanner-for-Android/issues/396.

barbeau commented 9 years ago

There is now a new option for Places API via Google Play Services that we can also check out, as discussed here: http://android-developers.blogspot.com/2015/03/google-play-services-70-places-everyone.html