[OSM-dev] Finding parent ways of a node - 400 error - inappropriate?

[Tom Hughes]

In message <200711202205.43192.nick at hogweed.org>
          Nick Whitelegg <nick at hogweed.org> wrote:

> I'm developing a routine on the osmajax editor which deletes a way *and* any
> nodes in that way which are not shared with other ways. As soon as the way is
> deleted, I loop through the nodes, calling the api/0.5/node/nodeid/ways call
> to see if the nodes have any remaining parent ways.
> 
> If the node has no parent ways, I want to delete it. On calling the API,
> however, it returns a 400 error. It doesn't however seem to be something for
> which raising an error is appropriate, it seems to me to be part of the
> normal course of flow, in which the node just so happens to not have any
> parent ways - something I'm deliberately trying to test for in my client code
> in order to determine whether to delete the node or not.

Can you clarify what request it is you're making that is returning
this error? Perhaps give an example so I can test it out?

Only I think 400 is a bad request, which usually means it couldn't
make sense of the XML but you seem to be talking about a GET request
that won't have any body to be parsed?

Tom

-- 
Tom Hughes (tom at compton.nu)
http://www.compton.nu/