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: frederik[at]remote.org [Submitted to the original trac issue database at 9.26am, Monday, 14th May 2007]
It is possible to issue DELETE requests for nodes or segmements that are in use by segments or ways, respectively.
This problem has always existed but is now more dangerous, as the modified "map" call will return segments and nodes outside of the bounding box and without their context (i.e. other segments/ways using the nodes/segments that are outside the bounding box are NOT returned).
To protect data integrity, requests for deletion of items that are in use should be answered with something like "412 precondition failed" or so (I thing this is what is used when one tries to create a way from non-existing segments, so that would be related).
It will of course be very difficult for editors to handle this right - say I removed a node from a way in JOSM, this will result in one node and one segment being removed and another segment being changed to span the gap, then when uploading the lot suddenly deletion of the node fails and the whole operation would theoretically have to be cancelld. But that is another problem which the editors need to deal with.
The text was updated successfully, but these errors were encountered:
Reporter: frederik[at]remote.org
[Submitted to the original trac issue database at 9.26am, Monday, 14th May 2007]
It is possible to issue DELETE requests for nodes or segmements that are in use by segments or ways, respectively.
This problem has always existed but is now more dangerous, as the modified "map" call will return segments and nodes outside of the bounding box and without their context (i.e. other segments/ways using the nodes/segments that are outside the bounding box are NOT returned).
To protect data integrity, requests for deletion of items that are in use should be answered with something like "412 precondition failed" or so (I thing this is what is used when one tries to create a way from non-existing segments, so that would be related).
It will of course be very difficult for editors to handle this right - say I removed a node from a way in JOSM, this will result in one node and one segment being removed and another segment being changed to span the gap, then when uploading the lot suddenly deletion of the node fails and the whole operation would theoretically have to be cancelld. But that is another problem which the editors need to deal with.
The text was updated successfully, but these errors were encountered: