Modify

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#11773 closed defect (fixed)

Saving osm files in JOSM will save the nodes in one of two orders

Reported by: cmeeren@… Owned by: team
Priority: normal Milestone: 16.01
Component: Core Version:
Keywords: template_report Cc:

Description

What steps will reproduce the problem?

  1. Open an OSM file in JOSM
  2. Save the file without changing anything
  3. Look at the file in a text editor (or make an md5 hash, or similar)
  4. Re-save the file a couple of times (without restarting JOSM), observe in the text editor that nothing changes
  5. Restart JOSM
  6. Redo steps 1-5, observe significant changes in the OSM file
  7. Redo steps 1-5 again, observe in the text editor that the file matches the 1st time you saved it
  8. Redo steps 1-5 ad lib, observe that JOSM seems to change between two "states" every time the file is saved

What is the expected result?

Nothing should change when an osm file is saved without editing. The order of the nodes should be the same each time the file is saved.

What happens instead?

Everything is changed, seemingly between two states every other time JOSM is started. This makes it difficult to version-control the OSM files with e.g. git (workaround: restart JOSM and re-save the file again to bring it back to the "node order" you have versioned).

Please provide any additional information below. Attach a screenshot if possible.

Revision: 8491
Repository Root: http://josm.openstreetmap.de/svn
Relative URL: ^/trunk
Last Changed Author: Don-vip
Last Changed Date: 2015-06-16 23:27:08 +0200 (Tue, 16 Jun 2015)
Build-Date: 2015-06-16 21:45:58
URL: http://josm.openstreetmap.de/svn/trunk
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last Changed Rev: 8491

Identification: JOSM/1.5 (8491 en) Windows 7 64-Bit
Memory Usage: 246 MB / 247 MB (34 MB allocated, but free)
Java version: 1.8.0_51, Oracle Corporation, Java HotSpot(TM) Client VM
VM arguments: [-Djava.security.manager, -Djava.security.policy=file:C:\Program Files (x86)\Java\jre1.8.0_51\lib\security\javaws.policy, -DtrustProxy=true, -Djnlpx.home=<java.home>\bin, -Djnlpx.origFilenameArg=C:\Users\Christer\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\56\1ee8cfb8-23a0e964, -Djnlpx.remove=false, -Djava.util.Arrays.useLegacyMergeSort=true, -Djnlpx.splashport=11371, -Djnlp.application.href=https://josm.openstreetmap.de/download/josm.jnlp, -Djnlpx.jvm=<java.home>\bin\javaw.exe, -Djnlpx.vmargs=LURqYXZhLnV0aWwuQXJyYXlzLnVzZUxlZ2FjeU1lcmdlU29ydD10cnVlAC1Eam5scC5hcHBsaWNhdGlvbi5ocmVmPWh0dHBzOi8vam9zbS5vcGVuc3RyZWV0bWFwLmRlL2Rvd25sb2FkL2pvc20uam5scAA=]
Dataset consistency test: No problems found

Plugins:
- turnrestrictions (31241)
- utilsplugin2 (31241)

Attachments (1)

example_osm_file.zip (6.0 MB) - added by cmeeren@… 4 years ago.
Note that this file is made using another tool. Save it once in JOSM to bring it into one of JOSM's two "states" as per the ticket instructions

Change History (3)

Changed 4 years ago by cmeeren@…

Attachment: example_osm_file.zip added

Note that this file is made using another tool. Save it once in JOSM to bring it into one of JOSM's two "states" as per the ticket instructions

comment:1 Changed 4 years ago by simon04

Resolution: fixed
Status: newclosed

In 9310/josm:

fix #11773 - Saving osm files in JOSM will save the nodes in one of two orders

comment:2 Changed 4 years ago by simon04

Milestone: 16.01

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.