Opened 13 years ago
Last modified 3 years ago
#5746 new enhancement
Implement "if-unused" osmChange API feature for outside BBOX nodes — at Version 3
Reported by: | anonymous | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | if-unused API diff API0.6 node delete | Cc: |
Description (last modified by )
API 0.6 has been extended to support a "if-unused" delete node attribute on osmChange diff uploads.
Introduced here: http://git.openstreetmap.org/rails.git/commitdiff/2d937f94d55c0b8f94b024f579a78271d85fbe9a
It would make sense to start using this for nodes which are deleted, instead of prompting user when they attempt to delete a node outside known BBOX.
Change History (3)
comment:1 by , 13 years ago
follow-up: 3 comment:2 by , 13 years ago
It is probably not good to use this for *all* nodes that are deleted because this means that editing conflicts go unnoticed. And it is probably not good either to drop the "you are deleting stuff outside the downloaded area" message either because doing so is usually not a good thing - some things might rely on what you're deleting without actually using it, e.g. you delete a road for which someone else has made a corridor through a forest just outside your downloaded area - so you want to delete the road and let the corridor remain? etc.
comment:3 by , 11 years ago
Description: | modified (diff) |
---|
framm: We had talked a couple of weeks ago, do you have any further thoughts on this? I think it makes sense to do if-unused for all nodes outside the downloaded area
Potlatch 2 now implements: http://trac.openstreetmap.org/changeset/24776