This was a manual edit for the record.

Newly discovered designation renderings include:

Sthy East (botched form of "State Highway E")
N Route East (botched "North Route East" with inappropriate directional prefix)
East Highway E
State NN and State Nn
Bb Highway

^ To clarify, a local community may refer to a road by whatever name is chooses. The directional affixes on MO supplemental state routes from TIGER, however, are poor quality. The TIGER import wrongly assumed, for example, the letters N, E, S, and W were directional indicators rather than highway designations.

Directional affixes are not part of the state designation, by the way. Counties may have their own locator systems, but those locators do not render as affixes on state designations.

This is a manual edit. Some varying renderings discovered:

Highway Af
State Route Af
State Highway Z
East State Highway HH
East Route HH
State Highway Y North

There is a possibility that this was a misnomer "Audrain Road E" in the same vein as "County Road E" as is seen frequently with supplemental state routes, and the E got expanded to East... In that case, there should be no name.

Correction: this impacted tag name="State Highway ZZ", not tiger:name=

Continues 155661352

Continues cleanup operation from changeset/155633221.

This also found and fixed instances of ways named "Foo;State Highway X" and "Bar / State Road X", etc., where delimiters were put in the name tag. I felt these were in scope for this changeset due to the route lettering

By leveraged, I mean I'm using search in JOSM.

This primarily impacts tiger:* tags, although many name="State Road X" and name="Highway X" are removed, as well.

There seems to be a million ways to render a state route designation into text, and none of them can elegantly handle concurrencies

I am aware that this left some ways with name_2 tags but no name tags when the latter was targeted. This will be remedied by promoting name_2 when it wouldn't overwrite name

Query used:

[timeout:120];
area[name="Missouri"];
way(area)[ref~"(^|;)MO A(;|$)"][name="State Highway A"];
(._;>;);
out meta;

This changeset continues effort from changeset/155583386

"is_in" is completely redundant nowadays, and I am confident that, on state route ways specifically, they will not be missed. Redundancy/denormalization is good for perf optimizations sometimes, but it's super easy to find enclosing munis/CDPs

This only affected ways participating in state routes, also, as determined by this Overpass Turbo query:

area[name="Missouri"];
way(area)[ref~"(^|;)MO "]["addr:postcode"];

This tag is meant for buildings and POIs

Some addr:postcode tags were also removed

This was the code I used in JOSM:

from org.openstreetmap.josm.command import ChangePropertyCommand, SequenceCommand
from org.openstreetmap.josm.gui import MainApplication

def println(x):
from org.openstreetmap.josm.plugins.scripting.ui.console import ScriptingConsole
ScriptingConsole.getInstance().getScriptLog().getLogWriter().println(x)

# equal and non-null
def enn(x, y):
return x and y and x == y

def check(way, x, y):
if enn(way.get(x), way.get(y)):
return ChangePropertyCommand(way, x, None)
return None

layer = MainApplication.getLayerManager().getEditLayer()
cmds = []
for way in layer.data.getWays():
cmds.append(check(way, 'tiger:name_base', 'name'))
cmds.append(check(way, 'tiger:name_base_1', 'name_1'))
cmds.append(check(way, 'tiger:name_base_2', 'name_2'))
cmds.append(check(way, 'tiger:name_base_3', 'name_3'))
cmds = filter(None, cmds)
seq = SequenceCommand('Remove redundant name_bases', cmds)
seq.executeCommand()