-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 19.0.1, 19.1.0
-
Fix Version/s: 20.0.1, Meridian-2017.1.0
-
Component/s: Assets, Provisioning / Discovery / Importer
-
Security Level: Default (Default Security Scheme)
-
Labels:None
-
Environment:OpenNMS V19.0.1 on Ubuntu 1604
OpenNMS V19.1.0 on Ubuntu 1604
-
Sprint:Horizon - May 10th, Horizon - May 17th
Samples:
geocoder produced invalid latitude/longitude data in table assets.
zip | address1 | city | latitude | longitude ----------+----------------------------------------+--------+-----------+---------- 2415-026 | Regueira de Pontes, Fracção N, Nave 13 | Leiria | -Infinity | -Infinity 2415-026 | Regueira de Pontes, Fracção N, Nave 13 | Leiria | -Infinity | -Infinity 2415-026 | Regueira de Pontes, Fracção N, Nave 13 | Leiria | -Infinity | -Infinity 2415-026 | Regueira de Pontes, Fracção N, Nave 13 | Leiria | -Infinity | -Infinity
When using http://www.freegeocoding.com/batch.php the address results in
39.7861962,-8.818807099999958
This such entrys, the map-box.jsp freezes (see NMS-9339)
Edit mvrueden:
As mentioned in the comments below this is only affecting Horizon 19 and with backporting HZN-1016 to foundation-2017 this is solved at least for Meridian 2017 and possible next Horizon 19 releases. However a database update script should remove these entries from the database.
- Causes
-
-
- Closed
-
