Skip to content
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

Closed
Tylerlhess opened this issue Nov 29, 2023 · 8 comments
Closed

Support for new Places API endpoints #509

Tylerlhess opened this issue Nov 29, 2023 · 8 comments
Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@Tylerlhess
Copy link

I would like to see support for the new Places API endpoints.

@Tylerlhess Tylerlhess added triage me I really want to be triaged. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels Nov 29, 2023
@wangela
Copy link
Member

wangela commented Nov 29, 2023

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. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

This is an automated message, feel free to ignore.

@theRocket
Copy link

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

With the release of Places API (New), your first task is to decide which set of APIs to use. This is true if you are a new customer or an existing customer already using the APIs. Use this guide to understand the key differences between the two APIs.

I am mainly interested in the expanded place types, specifically electric_vehicle_charging_station as I want to write some optimization logic using python (pandas) dataframes using popular machine learning libraries (such as Tensorflow) and do not want to have to transfer the location data from a Javascript API framework over to a Python framework via file exports since it will be quite large.

@wangela wangela pinned this issue Dec 4, 2023
@wangela
Copy link
Member

wangela commented Dec 4, 2023

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.

@wangela wangela closed this as completed Dec 4, 2023
@wangela wangela removed the triage me I really want to be triaged. label Dec 4, 2023
@theRocket
Copy link

@wangela:

The new APIs will not be added to this client library.

Thanks! Does this library correspond to this documentation?
https://googleapis.dev/python/places/latest/

@wangela
Copy link
Member

wangela commented Dec 6, 2023

@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".

@Tylerlhess
Copy link
Author

Thanks!

@karux
Copy link

karux commented Aug 25, 2024

"@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?

@chemeng
Copy link

chemeng commented Oct 8, 2024

Should we expect this library to stop being maintained and transition over to the google cloud client libraries?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

5 participants