Status Update
No update yet.
Comments
ee...@google.com
Thank you for posting!
Upon checking, Geocoding API returns the correct result for. Here is a sample request:
Could you please check if you can still reproduce the issue on your end?
If yes, for us to further investigate, could you please provide more information on your issue?
- Please provide us with a sample request that demonstrates the issue.
- Please provide us more info on what is the expected result.
[Deleted User] <[Deleted User]>
ee...@google.com
Thank your for your response!
Please reply to us through Public Issue Tracker, and not through e-mail because we cannot open the printscreen file, image.png.
Also, replying through your e-mail will expose your name and contact details, which are considered as Personal Identifiable Information (PII).
That said, we will be removing your
[Deleted User] <[Deleted User]>
Thank you for the information.
We tested with two adresses this afternoon and made a printscreen of the result. The one on the left is the one that is not working in our application. The one on the right is working. The differences are marked with yellow. Please see the attached image
[Deleted User] <[Deleted User]>
Is there new information available on this issue?
ee...@google.com
Thank you for waiting!
For us to help you further, please provide us with a full web API request(s) without your API key that shows the problem.
ee...@google.com
Thank you for the additional information!
It looks like that the country component was specified 3 times in the request that you are sending. Please note that component filters (e.g. country, postal_code) should only be specified once per request. Repeating component filters should return INVALID_REQUEST which is the intended behavior of the API .
However, there is a known issue where multiple country component filter returns results when instead it should return an INVALID_REQUEST error. You can check it here:
To solve this issue, you should only use one country component in your request which in this case country:NL. Here is a sample working request for the address Koolmees 13, 2411 MV Bodegraven, Netherlands:
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
===========================================================================================
Issue report
----------------
What steps will reproduce the problem? Please provide a link to a
demonstration page if at all possible, or attach code.
1. We are using the googleGeoApi in our application to calculate the travel distance, so that we can calculate the trave costs. A couple of address cannot be found by the api. If I fill in the adresses in maps, they can be found. Is it possible for me to add address to the GoogleGeoApi or will there be an adresses synchronisation between the api's?
2. For example the followin address: Koolmees 13, 2411MV Bodegraven Nederland
3.
Thank you very much for you time