Error reverse geocoding: failed to determine hierarchy...

[stepps00]

Error message: Error reverse geocoding
Logging message: Error reverse geocoding: failed to determine hierarchy, because 429 Client Error: Too Many Requests

When importing new venue records from a CSV, I encountered the above error/logging messages.

There are no steps to repeat, since this error message automatically appears when BI loads this row from my CSV file. Clicking the "find it on the map" link causes the error to reappear, so I am unable to build a hierarchy for this record.

[dphiffer]

Eek, thanks for reporting. Updating the python libraries seems to have fixed this, @stepps00. Can you confirm it's working for you?

[stepps00]

I re-uploaded the CSV and stepped through a few records, still seeing the error messages. I am also seeing another (unrelated?) logging message. Screenshots below:

1

2

[dphiffer]

Thanks, I'm looking into this more. I am seeing requests to both whosonfirst-api.mapzen.com and places.mapzen.com in the debug logs.

[dphiffer]

Found the source of the API endpoint issue. Also realized that the custom limits on our API key had to be updated for the new service. I think that should do it? (I hope?)

[stepps00]

Thanks, that did it! I've stepped through a dozen or so records, tried to build the hierarchies, and found no issues.

[dphiffer]

Excellent, glad to hear it!