Assigned
Status Update
Comments
ca...@google.com <ca...@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?)
cr...@casavo.com <cr...@casavo.com> #3
Making popular times available by day of the week would be awesome
cr...@casavo.com <cr...@casavo.com> #4
It already is Jeffrey, you can toggle by day on mobile or desktop
ca...@google.com <ca...@google.com> #5
Thank you for posting.
We have verified and logged this issue internally. Please note that we cannot give you any timelines, but you can star the issue to get notifications.
Description
Description:
The Geocoder API produces inconsistent results when querying addresses with street numbers equal to 1. Specifically:
Using the address parameter often returns incomplete or incorrect results, particularly omitting the street number or prioritizing a different street in the result. Using the place_id parameter consistently provides accurate and detailed results. The issue does not occur when querying addresses with other street numbers (e.g., 2, 3, etc.) on the same street.
Steps to Reproduce:
Query the API using the address parameter for:
Compare the results with a query for the same addresses using the place_id parameter.
Findings (Examples):
Example 1: Via Paolo Sarpi 1 (Using address)
Input Query: address=Via Paolo Sarpi 1, 20154 Milano, Italia
Result: The API incorrectly prioritizes Via Paolo Lomazzo instead of Via Paolo Sarpi.
Additionally, the street number 1 is omitted in the address_components.
Key Observation: The returned result is for Via Paolo Lomazzo, not Via Paolo Sarpi, despite the input explicitly mentioning Via Paolo Sarpi.
With Street Number = 2: The issue does not occur when querying "Via Paolo Sarpi 2, 20154 Milano, Italia". The result correctly prioritizes Via Paolo Sarpi with the accurate street number.
Example 2: Corso Italia 1 (Using address) Input Query: address=Corso Italia 1, Milano, Italia Result: The API recognizes Corso Italia but omits the street number 1 in the address_components.
Key Observation: The result identifies Corso Italia, but the street number 1 is not included in the address_components.
With Street Number = 2: The issue does not occur when querying "Corso Italia 2, Milano, Italia". The result correctly includes the street name and the street number.
Behavior When Using place_id:
For both examples above, querying with the place_id consistently returns the correct street name and street number. Example: The place_id for Via Paolo Sarpi 1 produces accurate results without any omissions or misplacements.
Use Case:
In my application:
Users often forget to include a street number when entering an address. I prompt users to add the missing street number later, but at that point, I only have the address (text) from their initial input, not the place_id. Since I do not call Autocomplete in these cases, I cannot rely on the place_id to improve result accuracy. For this reason, I must use the address parameter, but the current inconsistencies significantly impact the reliability of results for certain addresses.
Expected Behavior:
The address parameter should produce results as accurate and complete as those obtained using the place_id parameter, particularly for street numbers equal to 1. The documentation should: Highlight the differences in behavior between address and place_id. Provide guidance on when to use each parameter and how to mitigate potential issues.
Observed Behavior:
Using address: Incomplete or incorrect results for addresses with street numbers equal to 1, while results for other street numbers in the same street are accurate. Using place_id: Consistently accurate and detailed results.
Request for Resolution:
Investigate and resolve the discrepancy in geocoding results for address queries involving street numbers equal to 1. Update the documentation to reflect the behavior differences between address and place_id and recommend best practices for these scenarios. Thank you for addressing this issue. Let me know if additional information is needed