I fixed up some power lines that were originally tiger-glued to the roads, too.

ref="MO O" was incorrectly set for some of these ways due to O being to the south of 160. Other ways were named "Northwest 60th Lane" which is another wrong tiger-ism

I accidentally had an edit queued up for Pomme Creek that got stuck in this changeset.

Bing imagery is iffy here, so I used Clarity to draw the culvert and roughly positioned it for Bing alignment.

There are some old exposed boat ramps that are exposed along the river in the abandoned Lakeside area which I used to decide that Bing gave the best river banks for a map.

Bing Aerial Imagery was used to retrace the riverbanks. Esri World shows the river running higher than average.

The county line is within the river area. Arnold Township extends to the county line. The City of Arnold extends to the river banks afaict.

Also added some natural=tree.

This only affected Missouri.

Changeset #102703929 stripped this name from MO W for some reason. It's totally fine for a route to be given both a road name and a state letter designation.

I noticed this in the history of one of the ways for MO W (IIRC it was a name_1 key).

I verified the concurrency in the process.

^ Correction: the J-turn intersection is between Route B, Route P, and U.S. Route 63.

The way I implemented the J-turn is to add link roads (separated by islands, so these link roads are justified) to the route relations.

Also added the J-turn intersection between Route A, Route P, and U.S. Route 63.

This also fixes the concurrency between Route A and Route B which ignored A entirely.

Regarding the concurrency, it does not span the two counties. It is entirely within Harrison County, but Route M is a long east-west route that spans the two.

Also fixed a TIGER error on nearby YY.

I verified all north/south roles in the relation.

This looks like an editing mistake where someone forgot to deselect a node when merging? Hard to say