Can't Repro
Status Update
Comments
sh...@google.com <sh...@google.com> #2
If possible, can you please provide us with a self contained sample (http://sscce.org ) that will demonstrate the issue?
If you have attempted to reproduce the issue with a self contained sample, but failed, can you please explain the steps you have already taken to troubleshoot this and what were your findings.
If you have attempted to reproduce the issue with a self contained sample, but failed, can you please explain the steps you have already taken to troubleshoot this and what were your findings.
mi...@google.com <mi...@google.com> #3
The issue as described cannot be reproduce with any of the provided latlngs:
https://maps.googleapis.com/maps/api/geocode/json?result_type=country&latlng=32.7481682,-96.4458781
Please provide one of
- an SSCCE
- a Geocoding API web service request (such as mine above) that reproduces the issue
- a link such ashttps://google-developers.appspot.com/maps/documentation/utils/geocoder/#q%3D32.748168%252C-96.445878 where no results has Types: country
Please provide one of
- an SSCCE
- a Geocoding API web service request (such as mine above) that reproduces the issue
- a link such as
ga...@anuary.com <ga...@anuary.com> #4
Comment has been deleted.
ga...@anuary.com <ga...@anuary.com> #5
Comment has been deleted.
ga...@anuary.com <ga...@anuary.com> #6
* https://maps.googleapis.com/maps/api/geocode/json?result_type=country&latlng=52.6323813,4.753375399999999 (ZERO_RESULTS; should be Netherlands)
*https://maps.googleapis.com/maps/api/geocode/json?result_type=country&latlng=53.7465087,-3.031627499999999 (ZERO_RESULTS; should be UK)
*https://maps.googleapis.com/maps/api/geocode/json?result_type=country&latlng=25.7616798,-80.1917902 (ZERO_RESULTS; should be USA)
Point is, there are a lot of these and they are not hard to find.
If you guys can sponsor Google Place credits for my research, happy to provide thousands of these.
*
*
Point is, there are a lot of these and they are not hard to find.
If you guys can sponsor Google Place credits for my research, happy to provide thousands of these.
ga...@anuary.com <ga...@anuary.com> #7
* https://maps.googleapis.com/maps/api/geocode/json?result_type=country&latlng=40.45249429999999,-78.4019007 (ZERO_RESULTS; should be US)
*https://maps.googleapis.com/maps/api/geocode/json?result_type=country&latlng=28.3695167,-81.5198091 (ZERO_RESULTS; should be US)
*https://maps.googleapis.com/maps/api/geocode/json?result_type=country&latlng=39.1191163,-78.1944690999999 (ZERO_RESULTS; should be US)
*https://maps.googleapis.com/maps/api/geocode/json?result_type=country&latlng=39.0518683,-77.4549593 (ZERO_RESULTS; should be US)
*https://maps.googleapis.com/maps/api/geocode/json?result_type=country&latlng=65.84274409999999,24.14305509999999 (ZERO_RESULTS; should be FI)
*https://maps.googleapis.com/maps/api/geocode/json?result_type=country&latlng=47.7559401,-122.1542136 (ZERO_RESULTS; should be US)
*https://maps.googleapis.com/maps/api/geocode/json?result_type=country&latlng=39.3707032,-76.4645455 (ZERO_RESULTS; should be US)
*https://maps.googleapis.com/maps/api/geocode/json?result_type=country&latlng=42.0976471,-76.0106954 (ZERO_RESULTS; should be US)
*https://maps.googleapis.com/maps/api/geocode/json?result_type=country&latlng=33.5631406,-84.3293851 (ZERO_RESULTS; should be US)
*https://maps.googleapis.com/maps/api/geocode/json?result_type=country&latlng=40.032081,-82.4475324 (ZERO_RESULTS; should be US)
*
*
*
*
*
*
*
*
*
ra...@google.com <ra...@google.com>
g....@gmail.com <g....@gmail.com> #8
I have literally included verbose cURL output showing the entire HTTP exchange. Look through the logs based on the timestamp of the request and the coordinates.
It is clear that the issue is intermittent: the previously submitted coordinates included in the bug report now produce expected result.
I am happy to aid you to identify the issue by seeking out more examples if you are willing to escalate this and provide a reasonable response time.
It is clear that the issue is intermittent: the previously submitted coordinates included in the bug report now produce expected result.
I am happy to aid you to identify the issue by seeking out more examples if you are willing to escalate this and provide a reasonable response time.
mi...@google.com <mi...@google.com> #9
Thanks for reporting this issue. We have verified and logged it internally. Please note that we cannot give you any timelines, but you can star the issue to get notifications.
mi...@google.com <mi...@google.com> #10
This appears to be an issue caused by transient quality issues in Google Maps data. Such issues are resolved over time but new ones may appear later.
We'll be looking into making the Geocoding API more resilient to these in the future.
We'll be looking into making the Geocoding API more resilient to these in the future.
mi...@google.com <mi...@google.com> #11
We have been monitoring the situation; it appears the issue is no longer manifesting and is not likely to do so again. Please let us know otherwise.
Description
* result_type: country, latlng: 36.0437223,-96.0038623
* result_type: country, latlng: 36.2798985,-95.8330027
* result_type: country, latlng: 40.4524943,-78.4019007
* result_type: country, latlng: 40.4699385,-78.4108373
* result_type: country, latlng: 39.4270445,-87.4251704
* result_type: country, latlng: 36.7377542,-97.0733942
* result_type: country, latlng: 42.445722,-96.35282199999999
* result_type: country, latlng: 39.9208753,-88.95733059999999
* result_type: country, latlng: 39.7546345,-89.727282
* result_type: country, latlng: 32.7481682,-96.4458781
All of these queries return ZERO_RESULTS error.
Related: