If there is no physical presence, then it doesn't belong on a map.

The "MO" prefix is used on the ways. It's the relation that we keep the prefix out of.

These ways are distributed across Linn and Sullivan counties of MO.

The TIGER-imported name for the road was "County Road 195" which was completely wrong. South of US 160 the road is called "South Dade 191", and north is designated Route EE (probably "North Dade 191" completing the pattern).

I added two bridges as well.

Stream names came from National Map which is public domain by USGS.

Also also I bumped the classification up to tertiary which appears to be the consensus for MO supplemental state routes.

I also used Bing StreetSide in addition to Bing aerial.

note #3773063

This is not to be confused with the nearby I-44 Business Loop that goes to Waynesville

Also added turn restrictions

Bing Aerial Imagery

Also added a new bridge on MO D just west of Osage County Route 727.

Bounding box is large because I added layer=5 to some power lines.

Renamed "Chicksaw [sic] Lane" to "Chickasaw Lane" and moved it into the correct location.

Bing StreetSide has better coverage than I expected here

I was not aware that boundary=census was not rendered in Carto which implies that CDPs that DO render in Carto are incorrectly tagged as admin boundaries...yikes

I still believe this belongs in OSM if it's tagged appropriately since an app can render it if it likes

I used boundary=census since this is a CDP without legal status.

I also added a bridge.

The bounding box is extra large because I added layer=5 to a pair of power lines going over N.

I also added a pair of missing link roads and cleaned up some untouched TIGER roads connected to N.