Saving and reopening of downloaded gpx segments displays distorted data

[Fabi2]

I downloaded a bounding box together with it's GPS-data from the server. Then I saved the downloaded gpx-layer in a file as there are only few changes in the downloaded area. After closing and reopening JOSM and the saved gpx file JOSM displays distorted data.

JOSM 1759 + OpenJDK 1.6.0

[xeen]

I just downloaded an area from where I lived, exported and re-opened the gpx file and it worked fine for me. Can you specify where this does not work and/or upload a defect file?

[bastiK]

downloaded gpx (​http://www.openstreetmap.org/?lat=54.087&lon=13.392&zoom=11)

[bastiK]

saved and reopened

[bastiK]

Here are some screenshots that show the problem.

Saving and reopening should really be transparent.

This way we can some day implement sessions, e.g. close and restart JOSM such that all opened layers are recovered the way they were before.

[stoecker]

Hmm, I think this is a wontfix. The OSM server does not give us traces, but only one big lump of positions. So we have different display settings for server and files to work around this. As soon as you save and reopen, the state changes from server to file and other settings apply.

Maybe we can add a special JOSM key to saved GPX files to transport the "server"-state across saving.

[bastiK]

Well, I think wontfix is not an option here. :)

If you download several MB of traces, then right click on the layer -> save as, afterwards reopen it and have the etire screen full of useless trash - that's just not acceptable.

Nowadays, there should be tracks with timestamps as well (​http://wiki.openstreetmap.org/wiki/Visibility_of_GPS_traces). Im not sure it is already supported by JOSM, but, "Layer->save as" should really be renamed to "Layer->export as gpx" if it does just that.

Putting some extra tags in the gpx file sounds fine (unless it confuses other apps).

[stoecker]

A note to clear situation: The useless trash can be changed simply by applying the same distance measure for GPX files as for server. This trashy behavior is based on the fact, that for server we have a very short value, for GPX files a much larger one. The value how long a segment may be can be changed in preferences.

[bastiK]

In 5679/josm:

fixed #2900 - Saving and reopening of downloaded gpx segments displays distorted data (see #7247; namespace aware xml parsing is needed now, so #7247 is open again)