[Heath]

Much-belated thanks, Cliff – appreciate the clarification.

Not sure what the error message is actually indicating if the lookups are indeed, as it seems, populating through, but that’s a mystery for another day.

Cheers,

Heath

[Heath]

Hi Cliff,

Apologies for the confusion, hopefully I can clarify –

I’ve seen the grey box you’re talking about, when testing / regenerating the API key and no, that’s not a problem I’ve had.

What seems to happen is that, regardless of the time of day (and I’ve tried right at the Midnight PST query reset time), we see the error message in the image attached. The Settings window thus always shows the info in the screenshot, where the Fix Venues Data button is shown.

It looks like when that happens that it can use the API to get a ballpark location, but for venues where geocoding fails, and we don’t get lat and long, the displayed map is not precise – as in the map image below. That pin, if the API lookup worked perfectly, would have the pin set at the garden centre as when manually searched on Google Maps.

For those venues where it’s able to pull through the lat & long this works without issue, it’s just those where we see the error below in geo2 where the mapping isn’t exact.

Thanks again for your help, I appreciate it!

Heath

• This reply was modified 9 years, 8 months ago by Heath.

[Heath]

This reply is private.

[Heath]

Oh, I forgot to mention – I’ve experimentally enabled billing on the Google Maps JavaScript API and still seeing the error above.

Cheers,

Heath

[Author]

Posts