Opened 11 years ago

Closed 10 years ago

#2123 closed defect (fixed)

removing way sometimes leaves behind nodes

Reported by: doctau@… Owned by: richard@…
Priority: major Milestone:
Component: potlatch (flash editor) Version:
Keywords: Cc:


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

Change History (4)

comment:1 Changed 11 years ago by SpeedEvil

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.

comment:2 Changed 11 years ago by doctau@…

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.

comment:3 Changed 11 years ago by Richard

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.

comment:4 Changed 10 years ago by Richard

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.