- Status Closed
- Percent Complete
- Task Type Bug Report
- Category web → osmhv
-
Assigned To
cdauth - Operating System All
- Severity High
- Priority Very Low
- Reported Version master
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#72 - NumberFormatException in OSM History Viewer
OSMHV shows the following exception for the analysis of changeset 12762910 (maybe for others as well):
http://osmhv.openstreetmap.de/changeset.jsp?id=12762910
This analysation was created on 2012-08-20T10:25:14Z.
java.lang.NumberFormatException: empty String
The only thing that I can think of is that this changeset has an empty message.
Closed by cdauth
Monday, 04 March 2013, 01:47 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in commit 19cac6fbf8911a9c9f874d630346104d92d66cc6
Monday, 04 March 2013, 01:47 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in commit 19cac6fbf8911a9c9f874d630346104d92d66cc6
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
The stack trace is:
java.lang.NumberFormatException: empty String
at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1012)
at java.lang.Double.parseDouble(Double.java:527)
at eu.cdauth.osm.lib.api06.API06Node.<init>(API06Node.java:48)
at eu.cdauth.osm.lib.api06.API06API.makeObjects(API06API.java:165)
at eu.cdauth.osm.lib.api06.API06Changeset.fixMemberObjects(API06Changeset.java:129)
at eu.cdauth.osm.lib.api06.API06Changeset.getMemberObjects(API06Changeset.java:93)
at eu.cdauth.osm.lib.api06.API06Changeset.getPreviousVersions(API06Changeset.java:219)
at eu.cdauth.osm.web.osmhv.ChangesetAnalyser.<init>(ChangesetAnalyser.java:116)
at eu.cdauth.osm.web.osmhv.ChangesetAnalyser$1.work(ChangesetAnalyser.java:58)
at eu.cdauth.osm.web.common.Queue$ExecutionThread$1.run(Queue.java:140)
This is caused by the fact that the coordinates of deleted nodes are not in the changeset XML. This means that in API06Changeset.java:129, instead of just creating objects for the items, we need to actually fetch the previous versions of nodes.
Same for http://osmhv.openstreetmap.de/changeset.jsp?id=14509484
Fix this bug
0001-fix-bug-using-LatLon-of-...