Fixed
Status Update
No update yet.
Comments
ca...@google.com
ca...@google.com
Thanks for your suggestion! We are currently evaluating this request, but do not have any plans to implement it at the moment. Please star to add your vote and receive further updates, and feel free to add any comments to discuss your use case.
ha...@gmail.com
I've transitioned from this team. Thanks!
ca...@google.com
Thank you for the information.
We have logged this issue internally. Please note that we cannot give you any timelines, but you can star the issue to get notifications.
ca...@google.com
We greatly appreciate your patience.
We believe this issue is now fixed, hence marking it as such.
Thanks for working with us!
ha...@gmail.com
Thank you for looking into this issue. While the problem seems to be resolved for the previously reported address, we have noticed that the same inconsistency persists in other cases.
For example:
Address: "10534 FM 2813 Flint TX 75762"
Formatted Address: "10534 FM 2813, Flint, TX 75762, USA"
Location Type: RANGE_INTERPOLATED
Coordinates: lat: 32.2361, lng: -95.3427585 (points to the road)
Address with Space Removed: "10534 FM2813 Flint TX 75762"
Formatted Address: "10534 FM2813, Flint, TX 75762, USA"
Location Type: ROOFTOP
Coordinates: lat: 32.236142, lng: -95.3427797 (points to the building)
This suggests that the issue is not fully resolved and continues to affect addresses where space formatting between road identifiers (e.g., "FM 2813" vs. "FM2813") changes the geocoding accuracy.
To ensure consistent results across all affected US addresses, could you please investigate and apply a general fix for this issue rather than resolving it on a case-by-case basis?
Thank you for your assistance.
For example:
Address: "10534 FM 2813 Flint TX 75762"
Formatted Address: "10534 FM 2813, Flint, TX 75762, USA"
Location Type: RANGE_INTERPOLATED
Coordinates: lat: 32.2361, lng: -95.3427585 (points to the road)
Address with Space Removed: "10534 FM2813 Flint TX 75762"
Formatted Address: "10534 FM2813, Flint, TX 75762, USA"
Location Type: ROOFTOP
Coordinates: lat: 32.236142, lng: -95.3427797 (points to the building)
This suggests that the issue is not fully resolved and continues to affect addresses where space formatting between road identifiers (e.g., "FM 2813" vs. "FM2813") changes the geocoding accuracy.
To ensure consistent results across all affected US addresses, could you please investigate and apply a general fix for this issue rather than resolving it on a case-by-case basis?
Thank you for your assistance.
Description
We encountered an inconsistency in the Google Geocoding API response when a minor formatting change (removal of space) was applied to an address.
For the address: "10760 FM 2813 Flint TX 75762", the API returns:
Formatted Address: "10760 FM 2813, Flint, TX 75762, USA"
Location Type: RANGE_INTERPOLATED
Coordinates: lat: 32.2347722, lng: -95.3462144 (points to the road)
However, when the space between "FM" and "2813" is removed: "10760 FM2813 Flint TX 75762", the API response changes significantly:
Formatted Address: "10760 FM2813, Flint, TX 75762, USA"
Location Type: ROOFTOP
Coordinates: lat: 32.2351984, lng: -95.3459316 (points to the building)
Bounds Provided: Yes (indicating a more precise location)
This issue suggests that a minor formatting change (removal of space) is altering the geocoding accuracy, changing the result from RANGE_INTERPOLATED (road-based) to ROOFTOP (building-based). This behavior is unexpected as both address formats refer to the same location.
Could you please investigate why this discrepancy occurring.
Thank you.