You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: osm[at]randomjunk.co.uk [Submitted to the original trac issue database at 11.00pm, Tuesday, 5th February 2008]
People often play with JOSM where they create themselves a .osm file via some script they've written, then they try to get JOSM to upload it. Unfortunately they've forgotten to use -ve IDs, and have managed to figure out how you convince JOSM to think the node has "changed".
When they upload it causes devastation, usually to low numbered nodes. They haven't got a big enough file to generate IDs bigger than that.
One way to catch this then, is to not have node IDs smaller than some "quite large" number. I picked 50000 randomly, there aren't actually that many nodes numbered below this anyway.
The text was updated successfully, but these errors were encountered:
Reporter: osm[at]randomjunk.co.uk
[Submitted to the original trac issue database at 11.00pm, Tuesday, 5th February 2008]
People often play with JOSM where they create themselves a .osm file via some script they've written, then they try to get JOSM to upload it. Unfortunately they've forgotten to use -ve IDs, and have managed to figure out how you convince JOSM to think the node has "changed".
When they upload it causes devastation, usually to low numbered nodes. They haven't got a big enough file to generate IDs bigger than that.
One way to catch this then, is to not have node IDs smaller than some "quite large" number. I picked 50000 randomly, there aren't actually that many nodes numbered below this anyway.
The text was updated successfully, but these errors were encountered: