Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Google Maps API rate-limit leads to persistent (-Inf,-Inf) coordinates in DB

Description

If the Google geocoder hits the daily rate-limit (currently quoted as 2500 requests per day) then it appears that coordinates of (-Infinity, -Infinity) start to go into the longitude and latitude fields. Worse, it appears these values never get recognized as invalid, so the geocoder never attempts to replace them with valid coordinates. The only workaround seems to be to delete the invalid records manually from the database.

Creating this issue in response to commercial support ticket https://mynms.opennms.com/Ticket/Display.html?id=2504

Environment

Any system configured (e.g. by default) to use the Google Maps API geolocation service and having >= 2500 nodes with address asset fields

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Benjamin Reed October 2, 2013 at 5:27 PM

Fixed in 1.12.

Jeff Gehlbach September 18, 2013 at 2:39 PM

All the info I have is in the support ticket linked above.

Benjamin Reed September 18, 2013 at 1:56 PM

Do you happen to have the log/error that google responds with when we've hit the limit? If so, should be easy to trap it.

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

PagerDuty

Created September 18, 2013 at 12:48 PM
Updated January 27, 2017 at 4:20 PM
Resolved October 2, 2013 at 5:27 PM

Flag notifications