Modify ↓
#6519 closed defect (fixed)
NPE after opening offline osm file
Reported by: | stephankn | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | Cc: |
Description
opened offline osm file by drag-drop into josm. focus on edit window caused npe.
Console has this output during opening of file:
Defaults for color.validation.warning differ: #FFC800 != #FFFF00 Defaults for color.validation.other differ: #FFFF00 != #00FFFF Error: NaN in greatCircleDistance Error: NaN in greatCircleDistance
Attached file can reproduce the problem. The problem seams to be related to the bounds line.
Repository Root: http://josm.openstreetmap.de/svn Build-Date: 2011-06-27 01:31:44 Last Changed Author: stoecker Revision: 4177 Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b URL: http://josm.openstreetmap.de/svn/trunk Last Changed Date: 2011-06-26 17:45:48 +0200 (Sun, 26 Jun 2011) Last Changed Rev: 4177 Identification: JOSM/1.5 (4177 en) Memory Usage: 981 MB / 5461 MB (880 MB allocated, but free) Java version: 1.6.0_26, Sun Microsystems Inc., Java HotSpot(TM) 64-Bit Server VM Operating system: Windows Vista Dataset consistency test: Exception during dataset integrity test: java.lang.NullPointerException Plugin: OpeningHoursEditor (26174) Plugin: download_along (26174) Plugin: editgpx (26174) Plugin: lakewalker (26174) Plugin: openstreetbugs (26174) Plugin: turnrestrictions (26174) java.lang.NullPointerException at org.openstreetmap.josm.data.osm.QuadBuckets.search(QuadBuckets.java:733) at org.openstreetmap.josm.data.osm.DataSet.searchNodes(DataSet.java:227) at org.openstreetmap.josm.gui.NavigatableComponent.getNearestNodesImpl(NavigatableComponent.java:512) at org.openstreetmap.josm.gui.NavigatableComponent.getNearestNode(NavigatableComponent.java:618) at org.openstreetmap.josm.gui.NavigatableComponent.getNearestNodeOrWay(NavigatableComponent.java:990) at org.openstreetmap.josm.actions.mapmode.SelectAction.mousePressed(SelectAction.java:425) at java.awt.AWTEventMulticaster.mousePressed(Unknown Source) at java.awt.Component.processMouseEvent(Unknown Source) at javax.swing.JComponent.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEventImpl(Unknown Source) at java.awt.EventQueue.access$000(Unknown Source) at java.awt.EventQueue$1.run(Unknown Source) at java.awt.EventQueue$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source) at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue$2.run(Unknown Source) at java.awt.EventQueue$2.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source)
Attachments (1)
Change History (5)
by , 14 years ago
comment:2 by , 14 years ago
@jtt: For longitude values you should not take min/max, but rather subtract/add 360.0 until you are in the right interval.
comment:3 by , 14 years ago
meanwhile problem of swapped lat/lon is also fixed in osmfilter (which was the generator of the faulty osm)
Note:
See TracTickets
for help on using tickets.
open to reproduce the crash