de-dupe three sets of node pairs

dupe node at intersection

delete amazon iD untagged node co-located on turning loop

continued unbreakage

merge iD branch dupe nodes

one added iD co-located node here, looks to be an occasional and not consistently regular thing.

another amazon iD service drive dupe node issue

remove overlapping segment at end

blindly fix geometry issues on trails i cannot make out in imagery

i have spoken `what the he**' verbally so no need to repeat it here

wait, what? pair of 8-digit dupe intersection nodes i'm discovering today? #TimeTravel #RetroMaps #PokemonWithSideboards #DiscoPokemon #mapsme

fix the obviously wrong overlap. leave the shared non-junction for now.

fix the obviously wrong bit, leave the iffy bit that is not clearly wrong to see if osmi meckers further

fix dupe nodes where iD did not re-use the node it had just created, when branching

fix extra details. wish they'da used mapbox

unglue differing areas, geometry overlap

somehow drawn to turn on itself

fence doubled back on itself

delete some of many duped nodes. rather a lot here middle of ways so i wonder how much is equipment or user fault. leave some dupes as reminder i can see unrelated issues nearby that need work. must be amazon.

merge and join one pair of nodes. start to detach area from linear feature until i see repositioning it needs physical shift modifier. choose to leave in a state of b0rkenness.