ejont's Comments
| Changeset | When | Comment |
|---|---|---|
| 60215392 | over 6 years ago | These are the changesets with deletions that I've found. This is surely not a complete list, the method was simply to look at orphaned nodes (nodes not part of any way) in overpass-turbo with this query: [bbox:{{bbox}}];
The list with changeset, username, what was (partly) deleted, is it fixed?: changeset/46006098 @LiJuThomas unclassified road
|
| 60215392 | over 6 years ago | I've since found about 70 deletions showing this pattern (part of a way is deleted, the way history is on the remaining part, the nodes are not deleted). 19 of those are already fixed, the rest needs to be fixed. Almost all of them seem to be by paid mappers who import gps traces of delivery trucks or such into osm. My hypothesis is they are using a common tool that sometimes cuts ways off. But I'm open for other explanations. I've commented on one changeset by a mapper who doesn't seem to be in the business of importing gps traces (@mottiger changeset/63531134). It could be a bug in JOSM. Maybe they remember how they did it. |
| 63531134 | over 6 years ago | Hello mottiger!
|
| 61047566 | over 6 years ago | Actually, the deletion happened here: changeset/61042893 |
| 65835754 | over 6 years ago | The deletion happened actually here: changeset/65835703 |
| 66150424 | over 6 years ago | This changeset damaged three roads at the top of the bounding box. |
| 65775988 | over 6 years ago | Hm, ok, I'm using JOSM too. I've explained here changeset/60215392 why I think it's very hard to produce an error like this intentionally or accidentally with a standard install of JOSM. So you're saying you use nothing but JOSM? In this changeset changeset/66150424 you managed to cut pieces off of three roads accidentally (one secondary, one primary, one tertiary, the first two have been fixed the last one not)? To me it seems more like the work of some kind of tool that applies a bounding box which bugs out sometimes. I'd really like to get to the bottom of this because the more I look into this the more instances of this kind of error I find (you're not the only user that produced deletions like this) and I don't think it's a bug in JOSM. If it's the latter it would be very useful to file a bug report. |
| 65775988 | over 6 years ago | Thanks. What's for workflow? Are you using any non-standard tools? |
| 61047566 | over 6 years ago | I've restored the road. See also similar deletion in changeset/60215392 |
| 60215392 | over 6 years ago | Since the user seems to be no longer active, I've restored the road. However, there seems to be a systematic problem here. With a default install of JOSM it is quite hard to replicate the behaviour that leads to a deletion of a road in this way. You'd first have to split the way, but in this case so that the shorter part retains the history (needs to be done explicitly). Then you'd need to select the other part, but unselect the nodes first (because those were still there), and only then hit delete. Hence I believe this is not how it was done. My guess is there exists a buggy piece of software that is used by some editors. This needs to be investigated as I've come across a number of similar deletions, done as recently as 5 days ago (see changeset/68665342). |
| 65775988 | over 6 years ago | Hi! You deleted part of a National Highway here. Why? |
| 68665342 | over 6 years ago | Hey, you deleted part of a National Highway here! Why? |
| 45301830 | over 6 years ago | Hello,
|
| 60407615 | almost 7 years ago | Hello Halloween123!
|
| 65780919 | almost 7 years ago | ? |
| 64686030 | almost 7 years ago | I restored the ways. |
| 57793703 | almost 7 years ago | This changeset deleted part of way/278326392. Please revert! |
| 56628094 | almost 7 years ago | This changeset deleted part of way
|
| 65887464 | almost 7 years ago | Hello,
|
| 64686030 | almost 7 years ago | Hi,
|