Hello, it looks like you accidentally untagged the city boundary, moved a street lamp, and deleted a residential road in the process of adding your business location.

I rolled this changeset back and added your location properly in changeset/155393729.

Hello, it looks like you accidentally untagged the city boundary, moved a street lamp, and deleted a residential road in the process of adding your business location.

I rolled this changeset back and added your location properly in changeset/155393729.

Welcome to OSM! It seems you've tagged your location as a place of worship which is probably not what you intended. Your change also seems to have deleted a residential street named South McCoy.

Let me take a look at this changeset; don't take it personally if I undo it and add your location myself.

Feel free to ask me anything about how OSM works or how to go about a certain kind of change. You can also check the wiki to learn almost anything OSM related: osm.wiki

It was previously tertiary, but this short road section connects it to a double state route very nearby.

The turn restrictions no longer apply since there is no U-turn connection anymore.

Spencer Creek Road did not even remotely deserve primary classification, too.

Please do not abbreviate road names! Downstream users and companies can easily abbreviate the names if they want the abbreviated forms, but the abbreviated forms carry less information.

It was already mostly secondary, but some small bits were randomly primary.

Let the downstream companies like Mapbox abbreviate the road names. It's much easier to convert from un-abbreviated to abbreviated than vice-versa

FYI the county is not the authority for state designations. Camden County can provide local names for stretches of state road, of course, but the county cannot dictate where MO 5 and its special routes go.

This is not one of those cases, though, since this MO 5 Business is not a state designation. Weird.

This changeset focused on a business route of Missouri Route 5 in Camdenton, Missouri.

This is a strange business route, as it's not acknowledged by MoDOT as one. It would appear local government designated it as such, and it functions just like one, so...

Docs for the historic site call it RA 13 which is nomenclature I've not seen before...

I don't know the history of route alignments in this area, but MoDOT data does, indeed, support John Shea Drive being MO 13 Spur despite the fact that it does not currently connect to MO 13. (Its travelways are designated SP 13 N and SP 13 S.)

^ Looks like a relation already exists for it: #7785857

modifier does not go on road ways. That tag is meant for use in route relations.

FYI this is not a state business route. It's a local route named North/South Business Route 5. It probably still deserves a route relation for semantics, but it's not in the US:MO:Business network.

And #155354621

This is a large bounding box, but the edits are very sparse. Everything was done manually.

I copied and pasted the text in my previous comment from my comments on changeset #155351001, so that's why it reads awkwardly.

We try to avoid abbreviation in OSM unless the "true" name contains the abbreviation...that's always a case-by-case debate, but in this case it should have been "Highway" if anything.

And to be clear, this road is named, but it's not a simple string name that can be canonicalized in the name tag. This is a state road designated as part of State Route 7...or Route 7, State Highway 7, Highway 7, Missouri 7, etc. That's the issue: there is not a canonical text rendering of this designation. So we use route relations to convey this and also ref tags for data consumers that don't process the route relations.

I did not add noname=yes back to the ways