Fixed
Status Update
No update yet.
Comments
mi...@google.com
Thank you for waiting.
The expected behavior is that addresses are formatted in the local language of their location.
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.
Currently the Address Validation API does not support the languageCode parameter in the postal address in the request. If you would like for this to be supported, would you please
ly...@gmail.com
Comment has been deleted.
de...@gmail.com Restricted
Restricted
Comment has been deleted.
mi...@google.com
Apologies, linked corrected now in
ed...@gmail.com
This problem was created with the objective, to validate the address
ra...@google.com
We greatly appreciate your patience.
The fix for this issue will be included in the next version release, hence setting the status of it accordingly.
Thanks for working with us!
gh...@gmail.com
Thanks for doing that
ho...@gmail.com
Hi
Description
----------------
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).
The issue I'm currently having is that addresses submitted for verification are translating the country code into a different language, even when provided the result.
My request was: {"address":{"addressLines":["240 Knapp Blvd, Nashville, TN 37217, USA"],"regionCode":""},"enableUspsCass":false}
It returned with a formatted address of: 240 Knapp Boulevard, Nashville, TN 37217-2556, Spojené štáty americké
The issue of course is that the USA country code was translated into a different language. I could fix this issue by changing the regionCode to specify the United States, but what about other countries? If I ask for a German Address, I should be able to request the country code translated into the language of my choice, but nothing is listed.
All in all, adding support for a language code parameter in the json request would help eliminate this issue, while still allowing international verification.