[v0/v1] Migrate website to /v2/recognize/places #6139
[v0/v1] Migrate website to /v2/recognize/places #6139rohitkumarbhagat merged 4 commits intodatacommonsorg:masterfrom
Conversation
rohitkumarbhagat
commented
Mar 27, 2026
- /v2/recognize/places - new endpoint is live in staging and inline for next prod rollout.
- Tested locally, goldens are passing
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request migrates the website's place recognition functionality to use the updated v2 API endpoint. This change ensures the application utilizes the latest service version, which has been verified in staging and is prepared for production deployment. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request updates the recognize_places function in server/services/datacommons.py to utilize the /v2/recognize/places endpoint and adds this new path to the discovery service configuration. A review comment suggests removing the now-obsolete /v1/recognize/places endpoint from the discovery list to ensure the configuration remains clean and prevents accidental usage of the old version.
This PR puts the change made by Rohit in #6139 behind the `use_v2_api` feature flag.