Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Undelete in cascade rejected by API on same chageset #4589

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

Undelete in cascade rejected by API on same chageset #4589

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment

Comments

@openstreetmap-trac
Copy link

Reporter: frodrigo
[Submitted to the original trac issue database at 11.20pm, Friday, 21st September 2012]

Probleme with API when undelete way that need undelete node. API report probleme because the undelete way refer as deleted node even is nodes are undeleted in same changeset.

Same probleme with relations and dependencies.

Probleme encroutred with JOSM undelete.

@openstreetmap-trac
Copy link
Author

Author: TomH
[Added to the original trac issue at 11.59am, Saturday, 22nd September 2012]

The API doesn't have any concept of an undelete action as such. You can bring an object back to life by writing a new version, but before you do so you will need to bring back any objects the new version depends on.

It sounds like any problem here is with JOSM not with the API.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant