-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for new Places API endpoints #509
Comments
If you would like to upvote the priority of this issue, please comment below or react on the original post above with 👍 so we can see what is popular when we triage.@Tylerlhess Thank you for opening this issue. 🙏
This is an automated message, feel free to ignore. |
This is a very good request. For reference, the API documentation now says you must choose which Places API when beginning a project: https://developers.google.com/maps/documentation/places/web-service/choose-api
I am mainly interested in the expanded place types, specifically |
If you are looking for Python client libraries for the following APIs, see the Google Maps Platform APIs in the Cloud Client Libraries for Python (releases). The new APIs will not be added to this client library. |
Thanks! Does this library correspond to this documentation? |
@theRocket Yes, as linked from the README. I've noted that the README and documentation text are confusing since they do not refer to the "new" term and the refdocs even call it "v1". |
Thanks! |
"@wangela: The new APIs will not be added to this client library." Why not support the New API? what alternative python library would you recommend using to obtain a wrapper around the Places (New) API? |
Should we expect this library to stop being maintained and transition over to the google cloud client libraries? |
I would like to see support for the new Places API endpoints.
The text was updated successfully, but these errors were encountered: