IssueTracker

I need that too

It would be great to have this feature. It would save me at least three web service requests.

I'd love to see that! At this time I'm using multiple calls to accomplish the same result and I'm probably risking get wrong results.

Seems like easy to accomplish from the google team. Please solve this issue, really helpful to gather correct results.

Could you (all) please explain what would you use this for?

The use case I'm working on is:
1- user types in a city name
2- user gets an autocomplete list of possible cities
3- user selects one result and next screen displays a breadcrumb of the destiny. Like this one: country > state > neighborhood > city. Each component of this breadcrumb has a link to proper destination.

By having place_id in each component we can better get information about the higher destination components.

Thanks for your prompt response. Could you please explain in more detail what do you do then with each component's details?

Sure, no problem ;)

I'm building a marketplace of services for travellers and I'm willing to use Google Maps in order to provide more details about the locations.

Visitors will face a list of featured destinations (suggested by my service) and they can also reach another locations by textual search (autocomplete).

I'm studying multiple Google Maps API's (autocomplete, photos, place details..) in order to create an interface rich in content that helps the visitor to decide which place to travel to.

By having this feature request implemented I can reduce drastically the number of requests to Maps API therefore leading to reduce response time.

Feel free to request more details. I'm glad to help to get this feature deployed :)

Thanks, but I was looking for more details on what do you do with each address component's details in particular. You've described the high-level use case, but I'm looking for the low-level details of which fields in each address component's details (as they come from Geocoding API when querying by Place ID).

Got it. Let try again:

I start by using the visitors input in the following request:
https://maps.googleapis.com/maps/api/place/autocomplete/json?components=country%3ABR&input=INPUT&language=pt-BR&type=%28cities%29&key=KEY
(I'm looking only for cities in Brazil, written in pt-BR) Sample result:

Then I display this results to the user. Once he picks one, I send the proper place_id back to my server in order to display the next view.
The next view will display info for the city, its state and its country.
Since I don't have the place_id for each component, I need to query GoogleMaps again in order to get the list of components of the city (considering autocomplete response doesn't includes it) and then create multiple queries for each component, to get the right place_id's.
- Get components list
https://maps.googleapis.com/maps/api/place/details/json?language=pt-BR&placeid=ChIJ1Z3UnpMmk5QRqw733UypFJc&key=KEY 
- Then uses Geocode for each component
https://maps.googleapis.com/maps/api/geocode/json?language=pt-BR&COMPONENT_DATA

Note that this process is to expensive, slow and error prone, since there are multiple places with the same name all over the world.

Nearly there :)

What I'm looking for here, is what do you do with the details you get after querying for each of the components above the city. That is, what do you do with the country and state? Do you use their location, viewport, or other fields, and for what?

I would like to add my voice that this would be a great addition to the Place Detail response.

My specific use case is such:
Indexing a place for future queries in my database- which may include queries by city, region or country. Using a place ID instead of the returned strings, such as "Cape Town", "Western Cape" and "South Africa"- feels much safer in the long term- since names may change (and language can be fickle) but Place ID has been created to remain consistent.

So for example, if I wanted to get all the soccer Team entities listed within the region "Western Cape", I could just do a simple query like:

GET Teams WHERE REGION_PLACE_ID="ChIJ841peohdzB0Ri6I2IY95juk" && SPORT_TYPE="SOCCER"

I feel it provides a relatively simple method of achieving consistent geographical granularity.

We have an almost identical use case as #14.

We reported https://issuetracker.google.com/issues/37886842 but this proposition would allow for a significantly more elegant solution.

The problem we're trying to solve is to determine if a specific location is a part of a greater location.

For example, an entity is tagged with a specific location like "19 Victoria Street, Auckland, New Zealand". Entities can be tagged with less specific components as well, so another one might be tagged with "Victoria Street", or just "Auckland". We need to find all entities that exist under any location component. So if I do a query for "Auckland", that entity at "19 Victoria Street" should qualify and be included in the result set.

At the moment the only way to achieve this is to take the street address (19 Victoria Street) and geocode each component below that, ie:

1. Autocomplete provides the place_id
2. Look up the place_id details
3. Geocode each component

If the API provided the place_id for each of those components in the details it would remove the need to geocode them. It would also be less fragile because we wouldn't have to search on the names of each component assuming the first result is the one we want. There's risk involved here that we might link to the wrong component.

In our database we would then set a place_id for each component on the entity, allowing for a query such as "all entities in Auckland (City)", exactly like the example in #14.

Same thing here. Having this feature would be awesome.

Any chance to see this request implemented anytime soon?

Until now, I rely on reverse geocoding to circumvent the issue, which is a kind of hack:

