Skip to content
This repository has been archived by the owner on May 27, 2024. It is now read-only.

Android geocoder and Google Places data usage limits #364

Open
vreixo opened this issue Aug 27, 2014 · 3 comments
Open

Android geocoder and Google Places data usage limits #364

vreixo opened this issue Aug 27, 2014 · 3 comments
Labels
enhancements

Comments

@vreixo
Copy link
Contributor

vreixo commented Aug 27, 2014

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
Copy link
Contributor Author

vreixo commented Sep 12, 2014

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
Copy link
Member

barbeau commented Sep 12, 2014

@vreixo Good point. Android Geocoder bug is being tracked in #396.

@barbeau
Copy link
Member

barbeau commented Mar 5, 2015

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancements
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@barbeau @vreixo