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: jfuredy [Submitted to the original trac issue database at 9.23pm, Friday, 28th August 2009]
While cleaning up track number 16843901 (a hiking trail in the Grand Canyon) I was going to break the track into two parts so I could more easily insert new points along a complicated section of switchbacks. When I hit "x" in Potlatch to break the way it gave me an error message about nodes not being present, but appeared to work anyway. I did a quick refresh by going to View mode, and then back to Edit mode and half of the track was missing, the only remnants being a string of loose, unconnected nodes from that way. I recovered an intact version of the way by reverting to an older version, but now there are hundreds of loose nodes in the map.
Is there any automated way to delete these duplicate nodes?
The text was updated successfully, but these errors were encountered:
Reporter: jfuredy
[Submitted to the original trac issue database at 9.23pm, Friday, 28th August 2009]
While cleaning up track number 16843901 (a hiking trail in the Grand Canyon) I was going to break the track into two parts so I could more easily insert new points along a complicated section of switchbacks. When I hit "x" in Potlatch to break the way it gave me an error message about nodes not being present, but appeared to work anyway. I did a quick refresh by going to View mode, and then back to Edit mode and half of the track was missing, the only remnants being a string of loose, unconnected nodes from that way. I recovered an intact version of the way by reverting to an older version, but now there are hundreds of loose nodes in the map.
Is there any automated way to delete these duplicate nodes?
The text was updated successfully, but these errors were encountered: