Assigned
Status Update
No update yet.
Comments
ca...@google.com
Thanks for your suggestion!
We'll be reviewing this for further consideration. Please star this issue to get updates and leave comments for additional information. Please note that starring the issue also provides our product team with valuable feedback on the importance of the issue to our customers.
in...@ninopizza.ch
Thank you for your prompt response!
I'm glad to hear that my suggestion is being considered. I have marked the issue as a favorite and will eagerly follow any updates. If additional information is needed or if there's anything else I can provide to assist in the process, please feel free to let me know.
Once again, thank you, and I appreciate your efforts in enhancing the Google Maps API.
Best regards,
I'm glad to hear that my suggestion is being considered. I have marked the issue as a favorite and will eagerly follow any updates. If additional information is needed or if there's anything else I can provide to assist in the process, please feel free to let me know.
Once again, thank you, and I appreciate your efforts in enhancing the Google Maps API.
Best regards,
Description
#REMINDER: Please do not disclose any possible PII such as: email address, IP, contact number, any part of name, project numbers and billing accounts as these information may violate security and privacy. Comments or attachments that include PII will be removed and restricted from public viewing.
Furthermore, please refrain from replying to a comment as this will make your email address visible. Instead, you may use the Issue Tracker’s comment feature for your replies.
It is OK to share your API Project ID, but _not_ API keys or client ID credentials.
To learn more about personal data, visit
===========================================================================================
Hello,
I hope this message finds you well. I am a user of the Google Maps API and have been impressed with its functionality. I would like to suggest an enhancement that I believe would greatly benefit users like us.
Feature Request: Improved Address Validation and Correction
Description:
Currently, I have noticed discrepancies in address recognition, particularly with streets like "Sankt Galler Strasse," where the API interprets it as "St. Gallerstrasse," causing inaccuracies in location data.
Suggested Solution:
Implement a more robust address validation and correction mechanism. This would involve recognizing common variations of street names, such as "Sankt" and "St.," and automatically correcting them to ensure accurate geolocation.
Use Case:
Our organization relies heavily on accurate location data for efficient logistics. The current discrepancies have led to misrouted requests, resulting in time losses for our employees. With improved address validation, we anticipate a significant reduction in such issues.
Benefits:
Enhanced accuracy in geolocation data.
Reduced instances of misrouted requests.
Improved user experience for API consumers.
I understand the complexity of such a feature but believe it would greatly enhance the overall usability of the Google Maps API. Thank you for considering this suggestion, and I would appreciate any feedback or updates on the possibility of implementing this enhancement.
Best regards,