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: 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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: