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: doctau[at]mac.com [Submitted to the original trac issue database at 11.17pm, Saturday, 1st August 2009]
Occasionally when you delete a way, nodes which should be deleted (not part of any other way, no tags) aren't. I've seen this happen twice, both times it was replacing some sections of PGS-derived coastline/riverbanks with better data. What I did was add natural=coastline or waterway=riverbank to the ways and then delete the old PGS-derived ways.
Author: SpeedEvil [Added to the original trac issue at 12.33am, Sunday, 9th August 2009]
Seen this also - I left the nodes without deleting them. I was I think straightening a constituent way - and these appeared like a spray of green gobbets across the map.
node 55789384 - descendant drive - I'd cut the way into half, straightened one half.
Author: doctau[at]mac.com [Added to the original trac issue at 9.40am, Sunday, 9th August 2009]
I've noticed something slightly odd while repairing the broken way, which may (or may not) be related to what caused this.
If I re-connect a bunch of nodes to re-form the way, and then drag the map to continue causing Potlatch to load more data from the server, then Potlatch contains duplicates of those nodes - one as part of the way, and one as a green POI dot. Both have the same node ID, and it's fine when saved, but during that editing session I see the node twice.
I haven't tried to find out what happens if I move a duplicate node so that the two aren't in the same location.
Author: Richard [Added to the original trac issue at 12.36am, Thursday, 17th September 2009]
1.2b fixes a likely cause of this (split a way, then delete the half of the way with a negative ID). Would be interested if there's any other occurrences and if, so, steps to reproduce.
Reporter: doctau[at]mac.com
[Submitted to the original trac issue database at 11.17pm, Saturday, 1st August 2009]
Occasionally when you delete a way, nodes which should be deleted (not part of any other way, no tags) aren't. I've seen this happen twice, both times it was replacing some sections of PGS-derived coastline/riverbanks with better data. What I did was add natural=coastline or waterway=riverbank to the ways and then delete the old PGS-derived ways.
The second time this happened was earlier this evening, for the changeset http://www.openstreetmap.org/browse/changeset/2011692
The text was updated successfully, but these errors were encountered: