OpenTripPlanner-for-Android icon indicating copy to clipboard operation
OpenTripPlanner-for-Android copied to clipboard

Published 20 hours ago • verified publisher icon CUTR-at-USF

Android geocoder and Google Places data usage limits

Open vreixo opened this issue 10 years ago • 3 comments

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 avatar Aug 27 '14 19:08 vreixo

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.

vreixo avatar Sep 12 '14 12:09 vreixo

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

barbeau avatar Sep 12 '14 15:09 barbeau

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

barbeau avatar Mar 05 '15 20:03 barbeau