Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
Needs more info comment that > 10 days [ID: 963198]
Comment such as: SPAM, non-actionable [ID: 963127]
Resolved actionable follow-up comments [ID: 963027]
View issue level access limits(Press Alt + Right arrow for more information)
Attachment actions
Request for new functionality
View staffing
Description
Issue:
In the USA (and/or in English dominating speaking countries), we assume most users entering an address into an application that uses Google Maps Address Validation component do not have their keyboard default settings to type in diacritics and/or would normally not type in the diacritic version of an address. For example, for Microsoft users, in the USA the default Language setting is set to English (United States).
Suggestion: Since some applications may only respond to non-diacritic alphabet characters, or won't parse addresses with diacritics, could Google add non-diacritic equivalent suggestions to their Address Validation suggester component to allow a user to select that address to be used by the application?
Example of issue we are dealing with (See attachment).
Please let us know if this is something that can be considered. If you have any other suggestions that would allow us to continue to use the Google Address Validation component.
Thank you,
HSF Affiliates A Berkshire Hathaway subsidiary
#IMPORTANT: If your production system or service is down file a Severity 1 support case at console.cloud.google.com/google/maps-apis
======================================================================== #REMINDER: Please do not disclose any PII. Some examples of PII are email address, IP, contact number, any part of name, project numbers and billing accounts. Comments or attachments that include PII will be removed and restricted from public viewing as it may violate our security and privacy policies.
Please refrain from emailing a reply 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, visithttps://en.wikipedia.org/wiki/Personal_data
Issue report
If you are seeing an incorrect address interpretation, validation or geocode result from the Address Validation API, please include the full request in JSON format and explain which sections of the API response are incorrect (and why).