Step 1: get place details
Step 2: reverse-geocode lat/lng returned by step 1. Hopefully, you'll find your place components, with their place_id.

But reverse geocoding returns fewer results now (see https://issuetracker.google.com/issues/35829979 ). Therefore, I see more and more failures in my logs.

Thanks

+1 Trying to get detailed information about a larger area would be significantly simplified if the place_id for each component were provided...

Moving PlacesAPI bugs to new PM

Another star for this issue, I also need that

+1 StackOverflow:
https://stackoverflow.com/questions/49590171/hierarchical-translated-results-of-a-placeid-using-google-places

+1

Hello google ? Have the same issue as #14.

Assigning to new Places PM

+1 StackOverflow:
https://stackoverflow.com/questions/37654034/check-if-one-placeid-is-within-another-placeid

+1 Same (#14 and #15) situation here.

I'd say anyone working with Places API in a hierarchical fashion will hit the same problem. For any further exploration of the Places info, especially when mixed with local/business/app-specific data, the place_id is the only reliable element that can be used to identify each region, since any name/text provided for address components could/will change for each different language supported by the API. Even if the app is restricted to one language, the official name of any component could/will change at any time.

I will add my specific use case to those already provided. In my crowdfunding platform, each project is "based" on a city/locality that is selected by the author. When users visit the page of a crowdfunding project we give them the ability to discover other projects in the *same administrative area*, eg. a Project based on Dallas will have a link to see other projects in Texas, a project in Frankfurt a link to the state of Hesse, inside Germany, etc. It must be noted that this can't be geographically computed by doing calculations with areas and the lat/lon of the city. Many business cases require working at an administrative level because of social, financial, tax, historical reasons…

This is easy and fast to accomplish by looking up local data, eg. projects, that have same place_id on their eg. `administrative_area_level_1` attribute (or area_level_2, or country…) and in return this kind of exploration is only possible in a performant way by pre-storing the IDs of the administrative chain at different levels for a given location:

locality    country     admin_1     admin_2     admin_3     Other app-speficic-data
----------  ----------  ----------  ----------  ----------  ------------------------
ChIJ...IgQ  ChIJ...99m  ChIJ...3EI  ChIJ...vtk  ChIJ...x8K  PROJECT_ID, TEAM_ID

Right now the only safe-ish workaround to implement the retrieval of each hierarchical level is the workaround described here https://stackoverflow.com/questions/49590171/hierarchical-translated-results-of-a-placeid-using-google-places#answer-49600674.

It's a non-optimal solution for us, the consumers or for Google as data provider since it -at least- duplicates the number of requests to be made to retrieve the info of a city/locality. Including the place_id for each component in the API responses, will simplify this use case and in general improve the discoverability of the data. From the outside, it looks like an easy thing to do without breaking any backward compatibility and the place_id is already ubiquitous in the responses provided for the geocoding results, but of course, we don't know the internals required to implement this.

Google, the issue has been open now for +3 years. It would be fantastic to get the place_id added to the components but if this is not going to be added, please close the ticket to make it clear, so we can all move forward.

+1 It's been over a year since I last visited this issue and I'm still awaiting some sort of news or update on when or if this will ever be implemented. It's triaged as a "NeatIdea", I'm not sure what that actually means... I see it more as a fundamental concept that should have been in place since the beginning; there's nothing really neat or profound about it, just something that should be expected.

Please I need this feature. Can we expect it in this year?

+1 StackOverflow:
https://stackoverflow.com/questions/54459688/place-administrative-area-level-1-return-different-values-for-same-area

+1 StackOverflow:
https://stackoverflow.com/questions/43499392/get-place-id-of-address-components

+1
Are you going to implement it? Are there any alternatives?

+1

+1

+1

Where is this

I would prefer a higher cost of the API call with all the info, rather than calling Geocoding several times. Waiting for it.
+1

Same problem, but it seems any solution is in standstill for more than 5 years. I guess its a better business to force more calls from the consumers...

This feature is very helpful specially for my use-case... I'm building an Ecommerce platoform. Hope this feature gets attention from Google

+1

+1

+1

+1

+1

+1

+1

+1

I want get city name only from this respponse because the city name shown from diff diff indexing so how can I get from all indexing at same time

JSON
0
long_name : "Ratina"
short_name : "Ratina"
types
0 : "neighborhood"
1 : "political"
1
long_name : "Tampere"
short_name : "Tampere"
types
2
long_name : "Finland"
short_name : "FI"
types
3
long_name : "33100"
short_name : "33100"
types
0 : "postal_code"

+1

+1

Any progress on this one?

Any news?

+1

+1

+1