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

New inconsistencies in OSM database #1016

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 2 comments
Closed

New inconsistencies in OSM database #1016

openstreetmap-trac opened this issue Jul 23, 2021 · 2 comments
Assignees
@openstreetmap-trac
Labels
Component: api Priority: major Resolution: wontfix Type: defect

Comments

@openstreetmap-trac
Copy link

Reporter: martin.schaller[at]gmx.de
[Submitted to the original trac issue database at 1.16pm, Tuesday, 8th July 2008]

After fixing all ways which refer to no-longer-existing nodes, there are still new ones generated.
For example way 17158744 contains in the database the following nodes:
178219818,178219821,276982595,276982596 and 276820070

However nodes 178219818 and 178219821 do no longer exist.

When querying the way via the api, hey are contained in the current (visible="true") history of the way, but not in the way data without history.

Regards,
Martin Schaller
@openstreetmap-trac openstreetmap-trac self-assigned this Jul 23, 2021
@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 3.14pm, Tuesday, 8th July 2008]

Shit happens - until we have transactions there is no way to stop this kind of stuff happening.

@openstreetmap-trac
Copy link
Author

Author: schuetzm[at]gmx.net
[Added to the original trac issue at 1.06pm, Wednesday, 9th July 2008]

@martin Schaller: Transactions will be introduced in the next version of the API.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@openstreetmap-trac openstreetmap-trac

Labels
Component: api Priority: major Resolution: wontfix Type: defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@openstreetmap-trac