Assigned
Status Update
Comments
mi...@google.com <mi...@google.com> #2
Yes please :) Along with a more specific definition of how the Popular Times are determined (how much history? done by mobile device activity? check ins?)
yo...@gmail.com <yo...@gmail.com> #3
Making popular times available by day of the week would be awesome
mi...@google.com <mi...@google.com> #4
It already is Jeffrey, you can toggle by day on mobile or desktop
[Deleted User] <[Deleted User]> #5
HI, when this fix will be done and how autocomplete work with multi countries based search?
[Deleted User] <[Deleted User]> #6
@r22, I think Jeff is referring to the ability to split popular times by day of week in the information released by the API, not the currently existing web GUI.
Maybe the info appears as a nested object? e.g. "popular times" > "day of week" > "hour of day" > traffic count
Maybe the info appears as a nested object? e.g. "popular times" > "day of week" > "hour of day" > traffic count
mi...@google.com <mi...@google.com> #7
We are looking into fixing this, but not as high priority.
Specifying multiple country restricts in the Geocoding API is an invalid request, the fix will be returning ZERO_RESULTS as per API documentation.
Place Autocomplete does support multiple (up to 5) country restricts.
Please see how to add multiple county restricts here:
https://developers.google.com/places/web-service/autocomplete#place_autocomplete_requests
https://developers.google.com/maps/documentation/javascript/places-autocomplete#add_autocomplete
See also this new example: Place Autocomplete Restricted to Multiple Countries
https://google-developers.appspot.com/maps/documentation/javascript/examples/places-autocomplete-multiple-countries
Specifying multiple country restricts in the Geocoding API is an invalid request, the fix will be returning ZERO_RESULTS as per API documentation.
Place Autocomplete does support multiple (up to 5) country restricts.
Please see how to add multiple county restricts here:
See also this new example: Place Autocomplete Restricted to Multiple Countries
mi...@google.com <mi...@google.com> #8
We have an update of this.
Starting soon (this or next week), the Geocoding API will return INVALID_REQUEST (not ZERO_RESULTS) if there are 2 or more country: or postal_code: filters.
Examples:
https://maps.googleapis.com/maps/api/geocode/json?address=Travelodge+Torrelaguna&components=country:uk|country:es
https://maps.googleapis.com/maps/api/geocode/json?address=Travelodge+Torrelaguna&components=postal_code:28027|postal_code:28028
ZERO_RESULTS will be returned when the request is valid in terms of the number of filters, but the filters are mutually exclusive.
Examples:
https://maps.googleapis.com/maps/api/geocode/json?address=Travelodge+Torrelaguna&components=country:es|postal_code:HA5+1AG
https://maps.googleapis.com/maps/api/geocode/json?address=Travelodge+Torrelaguna&components=country:uk|postal_code:28027
Starting soon (this or next week), the Geocoding API will return INVALID_REQUEST (not ZERO_RESULTS) if there are 2 or more country: or postal_code: filters.
Examples:
ZERO_RESULTS will be returned when the request is valid in terms of the number of filters, but the filters are mutually exclusive.
Examples:
al...@webtomed.com <al...@webtomed.com> #9
Regarding this issue, as well as https://issuetracker.google.com/issues/123377220 , is there any intention to provide support for multiple countries in Geocoder as it exists in Places Autocomplete, without having to go through Autocomplete first?
mi...@google.com <mi...@google.com> #10
Would be extremely helpful to have access to this data directly via the API. Is it maybe available via another API?
Description
# It is OK to share your API Project ID, but _not_ API keys.
Issue report
----------------
query:
Expected behaviour:
as the component filter contains multiple countries and the documentation (
Actual behaviour:
However, it returns the expected result (for country:es), plus some extra match data.
Running the query with just 'country:es' also returns the expected result of 1 entry.
Either the documentation is wrong, (has there been an update that changed this logic?) or the logic in the codebase is incorrect.
This is leading to a lack of confidence that we are actually querying the api properly.
Please can you confirm that the OR logic is correct and the docs are wrong? Or do we need to change our approach and expect a change in behaviour?