The southern terminus of MO 39 is defined by the state border, so I felt it appropriate to glue it there.

Some of the ways were named "State Road H" and others simply "Route H". While they all had ref tags, this designation refers to the *route*, not the *road*. So I added a route relation and tagged the ways with noname=yes.

AIUI The road itself is unnamed, but state route H follows the road.

The roads themselves are named East Dade XX, North Dade YY, etc. The number is in the road name, but that does not make them "routes" in the sense of Missouri's route network.

See changeset/137182823

I have subsequently added the names back to the ways.

As of this moment, the township border is NOT conflated with the county border. I plan to conflate the township/county border in one fell swoop after the townships are added and resolve some notes in the process.

The eastern county line should be conflated with the state line and the river as appropriate all in one go after the townships are all in place IMHO.

However, the northern border of the township is conflated with the southern border of Imperial Township and Barnhart CDP.

Gotcha, thanks!

The road is a single, flat road with one or two lanes in each direction and a bothways turn lane. This should not be mapped as dual-carriageway

Yellow crosshatching without grade separation does not call for dual-carriage mapping.

The bus route was already broken in one direction. I am working to fix the unnecessary dual-carriage-ness and repair the bus route.

were*

My sources was Bing Aerial Imagery and Esri Clarity. Sorry for not tagging those in the changeset.

Although maybe "MO 21" and "MO 34" are better names.

It feels like a good idea to at least make the form match the form of the Wikipedia article title (less anything in parens).

Apps probably don't even use this tag anyway. It would make more sense for an app to build it from network= and osm.wiki/Tag:ref=.

One siren is on the county courthouse roof in Clayton.

All map locations are derived from Bing or Esri imagery. Manufacturer, model, decibels, and range are provided as open data from Saint Louis County.

All map locations are derived from Bing or Esri imagery. Manufacturer, model, decibels, and range are provided as open data from Saint Louis County.