I am trying to debug Relation removal? · Issue #5243 · streetcomplete/StreetComplete · GitHub involving https://www.openstreetmap.org/relation/1318928
Is there some way to see its history, especially membership of ways in it over time?
I am trying to debug Relation removal? · Issue #5243 · streetcomplete/StreetComplete · GitHub involving https://www.openstreetmap.org/relation/1318928
Is there some way to see its history, especially membership of ways in it over time?
A couple of other options: http://osmlab.github.io/osm-deep-history/ (which shows graphics for ways, which would have been useful here) and https://map.atownsend.org.uk/maps/osm-deep-history/ (no graphics, but a few other links).
Another option. which will work if there aren’t too many revisions, is https://osm.mapki.com/history/.
SomeoneElse: “Another option. which will work if there aren’t too many revisions, is https://osm.mapki.com/history/.”
I agree, this was my favorite tool for such a work.
After a period of time the service was down for a while. Fortunately then there was a kind of switch from close source to open source code, but unfortunately the color scheme still has a minor bug, see issue:
If a one of the software developers could have an eye on it to fix it - i would appreciate it
FWIW This query shows for each
relation version the number of loose ends at the creation date.
However, I suggest to uncomment line 3 to look only at what happened in
2023 because this reduces the runtime from several minutes in a couple
of seconds. For reference
[timeout:900][out:csv(version,timestamp,open)];
timeline(rel,1318928);
//derived._(if:t["created"]>"2023-01-01");
for (t["created"])
{
retro (_.val)
{
rel(1318928);
way(r)->.w;
node(way_link.w:1)->.n;
make info
timestamp=set(timestamp()),version=set(version()),open=n.count(nodes);
out;
}
}
Please note that subsequent edits to the ways can change that number
without generating a new version. The data model update is designed to
tackle that problem, although only for ways first, because for relations
it may have unwanted downsides.
Afterwards, the query
[date:"2023-08-22T13:27:10Z"];
rel(1318928);
way(r)(newer:"2023-08-22T13:27:09Z");
out meta;
shows that no edits to ways only are responsible, and that the changes
to the relation itself in version 494 itself have created the dangling ends.