usaush: United States Historic US Routes

[si404]

Amarillo has started using proper signs

Someone has made a (not up-to-date) map of where the green/white (and occasional 'OLD US66' brown) signs are. It's a little bit of a hot mess - which is why I've not made a file for it.

[oscar]

Some notes on New Mexico's historic US 66, after reviewing the insets on the state highway map I picked up last month. These are FWIW, and I'm not sure any edits to the HB are in order.

-- The Santa Fe inset indicates that southeast of the city, historic US 66 follows at least part of the Old Las Vegas Trail (frontage road along the SB side of I-25, recently added to the HB as NM 300), rather than I-25 as the HB has it.

-- The Albuquerque inset indicates that historic US 66 follows NM 313 south of Bernalillo (where the HB has the historic route ending) into Albuquerque, then following a decommissioned part of NM 47 (still shown in OSM) into downtown Albuquerque. Then that or another historic US 66 route (this in addition to the east-west route along Central Ave.) continues on the other side of downtown, along Isleta Blvd. south to at least I-25 exit 213. The inset doesn't provide enough detail in downtown Albuquerque to indicate how the historic route segments north and south of downtown connect with each other or to the Central Ave. route, if at all.

If it helps, I can scan, and e-mail or post, the Santa Fe and Albuquerque insets.

I don't know if these mean anything:

-- NM's state highway map is undated, so all I know from the current governor's smiling face on the map is that the map was printed after she took office in 2011. But the map doesn't reflect truncation of NM 47 in Albuquerque ca. 2015, so it might not be real current.

-- Also, I don't know if the state maps' routings are consistent with signage in the field, or other info on where the routes actually went. I haven't looked at GMSV, which someone might've done already. When I passed through the Santa Fe area on my latest trip, I don't recall seeing any historic US 66 signage on NM 300 either confirming or disconfirming that the historic route followed NM 300 rather than I-25. On a previous trip, I drove NM 47 north of I-25 (including the former routing through downtown Albuquerque), and don't recall seeing any historic US 66 markers except for the Central Ave. route.

[mapcat]

Historic US 10 is signed at several exits along I-90 in Washington. I saw signs for it at Exits 196, 215, and 220 as well as at the intersection of Danekas and Schoessler Rds northeast of Ritzville (heading to the NE on Danekas). The signs must be more recent than 2015, since neither GMSV nor Bing Streetview show them anywhere.

[mapcat]

In Illinois, US66HisCar, US66HisLit, US66HisLiv, and US66HisMou all have endpoints named US66His_S and US66His_N. Shouldn't these be US66His_W/US66His_E?

Also, the city names for two have typos:

Carlingville -> Carlinville
Livingstone -> Livingston

[froggie]

^ Depends on if you follow Tim's old insistence on "uniformity" with US route directions on the old CHM or how local states sign their routes.  IIRC, US 66 was signed north-south in Illinois, much like how US 52 is in that state (and others).

[si404]

Looking, there isn't directional signage on US66His in IL. I went with N-S mostly unthinkingly as I default to non-gridded systems and thus reflect geography rather than odd/even. Changing these, leaving alt labels, is very simple but I'll await confirmation/consensus that it ought to be changed.

I've fixed the US66 typos.

Historic US10 I've done, however I've not changed I-90BL (where the point at Danekas/Schoessler was way off, so I fixed it on US10HisRit) or WA21 (where there's an intersection). I found this article where $50k was secured to sign US10His in Eastern WA. Given it's apparently signed county boundary to county boundary in Adams County, but obviously won't have end signs, I've extended it to the next intersection either way.

[mapcat]

US66HisWil and US66HisLin have the _W/_E endpoints, so I was pointing out that the set weren't uniform. It would be difficult to change US66HisWil to _S/_N, however, given its shape.

[cl94]

An issue I noticed with 66 in Barstow, California: the concurrency with BL 15 in Barstow is not being marked automatically. This should be a simple fix by syncing the coordinates.

[Duke87]

There is no signage in the field for MA US20HisSud. Can confirm personally as of yesterday. So that one needs to be deleted too.

This means the Huntingdon segment is the only one in MA that currently has any signage at all.

[yakra]

ca.us040hisaub has two LABEL_INVALID_CHAR datacheck entries.

[yakra]

Is IA US6HisCou actually signed as such?

[si404]

Not as well as it's signed as the Lincoln Highway (but very few roads are signed with the density of reassurance shields that the Lincoln Hwy has over this stretch!*), but there's this sign eastbound and this one westbound.

*Something like 6 eastbound and 4 westbound. The route's only a mile long, doesn't turn, doesn't meet any major roads...

[Highway63]

Is IA US6HisCou actually signed as such?

Eh, yes and no. It's a project from a US 6 enthusiast who, when he started it, probably didn't have any idea that it would become OLD old US 6 while Broadway became Old 6.

Taking another look at the historic routes is on the to-do list.

[mapcat]

It's a project from a US 6 enthusiast

Should usaush really include something like that?

[si404]

Should usaush really include something like that?

How can drivers in the field differentiate by this, signed properly by a hobbyist, and similarly signed by the state, or a larger private sector group?

Unlike the temporary signage work by the US20 guy, this is signed permanently to a decent standard. So absolutely this deserves inclusion!