dupe nodes as always

pair of pair dupes

amazon iD branch added-node fix

another node merge, iD seems sometimes unwilling to re-use its current nodes.

nerd mojo. think it follows the pattern.

merge nodes, nothing to learn here

merge nodes, one theory shot but i could be confused or tired.

two nodes merged, but one twice in the sequence. will have to check if this also was flagged self-intersecting.

merge nodes. i'm beginning to see a pattern...

merge. iD did not re-use the 708 it created, but added a new 721 in series, where it looks like merges will end up, so i gotta watch tagged nodes at junctions.

merge 3 co-located nodes into one. note that one was tagged and if not selected in potlatch, that tagging would be lost, now i know i have to analyse everything which is not obvious.

newly-added null node over intersection node, presumed amazon

merged nodes.

merge dupe node with no rhyme nor reason

merge an amazon iD newly-added intersection node from one new branch, with the old road node used as intersection from the other new branch.

dupe node at crosswalk end

another golf node dupe

merge overlapping intersection

don't start at a gate in the middle of the fence

obsolete