Use google geocoder v3. #5
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Since from the Google Maps Api's documentation we know that from May 2013 the v2 of this API will be dismissed, we use the v3. In order to use them we have to use at least geopy 0.95.
|
Thanks for the patience! I decided to do more changes (it is now possible to have a custom geocoding function) so I didn't merge your pull request (and 2 other similar pull requests at bitbucket). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since from the Google Maps Api's documentation we know that from May 2013 the v2 of this API will be dismissed, we use the v3. In order to use them we have to use at least geopy 0.95.
I'm using the development version of geopy on github, the 0.95 version seems to not be rolled out yet.