[OSM-dev] deleting nodes/ways that are members of relations

Christopher Schmidt crschmidt at metacarta.com
Mon May 12 12:15:01 BST 2008

On Mon, May 12, 2008 at 08:29:23AM +0100, Tom Hughes wrote:
> In message <20080512015522.GA21411 at metacarta.com>
>         Christopher Schmidt <crschmidt at metacarta.com> wrote:
> > It looks like the main API and Potlatch have different ideas of what
> > should be done when a node is deleted which is a member of a way or
> > relation. Potlatch deletes the node from any way or relation that it is
> > a member of: the main API just rejects the edit.
> It's more complicated than that. The main API expects the client
> to do all the work and send individual instructions for each object
> while the Potlatch API is sent a complete definition of a way with
> all the node locations and is expected to work out which nodes need
> to be moved, created and deleted and to do all the work.

This is a question about deleting nodes, not ways. I understand that
ways are more complex.

> > To consolidate these a bit, might it make sense to take a 'force
> > deletion' parameter in the API which says 'delete this node from any way
> > which it is a member of and remove it from any relations which it is a
> > member of'? This would likely be added as a parameter to the 'delete'
> > method of the node_controller, and then added as a parameter to the
> > 'delete_with_history' api call... 
> The vague plan is to have a /api/0.5/way/X/full method which can
> be called with PUT with a complete definition of a way and which
> will do a Potlatch style update.

Which is unrelated to deletion of a node.

Christopher Schmidt

More information about the dev mailing list