I discovered by chance today in our Google cloud console account that a significant percentage (43%) of all queries to the geocoding API are failing.

I am looking to set a geofence that is (mostly) centered in a given address. Sometimes the coordinates for that “pin” are in the front/back/side of the property and I would like to check that the coordinates are mostly centered by comparing the distance of the location coordinates to the NE and SW coordinates given as bounds but sometimes bounds are not provided at all. In this case, I only receive viewport coordinates and am left without clear property boundries with which to set my geofence properly.

Using Google Geocoding API, we linked the API based on “310-0026”, so a value different from the actual address will be issued. The information marked ☓ below will be returned. Please fix it so that it can be returned with the correct value (〇).

Closed 15 mins ago.