Opened 16 years ago
Last modified 22 months ago
#3188 closed enhancement
osmChange has create before modify — at Initial Version
Reported by: | Ldp | Owned by: | team |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core | Version: | |
Keywords: | osmChange | Cc: |
Description
I'm working with >2000 node ways, which I'm splitting up into smaller sections. Sometimes, I have to create a new multipolygon relation to hold the split ways.
In this scenario, JOSM sends an osmChange to the server with all the creates (the new split ways and the relation to hold them) before the modify (of the original way). This way, the api sees the instruction to place the (to the api) still unsplit >2000 node way in the relation, which it will refuse*.
This means I have to do 2 uploads, first to break up the way, and the 2nd to create the relation. If the osmChange that JOSM sends would have all the new way creations first, then the original way modification, and then another create for the relation, it could probably be done in a single upload.
- "You tried to add #{provided} nodes to way #{id}, however only #{max} are allowed"