JOSM cannot handle nodes without versions

[pangoSE]

I just got an error with JOSM complaining about a node missing a version.

Could you add a possibility of skipping such nodes or better yet ask the user to update the offending node-ids from the server after or during the opening of the file?

[pangoSE]

In my case I solved it by cleaning the file by grepping (grep -v node-id) on the .osm file because the node had been deleted on the server.

[Klumbumbus]

Thanks for your report, however your ticket is incomplete and therefore not helpful in its current form.

Please add all needed information according to this list:

• The required parts of the Status Report from your JOSM.
  • Please, use Report Bug from Help menu and copy & paste.
• Describe what behaviour you expected.
• Describe what did happen instead.
• Describe if and how the issue is reproducible.
• Add any relevant information like error messages or screenshots.

To ensure that all technical relevant information is contained, create new tickets by clicking in JOSMs Main Menu on Help → Report Bug.

Remember: This is a generic notice so we don't need to write the same stuff again and again. It may only apply in parts to the specific case!

[GerdP]

I see such a message when I use osmconvert with option drop-version. It creates osm files with a header saying version='0.6'
but 0.6 requires a version. You can use osmconvert with option fake-version to fix that or you can convert it to pbf or o5m format and use the corresponding plugin to load the file.