Addresses note/3791543

Also Source: Bing for redrawing the footprints

Also excluded are Route 64A and Route 64B which are considered related routes of Route 64. I treated them like special routes.

I used Notepad++ macros to convert the resulting CSV into JavaScript function calls which I pasted into the Scripting console in JOSM.

I then, of course, manually verified. But I wanted the extra layer.

I used Excel to construct the enwiki article title for each route, called the Wikipedia API with the WEBSERVICE and FILTERXML formula functions to get the QID, and then called Wikidata API to get the enwiki article for each item. Then I used conditional formatting to double check that the predicted and actual enwiki article titles matched indicating non-conflated articles (e.g. Route 27 being folded into Avenue of the Saints or the Martin Luther King Bridge of which half is Route 799).

addresses note #3783815

Also added wikidata and wikipedia links to 172 rel

Also addressed note #3646245 O-SAKI

I think Coinos automatically places POIs when merchants join them to accept cryptocurrency.

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