Travel Mapping

Highway Data Discussion => In-progress Highway Systems & Work => Topic started by: si404 on February 16, 2016, 10:53:38 am

Title: usaush: United States Historic US Routes
Post by: si404 on February 16, 2016, 10:53:38 am
Scope: routes signed with Historic USxx signs

Routes already mapped: see http://tm.teresco.org/devel/hb.php?sys=usaush&rg=

Issues: long banner text with dates are hard to implement, as is the historic bit

Requests: other signed routes - where are they?

Comments: over to you
Title: Re: usaush (United States Historic US Routes)
Post by: the_spui_ninja on February 16, 2016, 11:53:55 pm
Well here's something: http://www.historicus20.com/historic-route-signage.html (http://www.historicus20.com/historic-route-signage.html)
As far as I can tell from the pics there is an extant US20His in Marlborough and Becket, MA (although I have no idea of the routings).
There are also some links at the bottom that may or may not be useful.

I'm not sure whether this info is relevant or not, but I put it here for what it's worth.
Title: Re: usaush (United States Historic US Routes)
Post by: Bickendan on February 17, 2016, 04:30:37 pm
Hist US 30 The Dalles should be removed: Its entire length is still US 30.
The segment that should be included is from Troutdale to I-84 exit 35 near Warrendale. In fact, I'll send this to Jim now.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on February 17, 2016, 05:41:42 pm
Hist US 30 The Dalles should be removed: Its entire length is still US 30.
The segment that should be included is from Troutdale to I-84 exit 35 near Warrendale. In fact, I'll send this to Jim now.
Thanks for correcting my misinterpretation the description given in discussions of US30 in OR.

Collaborators - please feel free to make alterations to routes in your regions like Bickendan has done.
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on February 18, 2016, 02:06:15 am
Quote
Issues: long banner text with dates are hard to implement, as is the historic bit
As usaush.csv is currently formatted, NM HistoricUS66PRE-1937SFe is what would have to go into a .list file to mark a segment as clinched. That's a mouthful. Clunky.
My preference: usaush;NM;US66;His;SFe;Santa Fe;nm.us066hissfe;
That example doesn't include the date information. Leaving it out doesn't seem to create any collisions between same-numbered same-city routes, from my quick look at the CSV. I have no problem including it, as long as it's in the city field, e.g. usaush;NM;US66;His;SFe;(PRE-1937) Santa Fe;nm.us066hissfe; or such.

Quote
Collaborators - please feel free to make alterations to routes in your regions like Bickendan has done.
I remember there was one route in TX that needed some fixes. Don't remember which one though...
Edit: I guess not. Maybe I was thrown off by tx.i040bsgle having the points in reverse order from tx.us066hisgle, or something.

Routes in my regions, a checklist:
tx.us066hisgle / tx.us066hisgle;I-40(0);;;EXIT0;
tx.us066hisadr
tx.us066hisveg
tx.us066hiscon
tx.us066hisgro
tx.us066hisala
tx.us066hismcl
tx.us066hissha
ks.us066hisgal / ks.us066hisgal;KS26/66;;;LABEL_SELFREF;

[Si's post with shield images] (http://tm.teresco.org/forum/index.php?topic=43.msg398#msg398)
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on February 21, 2016, 02:11:11 pm
Well here's something: http://www.historicus20.com/historic-route-signage.html (http://www.historicus20.com/historic-route-signage.html)
As far as I can tell from the pics there is an extant US20His in Marlborough and Becket, MA (although I have no idea of the routings).
and Weston, MA, New Lebanon, NY, North East, PA, Sandhills, NE...

Sadly the Ostriches haven't roamed those parts for a long time, so route discernment is difficult (the Becket, MA is a tiny former alignment segment where the turnpike diverted it - called Morse Rd).

I've also found a US6His in Provincetown, MA, with a same lack of decent and recent GMSV


I've also fixed the .csv
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on February 21, 2016, 04:59:31 pm
You've made it known that you don't believe that a route being coextensive with an existing route should preclude it from being included in any set it's qualified to be in, and I don't disagree with you in principle. But in the case of Historic US 20 (Painesville, OH) (http://tm.teresco.org/devel/hb.php?r=oh.us020hispai), the entire route is also the current routing for US 20. To me this seems unnecessary. At least a small part of Historic US 20 (Norwalk, OH) (http://tm.teresco.org/devel/hb.php?r=oh.us020hisnor) deviates from the unbannered route.
Title: Re: usaush (United States Historic US Routes)
Post by: vdeane on February 28, 2016, 12:42:06 am
Well here's something: http://www.historicus20.com/historic-route-signage.html (http://www.historicus20.com/historic-route-signage.html)
As far as I can tell from the pics there is an extant US20His in Marlborough and Becket, MA (although I have no idea of the routings).
and Weston, MA, New Lebanon, NY, North East, PA, Sandhills, NE...

Sadly the Ostriches haven't roamed those parts for a long time, so route discernment is difficult (the Becket, MA is a tiny former alignment segment where the turnpike diverted it - called Morse Rd).

I've also found a US6His in Provincetown, MA, with a same lack of decent and recent GMSV


I've also fixed the .csv
A small portion of the New Lebanon one appears to follow a local street.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on February 28, 2016, 04:11:03 am
the entire route is also the current routing for US 20. To me this seems unnecessary.
Tell that to the people who erected signs! There's loads of US20His concurrent with US20. And US6His in Provincetown doesn't even have the excuse of the road still being on the original alignment when it does it!
Title: Re: usaush (United States Historic US Routes)
Post by: Quidditch33 on June 09, 2016, 11:32:59 pm
Just out of curiosity, what color will these routes be on the map?

Thanks,
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on June 10, 2016, 08:03:42 am
colors are changeable, but the default will be brown.

Are there any routes I've missed?

What needs to happen to get this system to preview?
Title: Re: usaush (United States Historic US Routes)
Post by: Jim on June 10, 2016, 10:38:30 am
colors are changeable, but the default will be brown.

Are there any routes I've missed?

What needs to happen to get this system to preview?

I guess I don't know how we know when this is substantially complete.  I doubt there's an authoritative list out there somewhere we can refer to.  I admit I've been blindly running site updates that include new usaush routes without paying much attention to what's in them (or not).
Title: Re: usaush (United States Historic US Routes)
Post by: Quidditch33 on June 10, 2016, 01:24:39 pm
colors are changeable, but the default will be brown.
Thank you.
Title: Re: usaush (United States Historic US Routes)
Post by: sipes23 on June 10, 2016, 05:18:15 pm
I guess I don't know how we know when this is substantially complete.  I doubt there's an authoritative list out there somewhere we can refer to.  I admit I've been blindly running site updates that include new usaush routes without paying much attention to what's in them (or not).

I know it's not an ideal solution, but could we call our selection authoritative and add to it as more new historic routes are "found"? I know it would count as original research in the Wikipedia sense, but do we have a problem with the US Historic roads being a little beta all the time?
Title: Re: usaush (United States Historic US Routes)
Post by: Highway63 on June 26, 2016, 08:18:52 pm
Who's putting these together? Apologies if I missed an announcement, but I see IL and MO US 66 files have been created. I don't have any problem with it (I certainly wouldn't have had time to do it), but if a signed route changes that could affect things.

On the portions where the historic route overlaps an active route, are waypoints being taken from existing files? If so, should concurrencies automatically show up yet? Or can that not happen until the system is activated? I'm marked as having 0% of 66 in IL/MO, and I have a bunch of interstate/business loop portions that would count.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on June 27, 2016, 12:12:52 pm
Who's putting these together?
I did about a year ago (well for '66 it was - US20 was more recently).
Quote
On the portions where the historic route overlaps an active route, are waypoints being taken from existing files?
Yes, though there's places where I've had to tweak things (eg add extra points if there wasn't a point where the usush route left a state route), which I didn't do with the state highways. IIRC, there's maybe 20 such points in IL/MO and perhaps 30 in total - it's hard to know exactly at the moment as the easiest ways to find out (broken concurrencies, etc) won't happen unless the system is preview/active.
Quote
If so, should concurrencies automatically show up yet? Or can that not happen until the system is activated?
Not until it's preview, so a 0% score is correct.
I guess I don't know how we know when this is substantially complete.
True, but I'm pretty sure I've got most of them, and we can always add more as people spot them or they get signed (more so the latter, as I look at various groups' sites and they tend to have pictures for every new section signed) - a quick check suggests I'm missing US20 in Termopolis, WY (which shouldn't take long to add)
Quote
I doubt there's an authoritative list out there somewhere we can refer to.
Sure, but the same is the case for various other systems - eg truck routes, several European systems, etc.
I know it's not an ideal solution, but could we call our selection authoritative and add to it as more new historic routes are "found"? I know it would count as original research in the Wikipedia sense, but do we have a problem with the US Historic roads being a little beta all the time?
I don't have a problem with this, though I skew fairly strongly towards P on Myers-Briggs (among other factors that mean similar things), and so a system that might not be fully complete, making a couple of statistics not very authoritative (eg percentage of system clinched) doesn't bother me anyway near as much as I'm sure it would bother other people.
Title: Re: usaush (United States Historic US Routes)
Post by: vdeane on June 30, 2016, 06:07:38 pm
I'm not sure what else could be done for Historic US Routes, unless there's a log somewhere we don't know about.
Title: Re: usaush (United States Historic US Routes)
Post by: Highway63 on July 06, 2016, 12:10:39 am
The IA Historic US 20 that right now is confined to Dubuque County can be stretched nearly across the state to Early. Use Olde Castle Road, present 20 to the next intersection into Dyersville, and then the rest of the pre-freeway route should be easy to follow. (Or look at the Iowa DOT map archive.) I'd stick with the ca. 1960s route; the 1926-58 route from Cedar Falls to Jesup has at least two breaks in it, and the 1986-2000/2003 segment via D19 and IA 14 doesn't hold much significance IMO.

IA Historic US 6 can get an Altoona-Newton segment too (F48).

I can make the files if you want.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on July 06, 2016, 05:48:03 am
The IA Historic US 20 that right now is confined to Dubuque County can be stretched nearly across the state to Early. Use Olde Castle Road, present 20 to the next intersection into Dyersville, and then the rest of the pre-freeway route should be easy to follow.
Is it signed?
Quote
(Or look at the Iowa DOT map archive.) I'd stick with the ca. 1960s route; the 1926-58 route from Cedar Falls to Jesup has at least two breaks in it, and the 1986-2000/2003 segment via D19 and IA 14 doesn't hold much significance IMO.
Surely we have what is signed, not a specific year?
Quote
IA Historic US 6 can get an Altoona-Newton segment too (F48).
Again, is it signed? A single sign would be enough to please me.

I gather there are (given the cost given, 2 or 3?) signs in Atlantic http://usroute6iowa.org/node/22, so the Redfield can presumably be extended along US6 (and renamed for the larger city?) a few miles.
Quote
I can make the files if you want.
Thanks.
Title: Re: usaush (United States Historic US Routes)
Post by: Highway63 on July 06, 2016, 02:25:02 pm
Oh, I completely misread your intent then. If the old routes have to be SIGNED, then the only highway in Iowa that qualifies is US 6. I thought you were looking for significant segments of bypassed road that one could follow independently, since old 20 in Dubuque County isn't signed, nor is 6 on Broadway in Council Bluffs (unless that's changed since I was last there).

I believe, but am not 100% sure, that Historic 6 has been signed all or mostly all across the state, even where it overlaps with existing 6 - there's a Historic 6 shield with 6 at the IA 48 intersection west of Atlantic. (But it could be only Cass County.) That's only happened in the last couple of years so Google Street View hasn't caught up. Polk County would be a potentially large exception because 6 is partially apart from 80, and the question becomes which route to sign, existing 6 or the really old route that went into downtown Des Moines.

I know old 6 is signed from 63/6 to Ladora (F29).

In Iowa and Illinois the route of the Lincoln Highway is signed, but not (in Iowa's case) Historic US 30.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on July 06, 2016, 08:10:28 pm
Oh, I completely misread your intent then. If the old routes have to be SIGNED, then the only highway in Iowa that qualifies is US 6. I thought you were looking for significant segments of bypassed road that one could follow independently, since old 20 in Dubuque County isn't signed,
https://www.facebook.com/HistoricUSRoute20IA (https://www.facebook.com/HistoricUSRoute20IA) has a clear picture of a Historic US20 sign on Y21.
Quote
nor is 6 on Broadway in Council Bluffs (unless that's changed since I was last there).
GMSV June 15 (https://www.google.co.uk/maps/@41.261162,-95.8480389,3a,37.8y,89.72h,91.34t/data=!3m6!1e1!3m4!1s2cc2bdvQEXDJTrVJ-mLt-A!2e0!7i13312!8i6656!6m1!1e1).

End points might not be exact, and routes aren't fully up-to-date, but I've found signs for all routes in the browser.
Quote
I know old 6 is signed from 63/6 to Ladora (F29).
Along current US6?
Title: Re: usaush (United States Historic US Routes)
Post by: Bickendan on July 07, 2016, 07:07:20 pm
Apparently I-5 runs on old US 99 in Wolf Creek, Oregon... https://goo.gl/maps/iFGe1X5BBqv
No sign of Hist US 99 shields, though -- I might have to swing down south to investigate.
Title: Re: usaush (United States Historic US Routes)
Post by: Highway63 on July 08, 2016, 01:59:15 pm
https://www.facebook.com/HistoricUSRoute20IA (https://www.facebook.com/HistoricUSRoute20IA) has a clear picture of a Historic US20 sign on Y21.
That's a temporary sign Mr. Farr put up while he was traveling to promote his site. I e-mailed him about it. If you look closely, "Iowa" is taped onto it. There is no comprehensive signage of Historic 20 in Dubuque County, although Farr is trying to get some.

Quote
nor is 6 on Broadway in Council Bluffs (unless that's changed since I was last there).
GMSV June 15 (https://www.google.co.uk/maps/@41.261162,-95.8480389,3a,37.8y,89.72h,91.34t/data=!3m6!1e1!3m4!1s2cc2bdvQEXDJTrVJ-mLt-A!2e0!7i13312!8i6656!6m1!1e1).[/quote]
That's new, then.

Quote
End points might not be exact, and routes aren't fully up-to-date, but I've found signs for all routes in the browser.
Quote
I know old 6 is signed from 63/6 to Ladora (F29).
Along current US6?
If you mean, are there signs pointing to old 6 from current 6 (https://www.google.com/maps/@41.7457658,-92.5916293,3a,75y,135.05h,82.16t/data=!3m6!1e1!3m4!1sDsuoP65iyXS2ZkKZ6e05yQ!2e0!7i13312!8i6656), yes.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on July 09, 2016, 03:10:53 pm
https://www.facebook.com/HistoricUSRoute20IA (https://www.facebook.com/HistoricUSRoute20IA) has a clear picture of a Historic US20 sign on Y21.
That's a temporary sign Mr. Farr put up while he was traveling to promote his site. I e-mailed him about it. If you look closely, "Iowa" is taped onto it. There is no comprehensive signage of Historic 20 in Dubuque County, although Farr is trying to get some.
Oh yes, I hadn't realised that taping. IA is your state, if I recall correctly in my current state (just finished crewing a beer festival, and drinking too much of the leftovers), therefore feel free to delete/extend/change files in IA, etc as you see fit.
Title: Re: usaush (United States Historic US Routes)
Post by: oscar on August 14, 2017, 11:37:34 pm
There are very well-signed segments of Historic US 40 in Dixon CA and Sacramento CA, not included in the California HistUS40 segments already in the HB, I don't know the full extent of those segments, or even if they are separate, but IIRC they are on West A Street, N Adams Street, and CA 113 in Dixon, and on 16th Street in downtown Sacramento. That Sacramento segment is currently covered by the HB as part of CA 160, but not for long (at least south of the American River) as explained in the usaca thread.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on August 15, 2017, 10:22:18 am
The Dixon bit goes down Porter Road, but I can't see any signs on Midway Road. I had a dummy file for Sacramento, but had forgot about it. With the recent GMSV update I've been able to work out the extent of signage to add it.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on August 18, 2017, 11:17:03 am
I've synced up points so that these routes intersect properly with other routes. I've not fixed NMPs.

This means that various I-, US and state route files have been changed slightly. I've pinged the relevant people via Github (apart from Jeff M, who isn't on there). Please check you are OK with the changes I'm proposing.

Jeff M: IA (https://github.com/si404/HighwayData/commit/4679d10a2b29b43ed95622450d2f9bcd9da37309), IL (https://github.com/si404/HighwayData/commit/9706093c15fb8b9fc5cdf0d1bdd4780389a85d2a), MO (https://github.com/si404/HighwayData/commit/1e22633a250bcbdc341172a14a825f82b8099bbd)
Mapcat: OH (https://github.com/si404/HighwayData/commit/f264793200b099b4e6b4f4323b158cd05b9dae5b)
Oscar: CA (https://github.com/si404/HighwayData/commit/6e85d3aa0add063889de6e7f160478a444bfcebc), NM (https://github.com/si404/HighwayData/commit/7303abf53f4a2c202d7a5eeb7dbd10cae8b9c937)
Rickmansfast67 / theFXexpert: GA (https://github.com/si404/HighwayData/commit/dea543717278e5acb682b633fc428c53a118a9d1)
Yakra: MA (https://github.com/si404/HighwayData/commit/546d5e49d690191bf81be92f6a50fd17c20a7ef5), NE (https://github.com/si404/HighwayData/commit/05d8a1d846b8d5a121a55b3673aa2cf638da57ff), NY (https://github.com/si404/HighwayData/commit/b77de57ef03a21b4078e373be14f68e9dd8a2a92), OK (https://github.com/si404/HighwayData/commit/2b221c629851c12ddb661c07125b0c7ffba50d95)
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on August 18, 2017, 03:11:02 pm
Please check you are OK with the changes I'm proposing.
Yakra: MA (https://github.com/si404/HighwayData/commit/546d5e49d690191bf81be92f6a50fd17c20a7ef5), NE (https://github.com/si404/HighwayData/commit/05d8a1d846b8d5a121a55b3673aa2cf638da57ff), NY (https://github.com/si404/HighwayData/commit/b77de57ef03a21b4078e373be14f68e9dd8a2a92), OK (https://github.com/si404/HighwayData/commit/2b221c629851c12ddb661c07125b0c7ffba50d95)
I'm not sure how wild I am about US20His style labels in general, but I'll let that matter go for the time being...

OK:
The US66HisWea changes effectively revert a change (https://github.com/TravelMapping/HighwayData/commit/a262c7154cc919bd7f55173d66734159ecdc47b5) I made a while back. I removed the point on I-40, as there was no junction there; the point wasn't on the US66His roadway. US66His uses just the northern frontage road here, but northbound OK58Med uses the northern frontage road, and southbound OK58Med uses the southern one. Thus I-40 & OK58Med intersect at (35.536352°, -98.575079°), but I decided a different solution was in order for US66His. I went with one OK58 point (where OK58Med crosses SB, and leaves the concurrency NB), and then added the other point at N2480 for those travelers who'd passed through the area on northbound OK58Med, and would want to mark off the corresponding section of US66His as clinched.

US69: US66His -> US66His_Nar. Fine for US59, as it's the only US66His point on that route.

OK66: US66His_LkOW & US66His_LkOE -> US66His_Yuk & US66His_Okl

NE:
US20: might as well leave OldSmiSDr_E out. It's a minor one-way (https://www.google.com/maps/@42.6616924,-103.5691808,3a,16y,16.86h,89.65t/data=!3m6!1e1!3m4!1sOFc5LyUkbcvOKcOHCYjGvQ!2e0!7i13312!8i6656) park road, not needed for shaping. (I just recently added in SolCreRd per a request in for forum for a point in the state park; that should suffice.) As for the existing OldSmiSDr_W, that was just added in as a shaping point. Its name is not up to current labeling standards; it should probably be SmiCanDr instead.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on August 18, 2017, 06:29:50 pm
I'm not sure how wild I am about US20His style labels in general, but I'll let that matter go for the time being...
What would you prefer? Very happy to change where possible. oscar wanted road names, so I changed them to that.
Quote
NE:
US20: might as well leave OldSmiSDr_E out. It's a minor one-way (https://www.google.com/maps/@42.6616924,-103.5691808,3a,16y,16.86h,89.65t/data=!3m6!1e1!3m4!1sOFc5LyUkbcvOKcOHCYjGvQ!2e0!7i13312!8i6656) park road, not needed for shaping.
It was needed for the intersecting route, not shaping - somewhere some time ago, I saw fit to include the park road due to signage. However I can't find it now and I'm pulling the route back and dropping it.
Quote
As for the existing OldSmiSDr_W, that was just added in as a shaping point. Its name is not up to current labeling standards; it should probably be SmiCanDr instead.
relabelled, along with the other suggestions.
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on August 19, 2017, 02:01:19 am
What would you prefer? Very happy to change where possible. oscar wanted road names, so I changed them to that.
Not sure I follow. Road names, like ElmSt & MainSt? Or route names? I see US66His etc. in the CA & NM commits.

Quote
As for the existing OldSmiSDr_W, that was just added in as a shaping point. Its name is not up to current labeling standards; it should probably be SmiCanDr instead.
relabelled, along with the other suggestions.
I see (https://github.com/si404/HighwayData/blob/master/hwy_data/NE/usaus/ne.us020.wpt) OldSmiDr (https://github.com/si404/HighwayData/blob/abe48d1bd2591d4d975043bb310ef05cb39101fc/hwy_data/NE/usaus/ne.us020.wpt) right now. Mind changing it to SmiCanDr, since you'll be the next one to have a commie LOL commit merged in for that file?
Thanks for making all those fixes.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on August 19, 2017, 04:03:55 am
Not sure I follow. Road names, like ElmSt & MainSt?
Yes
Quote
I see US66His etc. in the CA & NM commits.
Which I've since changed to road names.
Quote
I see (https://github.com/si404/HighwayData/blob/master/hwy_data/NE/usaus/ne.us020.wpt) OldSmiDr (https://github.com/si404/HighwayData/blob/abe48d1bd2591d4d975043bb310ef05cb39101fc/hwy_data/NE/usaus/ne.us020.wpt) right now. Mind changing it to SmiCanDr, since you'll be the next one to have a commie LOL commit merged in for that file?
You're right, fixed now.
Title: Re: usaush (United States Historic US Routes)
Post by: Bickendan on August 19, 2017, 03:40:53 pm
Si, remember when I had you switch out the Rowena Crest section of Hist US 30 for the Columbia River Gorge section a while back?
Turns out both are signed in the field! US 30 prime is also signed (or just becomes US 30H) through Rowena Crest after leaving The Dalles.
I'll upload the Rowena Crest section with my update to US 97 and the OR 99s. Since both segments of US 30H are in the Columbia River Gorge, the first segment should be renamed --
Crown Point?
Columbia River Gorge Waterfalls?
Multnomah Falls?
Troutdale-Dodson?
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on August 20, 2017, 02:17:29 am
Not sure I follow. Road names, like ElmSt & MainSt?
Yes
Oh nice. I prefer that style too actually, and feel better about asking for it if Oscar already did so & you were happy to make the changes.
FWIW, I followed this same convention when developing cannss. EG, NS NS4 PepSt (http://www.openstreetmap.org/?lat=45.655972&lon=-60.875081), instead of BrasdOrDr_WhateverDirectionalOrCitySuffix...

I remember there was one other US66His label in KS. Other than that I'm not aware of anything else you changed in my regions before these recent commits.

Quote
I see US66His etc. in the CA & NM commits.
Which I've since changed to road names.
Which I could have seen had I thought to do for Oscar's commits what I did for mine, and replace the arcane hexadecimal commit number in the GitHub url with "master" ;P
I don't see myself stopping posting on the Internet at 2am anytime soon though. :-/

You're right, fixed now.
Thanks!
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on August 21, 2017, 08:17:29 pm
MA US20:
US20His_Hun -> OldStaHwy
US20His_MarW -> MainSt_MarW
US20His_MarE -> MainSt_MarW

NE US20:
SmiCanDr +OldSmiSDr_W -> SmiCanDr

OK US59:
140Rd -> E0140
delete +X05930

OK US69:
140thRd -> E0140
delete +X05930

The rest looks good
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on August 23, 2017, 03:24:30 am
I've gone with everyone having names on existing routes, rather than USxxHis labels (some are OldUSxx or varients of, as that is what the road is named).

change log here: https://github.com/TravelMapping/HighwayData/pull/1551/files (Jim's waiting on confirmation before pulling in)
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on August 23, 2017, 04:16:00 am
https://github.com/TravelMapping/HighwayData/pull/1551/files#diff-ebbc96f75e12035e486661c9ef81de01
That's one funky filename. o_O
Isn't the Lincoln Highway outside the scope of the usaush system?

That said though, I approve of the changes in MA, NE, NY and OK.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on August 23, 2017, 04:03:57 pm
https://github.com/TravelMapping/HighwayData/pull/1551/files#diff-ebbc96f75e12035e486661c9ef81de01
That's one funky filename. o_O
It's obvious what it is though. I didn't want to add 20-something points to the actual US30 file, but didn't want to play hunt-and-name them should we include the Lincoln Highway to the project.
Quote
Isn't the Lincoln Highway outside the scope of the usaush system?
It's not in the .csvs, but I've drafted IL and IN should we decide to add this route which is in the sphere of this system, but not currently its scope, to the project (either in this, or another, system).
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on September 10, 2017, 02:08:02 pm
Can you post a link to where you found the endpoints for the US20His routes in Ohio? I'm wondering how you decided to limit them to those three particular segments.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on September 11, 2017, 09:20:21 am
the end points are rather random. I basically took the existing US20 points after a sign, or where I guessed a sign might be.

However, more have been added (this recent document (http://historicus20.com/iowa.html) about getting the route really well done in IA has Bellevue, Monroeville, Norwalk, Wakeman, Elyria, Willoughby, Mentor, Painesville and North Perry have signs, so I need to extend the Painesville section at some point) or I just gave up trying to find. It doesn't help that GMSV is either too old, or that the signs are very hard to find. I haven't found too many - this one in Monroeville (https://www.google.com/maps/@41.2361633,-82.689598,3a,22.5y,281.82h,88.76t/data=!3m6!1e1!3m4!1suPXLH2lc9ClWbF2L2nleWw!2e0!7i13312!8i6656), this one in Willoughby (https://www.google.com/maps/@41.621917,-81.4495758,3a,75y,91.44h,69.7t/data=!3m6!1e1!3m4!1sPDhd_dPhTUS8awgDLUDWJg!2e0!7i13312!8i6656), this one in North Perry (https://www.google.co.uk/maps/@41.7700949,-81.1737358,3a,35.3y,65.1h,81.22t/data=!3m6!1e1!3m4!1s3IpowU-jCYj1SjPUMlyB_Q!2e0!7i13312!8i6656), and this one in Painesville (https://www.google.com/maps/@41.7128917,-81.260045,3a,40.8y,289.2h,86.67t/data=!3m6!1e1!3m4!1sL7XhWYgsak3jirTkC0VfWA!2e0!7i13312!8i6656). Otherwise it is photos - eg Norwalk (http://www.norwalkreflector.com/gallery/Norwalk-unveils-special-signs-for-Route-20).
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on September 14, 2017, 08:36:02 pm
the end points are rather random. I basically took the existing US20 points after a sign, or where I guessed a sign might be.

Then how is this any different from looking at an old map, seeing where US20 used to be routed, and calling that US20HisFoo?

I finally had a chance to GMSV US20HisEly from end to end and didn't see a single sign. Imagery was from 2013-2016.

The Monroeville sign in your link was the only one I found on US20HisNor (the imagery for the intersection shown in the article predates the unveiling).

I'm just looking for some justification for these two (US20HisPai seems safe), or a reason not to add the former alignment in Fremont (which is actually signed, albeit in a nonstandard manner (https://www.google.com/maps/@41.3464278,-83.1068985,3a,40.1y,242.53h,91.64t/data=!3m6!1e1!3m4!1sQTAu6X2gyDZFdcFbofXkaw!2e0!7i13312!8i6656)).
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on September 15, 2017, 02:40:52 pm
Then how is this any different from looking at an old map, seeing where US20 used to be routed, and calling that US20HisFoo?
Because it's signed as Historic US20 rather than merely the old route of it?

That said, I can't find any signs, despite GMSV being mostly recent enough to fit the June 2016 date for the supposed signage in the town.
Quote
I'm just looking for some justification for these two
Why isn't Norwalk safe? - as you say, GMSV is pre-unveiling of signage. The end points might need tweaking (the west end seems to be OH113, with nothing further west in Bellevue), but it's clearly signed in several places. Here's a third (https://www.google.com/maps/@41.2686721,-82.8160253,3a,27.1y,355.77h,85.36t/data=!3m6!1e1!3m4!1sQ-CM0qqHnOH0ysahPXu6iw!2e0!7i13312!8i6656). Wakeman's GMSV is too early.
Quote
a reason not to add the former alignment in Fremont (which is actually signed, albeit in a nonstandard manner (https://www.google.com/maps/@41.3464278,-83.1068985,3a,40.1y,242.53h,91.64t/data=!3m6!1e1!3m4!1sQTAu6X2gyDZFdcFbofXkaw!2e0!7i13312!8i6656)).
I didn't realise 'City Route 20' signs are valid for inclusion as Historic US20.  :o

And especially silly when you are saying that Historic US20 signs aren't enough for the Norwalk section!
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on September 15, 2017, 11:31:36 pm
Because it's signed as Historic US20 rather than merely the old route of it?

*Some* of the route is signed, but a large part of your file seems to be guesswork. Ohio's historic US routes don't seem to be in the same class as the well-signed examples in California or Illinois. Granted, it would be pointless to have a 2-block route for the small segment signed in Monroeville and another tiny segment near another sign in Norwalk, but keeping all of US20HisNor in a single file demands a lot more guesswork than a route should require. The endpoints are ambiguous. The phantom Elyria segment is more than ambiguous.

Would it be better to unite all of these segments into a single one, since the organization (possibly just one extremely dedicated and/or obsessive gentleman) posting the signs evidently intends to use them to promote the entire route of US20?

Quote
I didn't realise 'City Route 20' signs are valid for inclusion as Historic US20.  :o

And especially silly when you are saying that Historic US20 signs aren't enough for the Norwalk section!

I didn't say I wished to include that segment, only that it was more clearly signed (as *something*) than the Norwalk section.

I'd prefer to hold off on all of the Ohio routes until signage becomes more consistent across the state. Is any other state as careless with its Historic Route signage?
Title: Re: usaush (United States Historic US Routes)
Post by: bejacob on September 18, 2017, 10:22:17 pm
I'm somewhat puzzled by this set of routes. I've seen a fair number of "Historic US Route" X in my travels and have even driven some, so I like the idea of being able to add a few more to my list.

What I don't know are the criteria for including a Historic route? I assume it must be signed. What else? Must the route be decommissioned or have a segment relocated?

I can see why it might be necessary when a route is signed as "Historic" though a town when a bypass was created and the old route was not designated a "Business" route or replaced by a state route of the same number (WA 99 in Federal Way for instance). The idea of a Historic route having a concurrency with the same numbered route that still exists seems like an oxymoron (how can it be a historic route if it is still a current route? I can understand for the segments that deviate from the current route).

One route I know is signed but not included is Historic US395 in Riverside, CA. Are there others?

I like the idea of adding Historic routes, but there seems to be a lot of confusion about appropriate waypoints, signage, concurrencies, and which routes to include. At least with most other systems, there usually some sort of official list maintained by the state DOT.

Now that this system is in "preview," I'll probably add several routes to my list. I'm still not sure I completely understand what's being included or left out of this system, but I'll go along with whatever is in the HB.
Title: Re: usaush (United States Historic US Routes)
Post by: oscar on September 19, 2017, 11:51:06 am
I've seen Historic US 99E signs in Chico CA, and US 99W signs somewhere along I-5BL Orland (a poorly-signed BL that was really borderline for staying in the HB). I have a photo of one of the latter. The Chico 99E segment followed in part the decommissioned CA99 Business route through Chico, but continued south on Midway where the business route turned east on Park Ave.

Is there a more systematic way of identifying CA's generally well-signed historic US routes, other than randomly through reports on this forum?
Title: Re: usaush (United States Historic US Routes)
Post by: bejacob on September 20, 2017, 08:50:47 am
the entire route is also the current routing for US 20. To me this seems unnecessary.
Tell that to the people who erected signs! There's loads of US20His concurrent with US20. And US6His in Provincetown doesn't even have the excuse of the road still being on the original alignment when it does it!

I know I am quoting an old comment, but it helps explain my confusion with this system.

Just because some group erected "Historic Route" signs, what makes a route worth including?
Is the some sort of "official designation" by state DOTs for historic routes?
If not, who determined which routes are included?
How will we know if the route list is complete? Is there some "master" list?
Will early US "auto routes" like the Lincoln Highway https://en.wikipedia.org/wiki/Lincoln_Highway (https://en.wikipedia.org/wiki/Lincoln_Highway) (which covered parts of US30, US50, and others) be included especially in places where is deviates from the existing alignment? (I know a great deal of signage exists in the Midwest on parts of this route).
What about routes that had different alignments over time?
Once usaush is done, will there be a push to do the same at a state level? (Are there even any signed historic state routes?)

I like the idea of adding historic routes, I just wonder whether enough consideration was given to the above questions. The system is already in "preview," so there is probably little chance of going back now. A little clarification might however be useful moving forward.

I'm all in favor of adding new systems. I was glad to see usanp and several state systems (CA, FL, GA) added to "preview" recently. I've still got some big gaps in places like AL, LA, and MS where state systems have not yet been developed.

This system just feels a bit slapdash especially if TM contributors are relying on "reports from the field" to make sure the route list is complete. Don't get me wrong. I appreciate the effort and will be glad to add any new routes to my list file. I'm just looking for a bit of clarity on this route system. It's still somewhat confusing as to the criteria for a route to be included.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on September 20, 2017, 10:16:29 am
What I don't know are the criteria for including a Historic route? I assume it must be signed. What else? Must the route be decommissioned or have a segment relocated?
Just signed. The other stuff adds a layer of complexity as to whether a route is included or not that a driver won't easily know about. Ideally, one would only see signs on decomissioned/bypassed sections, but alas that isn't the case.

Quote
The idea of a Historic route having a concurrency with the same numbered route that still exists seems like an oxymoron (how can it be a historic route if it is still a current route? I can understand for the segments that deviate from the current route).
I agree, but it seems that some people want to sign existing routes as historic routes and so have done so. My favourite example for this nonsense is the US6 Historic Route in Provincetown, MA - where it's clearly a bypass (MA6A going through the town) and is current US6.

Quote
One route I know is signed but not included is Historic US395 in Riverside, CA.
Added, though it seems to peter out at the north end.

Quote
At least with most other systems, there usually some sort of official list maintained by the state DOT.
The issue is that these routes are created or maintained by the state. In some cases they are, in others it's cities and counties (and, obviously, some are just businesses or campaigns).



US 99W signs somewhere along I-5BL(Orland -- a poorly-signed BL that was really borderline for staying in the HB).
I only found one sign on GMSV, in Willows, but added. There's also two in Williams, which is annoying as same first three-letters, so I'm going with Willows and Williams for the abbreviations
Quote
The Chico 99E segment followed in part the decommissioned CA99 Business route through Chico, but continued south on Midway where the business route turned east on Park Ave.
The late 2016 GMSV shows CA99 signs northbound on Main, but not His-99E signs either way on the old Bus-99 route, and I can't see it on Midway - this is a recent route, added in the last 10 months. I need more info to add it, though you can add it.
Quote
Is there a more systematic way of identifying CA's generally well-signed historic US routes, other than randomly through reports on this forum?
it seems to mostly be cities/counties signing these routes, so there's nothing really unified.



Just because some group erected "Historic Route" signs, what makes a route worth including?
How can a driver tell whether it's a state, county, city, lobby group/non-profit, or business that erected a sign? No one seems to have a problem if a state DOT is the one putting up signs (especially if has its beaurocracy Vogonishly catalogue the routes), what's the problem with signs put up by other entities if drivers can't tell the difference?

Quote
Is the some sort of "official designation" by state DOTs for historic routes?
I don't believe so. IA seems to be heading down that path, though - hence the US20 presentation to get the route designated, with Iowa DOT getting cities and counties signing the route.

Quote
If not, who determined which routes are included?
the contributors - I've gone with if it's signed, it's included.

Quote
How will we know if the route list is complete? Is there some "master" list?
We won't - to some extent. But think of it more of a grab-bag, rather than a coherent and complete system, and why does it matter? The point is to map these routes (and also doing the job of documenting them), where we've discovered them, and to map our travels on them.

For gbna, SABRE, is the master list that the DfT directs people too, and most of the changes I've made in the last year or two, I've also made on the 'official' list of SABRE, therefore the master list is basically TM contributor findings (from posts on road geek forums, signage on streetview/photos, etc) - ie the same as this system.

For a lot of European systems, I've found no official list for and used wikipedia or wegenwiki, along with mapping data, to make the routes.
Quote
Will early US "auto routes" like the Lincoln Highway https://en.wikipedia.org/wiki/Lincoln_Highway (https://en.wikipedia.org/wiki/Lincoln_Highway) (which covered parts of US30, US50, and others) be included especially in places where is deviates from the existing alignment? (I know a great deal of signage exists in the Midwest on parts of this route).
While I personally have no objections to signed Lincoln Highway segments being included in this system, the feedbank I've recieved so far that it doesn't belong in this system.

Quote
What about routes that had different alignments over time?
If there signed. cf US66's different routings.

Quote
I just wonder whether enough consideration was given to the above questions. The system is already in "preview," so there is probably little chance of going back now.
I've certainly considered all those questions. The move to preview has a lot to do with making the routes more accessible and getting other people to engage and consider questions like these - the system was devel status for two years and there was mostly silence on this.
Title: Re: usaush (United States Historic US Routes)
Post by: bejacob on September 20, 2017, 12:54:36 pm
I appreciate the thoughtful comments.

I'm still slightly concerned about "just signed" as the sole criteria.

I discovered a few years back that a US62Bus sign placed on the Ohio side of the Ohio River was a mistake http://www.aaroads.com/forum/index.php?PHPSESSID=6277c09d12eb9d5b31cc221a9c0be320&topic=15733.msg2121667#msg2121667 (http://www.aaroads.com/forum/index.php?PHPSESSID=6277c09d12eb9d5b31cc221a9c0be320&topic=15733.msg2121667#msg2121667) and that a US62Bus did not actually exist in this area despite signage to the contrary. That may not be relevant if there is no "official" list of Historic route, but recalling this old discussion, I thought it worth mentioning.

Then there is situation in Paso Robles with US101. It's in the HB as US101BusPas, but signed in the field as "Historic US101" http://tm.teresco.org/forum/index.php?topic=1937.msg5340#msg5340 (http://tm.teresco.org/forum/index.php?topic=1937.msg5340#msg5340). Does that mean this route needs to be included in both the usausb and usaush systems?

The bottom line for me is this. It's your (the TM contributors) sandbox. I just play in it. The thoughts and opinions of those developing and maintaining these systems are what really count.
If these routes are in the HB and I've driven them, they go on my list. (I didn't get to 100,000 miles by leaving things out  ;)).
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on October 12, 2017, 12:58:41 am
Si, don't know if this will actually provide any new info for you, but nonetheless:
http://www.kwwl.com/story/36568671/2017/10/11/turning-an-old-highway-into-the-new-route-66
Title: Re: usaush (United States Historic US Routes)
Post by: Barefoot Driver on October 18, 2017, 03:18:48 am
please note that there is a segment of historic us-6 in polk county, ia.
the link is http://usroute6iowa.org/about-us/route-description (http://usroute6iowa.org/about-us/route-description).
i can remember when this road went onto sw 8th in altoona (from hubbell, instead of staying with that to i-80 as it does now) and continued onto what is now f48 (and that county road sports some of the g. a. r. highway signage) but am unsure as to where it joined up with 6 beyond that.
i also recall when hickman rd east of merle hay was part of 6. i knew this because the street had no curbs, just shoulders.
finally, has there been any effort to find old alignments of other highways? i know that us-65 (the “jefferson highway”) used to follow ne 14th and turn onto grand, go to w 7th, cross the viaduct, follow 7th to indianola av, and rejoin se 14th from there. the reason for that was that the railroad bridge on se 14th had not been constructed yet. (i have no idea what us-69 did then, since that highway also followed e 14th and still does.)
happy travels all!
Title: Re: usaush (United States Historic US Routes)
Post by: Highway63 on October 22, 2017, 07:38:34 pm
I've synced up points so that these routes intersect properly with other routes. I've not fixed NMPs.

This means that various I-, US and state route files have been changed slightly. I've pinged the relevant people via Github (apart from Jeff M, who isn't on there). Please check you are OK with the changes I'm proposing.

Jeff M: IA (https://github.com/si404/HighwayData/commit/4679d10a2b29b43ed95622450d2f9bcd9da37309), IL (https://github.com/si404/HighwayData/commit/9706093c15fb8b9fc5cdf0d1bdd4780389a85d2a),
 (https://github.com/si404/HighwayData/commit/1e22633a250bcbdc341172a14a825f82b8099bbd)

I need to apologize for not being on this earlier. I don't check this forum every day, nor do I check every thread. That said, I have a HUGE problem with this. Manipulating active system files for a prototype defeats the entire purpose of having one person in charge of a state.

There is a world of difference between making suggestions and going in and changing stuff. That complicates my end for having a complete set of up-to-date local files, and for when I'm working on something else - the Baraboo bypass affected half a dozen files.

The change to IA 21 was unnecessary because there was already a waypoint name there, the name of the current route (CRF29). Does a historic route name supersede an existing designation? For a street without a current designation, is the naming convention "OldUSXX" or "USXXHist" or what?

I fear that adding all these historic routes is missing the forest for the trees - or missing the forest to catalog every dead stump. The segment of US 6 in Des Moines pointed out above hasn't been part of mainline 6 since 1934 and hasn't been signed as anything since the early 1960s.

I know it's two months after the fact, but I am very not OK with this. If we're going to make historic routes a thing, we need to set parameters, probably limit it to very significant highways and alignments, and have the routes maintained by that state's administrator.
Title: Re: usaush (United States Historic US Routes)
Post by: bejacob on October 23, 2017, 07:46:08 pm
I know it's two months after the fact, but I am very not OK with this. If we're going to make historic routes a thing, we need to set parameters, probably limit it to very significant highways and alignments, and have the routes maintained by that state's administrator.

Couldn't agree more. I don't think historic routes should be a system, signed or otherwise as noted by my earlier comments. Once upon a time they may have been actual signed "official" routes, but they aren't any more. I see the "Historic" route signage as akin to the roadside historical markers. Even Historic US66, which is undoubtedly the most famous historical route isn't well marked in all places as I discovered on a recent trip in Oklahoma. The majority of decommissioned US routes have been renumbered as state routes (i.e. OK66). At least there is some official repository at the state level for those routes. As someone mentioned previously, other than users just noticing signage in the field, there's no way of being certain this system could ever be complete.

While I'll hate to lose the mileage I have clinched on those few segments that aren't part of the state route systems, I believe the historic route system should be scrapped. If they do end up staying, the folks handling the appropriate regions need to take these on. I'm sure there will be a difference of opinion on the subject, and I'll be interested to hear the pros and cons.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on October 27, 2017, 09:24:40 am
Manipulating active system files for a prototype defeats the entire purpose of having one person in charge of a state.
Your not having reset the files back to how you want them is what defeats the entire purpose of having one person in charge of a state!

You've moaned and griped and done nothing to fix it - do you want to be in charge of your states, or do you want to sit on the sidelines and complain about how you apparently aren't?

You've ignored my apologies, you've ignored me saying (at least twice) that you should undo the changes if you don't like them. It's like you are deliberately holding a grudge!
Quote
The change to IA 21 was unnecessary because there was already a waypoint name there, the name of the current route (CRF29). Does a historic route name supersede an existing designation? For a street without a current designation, is the naming convention "OldUSXX" or "USXXHist" or what?
Sorry, I must have missed that one when reverting that type of change. CRF29 should be the label. I would change it back, but you don't want me anywhere near your fief.
Quote
I fear that adding all these historic routes is missing the forest for the trees - or missing the forest to catalog every dead stump.
'every dead stump'? No, just the ones that are actively signed! It was you that got confused as to why some dead stumps were missing last year, proposing adding former US20 and US6 across Iowa, even though it was not signed.
Quote
The segment of US 6 in Des Moines pointed out above hasn't been part of mainline 6 since 1934 and hasn't been signed as anything since the early 1960s.
The one Barefoot Driver lists? I couldn't find signage (I might have seen one sign), and so have no plans to add it.

The proposal made by Barefoot Driver sounds similar, though less excessive, to this post:
The IA Historic US 20 that right now is confined to Dubuque County can be stretched nearly across the state to Early. Use Olde Castle Road, present 20 to the next intersection into Dyersville, and then the rest of the pre-freeway route should be easy to follow. (Or look at the Iowa DOT map archive.) I'd stick with the ca. 1960s route; the 1926-58 route from Cedar Falls to Jesup has at least two breaks in it, and the 1986-2000/2003 segment via D19 and IA 14 doesn't hold much significance IMO.

IA Historic US 6 can get an Altoona-Newton segment too (F48).

I can make the files if you want.

Even Historic US66, which is undoubtedly the most famous historical route isn't well marked in all places as I discovered on a recent trip in Oklahoma.
OK is the exception here with US66 (due to OK66), but there's 10 different signed segments of Historic US66 in the state. And I'm not sure why we need routes to be long to include them!
Quote
The majority of decommissioned US routes have been renumbered as state routes (i.e. OK66).
Sure, but why should those bits that aren't, but are considered important enough to be signed as a historic US route be ignored?
Quote
At least there is some official repository at the state level for those routes.
You want me to delete gbna? Because there's NO official repository for those routes!
Quote
As someone mentioned previously, other than users just noticing signage in the field, there's no way of being certain this system could ever be complete.
Sure, but why does that matter??
Title: Re: usaush (United States Historic US Routes)
Post by: bejacob on October 27, 2017, 10:36:30 am
As I mentioned previously, I'm just a user of the site. You don't need my buy-in. I do think it appropriate to get the buy-in from those who maintain the individual regions/states. From the tone of a few of the past comments, that does not appear to have happened.

I've expressed my concerns. They don't seem to matter, so I'll leave the matter to those involved with updating routes in each state. Hopefully an agreement can be reached. I'll continue to update my travels based on whatever is included in the HB.
Title: Re: usaush (United States Historic US Routes)
Post by: oscar on October 27, 2017, 11:31:40 am
I have mixed feelings about a historic routes set. Basically, I like having them around, and indeed contributed a route file (Historic US 6 in southern California, which follows what used to be in the CA 14U route file, but when I cleaned up that file then truncated away most of it, the historic route set was a good home for the deleted segment). OTOH, I don't have a lot of interest in developing or maintaining those route files, so am content to let someone else do that. I did let Si alter some usaca route files after I objected to some of his point renames (basically, no "Hist___" points in non-historic files, instead use normal non-historic intersecting road names). I'm satisfied with how that got resolved.

One issue is that the California historic route files were drafted when the I-/US/CA routes in that state were still being worked on. As I've been fixing up routes to get usaca ready for peer review (still a few dozen left), that has created a lot of NMPs and broken concurrences with the draft historic routes. I'm not fixing them now so I can focus on usaca, but they will need to be fixed later once usaca goes active.
Title: Re: usaush (United States Historic US Routes)
Post by: Jim on October 27, 2017, 11:42:16 am
I think that a key point in this is that the "official" version of our data has to be that which is in the HighwayData repository rather than what's in anyone's local files.  Before making any changes, we all need to make sure we merge in the latest from the origin repository on GitHub.

I've stepped aside from highway data management for a while now, but I know I'd rather have minor fixes made (with a quick note to me that it happened) as long as by someone experienced enough that we trust they'll do the right thing, instead of having to see a problem report, go in and fix it, submit a pull request, go back and mark the request.  I do this kind of thing all the time if I notice a minor problem with labeling or the position of a route.  It's easier for me to fix than to type in the post here asking for that state's maintainer to do it.

The usaush situation is a little different, since it introduced new labels, etc, into active systems.  Even there, though it seems Jeff M. disagrees, if Si were adding a new devel system in a state I maintained, I would want him to make conforming changes to active systems.  Some new contributor without the experience, I'd be worried.  Sure, mistakes might be made but they can be worked out.

I'd like to be able to allow continued email submissions of highway data files from those uncomfortable with git and GitHub, but I think many actual and potential problems would go away if we could get more people using it.
Title: Re: usaush (United States Historic US Routes)
Post by: vdeane on October 29, 2017, 01:47:20 pm
Quote
As someone mentioned previously, other than users just noticing signage in the field, there's no way of being certain this system could ever be complete.
Sure, but why does that matter??
Some of us use Travel Mapping as a "checklist" of routes to clinch and strive to get to 100% for certain regions/systems (or, in my case, certain parts of the map, so it looks good).
Title: Re: usaush (United States Historic US Routes)
Post by: Highway63 on November 06, 2017, 03:08:58 pm
If the Historic Routes are going to be an active system, I want to take over Iowa's. IL and MO US 66 stuff is fine but the Iowa routes need work.

On the Lincoln Highway file in GitHub, there are multiple places where loop routes (as signed in the field) are incorporated into the mainline and should be parted out. The Marion loop is the biggest example.
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on February 10, 2018, 02:38:46 am
Route66 Historic Alignments (https://gis-okdot.opendata.arcgis.com/datasets/ed838af735da4f03ab820b190e2844bf_0?geometry=-98.466%2C35.535%2C-98.032%2C35.633)
Quote
Represents all known historic alignments of US Route 66 in the state of Oklahoma. Based on historical research using Oklahoma Department of Transportation records and other sources.
LOL have fun :D
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on February 10, 2018, 06:41:54 am
If the Historic Routes are going to be an active system, I want to take over Iowa's. IL and MO US 66 stuff is fine but the Iowa routes need work.
You can do so now. I'm really not that fussed about it being me doing the improving and such-like. I'd much rather state maintainers did it and then there's less toes trodden on, etc.
Quote
On the Lincoln Highway file in GitHub, there are multiple places where loop routes (as signed in the field) are incorporated into the mainline and should be parted out. The Marion loop is the biggest example.
Fair enough. I sought to follow the signs, but will bow to greater knowledge. Again - change how you want. Obviously we don't have that route in a system, but I drafted a route file for my own interest and felt it might as well be uploaded.

Route66 Historic Alignments (https://gis-okdot.opendata.arcgis.com/datasets/ed838af735da4f03ab820b190e2844bf_0?geometry=-98.466%2C35.535%2C-98.032%2C35.633)
LOL have fun :D
Most of that isn't signed as His US66. So we don't need to bother with it  :P

Some of us use Travel Mapping as a "checklist" of routes to clinch and strive to get to 100% for certain regions/systems (or, in my case, certain parts of the map, so it looks good).
If you are doing an area - then you'll see signs, know that it's something we're adding and probably drive it. Certainly you'd request the route be added/add the route yourself so that it exists and you can grab it. We've had lots of these "I was driving here, and this route was signed" posts with state routes, auxiliary US routes and the like.

If you are intrigued by this system specifically, then you'd know that there's no nice neat record and you'd keep your ear to the ground about new signs going up and such like. And, again, request/add routes as you are made aware of them. Now sure, it's a little harder than AASHTO publishing approved route changes (but isn't dissimilar to the many many states that add in/remove auxillary US routes/Business I-routes without informing AASHTO) or detailed lists being made and published by the state DoT regularly. But it's not impossible.
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on February 11, 2018, 12:50:16 am
There's a spur route of 66 (https://www.google.com/maps/@38.7621307,-90.1267948,3a,79.5y,286.07h,97.09t/data=!3m6!1e1!3m4!1sMcsxKmdbgWkSYEzRqVRxYQ!2e0!7i13312!8i6656) in Illinois along the road leading up to the old Chain of Rocks Bridge.
Title: Re: usaush (United States Historic US Routes)
Post by: vdeane on February 11, 2018, 10:46:49 am
If you are doing an area - then you'll see signs, know that it's something we're adding and probably drive it. Certainly you'd request the route be added/add the route yourself so that it exists and you can grab it. We've had lots of these "I was driving here, and this route was signed" posts with state routes, auxiliary US routes and the like.

If you are intrigued by this system specifically, then you'd know that there's no nice neat record and you'd keep your ear to the ground about new signs going up and such like. And, again, request/add routes as you are made aware of them. Now sure, it's a little harder than AASHTO publishing approved route changes (but isn't dissimilar to the many many states that add in/remove auxillary US routes/Business I-routes without informing AASHTO) or detailed lists being made and published by the state DoT regularly. But it's not impossible.
Not necessarily.  The Historic US 20 route near New Lebanon, NY has zero signage in the field, even on the small piece of the route that isn't concurrent with modern US 20 (which I made a special trip to clinch a couple years ago, since I had already seen everything else in the area and therefore have no other reason to go there).  Signage for the other Historic US 20 route in NY is a small shield attached with zip ties to an existing sign by the Historic US 20 group.
Title: Re: usaush (United States Historic US Routes)
Post by: Highway63 on February 28, 2018, 01:19:02 am
There's a spur route of 66 (https://www.google.com/maps/@38.7621307,-90.1267948,3a,79.5y,286.07h,97.09t/data=!3m6!1e1!3m4!1sMcsxKmdbgWkSYEzRqVRxYQ!2e0!7i13312!8i6656) in Illinois along the road leading up to the old Chain of Rocks Bridge.
I can make a file with a point at the parking lot and then across the river for those who walk it. I don't know quite what to do in MO, though, because a matching file would be the walking path across the bridge to the lot on that side.

I apologize for my non-attention to the historic routes and will try to spend some time on them this week.
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on February 28, 2018, 07:58:05 am
I can make a file with a point at the parking lot and then across the river for those who walk it. I don't know quite what to do in MO, though, because a matching file would be the walking path across the bridge to the lot on that side.
I think that ending it at the parking lot is fine. Is the walking path across the bridge signed as a highway?
Title: Re: usaush (United States Historic US Routes)
Post by: Highway63 on March 04, 2018, 01:10:44 am
It's got "Historic 66" signs but it's closed to vehicles, but it is walkable.
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on March 04, 2018, 02:35:38 am
VT65 Brookfield Floating Bridge?
Title: Re: usaush (United States Historic US Routes)
Post by: Duke87 on March 12, 2018, 11:03:14 pm
Well here's something: http://www.historicus20.com/historic-route-signage.html (http://www.historicus20.com/historic-route-signage.html)
As far as I can tell from the pics there is an extant US20His in Marlborough and Becket, MA (although I have no idea of the routings).
There are also some links at the bottom that may or may not be useful.

I would like to point out that the Historic US 20 signs shown in Massachusetts on this site were either photoshopped into those pictures, or temporarily mounted by the owner of that website (Bryan Farr) for the purpose of taking a picture and then removed.

Bryan has been lobbying to get Historic US 20 signage on old alignments in every state it passes through, but as far as I can tell none have actually been posted in Massachusetts.

For exaple this is what the location of the sign shown in Marlborough actually looks like as of August 2017: https://www.google.com/maps/@42.​3469468,-71.5471033,3a,15y,291.97​h,88.38t/data=!3m6!1e1!3m4!1slI4B​fV3qyoshnye-RXCzZg!2e0!7i13312!8i​6656 (https://www.google.com/maps/@42.​3469468,-71.5471033,3a,15y,291.97​h,88.38t/data=!3m6!1e1!3m4!1slI4B​fV3qyoshnye-RXCzZg!2e0!7i13312!8i​6656)
Title: Re: usaush (United States Historic US Routes)
Post by: froggie on March 27, 2018, 08:38:44 am
Quote
VT65 Brookfield Floating Bridge?

Has been reopened to vehicle traffic for over a year now...
Title: Re: usaush (United States Historic US Routes)
Post by: neroute2 on April 17, 2018, 07:02:43 pm
So...how does CA US40HisSac actually go downtown? The way TM handles one-way pairs makes it impossible to tell.
(It also doesn't seem to play well with the CA160 waypoint AmeRiv.)
Title: Re: usaush (United States Historic US Routes)
Post by: oscar on April 17, 2018, 11:45:24 pm
So...how does CA US40HisSac actually go downtown? The way TM handles one-way pairs makes it impossible to tell.
(It also doesn't seem to play well with the CA160 waypoint AmeRiv.)

It helps, on following the route in the field, that US40HisSac has pretty good signage, while the corresponding former CA 160 segment through downtown doesn't have even remnant signage.

The AmeRiv waypoint on CA 160 was added after the historic routes were drafted. Lots of other historic route waypoints are out of synch with intersecting/concurrent usaca routes, as one might expect when historic routes in CA were drafted while most everything else in CA was being comprehensively updated and overhauled.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on April 18, 2018, 05:48:52 am
I believe, when drafting the route, CA160 still extended there, so I just copied that (I have no other idea why I would have put a shaping point near Alkali Flat) - presumably only checking eastbound as it disagrees with westbound.

Eastbound reassurance signs on: Capitol Ave near the railway bridge (https://www.google.co.uk/maps/@38.5828681,-121.5159337,3a,75y,71.78h,93.46t/data=!3m6!1e1!3m4!1sD2wi12gENaxq1AF_ESQ33A!2e0!7i13312!8i6656), N just before 15th (https://www.google.co.uk/maps/@38.574109,-121.4888438,3a,37.6y,71.94h,91.41t/data=!3m6!1e1!3m4!1s7ZyBDgmf_toElKrNEG5giw!2e0!7i13312!8i6656), 16th just after N (https://www.google.co.uk/maps/@38.5740649,-121.486957,3a,75y,21.82h,85.77t/data=!3m6!1e1!3m4!1slictDajWjrVBryO0_AK-Aw!2e0!7i13312!8i6656), Del Paso near Globe (https://www.google.co.uk/maps/@38.6020847,-121.4671695,3a,75y,63.57h,81.59t/data=!3m6!1e1!3m4!1sKVDnhyK5RA-tQpJA41Ba8A!2e0!7i13312!8i6656).

Westbound signs on: Del Paso near Baxter (https://www.google.co.uk/maps/@38.6039378,-121.4638716,3a,75y,254.41h,85.96t/data=!3m6!1e1!3m4!1syP37Uc67ocoVYgn0iYWbmg!2e0!7i13312!8i6656), 12th at Fat Alley (https://www.google.co.uk/maps/@38.5836959,-121.4891025,3a,15y,165.9h,87.64t/data=!3m6!1e1!3m4!1sp14VlYsuAQF3iKzuSGczJw!2e0!7i13312!8i6656), Capitol Ave near the railway bridge (https://www.google.co.uk/maps/@38.5828135,-121.5156978,3a,75y,295.74h,86.95t/data=!3m6!1e1!3m4!1s9B1b1w0oNU3Khnwf8ZmwGg!2e0!7i13312!8i6656).

We can infer Tower Bridge as being part of the route, for obvious reasons. But how to get to it from 12th/G or from it to N/15th? Assuming there's no radical difference between the routes for each direction, we can assume Hist 40 comes down 12th to L. The question has to be (other than needing to fix the route north of downtown) whether it takes the L-N pair between 9th and 3rd, or whether it takes the Capitol Mall. I gather the Capitol Mall was part of 40 (pictures of old postcards supposedly showing signage), but if you went L or N instead, then you can fudge it and call it clinched!
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on June 25, 2018, 11:59:35 pm
@Si: in case you're unaware, there are a few Historic US 165 signs on LA 125 (and possibly other routes) in Louisiana:

https://www.google.com/maps/@31.9282339,-92.2011321,3a,39.5y,299.79h,94.24t/data=!3m6!1e1!3m4!1srez5dOHeS_U9jq_j0lGciQ!2e0!7i13312!8i6656
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on June 26, 2018, 05:50:06 am
So I traced them (and it's just LA125 for that bit) in GMSV, and when I move from 2014 imagery to 2016 imagery, the signs disappear. This isn't "I can't find signs on more recent imagery" but "this sign that I see in 2014 imagery doesn't exist when I move a tiny bit and the image date changes". All LA125/US165 junctions, and where LA124 turns west too. It seems the signs are gone, or meant to be going.
Title: Re: usaush (United States Historic US Routes)
Post by: neroute2 on June 26, 2018, 02:36:58 pm
It seems the signs are gone, or meant to be going.
Confirmed here:
http://www.google.com/maps/@31.8939923,-92.2614889,3a,75y,76.61h,86.71t/data=!3m7!1e1!3m5!1svgt51Fuqy9K9IPnGmSjXxg!2e0!5s20140601T000000!7i13312!8i6656 (2014)
http://www.google.com/maps/@31.8939972,-92.2614632,3a,75y,76.61h,86.71t/data=!3m7!1e1!3m5!1sjC7jgpLgtsfhzuEiXr8Klw!2e0!5s20160701T000000!7i13312!8i6656 (2016)
I wonder why they were removed. Ninjasigning without state approval?
Title: Re: usaush (United States Historic US Routes)
Post by: osu-lsu on June 26, 2018, 09:50:25 pm
Wonder where all the 'Historic US 61' shields for the bypassed routes, between Baton Rouge & the Louisiana/Mississippi Border, are?  ???
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on July 09, 2018, 12:01:18 pm
I drove the length of US20HisBri (http://travelmapping.net/hb/?units=miles&u=null&r=ny.us020hisbri) yesterday and didn't see any Historic US 20 signs, just these (https://i.pinimg.com/originals/7a/1e/61/7a1e61b1369a48669dbead79c4d74dd2.jpg).
Title: Re: usaush (United States Historic US Routes)
Post by: osu-lsu on July 09, 2018, 08:18:39 pm
I drove the length of US20HisBri (http://travelmapping.net/hb/?units=miles&u=null&r=ny.us020hisbri) yesterday and didn't see any Historic US 20 signs, just these (https://i.pinimg.com/originals/7a/1e/61/7a1e61b1369a48669dbead79c4d74dd2.jpg).

Somebody, who likes posting 'Historic' US 20 shields, is supposed to be giving a presentation, in Mentor, on the last weekend in September.
You're invited to attend.
Title: Re: usaush (United States Historic US Routes)
Post by: Jim on July 09, 2018, 08:52:37 pm
I drove the length of US20HisBri (http://travelmapping.net/hb/?units=miles&u=null&r=ny.us020hisbri) yesterday and didn't see any Historic US 20 signs, just these (https://i.pinimg.com/originals/7a/1e/61/7a1e61b1369a48669dbead79c4d74dd2.jpg).

It looks like the route is entirely concurrent with US 20 in our system.  Seems like no point in keeping it.
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on July 09, 2018, 09:46:42 pm
Somebody, who likes posting 'Historic' US 20 shields, is supposed to be giving a presentation, in Mentor, on the last weekend in September.
You're invited to attend.
I think most of the Historic US 20 segments Si put into the system are the result of that guy.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on July 10, 2018, 04:14:24 am
Oddly enough, not US20HisBri, which was someone else saying it was signed. Have removed it locally.

As entirely concurrent with US20, no one who clinched it isn't rewarded with mileage...
Title: Re: usaush (United States Historic US Routes)
Post by: vdeane on July 14, 2018, 06:01:50 pm
I think that guy went out one day, attached a few signs to existing US 20 signs with zip ties, and called it signed.  I think I've seen one at the Duanesburg end near I-88 during either the pavement survey or HPMS survey last year, so there was a sign up at least then.
Title: Re: usaush (United States Historic US Routes)
Post by: Duke87 on July 15, 2018, 09:45:51 pm
Generally yes, the photos of Historic US 20 signs on Bryan Farr's website in NY and MA are his own mock-ups, not official signage.

That said - I can confirm that as of today the Chester-Huntington segment of Historic US 20 is actually signed!  (https://i.imgur.com/3RwwqIy.jpg)That is the only sign for it, at the western end, but there is one. So, US20HisHun can stay.

Also checked out the Sturbridge segment, and found zero signs on it. So, US20HisStu definitely needs to be deleted.

The other segments remain suspect (and I still think should be deleted) given that we have no evidence of signage other than Bryan Farr's photos which by his own admission are of signs he temporarily put up for demonstration purposes.
Title: Re: usaush (United States Historic US Routes)
Post by: froggie on July 15, 2018, 11:03:01 pm
I'm not certain we should be including historic route segments that are only signed because of a guy on a one-man crusade.
Title: Re: usaush (United States Historic US Routes)
Post by: vdeane on July 17, 2018, 05:24:33 pm
I'm not certain we should be including historic route segments that are only signed because of a guy on a one-man crusade.
Agreed.  I think most of my issues with this system come back to this issue.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on July 21, 2018, 02:09:25 pm
I've purged US20His segements that I couldn't find evidence of.

Other than the California State Highway resync issue, I think we can push this system further along the road to activation now.
Title: Re: usaush (United States Historic US Routes)
Post by: oscar on July 21, 2018, 09:17:30 pm
Other than the California State Highway resync issue, I think we can push this system further along the road to activation now.

Don't forget neroute2's point requests which include some historic routes in CA (http://forum.travelmapping.net/index.php?topic=2509.0), erroneously posted in the Updates form. Neither I nor anyone else appears to have made those changes, but his suggestions for changes to usaca routes (which I'm still working on) seem to be mostly reasonable.

In addition to changes to usaca routes, all the active system routes in California were redone after usaush was drafted, and so would need to be part of the resync. The NMP log should flag them. Also, there is some danger that possible future removals of relinquished state route segments concurrent with historic routes, like CA 2/US 66 His (Hollywood), would require additional re-synching changes to usaush routes, though I hope such changes will be manageable in number.
Title: Re: usaush (United States Historic US Routes)
Post by: neroute2 on July 21, 2018, 10:31:31 pm
CA US66HisHol/CA US66HisAzu:
What's the deal at the west end of CA US66HisHol? US 66 never went that way; it always turned down Lincoln to end at Olympic. As of December 2017 (https://www.google.com/maps/@34.0198995,-118.490998,3a,75y,257.01h,104.21t/data=!3m6!1e1!3m4!1sJc9y8CYJP-VaaKYPRUM3Og!2e0!7i16384!8i8192) this was backed up by signage, along with an end sign (https://www.google.com/maps/@34.0151179,-118.4864376,3a,75y,147.64h,98.03t/data=!3m6!1e1!3m4!1sqmD1rMcoAeuqG8jYxzoK4Q!2e0!7i16384!8i8192) at Olympic.
How was it decided what route CA US66HisHol would follow through LA? I can't find any signs on the Goog, but if you're going for the longest-lasting alignment, that would be Sunset-Figueroa, then onto the Arroyo Seco Parkway to Pasadena. Pre-freeway (opened 1940!) it used Figueroa (partly repurposed for the freeway through Elysian Park) all the way to Pasadena. If it ever used Broadway to Mission, that was before 1934 (at which time the route was San Fernando-Eagle Rock-Colorado).
I did find two (https://www.google.com/maps/@34.1379783,-118.1874048,3a,22.2y,46.53h,107.19t/data=!3m6!1e1!3m4!1su72eSNL6PXVluEUfT4oqXA!2e0!7i16384!8i8192) signs (https://www.google.com/maps/@34.1380097,-118.1876575,3a,20.8y,189.21h,95.05t/data=!3m6!1e1!3m4!1sTITfR5THEQjWnu3BI3z3eA!2e0!7i16384!8i8192) at Figueroa and Colorado. So unless anyone has a good reason for a different alignment (such as signs I missed), we should change it to turn off the current route at Sunset and Figueroa, north on Figueroa to SR 110, then overlapping SR 110 between 24B and 26, then taking over CA US66HisAzu.

CA US66HisCaj should also be combined with these two, now that Cajon Boulevard has been built across I-15.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on July 22, 2018, 10:41:52 am
US40HisRos:
[KingRd]
RipRd http://www.openstreetmap.org/?lat=38.82651&lon=-121.19041
[PenRd]
EngColWay http://www.openstreetmap.org/?lat=38.85133&lon=-121.16450
SisRd http://www.openstreetmap.org/?lat=38.85222&lon=-121.16358
CalRd http://www.openstreetmap.org/?lat=38.86576&lon=-121.15188
(all parts of the original Lincoln Highway alignment)
[OldStaHwy]

US40HisAub:
[HighSt_S]
LinWay_S http://www.openstreetmap.org/?lat=38.89957&lon=-121.06995
[CA49_N]
LinWay_N http://www.openstreetmap.org/?lat=38.90383&lon=-121.06647
[CA49_S]
(old Lincoln Highway)
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on July 22, 2018, 02:15:01 pm
If it ever used Broadway to Mission, that was before 1934 (at which time the route was San Fernando-Eagle Rock-Colorado).
The sign at the west end of Broadway (https://www.google.com/maps/@34.0586346,-118.2400737,3a,75y,34.16h,112.1t/data=!3m7!1e1!3m5!1smU9vByWLi_X_Mkhm3WdCbg!2e0!6s%2F%2Fgeo2.ggpht.com%2Fcbk%3Fpanoid%3DmU9vByWLi_X_Mkhm3WdCbg%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D152.69778%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656), and the east end (https://www.google.com/maps/@34.0739549,-118.1967838,3a,49.9y,301.12h,97.4t/data=!3m6!1e1!3m4!1s9eb7d-z0SbDPsTloVatl6A!2e0!7i16384!8i8192) do say 'circa 1926-1934'. Ditto the one on Cezar Chavez Ave (https://www.google.co.uk/maps/@34.0585688,-118.2402629,3a,34.2y,327.31h,97.66t/data=!3m6!1e1!3m4!1sEQ7HFkVKsSqxInt9WpR69A!2e0!7i13312!8i6656?hl=en). Though at Avenue 20 (https://www.google.com/maps/@34.0726125,-118.220155,3a,60y,96.98h,92t/data=!3m6!1e1!3m4!1sNXVQrbLXeZ09juVnal3hLQ!2e0!7i16384!8i8192) the sign says 'circa 1934 to 1941'
Quote
I did find two (https://www.google.com/maps/@34.1379783,-118.1874048,3a,22.2y,46.53h,107.19t/data=!3m6!1e1!3m4!1su72eSNL6PXVluEUfT4oqXA!2e0!7i16384!8i8192) signs (https://www.google.com/maps/@34.1380097,-118.1876575,3a,20.8y,189.21h,95.05t/data=!3m6!1e1!3m4!1sTITfR5THEQjWnu3BI3z3eA!2e0!7i16384!8i8192) at Figueroa and Colorado. So unless anyone has a good reason for a different alignment (such as signs I missed), we should change it to turn off the current route at Sunset and Figueroa, north on Figueroa to SR 110, then overlapping SR 110 between 24B and 26, then taking over CA US66HisAzu.
There's zero signage on SR110 though...
Quote
CA US66HisCaj should also be combined with these two, now that Cajon Boulevard has been built across I-15.
Yep, agreed.
Title: Re: usaush (United States Historic US Routes)
Post by: neroute2 on July 22, 2018, 02:32:09 pm
Aha, I missed those signs. I'll look some more when I get home.
Title: Re: usaush (United States Historic US Routes)
Post by: neroute2 on July 22, 2018, 11:38:43 pm
I see now. This 1926-34 route has shields painted on the pavement (where they can't be stolen) in South Pasadena: http://www.route66news.com/2017/02/23/south-pasadena-fair-oaks-pharmacy/
I found shields eastbound (https://www.google.com/maps/@34.1161332,-118.150416,3a,36.4y,178.46h,80.01t/data=!3m6!1e1!3m4!1sLxyQ_x-v9F9P86dWW1jheQ!2e0!7i13312!8i6656) and westbound (https://www.google.com/maps/@34.116393,-118.150411,3a,24.5y,77.37h,76.65t/data=!3m6!1e1!3m4!1s9j-0qDNjee6HMdzSs2VckA!2e0!7i13312!8i6656) on Fair Oaks near Mission, and westbound (https://www.google.com/maps/@34.1140379,-118.1504034,3a,75y,226.17h,63.2t/data=!3m6!1e1!3m4!1s306AxFsEl_A6kYaEOMaGLg!2e0!7i13312!8i6656) near Oxley.
Given the original layout at Sierra Vista, Huntington North is almost certainly old 66. (Huntington itself was the Pacific Electric.) We could tie this South Pasadena piece into the Hollywood piece, or we could give it a separate segment. City limits are Huntington at Kendall/Alhambra and Fair Oaks at Columbia.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on July 24, 2018, 08:28:00 am
Amarillo has started using proper signs (http://www.route66news.com/2018/06/07/new-route-66-signs-unveiled-in-amarillo/)

Someone has made a (not up-to-date) map (https://www.google.com/maps/d/viewer?mid=14-a8I0S1xWH9N-D3pIH8BRaET9o&ll=35.205715488146524%2C-101.81731130347293&z=12) 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.
Title: Re: usaush (United States Historic US Routes)
Post by: oscar on August 02, 2018, 11:11:10 pm
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.
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on August 17, 2018, 10:22:31 pm
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.
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on August 20, 2018, 09:58:37 pm
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
Title: Re: usaush (United States Historic US Routes)
Post by: froggie on August 21, 2018, 08:04:36 am
^ 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).
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on August 21, 2018, 01:49:01 pm
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 (http://markschoesler.src.wastateleg.org/legislature-backs-effort-promote-historic-u-s-10-route/). 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.
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on August 21, 2018, 03:20:17 pm
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.
Title: Re: usaush (United States Historic US Routes)
Post by: cl94 on August 21, 2018, 05:41:45 pm
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.
Title: Re: usaush (United States Historic US Routes)
Post by: Duke87 on August 26, 2018, 12:17:28 pm
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.
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on November 03, 2018, 06:32:18 pm
ca.us040hisaub has two LABEL_INVALID_CHAR datacheck entries.
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on January 31, 2019, 12:22:25 am
Is IA US6HisCou actually signed as such?
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on January 31, 2019, 03:29:28 am
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 (https://www.google.co.uk/maps/@41.2611106,-95.8482361,3a,15.2y,80.46h,89.41t/data=!3m6!1e1!3m4!1s8PHQdRFV4VR5SPVe3y_a8w!2e0!7i13312!8i6656) and this one westbound (https://www.google.co.uk/maps/@41.2645572,-95.8416839,3a,51.8y,240.55h,79.97t/data=!3m6!1e1!3m4!1sZOmG0ThMBsOcsoHPpA7ZrA!2e0!7i13312!8i6656).

*Something like 6 eastbound and 4 westbound. The route's only a mile long, doesn't turn, doesn't meet any major roads...
Title: Re: usaush (United States Historic US Routes)
Post by: Highway63 on February 08, 2019, 01:58:15 am
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.
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on February 08, 2019, 02:33:45 pm
It's a project from a US 6 enthusiast
Should usaush really include something like that?
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on February 08, 2019, 03:21:01 pm
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!
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on February 08, 2019, 10:41:41 pm
Eric suggested that it wasn't signed particularly well, and I failed to find signs at either end when I did a quick check in GMSV, so I wasn't able to see how close to specs the "enthusiast's" signs were.
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on February 12, 2019, 04:15:02 pm
MO US66HisFlo:
Suggest centering waypoints along the  centerline of Dunn Rd. Even if it breaks intersecting/concurrent routes, it less confusingly & more accurately tracks where the route goes; more important IMO. There's even a false-positive multiplex from I-270(27) to I-270(28).
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on May 16, 2019, 02:01:07 pm
Well here's something: http://www.historicus20.com/historic-route-signage.html (http://www.historicus20.com/historic-route-signage.html)
As far as I can tell from the pics there is an extant US20His in Marlborough and Becket, MA (although I have no idea of the routings).
and Weston, MA, New Lebanon, NY, North East, PA, Sandhills, NE...

Sadly the Ostriches haven't roamed those parts for a long time, so route discernment is difficult (the Becket, MA is a tiny former alignment segment where the turnpike diverted it - called Morse Rd).
I don't see any references in the link at the quote, including at web.archive.org.
No historic route signage in GMSV either, including historic imagery.
On NE US20HisCra NWhiLakeRd AirRd_W, sattelite imagery shows badly deteriorated pavement, returning to nature. There's no GMSV coverage, and while I have no reason to suspect the road isn't open to traffic, I doubt this is the kind of road anyone would want to put historic route signs on for the tourists.

Barring anything really revelatory, I'll probably delete both Nebraska usaush routes soon.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on May 16, 2019, 03:18:47 pm
There's definitely non-fake signs in Gordon (https://sheridancountyjournalstar.net/news/item/2737-gordon-unveils-historic-us-route-20-signs). The article refers to Rushville, which also has at least one sign (screenshot of similar article from the same local paper preserved on the the Historic US20 website). GMSV is 2012, so doesn't show these more recent additions. I might have put the ends a waypoint too far, but there is decent evidence that Historic US20 is signed along US20 at these two towns.

I'm fine with routes, especially US20 ones, being removed if there's no evidence of them.

IIRC, the Historic US20 site used to have a map with cities with signs marked on it (hence Sandhills, NE, etc). These signs could have just been someone putting it up on their wall, rather than being used on the road.
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on June 22, 2019, 02:02:16 pm
OK, Gordon/Rushville is good enough for me. I'm not too fussed about trying to pin down more exact endpoints.
Deleting the Crawford segment, but I'll leave the unprocessed wpt, in case we find in the future that it should come back.
https://github.com/TravelMapping/HighwayData/pull/2934
Title: Re: usaush (United States Historic US Routes)
Post by: Bickendan on July 09, 2019, 04:45:02 pm
OR Hist US 99 does not have any field signage.
I will be emailing ODOT about this amongst other related matters.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on July 09, 2019, 06:18:22 pm
OR Hist US 99 does not have any field signage.
OK, it must have used to have had, as I didn't add it willy nilly and there's not some guy with a shield that goes and erects it, takes a photo and then takes it down - unlike US20!

There's no harm in removing it as its entirely concurrent with OR99
Title: Re: usaush (United States Historic US Routes)
Post by: Bickendan on July 09, 2019, 08:14:09 pm
The annoying thing is outside of the shields on the exit signs for I-5, OR 99 is not signed at all on the surface streets for Canyonville, Tri City-Myrtle Beach, or Yoncalla-Drain. Luckily the routings are easy to follow.
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on July 30, 2019, 05:08:47 pm
Found one (https://www.google.com/maps/@42.1124476,-72.1290945,3a,25.3y,99.48h,89.84t/data=!3m6!1e1!3m4!1snEUouBoHe3xdj7jmSfMGUg!2e0!7i13312!8i6656) along US 20 in Sturbridge, Mass.
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on July 30, 2019, 09:08:51 pm
Having these when concurrent with the present-day mainline never made much sense to me, or seemed very important. (Signed by That One Guy?) I may give GMSV a closer look, but it's a low priority.
Did you say you also saw one west of Springfield? Is that the one already in the HB?
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on July 30, 2019, 09:15:38 pm
Having these when concurrent with the present-day mainline never made much sense to me, or seemed very important. (Signed by That One Guy?) I may give GMSV a closer look, but it's a low priority.
Did you say you also saw one west of Springfield? Is that the one already in the HB?

Right, that one I mentioned the other night was the one that's already in the HB. Barely signed, but signed.
Title: Re: usaush (United States Historic US Routes)
Post by: Bickendan on August 06, 2019, 07:47:14 pm
US30 Columbia River Gorge doesn't end at Exit 35, but extends through Dodson and Warrendale, reentering the freeway at Exit 37.

There's an additional US30 Hist segment between Cascade Locks and Hood River, according to signage I spotted from the freeway on the old route. Looks like it's from Exit 44 to 51, taking Frontage Road and Wyeth Rd. It's entirely possible that US 30 proper through Cascade Locks is included.

No changes needed to the Rowena Crest segment.
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on August 14, 2019, 10:31:10 pm
Historic US 101 in San Diego ends at Harbor Dr (https://www.google.com/maps/@33.2092724,-117.3882437,3a,50.6y,149.36h,93.02t/data=!3m6!1e1!3m4!1sMy3ZVSzAUu2spMxYihU4Wg!2e0!7i16384!8i8192) (I-5 exit 54C) rather than at CA 76 (exit 54A).
Title: Re: usaush (United States Historic US Routes)
Post by: CharlotteAllisonCDTG on August 15, 2019, 01:17:49 am
I don't see any Historic US 101 signage on Harbor Drive.
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on August 15, 2019, 10:51:28 am
It's not on Harbor Dr. It's on Coast Hwy.
Title: Re: usaush (United States Historic US Routes)
Post by: CharlotteAllisonCDTG on August 16, 2019, 09:45:54 am
I still didn't see one.
Title: Re: usaush (United States Historic US Routes)
Post by: oscar on August 16, 2019, 10:36:38 am
The historic route intersection with Harbor Drive is also where ramps to and from SB I-5 meet Harbor Drive.

I think the intersection being part of the I-5(54C) interchange, it's appropriate to include points for both I-5(54C) to reflect the tie-in to I-5, and Harbor Drive (the latter point helps show the historic route as parallel to I-5 on the old US 101 bridge over the San Luis Rey River).

I'm not sure how to fix the I-5(54A) point on the historic route. CA 76 appears to end at I-5, with the connector to the Coast Hwy. not officially part of the state highway (I can check my paper Caltrans logbooks, once I get back home, to confirm). Maybe move the point to the Coast Hwy./Mission Expy, intersection, and rename it MisExpy?

As someone who grew up in Oceanside, extending the historic route over the old San Luis River bridge looks right to me.
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on August 16, 2019, 11:05:47 am
I think the intersection being part of the I-5(54C) interchange, it's appropriate to include points for both I-5(54C) to reflect the tie-in to I-5, and Harbor Drive (the latter point helps show the historic route as parallel to I-5 on the old US 101 bridge over the San Luis Rey River).
Since it appears to begin where the ramps intersect Harbor Dr, I think one point at I-5(54C) would be good enough, although a shaping point on the bridge could make it easier to see if necessary, depending on what you do with the I-5(54A) point.

Quote
I'm not sure how to fix the I-5(54A) point on the historic route. CA 76 appears to end at I-5, with the connector to the Coast Hwy. not officially part of the state highway (I can check my paper Caltrans logbooks, once I get back home, to confirm). Maybe move the point to the Coast Hwy./Mission Expy, intersection, and rename it MisExpy?
That's how I would handle it, although this sign (https://www.google.com/maps/@33.2049103,-117.3812793,3a,75y,339.47h,100.48t/data=!3m6!1e1!3m4!1sNd4bvsH44kEBjqnLnWgpvw!2e0!7i16384!8i8192) and this sign (https://www.google.com/maps/@33.2017684,-117.3839065,3a,44.9y,7.95h,88t/data=!3m6!1e1!3m4!1sSepzXBO_JJd6UaQvkHqPUw!2e0!7i16384!8i8192) make it look like it's worth investigating the true end of CA 76.
Title: Re: usaush (United States Historic US Routes)
Post by: oscar on August 17, 2019, 02:04:25 pm
^ I'm at home (briefly), was able to check out Caltrans' old paper logs as well as the more current online Postmile Query Tool. Both put CA 76's west end at I-5 rather than Coast Hwy (US 101 Historic), with CA 76's postmile 0.0 in the I-5 median. So I'm leaving CA 76 as is in the Highway Browser, even with the otherwise convincing signage shown in your GMSV links.

I think a labeled waypoint at the Coast Hwy./Harbor Dr. intersection (HarbDr_W, since there's an intersection with another Harbor Dr. in San Diego) best reflects the end of signage for the historic route, and the approximate north end of the old pavement (obliterated by the new I-5, until it resumes within the Marine Corps base). That also more clearly shows the historic route as separate from the parallel I-5, even with the moved and renamed I-5(54A) point on the south side of the river.

No signage on Harbor Dr. between Coast Hwy. and I-5, so I'm not as sure about including the I-5(54C) point as the historic route's north end just to maintain a graph connection with I-5 - @si404, any thoughts on that, as (I assume) the original drafter of the route file?
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on August 17, 2019, 02:22:59 pm
I'd suggest one point per interchange means that the Coast Hwy / Harbor Dr intersection is part of the I-5 interchange. The intersection is, after all, a crossroads with the southbound carriageway's ramps opposite Coast Hwy.

Moving the point with not-CA76 should make it separate enough from I-5.
Title: Re: usaush (United States Historic US Routes)
Post by: oscar on August 17, 2019, 03:31:59 pm
I'd suggest one point per interchange means that the Coast Hwy / Harbor Dr intersection is part of the I-5 interchange. The intersection is, after all, a crossroads with the southbound carriageway's ramps opposite Coast Hwy.

Moving the point with not-CA76 should make it separate enough from I-5.

Gotcha. I-5(54C), and I-5(54A) => MisExpy (relocated to Coast Hwy.), it is.

I can implement those changes later this weekend, before I disappear for a week camping in western Massachusetts.

EDIT: https://github.com/TravelMapping/HighwayData/pull/3061
Title: Re: usaush (United States Historic US Routes)
Post by: cl94 on August 27, 2019, 11:42:49 pm
Former US 66 in NM has the pre-1937 alignment signed on surface roads in a couple places not shown on TM:

- Santa Fe to I-25 Exit 339 follows the frontage road ("Old Las Vegas Highway" or "Frontage Road 2116") where it exists
- The old alignment in Albuquerque and south/West, following 4th Street, Bridge Blvd, and Isleta Blvd to NM 314, thence south to NM 6 and west along NM 6 to I-40. Yes, this means that all four legs of the Central/4th intersection in Downtown Albuquerque are signed as "Historic 66". I did NOT see if signs exist north/east of where 4th crosses I-40, but it is possible.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on August 28, 2019, 04:14:46 am
The old alignment in Albuquerque and south/West, following 4th Street, Bridge Blvd, and Isleta Blvd to NM 314, thence south to NM 6 and west along NM 6 to I-40. Yes, this means that all four legs of the Central/4th intersection in Downtown Albuquerque are signed as "Historic 66". I did NOT see if signs exist north/east of where 4th crosses I-40, but it is possible.
When the files were made, I couldn't see any signs between I-25/US550 and that Central/4th intersection. Nor any south of Central. There's also the issue that 4th disappears at the Civic Plaza. But that's because the GMSV wasn't that good/recent and I didn't know the route well enough to target my search in the right places.

edit: found a couple of signs at I-40/NM6 (https://www.google.co.uk/maps/@34.9846278,-107.1804135,3a,15.4y,116.81h,89.96t/data=!3m6!1e1!3m4!1sWeYLGzupPDD2Zh4ABA-X6A!2e0!7i16384!8i8192). There's this unhelpfully unarrowed one (https://www.google.co.uk/maps/@34.8075728,-106.7361843,3a,37.8y,121.49h,79.09t/data=!3m6!1e1!3m4!1sYinH7jp6G3VW1XwnCYIocA!2e0!7i13312!8i6656) at NM6/NM314. And another (https://www.google.co.uk/maps/@35.0527031,-106.6774947,3a,75y,49.12h,85.82t/data=!3m6!1e1!3m4!1sdQD1RnIp7GNwSmE5DKFvtQ!2e0!7i13312!8i6656) couple (https://www.google.co.uk/maps/@35.0685461,-106.6661457,3a,16.1y,269.83h,88.17t/data=!3m6!1e1!3m4!1sYL8ZeZ6ISVVfHIuUFMK6PA!2e0!7i13312!8i6656) where NM314 turns at either end of Isleta Blvd. Struggling to find anything on 4th or north other than at Central - which was the original problem.

Amarillo is another place where I've struggled to pin Historic 66: there's far too much going on.
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on August 28, 2019, 12:28:56 pm
Amarillo is another place where I've struggled to pin Historic 66: there's far too much going on.
Prominently signed on TXLp279, especially west of GeoSt.
Eastbound (https://www.google.com/maps/@35.2033119,-101.9046547,3a,15y,45.65h,90.89t/data=!3m9!1e1!3m7!1sbMgFac55eJXGrcQItGfOOQ!2e0!7i13312!8i6656!9m2!1b1!2i40) and westbound (https://www.google.com/maps/@35.2060157,-101.8992476,3a,15y,272.33h,94.02t/data=!3m10!1e1!3m8!1sqllzbMTHZeX19m5dg9vGuQ!2e0!6s%2F%2Fgeo2.ggpht.com%2Fcbk%3Fpanoid%3DqllzbMTHZeX19m5dg9vGuQ%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D337.38983%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656!9m2!1b1!2i40) at I-20BL, the turns are signed well enough (https://www.google.com/maps/@35.2061193,-101.9019297,3a,60.9y,282.72h,88.91t/data=!3m9!1e1!3m7!1sC3ZU2sjhy0Pr294VtjhfyQ!2e0!7i13312!8i6656!9m2!1b1!2i40) I suppose, if not at a complete 100% (https://www.google.com/maps/@35.2061236,-101.9024835,3a,43.4y,257.21h,88.04t/data=!3m9!1e1!3m7!1sLsxIOY7U9t0MYIUzf2dztQ!2e0!7i13312!8i6656!9m2!1b1!2i40).
Spotted some more signage (https://www.google.com/maps/@35.2097909,-101.8340123,3a,60.4y,28.39h,79.26t/data=!3m9!1e1!3m7!1sxhzBgZoJCQJpMqeFnJyLuA!2e0!7i13312!8i6656!9m2!1b1!2i40) on Fillmore AKA US87 AKA historic US66Bus (http://www.dot.state.tx.us/tpp/hwy/sl/sl0279.htm), but haven't looked beyond there because short attention span. I do know that at the I-20BL connector from US60 to I-40 Exit 85, signage is lacking.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on August 28, 2019, 01:04:29 pm
Amarillo is another place where I've struggled to pin Historic 66: there's far too much going on.
Prominently signed on TXLp279, especially west of GeoSt.
Eastbound (https://www.google.com/maps/@35.2033119,-101.9046547,3a,15y,45.65h,90.89t/data=!3m9!1e1!3m7!1sbMgFac55eJXGrcQItGfOOQ!2e0!7i13312!8i6656!9m2!1b1!2i40) and westbound (https://www.google.com/maps/@35.2060157,-101.8992476,3a,15y,272.33h,94.02t/data=!3m10!1e1!3m8!1sqllzbMTHZeX19m5dg9vGuQ!2e0!6s%2F%2Fgeo2.ggpht.com%2Fcbk%3Fpanoid%3DqllzbMTHZeX19m5dg9vGuQ%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D337.38983%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656!9m2!1b1!2i40) at I-20BL, the turns are signed well enough (https://www.google.com/maps/@35.2061193,-101.9019297,3a,60.9y,282.72h,88.91t/data=!3m9!1e1!3m7!1sC3ZU2sjhy0Pr294VtjhfyQ!2e0!7i13312!8i6656!9m2!1b1!2i40) I suppose, if not at a complete 100% (https://www.google.com/maps/@35.2061236,-101.9024835,3a,43.4y,257.21h,88.04t/data=!3m9!1e1!3m7!1sLsxIOY7U9t0MYIUzf2dztQ!2e0!7i13312!8i6656!9m2!1b1!2i40).
Spotted some more signage (https://www.google.com/maps/@35.2097909,-101.8340123,3a,60.4y,28.39h,79.26t/data=!3m9!1e1!3m7!1sxhzBgZoJCQJpMqeFnJyLuA!2e0!7i13312!8i6656!9m2!1b1!2i40) on Fillmore AKA US87 AKA historic US66Bus (http://www.dot.state.tx.us/tpp/hwy/sl/sl0279.htm), but haven't looked beyond there because short attention span. I do know that at the I-20BL connector from US60 to I-40 Exit 85, signage is lacking.
By 'far too much going on', I mean with signs in Amarillo.
Amarillo has started using proper signs (http://www.route66news.com/2018/06/07/new-route-66-signs-unveiled-in-amarillo/)

Someone has made a (not up-to-date) map (https://www.google.com/maps/d/viewer?mid=14-a8I0S1xWH9N-D3pIH8BRaET9o&ll=35.205715488146524%2C-101.81731130347293&z=12) 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.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on August 28, 2019, 01:11:13 pm
Let's document this 'PRE-1937' (as some signs banner it) alignment via Santa Fe in order to rejig parts that aren't quite right:

eastbound:
westbound:
I've tweaked the existing file to better match, but I've not chopped it (which might be an idea) up: https://github.com/TravelMapping/HighwayData/pull/3085
Title: Re: usaush (United States Historic US Routes)
Post by: mapmikey on August 28, 2019, 01:18:22 pm
Amarillo is another place where I've struggled to pin Historic 66: there's far too much going on.
Prominently signed on TXLp279, especially west of GeoSt.
Eastbound (https://www.google.com/maps/@35.2033119,-101.9046547,3a,15y,45.65h,90.89t/data=!3m9!1e1!3m7!1sbMgFac55eJXGrcQItGfOOQ!2e0!7i13312!8i6656!9m2!1b1!2i40) and westbound (https://www.google.com/maps/@35.2060157,-101.8992476,3a,15y,272.33h,94.02t/data=!3m10!1e1!3m8!1sqllzbMTHZeX19m5dg9vGuQ!2e0!6s%2F%2Fgeo2.ggpht.com%2Fcbk%3Fpanoid%3DqllzbMTHZeX19m5dg9vGuQ%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D337.38983%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656!9m2!1b1!2i40) at I-20BL, the turns are signed well enough (https://www.google.com/maps/@35.2061193,-101.9019297,3a,60.9y,282.72h,88.91t/data=!3m9!1e1!3m7!1sC3ZU2sjhy0Pr294VtjhfyQ!2e0!7i13312!8i6656!9m2!1b1!2i40) I suppose, if not at a complete 100% (https://www.google.com/maps/@35.2061236,-101.9024835,3a,43.4y,257.21h,88.04t/data=!3m9!1e1!3m7!1sLsxIOY7U9t0MYIUzf2dztQ!2e0!7i13312!8i6656!9m2!1b1!2i40).
Spotted some more signage (https://www.google.com/maps/@35.2097909,-101.8340123,3a,60.4y,28.39h,79.26t/data=!3m9!1e1!3m7!1sxhzBgZoJCQJpMqeFnJyLuA!2e0!7i13312!8i6656!9m2!1b1!2i40) on Fillmore AKA US87 AKA historic US66Bus (http://www.dot.state.tx.us/tpp/hwy/sl/sl0279.htm), but haven't looked beyond there because short attention span. I do know that at the I-20BL connector from US60 to I-40 Exit 85, signage is lacking.

Also posted on Amarillo Blvd. east of downtown - https://goo.gl/maps/5RwbqCkGDox1pNa26 and https://goo.gl/maps/xTGdyJrNXtV69zHQ9

Did not see anything EB past this back out to I-40
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on August 29, 2019, 04:27:22 am
Eastbound on I-40, this (https://www.google.com/maps/@35.1914096,-101.8876656,3a,16.9y,103.93h,92.68t/data=!3m6!1e1!3m4!1sIZbFultSuwvpbGHfjqgnkQ!2e0!7i13312!8i6656) and this (https://www.google.com/maps/@35.19447,-101.8703229,3a,37.3y,85.79h,97.23t/data=!3m7!1e1!3m5!1sVq8LIDRI_w1zcNSjb8h82g!2e0!5s20190401T000000!7i13312!8i6656) are where its signed - some way east of where Lp279 turns off I-40BL.

There's signage on Georgia Street, but not Western. Made a route goes on the frontage roads from exit 67 to 68B and up Georgia Street to Lp279, as well as the BL40-Lp279-US87-BL40 route.
Title: Re: usaush (United States Historic US Routes)
Post by: mapmikey on August 29, 2019, 09:41:13 am
Eastbound on I-40, this (https://www.google.com/maps/@35.1914096,-101.8876656,3a,16.9y,103.93h,92.68t/data=!3m6!1e1!3m4!1sIZbFultSuwvpbGHfjqgnkQ!2e0!7i13312!8i6656) and this (https://www.google.com/maps/@35.19447,-101.8703229,3a,37.3y,85.79h,97.23t/data=!3m7!1e1!3m5!1sVq8LIDRI_w1zcNSjb8h82g!2e0!5s20190401T000000!7i13312!8i6656) are where its signed - some way east of where Lp279 turns off I-40BL.

There's signage on Georgia Street, but not Western. Made a route goes on the frontage roads from exit 67 to 68B and up Georgia Street to Lp279, as well as the BL40-Lp279-US87-BL40 route.

The signage from I-40 at Georgia and Western is odd as neither of those streets has ever been part of US 66 as far as I can tell...?  The point of the signs is likely meant to be TO Historic US 66 as opposed to posting the actual historic route.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on August 29, 2019, 12:13:12 pm
The signage from I-40 at Georgia and Western is odd as neither of those streets has ever been part of US 66 as far as I can tell...?  The point of the signs is likely meant to be TO Historic US 66 as opposed to posting the actual historic route.
True, but there are no 'TO' banners at all, and if they were looking for 'TO' connections from I-40, you'd have thought signing eastbound before Western - most notably on the free-flow connection along I-40BL that's really rather short - would have surely made more sense.

It seems that the old signage along Georgia (https://www.google.co.uk/maps/@35.2059942,-101.8663163,3a,15y,5.63h,87.9t/data=!3m7!1e1!3m5!1sy7Ygy2_CepxWjxCvBaByOQ!2e0!5s20170201T000000!7i13312!8i6656) that the city had installed has gone, but that they signed it as if it was Historic US66, despite it never being such...
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on August 30, 2019, 08:37:05 am
The routing in the HB for US66HisChi in Springfield changed at the same time (https://github.com/TravelMapping/HighwayData/commit/51cedcb095481615911d2745fba787fb8c9895bd) that I-55BL was adjusted (June 23), but there's no updates entry for it, or any discussion here. Was the rerouting of Historic 66 confirmed in the field?
Title: Re: usaush (United States Historic US Routes)
Post by: michih on August 30, 2019, 09:24:59 am
but there's no updates entry for it

Because it's just a preview but not an active system?
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on August 30, 2019, 01:38:18 pm
Amarillo has started using proper signs (http://www.route66news.com/2018/06/07/new-route-66-signs-unveiled-in-amarillo/)

Someone has made a (not up-to-date) map (https://www.google.com/maps/d/viewer?mid=14-a8I0S1xWH9N-D3pIH8BRaET9o&ll=35.205715488146524%2C-101.81731130347293&z=12) 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.
A few more links found from surfing around from the first link. Saving for future reference.
https://www.thc.texas.gov/preserve/projects-and-programs/historic-texas-highways/route-66-texas
https://www.thc.texas.gov/historic-highways/route-66/explore-route-66
https://www.thc.texas.gov/preserve/projects-and-programs/historic-texas-highways/route-66/route-66-survey/route-66-maps
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on August 30, 2019, 01:44:11 pm
It seems that the old signage along Georgia (https://www.google.co.uk/maps/@35.2059942,-101.8663163,3a,15y,5.63h,87.9t/data=!3m7!1e1!3m5!1sy7Ygy2_CepxWjxCvBaByOQ!2e0!5s20170201T000000!7i13312!8i6656) that the city had installed has gone, but that they signed it as if it was Historic US66, despite it never being such...
Not gone, just relocated (https://www.google.co.uk/maps/@35.2069069,-101.8664176,3a,15y,47.18h,87.68t/data=!3m10!1e1!3m8!1s5QdYWebBb9_qVRoMzVZmzw!2e0!5s20181001T000000!7i13312!8i6656!9m2!1b1!2i40)...
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on August 31, 2019, 04:11:50 am
It seems that the old signage along Georgia (https://www.google.co.uk/maps/@35.2059942,-101.8663163,3a,15y,5.63h,87.9t/data=!3m7!1e1!3m5!1sy7Ygy2_CepxWjxCvBaByOQ!2e0!5s20170201T000000!7i13312!8i6656) that the city had installed has gone, but that they signed it as if it was Historic US66, despite it never being such...
Not gone, just relocated (https://www.google.co.uk/maps/@35.2069069,-101.8664176,3a,15y,47.18h,87.68t/data=!3m10!1e1!3m8!1s5QdYWebBb9_qVRoMzVZmzw!2e0!5s20181001T000000!7i13312!8i6656!9m2!1b1!2i40)...
Nah, that one was another one that was there, but isn't now (April 19 GMSV shows it gone).
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on September 05, 2019, 08:35:13 am
Speaking of signs that have gone. I was looking at Oklahoma City.

It seems like they have had a problem with signs on NW23rd being taken/removed:
September 2012 westbound at May (https://www.google.co.uk/maps/@35.4932114,-97.5651143,3a,38.8y,273.48h,85.57t/data=!3m7!1e1!3m5!1sD2P8fRG9wqBnGRtNyGdxnA!2e0!5s20120901T000000!7i13312!8i6656), March 2019 westbound at May (https://www.google.co.uk/maps/@35.4932095,-97.5651392,3a,46.8y,271.21h,85.17t/data=!3m7!1e1!3m5!1s2b51kO3Lqrb3YoZJTPPAzw!2e0!5s20190301T000000!7i13312!8i6656). February 2017 westbound at Classen (https://www.google.co.uk/maps/@35.4933154,-97.531296,3a,75y,279.21h,83.03t/data=!3m7!1e1!3m5!1sPspgajEVCuktRysa3ICwhw!2e0!5s20170201T000000!7i13312!8i6656), March 2019 westbound at Classen (https://www.google.co.uk/maps/@35.4933061,-97.5313098,3a,75y,279.21h,83.03t/data=!3m7!1e1!3m5!1soIpx3SViJJUVdvOBV5KWgw!2e0!5s20190301T000000!7i13312!8i6656).

They were never that good at signing it though. Here's where the signs I've found are (I'm going to document signs) and those other two are the only others I've found:
I-44 e/b approach at exit 124 (https://www.google.co.uk/maps/@35.5114291,-97.5714877,3a,31.6y,93.77h,84.96t/data=!3m6!1e1!3m4!1s4v0KKVv3pNeCSwgetI1fqA!2e0!7i13312!8i6656), May n/b at OK66 (https://www.google.co.uk/maps/@35.5117569,-97.5655783,3a,75y,38.69h,85.25t/data=!3m6!1e1!3m4!1s8CQDdlNwEdIbC8dJmxNZOA!2e0!7i13312!8i6656), NW23rd eastbound at Lincoln (https://www.google.co.uk/maps/@35.493141,-97.5067439,3a,39.6y,107.18h,86.14t/data=!3m6!1e1!3m4!1s68bH0UQYghMTvHV026npKA!2e0!7i13312!8i6656), I-44 eastbound between exits 128A and 128B (https://www.google.co.uk/maps/@35.5312949,-97.4991055,3a,75y,82.34h,89.38t/data=!3m6!1e1!3m4!1sD9czlXVi7cjgyEUpXBCzrQ!2e0!7i13312!8i6656), I-44 westbound between exits 128A and 128B (https://www.google.co.uk/maps/@35.5336617,-97.4965494,3a,75y,273.28h,86.66t/data=!3m6!1e1!3m4!1s-uKrptOTWImVASeDRofsBw!2e0!7i16384!8i8192), I-44 ramp eastbound at 128B (https://www.google.co.uk/maps/@35.5345048,-97.4945917,3a,34.6y,54.47h,89.53t/data=!3m6!1e1!3m4!1sjiNQZTgJ8YUQ_--0NjZxeg!2e0!7i13312!8i6656), US77 s/b ramp at Kelley Ave (https://www.google.co.uk/maps/@35.6123027,-97.4954913,3a,75y,254.25h,97.22t/data=!3m6!1e1!3m4!1sU-9e52rxib1-4YJh-VoFUQ!2e0!7i16384!8i8192), US77 s/b approaching Kelley Ave (https://www.google.co.uk/maps/@35.6167891,-97.491686,3a,41.4y,216.48h,83.12t/data=!3m6!1e1!3m4!1sHvFKna9JhDP63YxW1R4jFg!2e0!7i13312!8i6656), Broadway n/b approaching 2nd (https://www.google.co.uk/maps/@35.6518557,-97.4818118,3a,15y,47.76h,89.25t/data=!3m6!1e1!3m4!1sb71N7WCqe5sVGweaqN6aqg!2e0!7i13312!8i6656), 2nd w/b approaching Broadway (https://www.google.co.uk/maps/@35.6530362,-97.4791456,3a,47.6y,276.75h,87.66t/data=!3m6!1e1!3m4!1sKdNAFwv4mKL42140Y9C6ZA!2e0!7i13312!8i6656), 2nd west of I-35 (https://www.google.co.uk/maps/@35.6526762,-97.4302876,3a,16.2y,325.43h,88.46t/data=!3m6!1e1!3m4!1s9b_jILnlS_fatXOPToNs4Q!2e0!7i13312!8i6656).

What I can see is that OK state is relatively good at signing US66 Historic with the exception of in and around OK66 (when not concurrent with I-44). Cities are much more a mixed bag, and OK City is one of the worse ones - partially because the route is more complex than just 'the one main road through the town'.

Elk City has got signs that I must of missed initially (perhaps as they are all westbound): 1 (https://www.google.co.uk/maps/@35.4218956,-99.3738037,3a,75y,269.65h,86.09t/data=!3m6!1e1!3m4!1sAic_bpKLUgfzktxRUEZQ2A!2e0!7i13312!8i6656), 2 (https://www.google.co.uk/maps/@35.411773,-99.4039341,3a,42.6y,280.38h,90.25t/data=!3m6!1e1!3m4!1sEffId8KWsVNVoEG7B1s6Wg!2e0!7i13312!8i6656), 3 (https://www.google.co.uk/maps/@35.4118527,-99.4348493,3a,16.4y,262.34h,89.74t/data=!3m6!1e1!3m4!1sA4eQURqIm-Hn7AL2G6APIQ!2e0!7i13312!8i6656).

Also found signs in western OK as follows (west of El Reno) Near I-44 exit 50 (https://www.google.com/maps/@35.426902,-99.2133994,3a,75y,59.17h,87.33t/data=!3m6!1e1!3m4!1s0NwnIPWEaZjyANI4ss3llg!2e0!7i13312!8i6656), Erick 1 (https://www.google.com/maps/@35.2150208,-99.8666323,3a,50.8y,118.37h,87.26t/data=!3m7!1e1!3m5!1snD8dFALe6gP9q3iLQL7mQA!2e0!6s%2F%2Fgeo3.ggpht.com%2Fcbk%3Fpanoid%3DnD8dFALe6gP9q3iLQL7mQA%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D119.99108%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656), Erick 2 (https://www.google.com/maps/@35.2150208,-99.8666323,3a,50.8y,259.85h,85.01t/data=!3m7!1e1!3m5!1snD8dFALe6gP9q3iLQL7mQA!2e0!6s%2F%2Fgeo3.ggpht.com%2Fcbk%3Fpanoid%3DnD8dFALe6gP9q3iLQL7mQA%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D119.99108%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656), Erick towards Texola (https://www.google.com/maps/@35.215463,-99.9122136,3a,75y,330.35h,84.87t/data=!3m6!1e1!3m4!1sJ_2C-kBtE_d7qzauCeeM4A!2e0!7i13312!8i6656), I-40 BL in Sayre at Elm (https://www.google.com/maps/@35.2964839,-99.6401005,3a,34.2y,199.2h,81.56t/data=!3m6!1e1!3m4!1sMJqsrZ7986LA4MmLVQujCw!2e0!7i13312!8i6656), I-40 BL in Sayre at Pine (https://www.google.com/maps/@35.2981818,-99.6401126,3a,15y,34.05h,90.06t/data=!3m6!1e1!3m4!1sbhRl-3R_ezJs8MhfbbWt8Q!2e0!7i13312!8i6656), I-40 BL in Sayre at Washington (https://www.google.com/maps/@35.3064782,-99.6401132,3a,71.5y,190.89h,84.44t/data=!3m6!1e1!3m4!1sFnh5mjCLGIHm9pJGLPpkMQ!2e0!7i13312!8i6656)
frontage road between I-40 exits 61 and 62 (https://www.google.com/maps/@35.4796715,-99.0261106,3a,75y,315.5h,81.65t/data=!3m6!1e1!3m4!1sUmy_dAG8MgUTCfzj5ggyaA!2e0!7i13312!8i6656), road marking south of Clinton (https://www.google.com/maps/@35.4838723,-98.9798026,3a,26.8y,191.23h,83.67t/data=!3m7!1e1!3m5!1sw5ldcoK5HF-_c8i5VgD16Q!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3Dw5ldcoK5HF-_c8i5VgD16Q%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D112.82771%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656), on 10th in Clinton (https://www.google.com/maps/@35.5151507,-98.9720655,3a,24.4y,181.82h,84.83t/data=!3m6!1e1!3m4!1sEM1Y01XpZWlx4NIK71HXyA!2e0!7i13312!8i6656), on Gary in Clinton (https://www.google.com/maps/@35.5154022,-98.9684103,3a,75y,295.62h,86.66t/data=!3m6!1e1!3m4!1sAyzl4yqIwrsRgCEfa-wmwg!2e0!7i13312!8i6656), on OK54 west of Weatherford (https://www.google.com/maps/@35.5247824,-98.7156882,3a,75y,233.74h,69.34t/data=!3m6!1e1!3m4!1sa-PL3f2djyptofGqzwTscA!2e0!7i13312!8i6656), on I-40BL in Weatherford (https://www.google.com/maps/@35.5259569,-98.6952128,3a,75y,106.95h,78.37t/data=!3m6!1e1!3m4!1sovTMEuseDDHBH91vzewK2w!2e0!7i13312!8i6656), Main at Davis in Weatherford (https://www.google.com/maps/@35.5368418,-98.6764387,3a,38.9y,93.28h,86.22t/data=!3m6!1e1!3m4!1slg1osd7IgZNRWwAtZx1g8w!2e0!7i13312!8i6656), just west of OK58 (https://www.google.com/maps/@35.5368873,-98.5883966,3a,37.6y,85.63h,85.47t/data=!3m6!1e1!3m4!1sZbYHFDG7JW9EO9nkWwjtPg!2e0!7i13312!8i6656), just east of OK58 (https://www.google.com/maps/@35.5369403,-98.5705593,3a,25y,105.48h,80.01t/data=!3m6!1e1!3m4!1sajpZuO2zqq3_bQLyo_AgvA!2e0!7i13312!8i6656), at US281Spr (https://www.google.com/maps/@35.5366244,-98.2386816,3a,15.5y,105.65h,87.99t/data=!3m6!1e1!3m4!1sfrkrW8BitjYCfcfFkpP8bw!2e0!7i13312!8i6656)
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on September 06, 2019, 09:05:09 am
To document these - two standalone US6His signs in Ohio: Edgerton (https://www.google.com/maps/@41.4482967,-84.7480538,3a,75y,60.99h,91.72t/data=!3m6!1e1!3m4!1sbtCN3IxGzG0GY-5yBb0hJw!2e0!7i13312!8i6656) and, at the opposite end of the state, Andover (https://www.google.com/maps/@41.6071846,-80.5721966,3a,32.2y,131.43h,82.79t/data=!3m6!1e1!3m4!1s6I7P1rPTvbqIKuoxac3iYg!2e0!7i13312!8i6656).

See the Iowa thread for more US6 signs there

Nebraska has US6His signs off US6 either end of Gretna (Angus Road (https://www.google.com/maps/@41.1396175,-96.2401176,3a,75y,275.04h,92.38t/data=!3m6!1e1!3m4!1sF53Xnzsz3rPnw3q7hn2F0Q!2e0!7i13312!8i6656), 216th St (https://www.google.com/maps/@41.1335028,-96.2533796,3a,36.4y,63.33h,85.61t/data=!3m6!1e1!3m4!1sq76wRRhQ53sHVfiL1POJ3w!2e0!7i13312!8i6656).

Historic US80 is signed in places according to AA Roads - along AZ80 (with a detour or two) and from Tucson to US60
Title: Re: usaush (United States Historic US Routes)
Post by: osu-lsu on September 06, 2019, 11:28:13 am
There are two other stand along Historic US 6 signs on either end of Chardon, Ohio, as well.
(https://live.staticflickr.com/65535/48148451687_1a3036b07c_z.jpg)
(I only got the WB one, seen above)
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on September 06, 2019, 01:28:37 pm
(I only got the WB one, seen above)
I've found that one (near Grant Street), and here's (https://www.google.com/maps/@41.580692,-81.2268986,3a,39.2y,131.06h,82.06t/data=!3m6!1e1!3m4!1sbcMInkW5t3sMduH1GkEHRg!2e0!7i13312!8i6656) the eastbound one.
Title: Re: usaush (United States Historic US Routes)
Post by: michih on September 07, 2019, 07:37:06 am
What has happened instead with usaush is that with no single authoritative data source for it available, it has been languishing in limbo, routinely getting adjustments made as new information is found but never brought to a state of being "done" because there is no measuring stick by which to declare it done.

In this regard, the usaush system is effectively another example of "stupid truck routes".

Ergo, as I see it, we have two realistic options here:
- We need to realize that, without an authoritative data source, this system is lacking in officiality and go ahead and 86 it. Then it's no longer a problem.
- We need to realize that, without an authoritative data source, this system is never going to meet the usual threshold of being ready, and go ahead and promote it to active status. Then any further changes will get noted in updates and any waypoint relabelings will have their old labels preserved if in use, and we don't need to redefine anything about how preview systems are handled.

Since we still work on improving usaush, I guess that we tend to option 2? Is there anything left to be addressed before activation?

Or does anyone tend to option 1?
Title: Re: usaush (United States Historic US Routes)
Post by: froggie on September 07, 2019, 07:43:28 am
My personal viewpoint on Historic US Routes is Option 1.  There's no background system source, it seems to be shifting with the winds, and there's no consistency.  Worse than Truck routes in those regards.
Title: Re: usaush (United States Historic US Routes)
Post by: bejacob on September 07, 2019, 07:57:04 pm
My personal viewpoint on Historic US Routes is Option 1.  There's no background system source, it seems to be shifting with the winds, and there's no consistency.  Worse than Truck routes in those regards.

Seconded. While it's nice to be able to add some additional mileage, this entire system has been problematic from the beginning.
Here's an excerpt of my comments from 2 1/2 years ago.

Is the some sort of "official designation" by state DOTs for historic routes?
If not, who determines which routes are included?
How will we know if the route list is complete? Is there some "master" list?
What about routes that had different alignments over time?

This system just feels a bit slapdash especially if TM contributors are relying on "reports from the field" to make sure the route list is complete. Don't get me wrong. I appreciate the effort and will be glad to add any new routes to my list file. I'm just looking for a bit of clarity on this route system. It's still somewhat confusing as to the criteria for a route to be included.

Those comments were quickly shot down so I let it go. While I'd hate to lose the roughly 500 miles I've driven on these routes, my comments from Feb 2016 seem just as relevant today as they did then. As far as I can tell, if the route is signed (officially or otherwise) it gets included. Not a bad approach, but as others have also pointed out, there is no source material and no consistency.

I'd be fine if the system got activated as is or dropped. As the saying goes, "this decision is above my pay grade."
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on September 08, 2019, 02:13:17 am
this entire system has been problematic from the beginning.
The system hasn't been problematic, but Vogonish attitudes demanding paperwork in triplicate from governmental sources have been.

There were some creases (the US20 guy), but we've ironed them out now.
Title: Re: usaush (United States Historic US Routes)
Post by: bejacob on September 08, 2019, 12:22:40 pm
The system hasn't been problematic, but Vogonish attitudes demanding paperwork in triplicate from governmental sources have been.

Maybe I am confused as to why this page http://travelmapping.net/credits.php (http://travelmapping.net/credits.php) has so many governmental sources as references. I can't recall all the countless threads highlighting something official from state DOTs or the latest AASHTO meeting minutes. Correct my ignorance about whether national or regional systems need official sources before changes are made in the highway browser. This system won't have official sources. If no one cares, that's fine.

If it doesn't matter whether there is an underlying source, why has it been such a frequent topic of discussion?  I'm not trying to start an argument. I'm trying to understand.

As I said earlier, activate the system or kill it. I don't care either way.
Title: Re: usaush (United States Historic US Routes)
Post by: froggie on September 08, 2019, 09:02:58 pm
Someone remind me not to ask Si to recite his poetry...
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on September 08, 2019, 11:25:11 pm
Bypass.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on September 13, 2019, 05:07:09 am
Maybe I am confused as to why this page http://travelmapping.net/credits.php (http://travelmapping.net/credits.php) has so many governmental sources as references.
It's not the existence and use of Governmental sources for systems on this site that's an issue, but the demand for this system to be as sourced in the same way as them and if it can't be it should be ditched.

Absolutely, where Government sources exist and are helpful, go for it. However, just because something is different shouldn't mean its banishment. The problem with this system has always been the naysayers calling for its removal because it doesn't fit their preconceived notions. It's been far more work to deal with them than to hunt for signs, analysis the sometimes sparse data we have, etc.
Quote
This system won't have official sources. If no one cares, that's fine.
But you and froggie do care - "There's no background system source" is your complaint.

Are you saying you are revoking your objection? If so, great!
Someone remind me not to ask Si to recite his poetry...
My poetry is shite, but not as bad as you reading comprehension - its clear that I'm describing others as Vogons here.

I've found some stuff from official sources to appease the Vogons. I doubt it will be enough, but:
AZ: AZ DOT Map with US66 His and US89A His mapped (https://azdot.gov/sites/default/files/2019/05/scenic-map.pdf), US80 His signage discussed by ADOT (with map) (http://aztransportationboard.gov/downloads/Presentations/2018-092118-US80-Recommendations.pdf)
CA: pretty hopeless getting explicitly DOT sources - its just hobbyist/business group sites. There's some legislative designations, but only for US80 (http://www.leginfo.ca.gov/pub/05-06/bill/asm/ab_0101-0150/acr_123_bill_20060816_chaptered.html) (I think US66 in the state has some federal legislation), AFAICS
IA: the DOT site "can't be reached"
IL: US66 His map (http://idot.illinois.gov/Assets/uploads/files/Travel-Information/Maps-&-Charts/Scenic-Byways/HISTORIC%20ROUTE%2066.pdf) (a more interactive one here (http://idot.illinois.gov/travel-information/tourism/scenic-byways/index))
MO: MO DOT: Historic Route 66 Scenic Byways (https://www.modot.org/historic-route-66-scenic-byways)
OK: OK DOT: Route 66 Maps (http://www.okladot.state.ok.us/memorial/route66/route66maps.htm)
TX: TX THC Route 66 2018 survey (https://www.thc.texas.gov/preserve/projects-and-programs/historic-texas-highways/route-66/route-66-survey/route-66-maps)

Of course, a lot of stuff is done at the county/city level as well. I can't be bothered to find these as more general sources - wikipedia, tile mapping, etc provided enough information for my (what wikipedia would call) 'original research'. There's perhaps nothing in the above sources that add anything, but I'll cite them anyway. We don't seem to add newspapers as sources for openings, so we shouldn't for announcements about signage being posted - those (and contributor field reports), while invaluable, won't get added to the sources list.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on September 13, 2019, 07:09:37 am
From the US6 Historic (Durant) thread (http://forum.travelmapping.net/index.php?topic=3174.0). Just because it deals with some general stuff (namely obstacles, banners and along the existing route).
The problem with the McPherson alignment is that there's now an airport runway in the way. Going all the way out on McPherson would result in two dead-ends. Now that 6 has been removed from Broadway in CB, I can creating a segment from I-480 to I-80 - but then does the on-Kanesville off-Broadway segment get included, omitted, or is there a second file? (That is, the piece currently there becomes "US 6 (Historic)(1934-82)"
We're not following what is the actual historic alignment, but what is signed as such (and AFAICS, this bit isn't signed). This isn't a documentation of the past alignment, but a documentation of the present. Certainly with 66 there's cases where the signed route is on the wrong frontage road as the freeway chopped the original roadway in two.

Date banners only should be used if they are on the actual signs (and I've dropped some when including them in a larger route).
Quote
I doubt that Historic 6 signs will be placed in Des Moines, since it's still alive on the post-1934 Hickman/Euclid alignment and this seems ripe for ROW/maintenance issues.
Sure - we're only included signed sections, so if it doesn't get signed, even if designated (I believe US6 in Iowa
Quote
Extension to/past Grinnell: Would completely overlap existing 6. (This is historically accurate, as the River-to-River Route in Grinnell followed 4th Avenue instead but almost certainly was moved to 6th when US 32 was paved in 1928.)

<snip>

Overall, I believe only Cass and Poweshiek counties specifically put up Historic 6 shields where it overlaps the existing route. Everywhere else, it's marked only where current 6 is not. I don't see any Historic 6 shields in West Liberty, for example.

I believe it is best to stick with segments of Historic 6 where it is NOT overlapping the modern route. For example, the Atlantic segment should end at the 71/83 intersection, because right now it's redundant to Oakland.
I agree it is stupid to sign Historic 6 on current 6 (unless for short bits linking sections off US6, such as that brief bit leaving Davenport). But it is signed, so surely we include it?

Also, Pottawattamie County signs it along vanilla US6 (at least partially): 1 (https://www.google.co.uk/maps/@41.2889578,-95.4038282,3a,75y,298.36h,80.38t/data=!3m6!1e1!3m4!1sR6BwDlkSEcaW4sMiEl1twg!2e0!7i13312!8i6656), 2 (https://www.google.co.uk/maps/@41.2889618,-95.4039325,3a,75y,129.5h,72.06t/data=!3m6!1e1!3m4!1sUJFIBhWfLYGaFlfMhBx-Eg!2e0!7i13312!8i6656),3 (https://www.google.co.uk/maps/@41.2891142,-95.403462,3a,75y,6.49h,80.81t/data=!3m6!1e1!3m4!1siTqlE__dS3rlsgiLuE6jNg!2e0!7i13312!8i6656), 4 (https://www.google.co.uk/maps/@41.2895234,-95.4034588,3a,28.8y,213.3h,79.33t/data=!3m6!1e1!3m4!1s6QgOig-3uEK-YReTWshUxQ!2e0!7i13312!8i6656), 5 (https://www.google.co.uk/maps/@41.3176388,-95.3851111,3a,36.5y,315.69h,84.47t/data=!3m6!1e1!3m4!1sFxMuuLP3nJIP8YdsEmDbZg!2e0!7i13312!8i6656)
Title: Re: usaush (United States Historic US Routes)
Post by: bejacob on September 13, 2019, 01:08:48 pm
This system won't have official sources. If no one cares, that's fine.
But you and froggie do care - "There's no background system source" is your complaint.

Are you saying you are revoking your objection? If so, great!

If sources aren't needed, then yes, I revoke my objection.

Do you believe the system is ready for activation?
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on September 14, 2019, 08:57:48 am
Do you believe the system is ready for activation?
Not quite - it needs a formal review first, but given the number of reviews ongoing (including of my system), it won't be this month that I ask for it. Not least as I've not finished the checking to make sure it's ready.

I expect we can activate before the end of the year though!
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on September 14, 2019, 10:23:13 am
Nebraska has US6His signs off US6 either end of Gretna (Angus Road (https://www.google.com/maps/@41.1396175,-96.2401176,3a,75y,275.04h,92.38t/data=!3m6!1e1!3m4!1sF53Xnzsz3rPnw3q7hn2F0Q!2e0!7i13312!8i6656), 216th St (https://www.google.com/maps/@41.1335028,-96.2533796,3a,36.4y,63.33h,85.61t/data=!3m6!1e1!3m4!1sq76wRRhQ53sHVfiL1POJ3w!2e0!7i13312!8i6656).
I see you've already got it in the HB. Fair play.
I would have used that same routing, because:
 • the main thru alignment curving around the corner at 216thSt_N and SouSt_E
 • this avoids 2 at-grade RXRs
 • in satellite view, McKenna Ave does look like the business center of town's main street
...but not been 100% confident in it.
I don't see signage in GMSV for any of the turns. (Ecch, this is like, cannss-level lack of clarity...)
Si, do you have any sources on the alignment/turns, or did you just come to pretty much the same conclusions I did?
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on September 14, 2019, 01:39:25 pm
Si, do you have any sources on the alignment/turns, or did you just come to pretty much the same conclusions I did?
The latter.
Title: Re: usaush (United States Historic US Routes)
Post by: Highway63 on September 15, 2019, 01:26:38 pm
I agree it is stupid to sign Historic 6 on current 6 (unless for short bits linking sections off US6, such as that brief bit leaving Davenport). But it is signed, so surely we include it?
Not as long as it's entirely redundant, because we don't know where the endpoint should be.

Quote
Also, Pottawattamie County signs it along vanilla US6 (at least partially): 1 (https://www.google.co.uk/maps/@41.2889578,-95.4038282,3a,75y,298.36h,80.38t/data=!3m6!1e1!3m4!1sR6BwDlkSEcaW4sMiEl1twg!2e0!7i13312!8i6656), 2 (https://www.google.co.uk/maps/@41.2889618,-95.4039325,3a,75y,129.5h,72.06t/data=!3m6!1e1!3m4!1sUJFIBhWfLYGaFlfMhBx-Eg!2e0!7i13312!8i6656),3 (https://www.google.co.uk/maps/@41.2891142,-95.403462,3a,75y,6.49h,80.81t/data=!3m6!1e1!3m4!1siTqlE__dS3rlsgiLuE6jNg!2e0!7i13312!8i6656), 4 (https://www.google.co.uk/maps/@41.2895234,-95.4034588,3a,28.8y,213.3h,79.33t/data=!3m6!1e1!3m4!1s6QgOig-3uEK-YReTWshUxQ!2e0!7i13312!8i6656), 5 (https://www.google.co.uk/maps/@41.3176388,-95.3851111,3a,36.5y,315.69h,84.47t/data=!3m6!1e1!3m4!1sFxMuuLP3nJIP8YdsEmDbZg!2e0!7i13312!8i6656)
All of those pictures, save for one that's two miles away, are at the same intersection. Historic 6 is not marked with reassurance signs elsewhere in the county. It's a bare-minimum required for the one turn 6 makes there. Between there and Atlantic, the only sign is at IA 48. It's not signed at the IA 83 or south US 71 intersections, which makes me think I was wrong in saying that Cass does the whole thing.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on September 15, 2019, 02:37:18 pm
I agree it is stupid to sign Historic 6 on current 6 (unless for short bits linking sections off US6, such as that brief bit leaving Davenport). But it is signed, so surely we include it?
Not as long as it's entirely redundant, because we don't know where the endpoint should be.
The next waypoint after the signs run out? It might not be massively accurate, but it's better than nothing. We don't want to throw in points for city/county line because one city/county decides to sign and one doesn't - easier just to end it at the next highway. And the end points are arguably state lines, the current route, or a parallel interstate (depending on what state, what route, etc), just with large sections that aren't signed that we're not including.

Or we could go with a logical terminus concept - so, in the absence of info to the contrary, the route stops at the next major junction (similar to what you have asked for in OK extending routes to a more logical terminus like another route) rather than some minor road that happens to be the next point along.
Quote
All of those pictures, save for one that's two miles away, are at the same intersection. Historic 6 is not marked with reassurance signs elsewhere in the county. It's a bare-minimum required for the one turn 6 makes there.
True, they merely sign one interchange well, and put one other sign, but - as you say - they clear that bar of 'bear minimum'.

I was replying to "I believe only Cass and Poweshiek counties specifically put up Historic 6 shields where it overlaps the existing route." and said that Pottawattamie County "signs it along vanilla US6 (at least partially)" - that's surely undeniable.

Additionally, I don't see why it has to be signed loads. Especially as you take the opposite view for US66 and asked for it to extend through 4 TOTSOs with US281/US281Spr despite just one sign for all that navigation - a reassurance one just off US281Spr (where El Reno's section begins):
OK US 66 Weatherford: Again, wondering about the abrupt stop for the east end. I would encourage extending this to join El Reno's Hist 66.
But I'd be fine with chopping historic routes at their parent when there is a long signed (at least partially) concurrency with them, despite the existence of signs. Ditto not including sections entirely concurrent with their parent. I'd prefer to include such sections, despite them being silly, but...
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on September 28, 2019, 08:30:00 am
Not quite - it needs a formal review first, but given the number of reviews ongoing (including of my system), it won't be this month that I ask for it. Not least as I've not finished the checking to make sure it's ready.
Well, I was wrong, it is this month!

This system is ready for review.  :D

As well as the classic review, I'd like comment about routes in their states from those who will maintain them (if they haven't given them already):
CA, NM - oscar
GA - ntallyn
IA, IL, MO - Highway63
KS, MA, NE, OK, TX - yakra
OH - mapcat
OR - Bickendan
WA - compdude787
Title: Re: usaush (United States Historic US Routes)
Post by: Bickendan on September 29, 2019, 03:05:00 pm
Only things on Oregon's side is dropping 99 Myrtle Creek and adding 30 Cascade Locks and 30 Columbia River Gorge extension.
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on September 30, 2019, 06:13:34 am
ca.us080hisjac: McCainVlyRd -> McCVlyRd or McCValRd
Title: Re: usaush (United States Historic US Routes)
Post by: oscar on September 30, 2019, 06:32:50 am
ca.us080hisjac: McCainVlyRd -> McCVlyRd or McCValRd

I'd prefer McCValRd. "Val" is the abbreviation for "Valley" used for other California routes.

For ca.us080hiswin, CHS24 => CRS24 (reversion to the standard CR abbreviation for signed county routes is underway for other California routes). Similar change for any other CH__ labels in California historic route files, though I'm not sure there are any.

In general, many waypoints will need to be re-synched with intersecting/concurrent California Interstate/US/state routes. usaush was drafted while California routes were being extensively overhauled, with lots of changes made to their waypoint coordinates. Those coordinates now are stable (if you spot any that need to be changed, please reset them and let me know what needs to be changed in the non-historic routes).

I'll do a more complete look at CA and NM historic routes when I have more time.
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on September 30, 2019, 07:43:57 am

As well as the classic review, I'd like comment about routes in their states from those who will maintain them (if they haven't given them already):
OH - mapcat

US 6 in Chardon looks good. Silly, since it is marked along a few blocks of current US 6, but it's marked.
US 20 in the Painesville: I only found one marker (westbound in the westernmost segment). How did you determine the eastern end?

There is also a Historic 20 marker in Norwalk here (https://www.google.com/maps/@41.2322293,-82.6411615,3a,75y,99.59h,89.13t/data=!3m6!1e1!3m4!1sw_RHbhKNRMRkINoTonoDRw!2e0!7i13312!8i6656) (2018 imagery). I believe that you had included a Norwalk segment at some point in the past but deleted it. Here's one in Monroeville (https://www.google.com/maps/@41.236257,-82.6897362,3a,75y,264.35h,90.5t/data=!3m7!1e1!3m5!1sZmZ9zqDZF1PNLmOko_rYaA!2e0!5s20180901T000000!7i13312!8i6656) too. I'm not saying you need to add segments in either place, just attempting to be complete.
Title: Re: usaush (United States Historic US Routes)
Post by: mapcat on September 30, 2019, 07:45:31 am
@Highway63, could you address why you relocated Historic US66 in downtown Springfield IL when you adjusted the routing of I-55BL? Did the 66 signs move too?
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on September 30, 2019, 10:52:48 am
US 20 in the Painesville: I only found one marker (westbound in the westernmost segment). How did you determine the eastern end?
eastbound signs:
approaching intersection with Shankland (https://www.google.co.uk/maps/@41.6291868,-81.4201028,3a,90y,112.46h,79.74t/data=!3m6!1e1!3m4!1sKriuR6zzd6rRx-iDrIkbkg!2e0!7i13312!8i6656) (about halfway along OH91<->OH174 segment)

westbound signs: outside Champs Barber-Stylists (https://www.google.co.uk/maps/@41.7914534,-81.1065866,3a,39.5y,267.03h,82.14t/data=!3m6!1e1!3m4!1swUhyM3nw9cm1_7fyGxTqpA!2e0!7i13312!8i6656) (just after Townline Road, halfway between OH528 and CenRd)
outside Rider's Inn (https://www.google.co.uk/maps/@41.7129223,-81.2600095,3a,75y,244.37h,90.65t/data=!3m6!1e1!3m4!1srhs3mnbyo56aoAOGdXsInQ!2e0!7i16384!8i8192) (between OH615 and OH44).

Apparently, the City of Mentor (http://cityofmentor.com/along-historic-us-route-20/) have signed it, but I've not found those signs! Nor have I found this sign (http://lakehistorycenter.org/wp-content/uploads/2017/08/LCHS_Aug17.pdf) (which I believe is in North Perry[/url]. And I can't read this article (https://www.news-herald.com/news/ohio/route-in-eastern-lake-county-has-officials-wary/article_7d3e2765-d7be-51f8-9527-f809f54cad12.html) as the EU is a corporatist and protectionist racket creating regulations that small and foreign (and especially both) businesses cannot afford to comply with.


As it's entirely concurrent with US20, it doesn't have to be kept (ditto the US6 ones). Pretty sure those Monroeville and Norwalk ones were '86ed in the purge of US20, but updated Streetview is a boost. Got confirmation of the Norwalk sign that created that route (which included Monroeville): at Main and Church (https://www.google.com/maps/@41.2413541,-82.6177009,3a,15.1y,96.69h,87.77t/data=!3m6!1e1!3m4!1sRpV9RJ3dE62QEJSBAgBOIw!2e0!7i13312!8i6656). The file is still there. I'll modify it as I had it crossing the county and so ends are loose.
Title: Re: usaush (United States Historic US Routes)
Post by: yakra on October 06, 2019, 12:01:10 pm
Stats restricted to systems/regions/etc of interest (http://forum.travelmapping.net/index.php?topic=3247) topic split per Jim's suggestion on GitHub (https://github.com/TravelMapping/Web/issues/360).
Title: Re: usaush (United States Historic US Routes)
Post by: Highway63 on October 08, 2019, 06:36:48 pm
@Highway63, could you address why you relocated Historic US66 in downtown Springfield IL when you adjusted the routing of I-55BL? Did the 66 signs move too?
Per the AASHTO filing:

Quote
The proposed relocation is necessitated by the City of Springfield’s Rail Improvement Project which includes the construction of a railroad underpass near the current Business Route 55 designation (9th St. and Laurel St.). This proposed underpass will require ending the 9th St. pavement that currently carries the Business Route 55 designation. This proposed relocation also places more of the business route within the downtown Springfield business district. Please note the relocated route marking will be placed on streets under the jurisdiction of the City of Springfield.

Unless Illinois is going to dead-end the 66 signage it makes no sense that signs wouldn't be relocated as well.  The closest alternative I would see is to move the northbound-only east-west section to Laurel Street assuming the Laurel/9th intersection remained intact. If someone goes to Springfield AFTER the underpass project is done and sees 66 split from the redirected BL 55 and stay on 9th to some point, I'll change it back.
Title: Re: usaush: United States Historic US Routes
Post by: michih on December 31, 2019, 03:03:15 am
There is a duplicate label error in OH which cannot be used:

http://travelmapping.net/devel/datacheck.php?show=DUPLICATE_LABEL&sys=usaush
Title: Re: usaush: United States Historic US Routes
Post by: mapcat on December 31, 2019, 06:08:44 pm
There is a duplicate label error in OH which cannot be used:

http://travelmapping.net/devel/datacheck.php?show=DUPLICATE_LABEL&sys=usaush
Changed in my local copy.
Title: Re: usaush: United States Historic US Routes
Post by: si404 on December 31, 2019, 06:17:56 pm
There is a duplicate label error in OH which cannot be used:

http://travelmapping.net/devel/datacheck.php?show=DUPLICATE_LABEL&sys=usaush
Changed in my local copy.
Oh, I did it as well. Might have a conflict. Go with Mapcat's if there is one.
Title: Re: usaush: United States Historic US Routes
Post by: mapcat on December 31, 2019, 10:21:23 pm
Oh, I did it as well. Might have a conflict. Go with Mapcat's if there is one.
Shouldn't be, since I didn't submit a pull request yet, and yours has already been merged. Or was this not part of what you did on the 31st?
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 18, 2020, 11:16:19 am
I might as well go through and review these.

Arizona
US 66hisash: "Old Route 66" is signed along 8thSt (https://www.google.com/maps/@35.2248523,-112.4882581,3a,38y,288.45h,78.41t/data=!3m6!1e1!3m4!1slCLZuX2WmEk04BQujYKeTQ!2e0!7i13312!8i6656) from both directions of the business loop. Add this as a spur?
US 66hisfla/I-40blfla: EntRd -> PonPkwy (https://www.google.com/maps/@35.1950665,-111.6283701,3a,41.1y,91.73h,89.79t/data=!3m6!1e1!3m4!1s4oxc-nQgvc3zAPONQFiuvQ!2e0!7i13312!8i6656)
US 66hisfla: 4thSt_Fla -> 4thSt
US 66hisfla: US89_N -> US89/180?
US 66hisjos: extend west to I-40(269) (https://www.google.com/maps/@34.9570424,-110.3500456,3a,38.8y,293.75h,87.32t/data=!3m6!1e1!3m4!1sFcD49chFcX9h-1Hc5NpxKg!2e0!7i13312!8i6656)? I don't see anything at that exit, however (but the same is true with I-40(204) at the east end of US 66hisfla).
US 66hiskin: CR1 -> PowLakeRd and move north
US 66hiskin: OatRd -> CR153 (https://www.google.com/maps/@35.0002737,-114.408609,3a,25.1y,274.25h,79.9t/data=!3m6!1e1!3m4!1sX4CKJpgP1uGTTe-8EHeGUQ!2e0!7i13312!8i6656)
US 66hiskin: Oat -> QuaDr (https://www.google.com/maps/@35.0256846,-114.3825236,3a,30y,191h,84.45t/data=!3m6!1e1!3m4!1s1ad-q3k-4GwkFF67QwsyQg!2e0!7i13312!8i6656)
US 66hiskin: QuaDr -> QuaRd (but is this point necessary?)
US 66hiskin: AcqDr -> AquDr
US 66hiskin: ShiRd -> CR223 (https://www.google.com/maps/@35.1391325,-114.1071671,3a,15y,335.17h,86.46t/data=!3m6!1e1!3m4!1s92MrZ0IQDWpIaoHu-X0gRA!2e0!7i13312!8i6656)
US 66hiskin: 4thSt_Kin -> 4thSt
US 66hiskin/AZ 66: move MolLn west (https://www.google.com/maps/@35.4853969,-113.5622947,3a,15.6y,357.22h,85.98t/data=!3m6!1e1!3m4!1sirRoq_nbb7C5vmH7GIJT9Q!2e0!7i13312!8i6656)
US 66hiskin/AZ 66: move HydeParkRd northwest a bit
US 66hiskin: there's nothing at Aud except a random ranch driveway; replace with a necessary shaping point to the east
I-40blsel: ChiSt_* -> US66His_*
US 66hiskin/I-40blsel: 1stAve -> 1stSt (https://www.google.com/maps/@35.3269632,-112.8770119,3a,34.8y,331.05h,89.25t/data=!3m6!1e1!3m4!1sWGeGbAx4gccRPOG60d0sDQ!2e0!7i13312!8i6656)
US 66hiskin: RdL-43 is a gated gravel driveway (https://www.google.com/maps/@35.312583,-112.8109699,3a,43.1y,357.14h,83.79t/data=!3m6!1e1!3m4!1saE2WBpmfaF837f0jbRXlNg!2e0!7i13312!8i6656)
US 66hislup does not appear to be signed.
US 66hiswil/I-40blwil: GraCanBlvd -> 2ndSt (https://www.google.com/maps/@35.2504662,-112.1883927,3a,20.4y,105.81h,88.55t/data=!3m6!1e1!3m4!1sQfsh7g2hDrbnrQoh7u9mPg!2e0!7i13312!8i6656)
US 66hiswin/I-40blwin: AZ87_S -> AZ87/99

US 80hisdou/I-10blben: PatAve -> PatSt (https://www.google.com/maps/@31.9685585,-110.2974264,3a,75y,301.66h,76.79t/data=!3m6!1e1!3m4!1s6w2HzSN25OijJlkOkgksdQ!2e0!7i13312!8i6656)
US 80hisdou/AZ 80: PatSt -> PatSt_E
US 80hisdou/AZ 80: HorRanRd -> DraMouRan (https://www.google.com/maps/@31.87697,-110.2109455,3a,22y,108.53h,85.31t/data=!3m6!1e1!3m4!1sQNgkAEE8NJ1uYNZQu9xN9A!2e0!7i13312!8i6656)? or move somewhere that's not gated?
US 80hisdou/AZ 80: MainSt -> NacoRd (https://www.google.com/maps/@31.4417339,-109.913518,3a,15y,45.39h,87.62t/data=!3m6!1e1!3m4!1sYW7QIPFbL35iTpTJtolxdg!2e0!7i13312!8i6656)
US 80hisdou: US191_S -> US191/80?
US 80hisdou: 10St_W -> 10thSt_W - but how sure are we that it uses 10th Street? this is how US 80 went, but I can't find any signs at either turn in May 2019 GSV
US 80hisdou: LesCanRd -> AZ80_W?
US 80hisdou/AZ 80: DriWay is a blocked-off driveway (https://www.google.com/maps/@31.3758092,-109.522957,3a,22.6y,116.34h,78.86t/data=!3m6!1e1!3m4!1skrGnw2kjn-vg3NIPryS0FQ!2e0!7i13312!8i6656); move west to WasAve?
US 80hisdou/AZ 80: move PerSt northeast
US 80hisdou/AZ 80: KheRd doesn't exist
US 80hisdou/AZ 80: there's practically nothing at Ber
US 80hisdou/AZ 80: TexCanRd -> RucCanRd (https://www.google.com/maps/@31.5934456,-109.2399431,3a,44y,93.77h,80.46t/data=!3m6!1e1!3m4!1spSsyjDCqHqxJM8bxX1Wucw!2e0!7i3328!8i1664)
US 80hisflo: US60(212) -> US60
US 80hisflo/AZ 79: GasLineRd is fenced (https://www.google.com/maps/@33.1895921,-111.3505263,3a,15y,88.11h,84.14t/data=!3m6!1e1!3m4!1s8v9_iwJxVOn-WeZ8umdc3A!2e0!7i13312!8i6656); move south to CotCanRd
AZ 287's east end is at 79busflo, so AZ79Bus_S -> AZ79Bus and delete the last two entries
US 80hisflo: AZ79/287 -> AZ79_S, AZ79/79Bus -> AZ79_N (and move northeast)
AZ 79: AZ79Bus -> AZ79Bus_S, AZ79Bus/287 -> AZ79Bus_N
US 80hisflo/AZ 79busflo: AZ287_W -> AZ287
US 80hisflo: do we have confirmation that it uses AZ 79busflo? by 1965 (USGS), US 80 was on modern 79, and US 80 Business used Ruggles rather than Butte
US 80hisflo/AZ 79: MarRd doesn't exist; move north to AnyaWay (https://www.google.com/maps/@32.7455358,-111.1283062,3a,20y,18.82h,87.72t/data=!3m6!1e1!3m4!1s4Pj2zB5cETubGyFKTxeE4g!2e0!7i13312!8i6656)
US 80hisflo/AZ 79: ChiButRd -> PaloVerRd (https://www.google.com/maps/@32.6282554,-111.0023351,3a,15y,174.26h,87.57t/data=!3m6!1e1!3m4!1sBA_5CQQLEuSkPv4vrCBzvg!2e0!7i13312!8i6656) and move north
US 80hisflo: AZ77/79 -> AZ77_N
US 80hismar: do we have confirmation of signage? I can't find any in May 2019 GSV
US 80hismor: ditto (and rename it Dateland if it exists?)
US 80hismor: add OldHwy80_W near the west end
US 80hismor: shift I-8(73) north
US 80hisphe: WTF? this overlaps US 80hisflo; do we have confirmation of signage anywhere but Tucson-Florence Junction?
US 80hiswel: ditto (signage?)
US 80hiswel: WelSt -> WilSt
US 80hiswel: move I-8(54) west to the underpass
US 80hisyum: ditto (signage?)
US 80hisyum/I-8blyum: HarGisPkwy -> GissPkwy (https://www.google.com/maps/@32.7215931,-114.6245391,3a,51.9y,42.72h,89.99t/data=!3m6!1e1!3m4!1s--xcmygVLwmneOATlrVPkQ!2e0!7i16384!8i8192)
US 80hisyum/I-8blyum: 32ndSt -> 32ndSt_W
US 80hisyum/I-8blyum: move I-8(9) west to the underpass
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 18, 2020, 04:44:18 pm
California
US 6hissan: US99His_N -> US99His
US 6hissan: ClaRd doesn't exist
US 6hissan: add a point at CA14(6A)
US 6hissan: RowCanRd is a private driveway (https://www.google.com/maps/@34.5013587,-118.3809739,3a,19.1y,333.51h,82.3t/data=!3m6!1e1!3m4!1s3ToKi1RtiPrQCYtJOOYd7w!2e0!7i16384!8i8192); move south to RushCanRd
US 6hissan: ShaLaneRd -> ShaLn (https://www.google.com/maps/@34.5162283,-118.2766256,3a,32.5y,146.23h,93.02t/data=!3m6!1e1!3m4!1seoF5MePwZVQsUD4nFr7sZg!2e0!7i16384!8i8192)
US 6hissan: +x22 is unnecessary
US 6hissan: OldSieHwy -> OldSieHwy_E
US 6hissan: AngForHwy -> CRN3? I can't find any signs here though
US 6hissan: AveJ -> CRN5? I can't find any signs here though
US 6hissan: are there any signs past AveA, the county line? If not, truncate it there. If so, truncate it to End (https://www.google.com/maps/@35.0000933,-118.1576436,3a,39.3y,348.01h,81.98t/data=!3m6!1e1!3m4!1sL3L53W5V8BT50HpJxk7Pwg!2e0!7i13312!8i6656).
Title: Re: usaush: United States Historic US Routes
Post by: oscar on January 18, 2020, 07:38:54 pm
California
US 6hissan: add a point at CA14(6A)

If you're referring to the direct Sierra Hwy, ramps to/from CA 14, that intersection with the Sierra Highway is really, really close to the existing ViaPri waypoint. I'm also treating those ramps on CA 14 as part of the CA14(6) interchange, even though NB CA 14 has separate 6A (Sierra Hwy.) and 6B (Via Princessa) ramp numbers, so there is no separate 6A point.

Quote
US 6hissan: are there any signs past AveA, the county line? If not, truncate it there. If so, truncate it to End (https://www.google.com/maps/@35.0000933,-118.1576436,3a,39.3y,348.01h,81.98t/data=!3m6!1e1!3m4!1sL3L53W5V8BT50HpJxk7Pwg!2e0!7i13312!8i6656).

If there is no signage on the ~20% north of the county line, that doesn't mean it isn't part of the historic route. I think the signage south of the county line is enough to treat the entire route (to the extent still open to traffic) as signed for our purposes. Especially since historic route fans may be interested in clinching as much of the entire old route as still exists, even if only part has historic route signage.

(I'm not one of those people -- I traveled almost all of the route while figuring out what to do with CA 14U, and contributed my updated route file to usaush before ultimately truncating away most of it for CA 14U.)

In California, as I'm sure you've noticed in your usaca peer review, there are routes signed only in the middle like CA 153, or only at one end.
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 18, 2020, 07:51:42 pm
US 6hissan: are there any signs past AveA, the county line? If not, truncate it there. If so, truncate it to End (https://www.google.com/maps/@35.0000933,-118.1576436,3a,39.3y,348.01h,81.98t/data=!3m6!1e1!3m4!1sL3L53W5V8BT50HpJxk7Pwg!2e0!7i13312!8i6656).

If there is no signage on the ~20% north of the county line, that doesn't mean it isn't part of the historic route. I think the signage south of the county line is enough to treat the entire route (to the extent still open to traffic) as signed for our purposes. Especially since historic route fans may be interested in clinching as much of the entire old route as still exists, even if only part has historic route signage.

(I'm not one of those people -- I traveled almost all of the route while figuring out what to do with CA 14U, and contributed my updated route file to usaush before ultimately truncating away most of it for CA 14U.)

In California, as I'm sure you've noticed in your usaca peer review, there are routes signed only in the middle like CA 153, or only at one end.
There's a big difference when the local governments are responsible for signage. If Kern County hasn't installed signs, and there are none posted by others in Kern County, that portion doesn't belong here.
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 19, 2020, 10:30:05 am
US 40hisaub: yeah. That west end. As far as I can tell, the only "eastbound" signage in that area is on Lincoln Way. If you follow the signs westbound, you do in fact end up making a loop, turning right on Commercial and merging into Maple. I suggest that we treat the last two signs on Maple as errors, and assume that the intent was to point traffic over the bridge to I-80 west (the first can be explained as missing a left arrow, and the second...maybe for traffic from I-80 west to Historic US 40 east?). In fact there used to be a sign (http://google.com/maps/@38.8978193,-121.0785963,3a,27.9y,335.23h,89.49t/data=!3m7!1e1!3m5!1su1hcGjvCUSdlQccEO6bvOQ!2e0!5s20120701T000000!7i13312!8i6656) pointing left after crossing the bridge. So per 1PPI, the only change to make is removing the extra AubFolRd_S point (and AubFolRd_N -> AubFolRd).
US 40hisaub: LinWay_S -> LinWay_W, LinWay_N -> LinWay_E
US 40hisaub: the route between ForRd and BellRd is wrong per signs 1 (https://www.google.com/maps/@38.9223009,-121.0566885,3a,24.7y,86.79h,86.76t/data=!3m6!1e1!3m4!1sTGODadT2Q_UgdegPEAX1HA!2e0!7i13312!8i6656) 2 (https://www.google.com/maps/@38.9241669,-121.058248,3a,75y,231.86h,84.91t/data=!3m6!1e1!3m4!1srapGcG1uTv8yRYdMbEgvjg!2e0!7i13312!8i6656) 3 (https://www.google.com/maps/@38.9235596,-121.0580779,3a,24y,340.35h,84.08t/data=!3m6!1e1!3m4!1syLy8KszZRbuu1JVUlmYdTw!2e0!7i13312!8i6656); sign 4 (https://www.google.com/maps/@38.9232575,-121.0565031,3a,32.1y,124.87h,85.82t/data=!3m6!1e1!3m4!1sB62Oc71WNgMFzeL2GRWQqw!2e0!7i13312!8i6656) probably has the wrong arrow. So delete I-80(122) and instead add I-80(121), AubRavRd_W, and BowUCRd.
US 40hisaub: NieRd -> NeiRd
US 40hisaub: add PlaHilRd_N and AppRd_W the make the routing clear near I-80(125)?
US 40hisaub: HidMeaRd -> HidMeaWay? and move northeast

US 40hisaub: continue straight (https://www.google.com/maps/@39.0175592,-120.981493,3a,75y,347.81h,78.05t/data=!3m6!1e1!3m4!1s7qRC5o8kDIlyWiKlED6NYA!2e0!7i13312!8i6656) past I-80(129):
WPaoLn_N http://www.openstreetmap.org/?lat=39.035028&lon=-120.975652
I-80(130) http://www.openstreetmap.org/?lat=39.034436&lon=-120.975206
PaoLn_S http://www.openstreetmap.org/?lat=39.033828&lon=-120.974498
PonWay_S http://www.openstreetmap.org/?lat=39.035353&lon=-120.972358
CanWay http://www.openstreetmap.org/?lat=39.043086&lon=-120.973291
I-80(131) http://www.openstreetmap.org/?lat=39.044698&lon=-120.974091
Point 130 on I-80 needs to move to match. It's not signed beyond PonWay_S (https://www.google.com/maps/@39.0353351,-120.9723378,3a,75y,61.75h,64.99t/data=!3m6!1e1!3m4!1s7KfbG5TX645P3osngqtosA!2e0!7i13312!8i6656), so maybe don't include I-80(131).

US 40hiscol: delete; I don't see any signage except that mentioned above as part of US 40hisaub
US 40hisdix: maybe delete MidRd, since PittSchRd is the city limits and signage is apparently by the city?
US 40hisdix: I-80(66A) -> I-80
US 40hisros: I don't see any signs west of HoweAve, so delete I-80BL(11)?
US 40hisros: CA244 -> ToI-80(94B)?
US 40hisros: GreLn -> CRE14
US 40hisros: add GraSt (former 65 via Oak to the underpass) in downtown Roseville?
US 40hisros: GalBlvd -> WilRd (https://www.google.com/maps/@38.7580341,-121.2678022,3a,45.4y,124.75h,87.74t/data=!3m6!1e1!3m4!1saLGXbndl3yQU51EoQ4-Lwg!2e0!7i13312!8i6656)
US 40hisros: add EurRd_E after I-80(105A)?
US 40hisros: is this actually signed all the way to Auburn? It's well signed in Roseville, Rocklin, and Loomis, but I see nothing after that. So end it at ToRipRd http://www.openstreetmap.org/?lat=38.836235&lon=-121.178969 ?

US 40hissac: there is no signage and no defined traversable route between GraSt (note the reconfiguration just east of there, which removed the signs east of the underpass) and the capitol area. This needs to be split in two. The first eastbound sign in Sacto is on N after 9th, and the last westbound I can find is on 12th after F. But someone following actual historic US 40 (12th-F-15th) would not see the latter, since it's not on a road that was ever US 40! So what to do? How can we put the line in the middle if there's no westbound route? In any case, everything west of BSt needs to be redone.
US 40hissac: I think it's more appropriate to put it on Del Paso Boulevard east of 46A(CA160) (which should be CA160(46A) anyway). There were only a few years that US 40 went over the railroad on modern 160 and then exited onto Del Paso; the overpass was built almost simultaneously with the freeway to the east. So delete 46B(CA160) and DelPasoBlvd_S -> CA160(46B)?
US 40hissac: El Camino east of Auburn was never US 40. But there's a sign on it (https://www.google.com/maps/@38.6111712,-121.4291707,3a,32.2y,279.68h,89.47t/data=!3m6!1e1!3m4!1sKKK8ILiH4AnBEmE3ONAmEQ!2e0!7i13312!8i6656). Ugh. No change.

US 40histru: do we have any confirmation of signage near the west end? There's no GSV (or other street view site) coverage west of I-80(168), and I don't see any signs on GSV west of I-80(171) (meaning we'd end it at 168 if there's nothing else).
US 40histru: StaLn doesn't exist
US 40histru: where does the JudAcc name come from?
US 40histru: is the easternmost sign at I-80(186) (https://www.google.com/maps/@39.3260478,-120.1946305,3a,36.4y,179.98h,88.13t/data=!3m6!1e1!3m4!1seivVRnf7GqeDRTgnfRDxCQ!2e0!7i16384!8i8192)? If so, we should probably end it at GleDr, since Donner Pass Road east of there was never US 40.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on January 19, 2020, 11:58:31 am
For Sacramento Capitol Area, just to flag up this post for a refresher.
I believe, when drafting the route, CA160 still extended there, so I just copied that (I have no other idea why I would have put a shaping point near Alkali Flat) - presumably only checking eastbound as it disagrees with westbound.

Eastbound reassurance signs on: Capitol Ave near the railway bridge (https://www.google.co.uk/maps/@38.5828681,-121.5159337,3a,75y,71.78h,93.46t/data=!3m6!1e1!3m4!1sD2wi12gENaxq1AF_ESQ33A!2e0!7i13312!8i6656), N just before 15th (https://www.google.co.uk/maps/@38.574109,-121.4888438,3a,37.6y,71.94h,91.41t/data=!3m6!1e1!3m4!1s7ZyBDgmf_toElKrNEG5giw!2e0!7i13312!8i6656), 16th just after N (https://www.google.co.uk/maps/@38.5740649,-121.486957,3a,75y,21.82h,85.77t/data=!3m6!1e1!3m4!1slictDajWjrVBryO0_AK-Aw!2e0!7i13312!8i6656), Del Paso near Globe (https://www.google.co.uk/maps/@38.6020847,-121.4671695,3a,75y,63.57h,81.59t/data=!3m6!1e1!3m4!1sKVDnhyK5RA-tQpJA41Ba8A!2e0!7i13312!8i6656).

Westbound signs on: Del Paso near Baxter (https://www.google.co.uk/maps/@38.6039378,-121.4638716,3a,75y,254.41h,85.96t/data=!3m6!1e1!3m4!1syP37Uc67ocoVYgn0iYWbmg!2e0!7i13312!8i6656), 12th at Fat Alley (https://www.google.co.uk/maps/@38.5836959,-121.4891025,3a,15y,165.9h,87.64t/data=!3m6!1e1!3m4!1sp14VlYsuAQF3iKzuSGczJw!2e0!7i13312!8i6656), Capitol Ave near the railway bridge (https://www.google.co.uk/maps/@38.5828135,-121.5156978,3a,75y,295.74h,86.95t/data=!3m6!1e1!3m4!1s9B1b1w0oNU3Khnwf8ZmwGg!2e0!7i13312!8i6656).

We can infer Tower Bridge as being part of the route, for obvious reasons. But how to get to it from 12th/G or from it to N/15th? Assuming there's no radical difference between the routes for each direction, we can assume Hist 40 comes down 12th to L. The question has to be (other than needing to fix the route north of downtown) whether it takes the L-N pair between 9th and 3rd, or whether it takes the Capitol Mall. I gather the Capitol Mall was part of 40 (pictures of old postcards supposedly showing signage), but if you went L or N instead, then you can fudge it and call it clinched!
Title: Re: usaush (United States Historic US Routes)
Post by: neroute2 on January 19, 2020, 12:32:50 pm
For Sacramento Capitol Area, just to flag up this post for a refresher.
We can infer Tower Bridge as being part of the route, for obvious reasons. But how to get to it from 12th/G or from it to N/15th? Assuming there's no radical difference between the routes for each direction, we can assume Hist 40 comes down 12th to L. The question has to be (other than needing to fix the route north of downtown) whether it takes the L-N pair between 9th and 3rd, or whether it takes the Capitol Mall. I gather the Capitol Mall was part of 40 (pictures of old postcards supposedly showing signage), but if you went L or N instead, then you can fudge it and call it clinched!
Since this post, signs on Capitol near the railway bridge have been removed (and Capitol is now one-way eastbound there). I also found a sign at N/9th.

The last pre-one-way-pair routing of US 40 was Capitol-9th-N-16th. When one-way streets were implemented in the mid-1950s, westbound was moved to 12th-F-15th, rejoining eastbound at N (and using N-9th-Capitol). In the early 1960s, the one-block jog was moved from 9th to 7th (eastbound) and 8th (westbound). A temporary alignment was signed in 1965, using Capitol-3rd-Q-16th eastbound and 12th-F-15th-P-5th-Capitol westbound, and the 1967 official is the first to show US 40 signs removed.

The problem is that there's no good option for signing westbound 40, since all but the last temporary alignment have streets going the wrong way. The city seems to have given up and posted a sign at 12th and F, where it doesn't belong. And eastbound has two reasonable options and a third possible (temporary) one, which we know they didn't choose because of the signs on N. But we still have no knowledge of the intended street to jog on (7th or 9th), so we cannot map a route. "you can fudge it and call it clinched" is not acceptable. And the westbound route is unknown because they chose to place a sign where US 40 never went. All we can do is end westbound after that sign and only map eastbound around the capitol. Here's my suggestion for that area:

9thSt http://www.openstreetmap.org/?lat=38.576210&lon=-121.496730
NSt_E http://www.openstreetmap.org/?lat=38.573652&lon=-121.487149
ISt http://www.openstreetmap.org/?lat=38.579951&lon=-121.487653
ESt http://www.openstreetmap.org/?lat=38.584338&lon=-121.485765
BSt http://www.openstreetmap.org/?lat=38.589806&lon=-121.483383
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 19, 2020, 01:20:05 pm
US 66hisazu: the westernmost sign is at Avenue 26, not 110. So move it and rename it Ave26 (or US99His? but that doesn't seem to be signed anywhere nearby)
US 66hisazu: delete ToCA710? Move east and rename PasAve?
US 66hisazu: MadBlvd -> MadSt (https://www.google.com/maps/@34.1463997,-118.0815187,3a,17.8y,251.19h,94.38t/data=!3m6!1e1!3m4!1s6ZjSCzZywuezvkbiKQcACA!2e0!7i16384!8i8192)
US 66hisazu: EFooBlvd -> FooBlvd_E
US 66hisazu: CitAve_W -> CitAve_Azu, CitAve -> CitAve_Fon
US 66hisazu: SanDiaAve -> SanDimAve
US 66hisazu: add CamAve to match CA 66
US 66hisazu: CA66_E -> 5thSt_E? CA 66 doesn't seem to be signed here
US 66hisazu: BasRd -> BasSt
US 66hisazu: 21St -> 21stSt
US 66hisazu: PalmAve -> InsRd (https://www.google.com/maps/@34.1865959,-117.3637159,3a,15y,173.55h,93.84t/data=!3m6!1e1!3m4!1sjqZDwufk-Nuah1-ydv9rHA!2e0!7i16384!8i8192), move southeast
US 66hisazu: move KeeRd southeast
US 66hisbar: move points to match I-15blvic
US 66hisbar: HerWay -> BryRd (https://www.google.com/maps/@34.6745501,-117.3397247,3a,15y,319.1h,88.23t/data=!3m6!1e1!3m4!1s2yX7X_PxsnutH663s4ZJyA!2e0!7i13312!8i6656)
US 66hisbar: HogRd -> HodRd
US 66hisbar: LSt -> AveL (https://www.google.com/maps/@34.8913837,-117.0573995,3a,21.1y,42.29h,95.9t/data=!3m6!1e1!3m4!1sc5geH54Se4oi9vyBFFs40w!2e0!7i16384!8i8192) (or I-15BLBar_S?)
US 66hisbar: delete MonRd_S (which should be MonRd); 66 stays on I-40 to exit 1 (https://www.google.com/maps/@34.8838582,-116.9821987,3a,24.5y,298.18h,85.08t/data=!3m6!1e1!3m4!1snrEnWBnn8icnETU0NaFHnA!2e0!7i16384!8i8192) (and maybe split it at I-40, since I can't find any signs indicating an overlap)
US 66hisbar: add a point at NatTraHwy_W (https://www.google.com/maps/@34.8675719,-116.9307933,3a,15y,362h,90.03t/data=!3m6!1e1!3m4!1sU6XY7cFhMfF5OYi8F8vecA!2e0!7i13312!8i6656)
US 66hisbar: PisRd -> PisCraRd (https://www.google.com/maps/@34.7720118,-116.373754,3a,49.7y,302.95h,84.88t/data=!3m6!1e1!3m4!1s5G79Keq_YSd2eK5feaYlUA!2e0!7i3328!8i1664)
US 66hisbar: add points at CruRd_N and LudRd on either side of I-40(50)?
US 66hisbar: NatTrlHwy_E -> NatTraHwy_E? (since it's Trails, not Trail)
US 66hishol: SanMonBlvd_S -> SanMonBlvd_W
US 66hishol: RocAve -> CenAve and move to match CA 2
US 66hishol: AlvSt -> CA2
US 66hishol: LilTer -> DouSt and move southeast
US 66hishol: ElyParkAve -> VinScuAve
US 66hishol: Bdwy_S -> Bro_S?
US 66hisnee: RivRd -> NeeHwy_N (https://www.google.com/maps/@34.8767586,-114.6431195,3a,17.9y,217.34h,91.31t/data=!3m6!1e1!3m4!1sJu1tN3fQ8NZPIQyFcyt_nw!2e0!7i13312!8i6656)
US 66hisnee: add a point at TSt so it loops south of I-40?
US 66hisnee: ToAZ95 -> NeeHwy_E (https://www.google.com/maps/@34.8484201,-114.61402,3a,19.5y,14.91h,97.63t/data=!3m6!1e1!3m4!1s0f8UWExzgOu9M8jQU7RS_A!2e0!7i13312!8i6656)
US 66hisspa: should we extend this south to HunDr and north to the city limits at ColSt?
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on January 19, 2020, 03:36:01 pm
And the westbound route is unknown because they chose to place a sign where US 40 never went.
Is it unknown, or just vaguely/poorly defined? And is unknown non-existent?

And, surely a sign is a help for defining the route, rather than the reason for it being unknown?

I'm fine with a split - it seems sensible given the circumstance, but there's a lot of fallacious reasoning trying to justify it.
Title: Re: usaush (United States Historic US Routes)
Post by: neroute2 on January 20, 2020, 11:11:24 am
And the westbound route is unknown because they chose to place a sign where US 40 never went.
Is it unknown, or just vaguely/poorly defined? And is unknown non-existent?

And, surely a sign is a help for defining the route, rather than the reason for it being unknown?

I'm fine with a split - it seems sensible given the circumstance, but there's a lot of fallacious reasoning trying to justify it.

Maybe you should look at a map and plot out the signs rather than attack my supposedly fallacious reasoning.
Title: Re: usaush (United States Historic US Routes)
Post by: si404 on January 20, 2020, 12:46:36 pm
Maybe you should look at a map and plot out the signs
But in Sacramento and Auburn you've decided the signs are wrong and therefore so at the TM routes. What would be the point of looking at a map and plotting out the signs if you are just going ignore signs you don't like.  :pan:
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 20, 2020, 02:24:36 pm
That reply shows you have not plotted the route on a map, since I am not ignoring any signs in Sacto.
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 22, 2020, 07:18:21 am
US 80hiscaj: move MainSt_W southwest
US 80hiscaj: add LakeJenRd_N and RidHillRd on either side of I-8(23)?
US 80hiscaj: add DunLn and VieLn on either side of I-8(27)?
US 80hiscaj: add AlpBlvd_E and WilRd_W on either side of I-8(33)?
US 80hiscen: does this have any historic 80 signs? I can't find any on GSV
US 80hiscen: move I-8(89) north and rename CRS2
US 80hiscen: DrewRd -> CRS29
US 80hiscen: ForRd -> CRS30
US 80hiscen: DogRd -> CRS31
US 80hiscen: whenever CA 115 gets fixed, make the relevant changes to this too
US 80hiscen: I-8(143) -> ToI-8(143) or ToCA98 and move northeast - but again, if this is unsigned, it should be deleted
US 80hiscen: I-8(146) -> BroResRd
US 80hisfel: I can't find any signs on GSV (some from May 2019), so unless I'm missing some, delete
US 80hisjac: add CRS1_N west of I-8(47)
US 80hisjac: BucSprRd -> CRS1_S
US 80hisjac: StaLn -> StaSt (https://www.google.com/maps/@32.6466,-116.2388872,3a,15y,169.23h,93.29t/data=!3m6!1e1!3m4!1svJldiO8efrxR9h2YKJquzQ!2e0!7i16384!8i8192)
US 80hissan/US 395hissan: Wow, those signs on Market Street (https://www.google.com/maps/@32.7114811,-117.1601158,3a,15y,125.99h,90.04t/data=!3m6!1e1!3m4!1s-qM3fJFCjOvzZ3x2G_M5BQ!2e0!7i16384!8i8192) are tiny.
US 80hissan/US 395hissan: MarSt -> MarSt_E or ParkBlvd_S
US 80hissan/US 395hissan: ToCA94 -> GSt and move south?
US 80hissan/US 395hissan: WebAve is private access only (https://www.google.com/maps/@32.7276098,-117.1474099,3a,15.1y,170.03h,85.32t/data=!3m6!1e1!3m4!1si0ASa5-eTwZeYcXLv5UdSA!2e0!7i16384!8i8192); move southwest to InsPoiWay or north to SpaTheWay?
US 80hissan/US 395hissan: move US395His_N/US80His_E west half a block - or rename FaiAve and truncate US 395hissan here? I can't find any 395 shields on Fairmount Avenue
US 80hiswin: is this signed? I can't find anything on May 2019 GSV, so if it's unsigned delete it; otherwise WinRd_W -> I-8BL_W and CRS24 -> CRS24_E
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 22, 2020, 04:25:13 pm
US 99Ehischi: WTF?
US 99hisdun: WelSt -> WelAve (https://www.google.com/maps/@41.2311048,-122.2754015,3a,39.6y,250.48h,88.3t/data=!3m6!1e1!3m4!1s02W4bGSLWRsiOq1Pgn-NyA!2e0!7i3328!8i1664)
US 99hisind: how much of this is actually signed? all I can verify is south of CA111_S and a bit in Indio just south of IndBlvd; if there's nothing else split it into US 99hiscal (south of CA111_S -> CA111) and US 99hisind (Ave48 to IndBlvd -> Hwy111). In any case it's doubtful this route ever was or will be signed north of IndBlvd, since for most of its life US 99 used Indio Boulevard and the I-10 corridor.
US 99hisind: 1stSt/Hef -> 1stSt
US 99hisind: add 2ndSt_E in Calexico
US 99hisind: CA86/111_S -> CA111_Heb
US 99hisind: if it is in fact signed along CA 86, copy that file (once changes are made) south of 81stAve
US 99hisind: 81stAve -> 81stAve_W
US 99hisind: CA195 -> PieSt
US 99hisind: 52ndAve -> Ave52, 51stAve -> Ave51, 50thAve -> Ave50 (but again, is it signed here?)
US 99hislos: move CA110 southwest to the correct location (which should probably be a point on CA 110)
US 99hislos: add a point at FigSt?
US 99hislos: GleBlvd -> BraBlvd
US 99hislos: LosFelBlvd -> LosFelRd (https://www.google.com/maps/@34.1277733,-118.2604329,3a,15y,319.13h,87.07t/data=!3m6!1e1!3m4!1s0V41AoofRJsGO6THYqonqg!2e0!7i13312!8i6656)
US 99hislos has a gap in Burbank and needs to be split. There is a sign just south of MagBlvd (https://www.google.com/maps/@34.1830014,-118.3117044,3a,23.9y,142.72h,86.35t/data=!3m6!1e1!3m4!1sw2P4cGmMESBV6e4OXPHdPw!2e0!7i13312!8i6656), so that's a good northern end for the shortened US 99hislos. But I can't find anything north of there until VanNuys (https://www.google.com/maps/@34.266056,-118.4221559,3a,22.9y,150.82h,98.34t/data=!3m6!1e1!3m4!1suFcHdAZDIWdgx1YbVKwT1A!2e0!7i16384!8i8192), posted by LA. So do we cut it at the Burbank/LA city limit (north of HolWay)? Or just cut it at CypAve, GriDr, or BurBlvd?
US 99hislos: OsbPl -> OsbSt
US 99hislos: VanNuys -> VanNuysBlvd
US 99hislos: move CA118 to the correct interchange
US 99hislos: do we have the correct route through San Fernando? Neither San Fernando Road nor Truman Street is signed, as best as I can tell, and I'm not sure which one US 99 actually used.
US 99hislos: add a point at SepBlvd between RoxSt and BalBlvd
US 99hislos: BalBlvd -> BalRd (https://www.google.com/maps/@34.3201858,-118.4971906,3a,29.9y,89.98h,83.36t/data=!3m6!1e1!3m4!1syALNV0XFb5pj8OYxkCKS8g!2e0!7i16384!8i8192)
US 99hislos: US6His_N -> US6His
US 99hislos: are there any signs north of BalRd? If not, maybe the north end should be at US6His
US 99hislos: move CA14 to the overpass
US 99hislos: LyoAve -> PicoCanRd (https://www.google.com/maps/@34.3811522,-118.570901,3a,29.4y,193.27h,94.89t/data=!3m6!1e1!3m4!1s6-4kcveCtB5rNhMxCoam3g!2e0!7i16384!8i8192)
US 99hislos: McBeanPkwy -> SteRanPkwy (https://www.google.com/maps/@34.393382,-118.5745091,3a,35.4y,183.54h,94.71t/data=!3m6!1e1!3m4!1sycyIv3Z0dve4_6M6pXE43w!2e0!7i16384!8i8192)
US 99hislos: I-5(173) -> HasCanRd and move west
US 99hislos: RidRte -> ParRd (https://www.google.com/maps/@34.4891066,-118.6211228,3a,53.9y,45.75h,87.32t/data=!3m6!1e1!3m4!1szPcblnCQDiv3tl6Ycco-Yw!2e0!7i16384!8i8192)
US 99hislos: I-5(176B) -> LakeHugRd and move west - again, I can't find any signs in the Santa Clarita area, so maybe this part should be deleted
US 99hisrbl: where is this signed? I can't find anything on GSV, and it's a messy combination of 99W and 99E
US 99histul: ditto; where is this signed? if it does exist, Bar -> BarAve
US 99hiswee: fix coordinates to match I-5blwee
US 99Whiswlm: ditto; where is this signed? if it does exist, I5BL_S -> I-5BL_S
US 99Whiswlw: I5BL_S -> I-5BL_S
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 24, 2020, 04:31:16 pm
US 101hispas: US101_S -> US101(229), US101_N -> US101(232)
US 101hissan: ConWay -> ParkBlvd (https://www.google.com/maps/@32.7050465,-117.1576446,3a,33y,187.16h,88.4t/data=!3m6!1e1!3m4!1s5HP-T_zixEJtpozK5YOoVA!2e0!7i16384!8i8192)
US 101hissan: I cannot find any signs in the city of San Diego. Unless there are some I am unaware of, this should be truncated to the north city limits (the railroad overpass south of CarVlyRd; it is signed (https://www.google.com/maps/@32.9482859,-117.2609154,3a,28.1y,334.3h,83.64t/data=!3m6!1e1!3m4!1soq-jxck8xMHJ_kEEvtD_sg!2e0!7i13312!8i6656) in Del Mar). Also on US 80hissan, US101His -> HarDr.
US 101hissan: move JimDurBlvd north to the underpass
US 101hissan: CRS8 -> LomSFDr? S8 isn't signed here
US 101hissan: CRS9 -> EncBlvd? S9 isn't signed here
US 101hissan: CRS12 -> PalAirRd? S12 isn't signed here
US 101hissan: MisExpy -> CA76 (https://www.google.com/maps/@33.2017604,-117.3838064,3a,51y,9.63h,85.77t/data=!3m6!1e1!3m4!1sLxCppwUjac2u3pcscB-nNA!2e0!7i16384!8i8192)?
US 101hissan: add a point south of I-5(54C) at HarDr_W?

US 395hispow: CamNor -> TwinPeaRd (https://www.google.com/maps/@32.9834501,-117.061879,3a,45.2y,48.86h,87.97t/data=!3m6!1e1!3m4!1s-XVFdoJJRhGQFatC6fItLw!2e0!7i16384!8i8192)
US 395hispow: CRS5 -> CRS5_S (https://www.google.com/maps/@33.0186913,-117.0614823,3a,15y,133.31h,85.18t/data=!3m6!1e1!3m4!1sc5jiIxeyiXNeu7sfIxLc9g!2e0!7i16384!8i8192)
US 395hissan: truncate to US80His_E and rename FaiAve? I can't find any signs north of here

US 395histem has the wrong route south of I-15(51); it is instead signed on the original route through Fallbrook (https://www.google.com/maps/@33.3884138,-117.1775975,3a,20y,338.74h,89.82t/data=!3m6!1e1!3m4!1sxmwTD6qHnsSCKStocxHoTQ!2e0!7i16384!8i8192). Delete everything before I-15(51) and replace with the following (the farthest south shield I can find is in Escondido (https://www.google.com/maps/@33.1187821,-117.0830993,3a,29.6y,193.61h,85.37t/data=!3m6!1e1!3m4!1st3NmISedJCM_kV6TTqV4fw!2e0!7i13312!8i6656)):
I-15BLEsc_S http://www.openstreetmap.org/?lat=33.097042&lon=-117.071562 new EscBlvd point needed on I-15blesc
SunDr http://www.openstreetmap.org/?lat=33.101514&lon=-117.070911
9thAve http://www.openstreetmap.org/?lat=33.113116&lon=-117.079094
GraAve_W http://www.openstreetmap.org/?lat=33.120305&lon=-117.084212
GraAve_E http://www.openstreetmap.org/?lat=33.121680&lon=-117.081492
CA78_E http://www.openstreetmap.org/?lat=33.126962&lon=-117.083863
CA78_W http://www.openstreetmap.org/?lat=33.130359&lon=-117.085349 new MisAve point needed on CA 78
I-15BLEsc_N http://www.openstreetmap.org/?lat=33.128423&lon=-117.091615
AndDr http://www.openstreetmap.org/?lat=33.124101&lon=-117.106388
AutoParkWay http://www.openstreetmap.org/?lat=33.130494&lon=-117.122691
WooPkwy http://www.openstreetmap.org/?lat=33.141578&lon=-117.139036
SanMarBlvd http://www.openstreetmap.org/?lat=33.142151&lon=-117.160531
LasPosRd http://www.openstreetmap.org/?lat=33.148394&lon=-117.188931
CRS10 http://www.openstreetmap.org/?lat=33.153007&lon=-117.195513
RoBDr http://www.openstreetmap.org/?lat=33.173807&lon=-117.209406
MarVisDr http://www.openstreetmap.org/?lat=33.184982&lon=-117.223488
CivCenDr http://www.openstreetmap.org/?lat=33.193880&lon=-117.234335
CRS14_W http://www.openstreetmap.org/?lat=33.201565&lon=-117.243444
CRS13_S http://www.openstreetmap.org/?lat=33.203944&lon=-117.239721
BobDr http://www.openstreetmap.org/?lat=33.217220&lon=-117.226256
GopCanRd http://www.openstreetmap.org/?lat=33.247122&lon=-117.227983
CA76_W http://www.openstreetmap.org/?lat=33.257826&lon=-117.237371
RivRd http://www.openstreetmap.org/?lat=33.267312&lon=-117.236899
CamDelRey http://www.openstreetmap.org/?lat=33.288861&lon=-117.225537
CA76_E http://www.openstreetmap.org/?lat=33.294344&lon=-117.222088
CRS13_FalS http://www.openstreetmap.org/?lat=33.370051&lon=-117.251405
CRS15 http://www.openstreetmap.org/?lat=33.376618&lon=-117.251426
CRS13_FalN http://www.openstreetmap.org/?lat=33.384637&lon=-117.251340
WilGlenRd http://www.openstreetmap.org/?lat=33.393982&lon=-117.200555
OldHwy395_S http://www.openstreetmap.org/?lat=33.387091&lon=-117.176914

US 395histem: add SteViewDr just north of I-15(51)?

US 395histem is signed through Rainbow (https://www.google.com/maps/@33.4063859,-117.1641391,3a,55.3y,67.64h,84.75t/data=!3m6!1e1!3m4!1sDk1ZSM2UZ7iDpi8KfxgZyQ!2e0!7i16384!8i8192) as follows:
OldHwy395_RaiS http://www.openstreetmap.org/?lat=33.406860&lon=-117.163750
8thSt http://www.openstreetmap.org/?lat=33.410326&lon=-117.148257
WRaiValBlvd http://www.openstreetmap.org/?lat=33.428057&lon=-117.141525
OldHwy395_RaiN http://www.openstreetmap.org/?lat=33.433626&lon=-117.139943

US395histem: CRS16_E -> CRS16_S or PecPkwy_S? S16 isn't signed here
US395histem: JeffAve_N -> JefAve_N
US395histem: PalSt -> PalSt_N
US395histem: DiaDr -> I-15BLLak_S?
US395histem: add a point at LakDr_W
US395histem: GraAve_LE -> GraAve or GrahAve
US395histem: FliSt_E -> I-15BLLak_N?
74: add a point at DSt in Perris
US395hisriv: CorAve -> ComAve
US395hisriv: missing GSJ at Vine St (south of CA91)
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 24, 2020, 07:23:59 pm
Georgia
US 441hiscla/US 441buscla/105: WayStS -> WaySt_S, WayStNW -> WaySt_N
US 441hiscla/US 441buscla/105: OldUS123 -> WylySt
US 441hiscla/US 441buscla/385 takes the wrong route in south Clarkesville; GA197Con -> LouSt and GA17/197_S -> GA17/197 needs to move northwest; this also requires changes in the 17 and 197 files
US 441hiscla/US 441buscla/197/385: GA17/115_N -> GA17/115

Iowa
ignoring the Lincoln Highway files, since they're not in usaush.csv
US 6hisatl/83: WhitSt -> WhiSt
US 6hisatl: IA83/148 -> IA148_S
US 6hisatl: move I-80 west to the overpass
US 6hisatl: CRN54 -> CRN54_S (or 5thSt_S? N54 is signed only south at I-80), FroRd -> CRN54_N (https://www.google.com/maps/@41.5184208,-94.6434531,3a,15y,23.53h,89.64t/data=!3m6!1e1!3m4!1sNH8TSVQE2m56-dFJta811g!2e0!7i13312!8i6656)
US 6hisatl: JunAve -> CRN72 (https://www.google.com/maps/@41.5183432,-94.5671187,3a,15.4y,349.62h,86.41t/data=!3m6!1e1!3m4!1sp-xFmhpuNPmxI0YvEmLaVQ!2e0!7i13312!8i6656)
US 6hisatl: CRN77 -> AntCouDr? N77 isn't signed here
US 6hisatl: move IA25_N east
US 6hisatl: DivSt -> CRP28
US 6hisatl: add CRP32 (Zenith Road) east of ZebAve
US 6hisatl: add CRP48 (Maple Street) and MarSt in Dexter; remove ClaSt
US 6hisatl: 1stSt -> 2ndSt (https://www.google.com/maps/@41.5833723,-94.1960117,3a,25.8y,56.78h,80.87t/data=!3m6!1e1!3m4!1suh9HkOmrc2uESF0tOWXWMg!2e0!7i13312!8i6656)
US 6hisatl: add CRP58_N (K Avenue)
US 6hisatl: LAve -> CRP58_S, shift east
US 6hisatl: US6_E -> US6/169
US 6hisbro: 100thSt/390thAve -> 100thSt and shift north
US 6hisbro: US63_S -> US63_E or just plain US63
US 6hisbro: JacSt -> CRV18
US 6hisbro: CouLineRd -> CRV36
US 6hisbro: DAve -> DAve_S, move it north
US 6hiscou: IA192 -> KanBlvd_W?
US 6hiscou: HarSt -> 1stSt (https://www.google.com/maps/@41.2633323,-95.8437135,3a,75y,249.43h,82.88t/data=!3m6!1e1!3m4!1sHd24DzyLzFPFMrvop9ZkOA!2e0!7i16384!8i8192)
US 6hiscou: KanBlvd -> KanBlvd_E
US 6hisdur: US6_W -> US6/38
US 6hisdur: add CRY14_S (Cypress Street)
US 6hisdur: TayAve -> CRY14_N
US 6hisdur: YanAve -> CRY26_N, VailAve -> CRY26_S
US 6hisdur: 20Ave -> CRY30_N
US 6hisdur: add CRY30_S (Western Avenue)
US 6hisdur: 60Ave -> CRY40_N, 70Ave -> CRY40_S
US 6hisdur: BufAve -> CRY48
US 6hisdur: HicGroRd -> US6_E (or KimRd_E if that's no good for some reason)
US 6hisdur: LocSt -> LocSt_E and move east to the actual Main Street intersection (6 is signed to use Main Street, not the US 61 Business one-way pair)
US 6hisdur: any idea where the easternmost signs are? US 6 never used Main Street south of 4th Street, so unless signs are erroneously posted south of that intersection, we should end the route at 4thSt
US 6hisiow: US6_W -> US6_CorW? 1stAve_S -> US6_CorE?
US 6hisiow: RocShoDr -> RocDr (https://www.google.com/maps/@41.6660112,-91.5579924,3a,59.9y,292.8h,91.44t/data=!3m6!1e1!3m4!1syoY_Y1FnbkYmldufO6LkCg!2e0!7i13312!8i6656) (and add this and other relevant points to US 6)
US 6hisiow: RivDr -> RivDr_N
US 6hisiow: BurlSt -> MusAve_W
US 6hisiow: 1stAve_IC -> 1stAve?
US 6hisnew: 46thAve -> US6_W
US 6hisnew: CRS27_N <-> CRS27_S and move to the proper intersections (but it doesn't look like S27 is signed here, so 116thSt_S and 116thSt_N?)
US 6hisnew: 159 -> I-80 and move to the overpass
US 6hisnew: CRS23 -> CRS52 (https://www.google.com/maps/@41.6956063,-93.1714302,3a,32.5y,309.15h,75.55t/data=!3m6!1e1!3m4!1siChj1zebPRF3ezU9s1uPSw!2e0!7i13312!8i6656)

US 20hisepw: is this signed? I didn't see anything on GSV
US 20hisepw: Y13 -> 7thSt
US 20hisepw: SunRd_S -> CRY21_S, SunRd_N -> CRY21_N
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 24, 2020, 09:15:49 pm
Illinois
US 66hiscar: US66His_S -> OldRt16?
4: US66His_N -> OldRt16?
US 66hiscar/4: CR3 -> RenRd (https://www.google.com/maps/@38.9984585,-89.8014558,3a,15y,397.07h,89.67t/data=!3m6!1e1!3m4!1sd4lyfOUPiGvWRwnQYpdPUw!2e0!7i13312!8i6656)
US 66hiscar/4: CR19 -> MainSt (https://www.google.com/maps/@39.0120734,-89.7915258,3a,45.3y,131.8h,82.92t/data=!3m6!1e1!3m4!1s9GKJHcqcRuuN6PgkQBAj9w!2e0!7i13312!8i6656)
US 66hiscar/4: CR26 -> SawHilRd (https://www.google.com/maps/@39.0784239,-89.8114471,3a,17.8y,195.24h,88.71t/data=!3m6!1e1!3m4!1sCNlEPyGbGIFArOM5AIWOaw!2e0!7i13312!8i6656)
US 66hiscar/4: EasAve_W -> EasSt (https://www.google.com/maps/@39.1222773,-89.8173443,3a,31.6y,115.66h,86.07t/data=!3m6!1e1!3m4!1skWW95SyUkXx7YBmxvMWFeA!2e0!7i13312!8i6656)
US 66hiscar/4: LitRd -> CroCreRd (https://www.google.com/maps/@39.2443479,-89.8144676,3a,30y,308.63h,87.03t/data=!3m6!1e1!3m4!1s_oS_xYdHc-s-bcvkm_99rw!2e0!7i13312!8i6656)
4: AllSt -> AllRd (https://www.google.com/maps/@39.3767821,-89.8685829,3a,26.3y,298.97h,86.78t/data=!3m6!1e1!3m4!1s6onIfekOCCYFbnlBwBi7tw!2e0!7i13312!8i6656)
US 66hiscar/4: CR36 -> CarCutRd (https://www.google.com/maps/@39.3914476,-89.8594572,3a,18.9y,186.4h,87.28t/data=!3m6!1e1!3m4!1sQU0P7JJ0bqceWnvzkOAnlA!2e0!7i13312!8i6656)
US 66hiscar: StanCityRd_S -> StaCityRd_S
4: CroRd -> CroMineRd (https://www.google.com/maps/@39.4793244,-89.7809543,3a,15y,230.74h,88.04t/data=!3m6!1e1!3m4!1snQFr4qJpmY64krO3oKNO4A!2e0!7i13312!8i6656)
US 66hiscar: CroRd -> IL4_VirA
US 66hiscar: CroRd_E -> CroMineRd_E
US 66hiscar: move SneRd southwest and rename IL4_VirB (not the same intersection), add IL4_VirC northeast of the railroad
4: add OldRt4 (https://www.google.com/maps/@39.4849286,-89.7765463,3a,42.2y,31.58h,82.98t/data=!3m6!1e1!3m4!1sr-cAUQF7VDSCFj2nXQn6eA!2e0!7i13312!8i6656), move WriSt northeast
US 66hiscar: add a point at WriSt_N (https://www.google.com/maps/@39.497598,-89.7764328,3a,43.2y,17.9h,80.96t/data=!3m6!1e1!3m4!1s-sOKEVSg7_8Ej-GgojIaTg!2e0!7i13312!8i6656)
US 66hiscar: add a point at IL4_VirD (https://www.google.com/maps/@39.4971582,-89.7687322,3a,29.6y,229.81h,85.51t/data=!3m6!1e1!3m4!1s2WEcGnZgaGWA3WTJRZefjQ!2e0!7i13312!8i6656)
US 66hiscar/4: CR37_W -> DeanSt, CR37_E -> JacSt (37 isn't signed here)
US 66hiscar: I can't find any signs in the IL4_AubA to IL4_AubC area, so delete AckRd_* and rename the others to match 4
US 66hiscar/4: should we interpret this (https://www.google.com/maps/@39.5966872,-89.7528497,3a,30.6y,116.3h,83.95t/data=!3m6!1e1!3m4!1senmEhGoxd1vr4cVFnB-A8A!2e0!7i13312!8i6656) to mean that 66 uses Lincoln Street? If so, add LinSt_S and LinSt_N on 4 and IL4_AubA and IL4_AubB on 66
US 66hiscar: IL4_AubD -> IL4_AubC, IL4_AubE -> IL4_AubD
US 66hiscar: CurRd -> CurRd_N and move southwest
US 66hiscar: RecDr -> KniRecDr (https://www.google.com/maps/@39.7379079,-89.6895257,3a,24.2y,209.55h,89.72t/data=!3m6!1e1!3m4!1sQ-QE0AFoLyA0s_j9Lw1OWg!2e0!7i13312!8i6656)
US 66hiscar: 2ndAve_N -> 2ndSt_N

US 66hiscar has an incorrect route in Springfield. Delete US66His_N and replace it with the following:
CapAve_E http://www.openstreetmap.org/?lat=39.798315&lon=-89.648674
IL97 http://www.openstreetmap.org/?lat=39.803389&lon=-89.648550 new 5th/6thSt (?) point needed on 97
SanAve http://www.openstreetmap.org/?lat=39.830769&lon=-89.649425
8thSt http://www.openstreetmap.org/?lat=39.841742&lon=-89.644833
I-55BL/29 http://www.openstreetmap.org/?lat=39.841948&lon=-89.633117 new TaiRd point needed on I-55blspr/29/US 66hischi
4 needs a point at 8thSt to avoid crossing this.
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 25, 2020, 07:20:15 pm
US 66hischi: rename this just plain US 66his?
3: add ChaRocRd south of I-270
US 66hischi: add OldAltRd_S west of I-270(4A)?
US 66hischi: move I-270(4A) and I-270(4B) to the underpasses
US 66hischi: IL159_S -> BucSt (main thread (http://forum.travelmapping.net/index.php?topic=3497))
4: US66His_S -> FroRd?
US 66hischi: CR19 -> StaRd (https://www.google.com/maps/@39.0203071,-89.7656907,3a,38.7y,349.77h,87.28t/data=!3m6!1e1!3m4!1sQuFdWoo1Z7YqPJ3fW-HW-w!2e0!7i13312!8i6656)
US 66hischi: DouArchRd -> FroRd (https://www.google.com/maps/@39.0338236,-89.7504374,3a,17.8y,219.95h,84.66t/data=!3m6!1e1!3m4!1snrzp34d79jLVw9v8UFHHkA!2e0!7i13312!8i6656)_Sta, FroRd -> FroRd_Nor
US 66hischi: OldUS66_S -> OldRte66_MtOS (https://www.google.com/maps/@39.0438103,-89.7507744,3a,15.2y,336.76h,87.18t/data=!3m6!1e1!3m4!1s-dMfbMM_qyGspTPZbv2btQ!2e0!7i13312!8i6656), OldUS66_N -> OldRte66_MtON (https://www.google.com/maps/@39.0917738,-89.7091364,3a,18.4y,110.39h,86.15t/data=!3m6!1e1!3m4!1sS4ajalbdht__8JDqxyMJMw!2e0!7i13312!8i6656)
US 66hischi: CR175 -> 10thAve (https://www.google.com/maps/@39.1466405,-89.6687321,3a,43.1y,3.7h,89.48t/data=!3m6!1e1!3m4!1sHpEj2LMJSp2whael4uNBFg!2e0!7i13312!8i6656)
US 66hischi: ToIL48/127 -> ILRte48 (https://www.google.com/maps/@39.3225738,-89.6482311,3a,18.8y,246.53h,86.04t/data=!3m6!1e1!3m4!1szDyV-9C1sbh5YeJvs3ksmA!2e0!7i13312!8i6656)
US 66hischi: MainSt_Wag -> WagAve (https://www.google.com/maps/@39.3776255,-89.6437354,3a,15.1y,137.01h,84.52t/data=!3m6!1e1!3m4!1si6W1P4zjzAcZKeEYyQaUeQ!2e0!7i13312!8i6656)
US 66hischi: MvlAve -> MorAve
US 66hischi: MainSt_Far -> MineAve (https://www.google.com/maps/@39.4435716,-89.6472694,3a,56y,132.75h,78.15t/data=!3m6!1e1!3m4!1sy54VhpHt0_-cLYIPNpS4CQ!2e0!7i13312!8i6656)
US 66hischi: PulRd -> PonLn (https://www.google.com/maps/@39.6472811,-89.6479653,3a,21.4y,181.68h,82.69t/data=!3m6!1e1!3m4!1sn4gC2uT9ls2pvrlZh-1lOA!2e0!7i13312!8i6656)
US 66hischi/I-55BLspr: AdlSteDr -> SteDr (https://www.google.com/maps/@39.7573223,-89.6468584,3a,75y,12.31h,77.09t/data=!3m6!1e1!3m4!1sn02k4zlqBywKPmmGOb9gIA!2e0!7i13312!8i6656)
US 66hischi/I-55BLspr: do we have confirmation that the rerouting south of downtown Springfield has happened? If not, we should revert the changes.
US 66hischi/I-55BLspr: DirPky -> DirPkwy
US 66hischi: IL123 -> OldRte66 (https://www.google.com/maps/@39.9556686,-89.5528304,3a,27.2y,348.26h,85.75t/data=!3m6!1e1!3m4!1s81k82G0BNra0NBDZqhlpew!2e0!7i16384!8i8192)
US 66hischi: US66HisSpr -> ElmSt_S, OakSt -> ElmSt_N
US 66hischi: KenRd -> CR10_W (https://www.google.com/maps/@40.0208431,-89.4844021,3a,41.2y,249.51h,84.31t/data=!3m6!1e1!3m4!1sL-_rrujMZiOlNM43F7DauQ!2e0!7i13312!8i6656), add CR10_E just to the north
US 66hischi: CR22 -> ToCR22 (https://www.google.com/maps/@40.0712393,-89.4414699,3a,31.5y,25.84h,85.95t/data=!3m6!1e1!3m4!1sNEt7wEkf2DTBETcPegnc7w!2e0!7i13312!8i6656)
US 66hischi: LinPkwy_S -> I-55BLLin_A
US 66hischi/I-55BLlin: add a point at StrAve (https://www.google.com/maps/@40.1391391,-89.3860217,3a,28y,268.17h,78.81t/data=!3m6!1e1!3m4!1sC3Ze1XwxSKcu8qqH4ffTDg!2e0!7i13312!8i6656), which is where US 66hislin actually intersects
US 66hischi: 5thSt -> I-55BLLin_B
US 66hischi: CR121 -> OldRte121 (https://www.google.com/maps/@40.1731015,-89.3871421,3a,16.3y,276.49h,84.6t/data=!3m6!1e1!3m4!1setWSRVkApID7UYJ2taSbEA!2e0!7i13312!8i6656) and move south to the intersection with the frontage road near 21st Street
US 66hischi: KicSt -> I-55BLLin_Co
US 66hischi: LinPkwy_N -> OldRte66_AtlS (https://www.google.com/maps/@40.2504781,-89.2428508,3a,19.1y,295.49h,82.14t/data=!3m6!1e1!3m4!1sS0CD-ju5WsWTtZpzFiFpOg!2e0!7i13312!8i6656)
US 66hischi: 2440St -> 2400St (https://www.google.com/maps/@40.2669652,-89.221897,3a,55.4y,355.81h,77.74t/data=!3m6!1e1!3m4!1smQPI1X855ucZN1oeHay7tg!2e0!7i13312!8i6656) (or 2400thSt?)
US 66hischi: Main/CarSt -> CarSt_W
US 66hischi: 550N -> CR36 (https://www.google.com/maps/@40.36327,-89.111767,3a,18.7y,318.17h,88.66t/data=!3m6!1e1!3m4!1sQIH9487hkFID8pUri0V_Pg!2e0!7i13312!8i6656) or FunGroRd (https://www.google.com/maps/@40.3620068,-89.113325,3a,15.4y,66.46h,84.68t/data=!3m6!1e1!3m4!1sOowOQxnH_SKMYuH8ym5Oyw!2e0!7i13312!8i6656)
US 66hischi: 850N_W -> CR34_W (https://www.google.com/maps/@40.4073018,-89.0611169,3a,26.2y,245.52h,85.49t/data=!3m6!1e1!3m4!1sPOTo5K78pIG0bxp00KZ8yg!2e0!7i13312!8i6656) or ShiRd_W (https://www.google.com/maps/@40.4056761,-89.0630343,3a,26.4y,91.36h,85.99t/data=!3m6!1e1!3m4!1sp7N8W5jQSHoRQ_t5IAJp5A!2e0!7i13312!8i6656), 850N_E -> CR34_E (https://www.google.com/maps/@40.4081459,-89.060123,3a,32y,49.74h,87.53t/data=!3m6!1e1!3m4!1sNe-gXcuvfZLgcHPUgdn8uQ!2e0!7i13312!8i6656) or ShiRd_E (https://www.google.com/maps/@40.4099825,-89.0579708,3a,15y,253.6h,85.02t/data=!3m6!1e1!3m4!1sGvbfE82bxMKpOTWfUwrRhg!2e0!7i13312!8i6656)
US 66hischi: I-55BL_S -> I-55BLBlo_S, I-55BL_N -> I-55BLBlo_N, I-55BL -> I-55BLBlo
US 66hischi/US 51busblo: move OakAve west
US 66hischi/US 51busblo: move ColAve west
US 66hischi: 1900E -> CR29 (https://www.google.com/maps/@40.5663235,-88.8994471,3a,33.2y,211.63h,84.1t/data=!3m6!1e1!3m4!1s0MnsHhaXwg9vmRTi3dkBoA!2e0!7i13312!8i6656) or JefSt (https://www.google.com/maps/@40.5665076,-88.8995124,3a,15y,133.87h,84.08t/data=!3m6!1e1!3m4!1sTKGF4KiLY0P684AUJo9viA!2e0!7i13312!8i6656)
US 66hischi: CR12 doesn't intersect
US 66hischi: MainSt_Lex -> CR8 (https://www.google.com/maps/@40.6414961,-88.7912215,3a,15y,104.23h,87.46t/data=!3m6!1e1!3m4!1s-xxp9ft9lFU1-sq-SukU0Q!2e0!7i13312!8i6656)?
US 66hischi: DivSt -> CR19/26 or 2850E (https://www.google.com/maps/@40.7515864,-88.7186305,3a,20.2y,6.21h,88.36t/data=!3m6!1e1!3m4!1s3e3Na80qxjGl_4_OXISzOQ!2e0!7i13312!8i6656)
US 66hispon should be added as a city-marked 1930-1939 route (https://www.google.com/maps/@40.8864888,-88.638009,3a,15.8y,286.7h,78.55t/data=!3m6!1e1!3m4!1shb3jh9NWhJF2BZhoAZI4fA!2e0!7i13312!8i6656). The north end at 1600E on US 66hischi is signed, but I don't know about the south end (GSV photos on the bypass south of IL116_W are several years older than the rest). We should probably take it back to US 66hischi at IL116_W either way.
US 66hischi: 1600E -> PonRd (https://www.google.com/maps/@40.89731,-88.6262304,3a,15y,92.15h,84.78t/data=!3m6!1e1!3m4!1sc2PZdfWPSTnLu5vbv3tncw!2e0!7i13312!8i6656)
US 66hischi: 2000N -> 2000NRd (https://www.google.com/maps/@40.9153647,-88.607312,3a,18.1y,67.83h,85.45t/data=!3m6!1e1!3m4!1sh8I_7GDJ1qNSE0hQ6TJMqA!2e0!7i13312!8i6656)
US 66hischi: OdeByp_S -> OldRte66_OdeS (https://www.google.com/maps/@40.9960191,-88.5326247,3a,53.6y,265.39h,77.9t/data=!3m6!1e1!3m4!1s9ROpk9tfdKTJXU212lALUA!2e0!7i13312!8i6656), OdeByp_N -> OldRte66_OdeN
US 66hischi: PraSt -> PraSt_W, add PraSt_E (this may be signed as CR1; it is west of the bypass)
US 66hischi: DwiByp_S -> OldRte66_DwiS (https://www.google.com/maps/@41.1096165,-88.4136804,3a,15y,35.75h,85.58t/data=!3m6!1e1!3m4!1sh6hUU1TWsS7VbhZywNKKzA!2e0!7i13312!8i6656), DwiByp_N -> OldRte66_DwiN
US 66hischi/53: +53X01 -> StoRd
US 66hischi/53: +53X02 -> CarHillRd
US 66hischi/53: add a point at MitSt in Braceville?
US 66hischi/53: RivRd -> WRivRd? West is not a normal directional prefix here
US 66hischi/53: +53X04 -> 216thAve
US 66hischi/53: NapRd -> NapNorRd (https://www.google.com/maps/@41.6547943,-88.0802863,3a,15y,219.31h,97.32t/data=!3m6!1e1!3m4!1skGq6NBPTVyw8Ii1eJs7CsA!2e0!7i16384!8i8192)
US 66hischi: SacDr -> SacAve (https://www.google.com/maps/@41.8592531,-87.7017105,3a,30.4y,100.42h,93.42t/data=!3m6!1e1!3m4!1sUrL4UaOOuNkxK65olwlPyw!2e0!7i16384!8i8192)
US 66hischi: move I-90/94 north half a block; there are ramps at both streets
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 26, 2020, 08:31:27 pm
US 66hislin: US66His_W -> I-55BL and move it south to Stringer Avenue
US 66hislin: add I-55BL_S at Washington and 5th
I-55bllin: add WasSt
US 66hislin: IL10/121_* -> IL10_* since 121 is north-south?
US 66hislin: US66His_E -> I-55BL_N
US 66hislit: US66His_* -> ColBlvd (https://www.google.com/maps/@39.1468317,-89.6687965,3a,17.6y,100.1h,87.29t/data=!3m6!1e1!3m4!1sf-Ng8uAhB_-KtMvONHX4rA!2e0!7i13312!8i6656)_*
US 66hislit: add a point at KruRd (https://www.google.com/maps/@39.1467575,-89.6678176,3a,48.6y,134.65h,84.06t/data=!3m6!1e1!3m4!1s3mEuHWyDQ_9qVWaGRcw60g!2e0!7i13312!8i6656) for better shaping?
US 66hisliv: US66His_S -> IL4
US 66hisliv: SpaRdE -> SpaRd
US 66hisliv: I-55(41) -> I-55
US 66hisliv: US66His_N -> OldRte66 (https://www.google.com/maps/@39.0336582,-89.7505826,3a,47y,362.06h,83.96t/data=!3m6!1e1!3m4!1sSOsik0FKL2h68qjum9ex9g!2e0!7i13312!8i6656)
US 66hismou: US66His_S -> USHwy66_S (https://www.google.com/maps/@39.04396,-89.750779,3a,34.7y,274.38h,88.07t/data=!3m6!1e1!3m4!1sXXy30ZedV0xf972TZmQq7A!2e0!7i13312!8i6656)
US 66hismou: US66His_N -> USHwy66_N (https://www.google.com/maps/@39.0917243,-89.7091498,3a,18.2y,84.92h,88.7t/data=!3m6!1e1!3m4!1sLqNngfAySbGEwNNOR13MXw!2e0!7i13312!8i6656)
US 66hissprcha: IL3_S -> IL3
US 66hissprwil: US66His_W -> IL123
US 66hissprwil: US66His_E -> MainSt
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 26, 2020, 09:13:51 pm
Kansas
US 66hisgal -> US 66his; there's no other segment
US 66hisgal uses the Rainbow Bridge westbound, so move BeaRd northwest halfway to the road coming off the bridge

Massachusetts
US 6hispro: yuck. MA6A_Pro -> MA6A
US 6hispro/US 6: RacePtRd -> ConSt (https://www.google.com/maps/@42.0591262,-70.1888395,3a,16.1y,209.76h,88.66t/data=!3m6!1e1!3m4!1sqxtik8KNLwvHUG2yJ7GRcQ!2e0!7i16384!8i8192), since that one's signed
US 6hispro: MayAve is a bad place to end it, given that it's a private street. Maybe continue it east to the Provincetown limits, where state maintenance ends? that was probably Provincetown's intent when they posted the signs
US 20hishun: CookHillRd -> SkyTr (https://www.google.com/maps/@42.2404896,-72.903851,3a,75y,313.61h,73.28t/data=!3m6!1e1!3m4!1sXq2oLkgDJ-oSEKSBN4fRRQ!2e0!7i3328!8i1664)
Title: Re: usaush: United States Historic US Routes
Post by: oscar on January 26, 2020, 09:24:39 pm
US 99Ehischi: WTF?

I'm guessing this refers to the stray one-waypoint.wpt file, that's an unprocessed .wpt not in the HB.
'
I had mentioned to Si that I'd seen US 99E historic signage south of downtown Chico (probably summer 2017), but no photos or other details. Si couldn't find the signs I saw.

I have no problems with omitting this route, unless a better GMSV search spots adequate signage..
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 27, 2020, 09:30:06 pm
Missouri
US 66hiscar: US66His_W -> EstDr
US 66hiscar: US66His_E -> CR118

US 66hisejo is 1947-1975 (https://www.google.com/maps/@37.0841277,-94.5143442,3a,44.4y,50.31h,90.74t/data=!3m6!1e1!3m4!1swLQwcPNfJBidO5Ud9oGn6w!2e0!7i16384!8i8192), not 1940-1975
US 66hisejo: US66His_W -> MO43/66 or I-44BL/43
66: US71Bus -> I-49BL
US 66hisejo: US66His_E -> ZoraAve
I-49bljop: ZoraSt -> ZoraAve (https://www.google.com/maps/@37.1129088,-94.4760794,3a,49.1y,212.76h,88.76t/data=!3m6!1e1!3m4!1sNFglsil4Qwbhh31-ojFywA!2e0!7i13312!8i6656)

US 66hisesp: US66His_W -> I-44BL
US 66hisesp: US66His_E -> SROO_W

US 66hisflo: US66His_W -> MO366
US 66hisflo/US 61/US 67: BigBendBlvd -> BigBendRd (https://www.google.com/maps/@38.5666927,-90.4067762,3a,34.7y,9.37h,87.67t/data=!3m6!1e1!3m4!1s6rGAY3R6HFj85if3oJgb2w!2e0!7i16384!8i8192)
US 66hisflo: *_StL -> *
US 66hisflo/US 67: MOsAB_StL -> LadRd (Route AB is only west of I-270 (https://www.modot.org/sites/default/files/documents/stl_county_0.pdf))
US 66hisflo/US 67: missing GSJ at BayDr (south of MO340)
US 66hisflo/US 67: MOsTT_StL -> McDBlvd (Route TT is gone (https://www.modot.org/sites/default/files/documents/stl_county_0.pdf))
US 66hisflo: I-270(26B) -> HanRd
US 66hisflo: I-270(27) -> NewFloRd
US 66hisflo: I-270(28) -> WasSt
US 66hisflo: I-270(29) -> FloRd
US 66hisflo: I-270(32) -> BelRd
US 66hisflo: US66His_E -> I-270(34)

US 66hislaq: does this still exist? it was signed as the through route in 2014 (https://www.google.com/maps/@37.7518749,-92.313387,3a,20.1y,121.65h,85.6t/data=!3m7!1e1!3m5!1sPAka-bV4oObRT85iCyqCDg!2e0!5s20140201T000000!7i13312!8i6656), but in 2016 that sign was gone. At the other end, the route has gone straight (https://www.google.com/maps/@37.7708633,-92.2833876,3a,24.9y,221.43h,81.87t/data=!3m7!1e1!3m5!1sOtnljfe0-RXEmHGpZ1nIdQ!2e0!5s20131201T000000!7i13312!8i6656) since 2013. It seems that this alternate route no longer exists. But if it gets kept for some reason (such as new signs), US66His_W -> SRAB and US66His_E -> MO17

US 66hisman: US66His_W -> I-44BL/100
US 66hisman: *_Fra -> *, *_StL -> *
US 66hisman does not stick to 100 (https://www.google.com/maps/@38.5832135,-90.6150239,3a,37.4y,188.23h,86.45t/data=!3m6!1e1!3m4!1sz9MtEMiuzC7HCbd9Hi74Ig!2e0!7i16384!8i8192). MOsOO_Fra -> MO100/OO, new point at BasRd, new point at MO100_Hol (also needs a FoxCreRd point on 100). New point at MO100_FoxW (WooMeaDr on 100), BucCreLn (for shaping), MO100_FoxE (ManRd on 100), MOsT_StL -> StAlbRd (shifted east), GleRd (for shaping), shift MO109 south (new ManRd point on 109), WesRd -> MO100_Wil.
100: WesRd -> WesFarDr (https://www.google.com/maps/@38.5837851,-90.6152746,3a,35y,231.7h,91.85t/data=!3m6!1e1!3m4!1s9Fi7sQ9caWKIRiHHmpwbKA!2e0!7i16384!8i8192)
US 66hisman: SouAve -> SWAve?
US 66hisman: US66His_E -> TucBlvd

US 66hisnjo: US66His_W -> MO43_S or 2ndSt
43: BroSt -> 2ndSt (https://www.google.com/maps/@37.089642,-94.5131873,3a,29.6y,14.71h,95.18t/data=!3m6!1e1!3m4!1sU0irwVajl_5qRxHpMI9NIA!2e0!7i16384!8i8192)
US 66hisnjo/43: missing GSJ at ZoraSt
US 66hisnjo: MO171_E -> MO171_S
US 66hisnjo: US66His_E -> MadAve

US 66hisnsp: US66His_W -> I-44BL_W
US 66hisnsp: *_Spr -> *
US 66hisnsp: US160_W -> US160/744?
US 66hisnsp: US66His_E -> I-44BL_E

US 66hisstl -> US 66his? this is the main segment, so no need for a suffix
US 66hisstl: StLouAve -> StLouAve_S (66 turns here), delete NewRd, add StLouAve_N at Euclid Avenue, UtiSt_W at Euclid Avenue, UtiSt_E at Florida Avenue
US 66hisstl: MOsD_N -> MOsD_Jas
US 66hisstl: MOsHH_W -> MainSt_E (HH ends at 49BL/171)
US 66hisstl: MO171_E -> I-49BL/171
US 66hisstl: OakSt -> OakSt_W
US 66hisstl: add Old66Blvd_W at Esterly Drive
US 66hisstl: move CL124 southwest
US 66hisstl: CR118 -> MO96_W (more important and the CR 118 intersection is to the south)
US 66hisstl: MOsU_W -> MOsU_Jas
US 66hisstl: MOsAA_W -> MOsAA_Law
US 66hisstl: MOsUU_W -> MOsUU_Law
US 66hisstl: add MO96_SpeW east of MOsM_N, MOsN_W -> MO96_SpeE, add MOsN_S, add CR1210 at Paris Springs, delete MO96/266, OldUS66_W -> MO266_W
96: add CR2062 east of MOsN_N
266: OldUS66_W -> Old66 (https://www.google.com/maps/@37.1940149,-93.6707403,3a,15.3y,10.35h,90.04t/data=!3m6!1e1!3m4!1s3LPPJyohgpqDu566G8vCdg!2e0!7i13312!8i6656)
US 66hisstl/266: MOsF_N -> MOsF_Gre, MOsF_S -> MOsK
US 66hisstl: MOsT_W -> MOsT_Gre
US 66hisstl: MOsB_W -> MOsB_Gre
US 66hisstl/266: add a point at AirBlvd
US 66hisstl: SceAve -> I-44BLSpr_E, move MO13 south (and add ColSt on 13), add ParkCenSq at the downtown circle, delete CamAve and JefAve, move NatAve south, add US65Bus_S at St. Louis Street, US65Bus -> I-44BL/US65Bus
I-44blspr: SceAve -> ColRd (https://www.google.com/maps/@37.211981,-93.3306386,3a,41.8y,95.54h,92.61t/data=!3m6!1e1!3m4!1sF1rx2L5CuEEka0bAWTFgUQ!2e0!7i13312!8i6656)
US 66hisstl: I-44BL_N -> I-44BL/744
US 66hisstl: HolRd doesn't exist; replace with a shaping point
US 66hisstl: MOsB_E -> MOsB_Web
US 66hisstl: MOsHH_E -> MOsHH_Web
US 66hisstl: MOsJ_W -> MOsJ_Lac
US 66hisstl: MOsC_E
US 66hisstl: I-44(127) -> I-44BLLeb_W and move north; add MOsW on I-44blleb
US 66hisstl/I-44blleb: move UtahSt north as SprRd
US 66hisstl: I-44BL_E -> I-44BLLeb_E
US 66hisstl: MOsF -> MOsF_Lac
US 66hisstl: MOsAA_E -> MOsAA_Pul
US 66hisstl: I-44BL_W -> I-44BLWay_W
US 66hisstl/I-44blway/17: RepRd -> SweRd (https://www.google.com/maps/@37.8267115,-92.2088501,3a,15y,274.74h,84.38t/data=!3m6!1e1!3m4!1sIBc2-WTkU10-fN2jRDTDIw!2e0!7i13312!8i6656)
US 66hisstl: ChiSt -> MOsF_Pul
I-44blway: ChiSt -> MOsF
US 66hisstl: MOsZ_W -> TeaRd_W, delete TimRd, MOsZ_E -> TeaRd_E, create a new US 66hisdev (1926-1943?) (https://www.google.com/maps/@37.8424465,-92.0855301,3a,15y,113.5h,87.24t/data=!3m6!1e1!3m4!1smPEoM-BBQlmQfoPO80Cw4g!2e0!7i13312!8i6656) with points from MOsZ_W to MOsZ_E
US 66hisstl: MOsJ -> MOsJ_S
US 66hisstl: add MOsD_W just north of I-44(172), realign I-44(172)
US 66hisstl: add ArlRd just south of I-44(176)?
US 66hisstl: MOsC_W -> MacSt
US 66hisstl: MOsT_E -> MOsT_Phe
US 66hisstl: CR7050 -> CR7000 (https://www.google.com/maps/@37.9323802,-91.8384093,3a,75y,169.71h,69.32t/data=!3m6!1e1!3m4!1scdN0q1SpqTGusIR93afidA!2e0!7i13312!8i6656)
US 66hisstl: move I-44(184) east as I-44BLRol_W
I-44blrol: add MarSprDr
US 66hisstl: add MO72
US 66hisstl: 10thSt -> MOsBB_Phe, MOsBB -> MOsBB_Jas
I-44blrol: 10thSt -> MOsBB
US 66hisstl: 14thSt_Rol -> MOsE, 14thSt_StL -> 14thSt
I-44blrol: 14thSt -> MOsE
US 63: OldUS66 -> Rd2000 (https://www.google.com/maps/@37.9709967,-91.7611708,3a,37.3y,92.5h,83.86t/data=!3m6!1e1!3m4!1saGtZuBmOsFGwKpb4QUWzaQ!2e0!7i13312!8i6656)
US 66hisstl: add a shaping point west of MO68_N
US 66hisstl: MO68_N -> MO68_W (https://www.google.com/maps/@38.0073382,-91.6200537,3a,26.2y,346.69h,84.85t/data=!3m6!1e1!3m4!1sgURArfNYEuuGiDivJ505DQ!2e0!7i13312!8i6656)
US 66hisstl: MOsKK_W -> MO8/68
US 66hisstl: MOsF_E -> MOsF_Cra
US 66hisstl: MOsKK_E -> MOsKK
US 66hisstl: MOsUU_E -> MOsUU_Cra
US 66hisstl: MOsH_E -> MOsH_Cra
US 66hisstl: MOsN_E -> MOsC_Cra (https://www.modot.org/sites/default/files/documents/CrawfordCo2017%5B1%5D.pdf)
US 66hisstl: MOsJ_E -> MOsJ/N
US 66hisstl: add MOsFF east of BalRd
185: MOsD_E -> SprRd_W
US 66hisstl: MS185_N -> MO185_N
US 66hisstl/185: MOsD_W -> ToMOsD
US 66hisstl: SprRd_S -> MO185_S
185: SprRd_S -> SprRd_E
185: I-44 -> MOsAF and move east
US 66hisstl: MS185_S -> MO185
185: SprRd_N -> SprRd
US 66hisstl: add MOsW_E and MOsJJ_W on either side of I-44(230)?
US 66hisstl: add MOsAB_Fra west of I-44(239), MOsAB -> MOsAB_Gre?
US 66hisstl: add MOsAH south of I-44(242)?
US 66hisstl: MOs_O -> MOsO
US 66hisstl/I-44blpac: I-44(257) -> ViaSt
US 66hisstl/I-44blpac: 1stSt -> MOsF/OO
US 66hisstl/I-44blpac: HilVwDr -> HilDr (https://www.google.com/maps/@38.484646,-90.7031413,3a,16.1y,264.29h,87t/data=!3m6!1e1!3m4!1sTAOqaTObwHQzshUTRLC8Gw!2e0!7i13312!8i6656)
US 66hisstl/I-44/US 50: add 274A, 274 -> 274B
US 66hisstl/366: MacRd -> MOsP
US 66hisstl/366: missing GSJ at RivPerBlvd
US 66hisstl: KinBlvd_S -> KinBlvd_W, KinBlvd_N -> KinBlvd_E
US 66hisstl: add a point at MOsD_StL (MLK Drive, just south of Cole Street)
US 66hisstl: Bway_S -> Bro_S
US 66hisstl: RivBlvd_W -> RivDr_W (https://www.google.com/maps/@38.7261575,-90.228015,3a,75y,1.98h,98.01t/data=!3m6!1e1!3m4!1sF-NNG279GhQu5GYN4n2f9Q!2e0!7i16384!8i8192)
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 29, 2020, 07:09:22 am
Nebraska
US 6hisgre: route confirmed in 1923 Blue Book (https://books.google.com/books?id=LS1LAQAAIAAJ&pg=PA455)
US 6hisgre: AngRd_W -> AngSt_W (https://www.google.com/maps/@41.1396315,-96.2480044,3a,75y,329.62h,73.28t/data=!3m6!1e1!3m4!1sZqvOfOLyZ5b6DaRPbxhVow!2e0!7i13312!8i6656)
US 20hisrus: yuck, no touchy.
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 30, 2020, 05:26:45 pm
New Mexico
We have US 66hisalb and US 66hisabq, both for Albuquerque. This is probably not good.
US 66hisabq/6: CodLimLn doesn't exist
US 66hisabq/6: BIA548 is gated (https://www.google.com/maps/@34.8308943,-107.0471978,3a,15.1y,234.72h,81.58t/data=!3m6!1e1!3m4!1sTxXOeUviMyy9VzvlktlptA!2e0!7i13312!8i6656); to avoid making too much distance between points, add AccRd (https://www.google.com/maps/@34.7966236,-106.9931019,3a,15.1y,318.79h,86.07t/data=!3m6!1e1!3m4!1sItgRAsP5NIjIsgF-blg5TA!2e0!7i13312!8i6656)
US 66hisabq/6: replace QuiRd with EmeRd (https://www.google.com/maps/@34.8107948,-106.8777498,3a,16.3y,132.62h,94.4t/data=!3m6!1e1!3m4!1sRluJUduFRxIuexVoTf9oGQ!2e0!7i13312!8i6656), which has a street sign unlike the former
US 66hisabq: add LopRd between AreRd and BriBlvd_W to better define the route
US 66hisabq: BriBlvd_E -> AveCesCha (https://www.google.com/maps/@35.0700303,-106.6545258,3a,44.9y,197.09h,90.77t/data=!3m6!1e1!3m4!1sMax-7mpdhVb2vP0to_qSBA!2e0!7i13312!8i6656)
US 66hisabq: you can't drive straight through at CivPla. Nothing seems to be signed to fill the gap. Split at TisAve and MarAve, or at least replace CivPla with these two points to make it clear that this block has to be walked.
US 66hisabq: move I-40(159A) east a block
US 66hisabq: NM313/556 -> NM556_E
US 66hisabq/313: BIA701 -> SanLp (https://www.google.com/maps/@35.2568923,-106.5756919,3a,24.5y,15.83h,85.6t/data=!3m6!1e1!3m4!1sxzaom_t0PoBoXnISt-TKqg!2e0!7i13312!8i6656)
US 66hisabq: the turn onto US 550 is incorrect (https://www.google.com/maps/@35.3737148,-106.4940397,3a,16.7y,249.43h,83.07t/data=!3m6!1e1!3m4!1s-Pb93ESatfO6OCMiklL43Q!2e0!7i13312!8i6656). US550_N -> US550, delete I-25(242), add OldNM474 (-> Hwy474 (https://www.google.com/maps/@35.3747163,-106.4891166,3a,49.8y,66.22h,83.52t/data=!3m6!1e1!3m4!1s2NobTvqkEfMFl-LXXgQsXA!2e0!7i3328!8i1664)) from 313 and NM313_N and I-25(248) from 315 (https://www.google.com/maps/@35.3795052,-106.4696732,3a,19.9y,235.03h,86.14t/data=!3m6!1e1!3m4!1sdDBxnAJvBEVIzoh3y-Bo7A!2e0!7i13312!8i6656).

US 66hisalb: GraBlvd -> RioGraBlvd
US 66hisalb: add LomBlvd since you have to turn
US 66hisalb: JuaTabBlvd -> JuanTaboBlvd
US 66hisalb/333: add FourHilRd for the I-40 ramps
US 66hisalb/333: I-40(178) -> ToI-40(178)

US 66hisapa: I can't find any signs between I-25(307) and CRB47. So why do we continue 66 to I-40(319) but not fill the gap to I-25(307)? The one sign (https://www.google.com/maps/@35.4957407,-105.6727842,3a,51.2y,104.49h,87.07t/data=!3m6!1e1!3m4!1s1lJP95_OsksGD9Sqivr4iA!2e0!7i13312!8i6656) that shows it dead-ending at I-25(307)? Given the state of signage in New Mexico, it's easy to argue this is a simple error.
US 66hisapa: ToI-25 -> CRB26A (https://www.google.com/maps/@35.3927478,-105.3223016,3a,41y,278.26h,82.84t/data=!3m6!1e1!3m4!1s45QwsZmwGb27Px5BiX_W_Q!2e0!7i13312!8i6656)
US 66hisapa/US 84: CRA25A -> FR2137 (https://www.google.com/maps/@35.5201517,-105.2492054,3a,17.2y,132.95h,84.52t/data=!3m6!1e1!3m4!1sND0Kxdri2ExVoIkhWBNqvw!2e0!7i13312!8i6656)
US 66hisapa/US 84: FR45 -> AurSprRan (https://www.google.com/maps/@35.318702,-105.1465731,3a,16.5y,244.61h,86.74t/data=!3m6!1e1!3m4!1savTcjpCDOaDKzQGJAQm-xQ!2e0!7i13312!8i6656)

US 66hisgal/118: CR32 -> SaltWatRd (https://www.google.com/maps/@35.4880189,-108.8921706,3a,47y,282.99h,85.01t/data=!3m6!1e1!3m4!1sKOh52lLop6ujt9WZVcCBDg!2e0!7i3328!8i1664)
US 66hisgal/I-40blgal/118: MenBlvd -> ArmOrtBlvd (https://www.google.com/maps/@35.5097607,-108.8070463,3a,25.8y,104.67h,88.49t/data=!3m6!1e1!3m4!1snykeZD7YV7M_U4zJk-wJmg!2e0!7i13312!8i6656)
I-40blgal: move GalMunApt east to FloSt to match the other routes
US 66hisgal/I-40blgal/118: move NM602 west to Arnold Street

US 66hisgra/122: CR23 -> Hay (https://www.google.com/maps/@35.3495869,-108.0124304,3a,15.3y,15.18h,84.18t/data=!3m6!1e1!3m4!1sUF6Objfxy-7eqfcR_g6i-g!2e0!7i13312!8i6656)
US 66hisgra/122: NM615 -> I-40BL_W?
US 66hisgra/122: AspSt -> AspAve (https://www.google.com/maps/@35.164196,-107.8875874,3a,32.4y,127.3h,92.22t/data=!3m6!1e1!3m4!1s3E8D_j6TZAZUGbmeM0NPog!2e0!7i3328!8i1664)
US 66hisgra/122: move NM547 west half a block to match 547's file
US 66hisgra: NM122_E -> I-40BL_E?
US 66hisgra/124: BIA33_W -> AnzRd_W (https://www.google.com/maps/@35.0725727,-107.7513476,3a,20y,141.92h,86.79t/data=!3m6!1e1!3m4!1s9N2hHuVBBxQa4TZTU9N1BQ!2e0!7i13312!8i6656), BIA33_E -> AnzRd_E (https://www.google.com/maps/@35.0648776,-107.7167884,3a,15y,159.34h,85.16t/data=!3m6!1e1!3m4!1s3Ht-AzRxysHYe2nAO36bjg!2e0!7i13312!8i6656)
US 66hisgra/124: replace BIA380 with a point at PueRd_W (https://www.google.com/maps/@35.0654251,-107.6870129,3a,19.3y,122.14h,84.6t/data=!3m6!1e1!3m4!1sdmOAeV0gNnIh8sFh9eMx4A!2e0!7i13312!8i6656)
US 66hisgra/124: BIA36 -> AcoRd (https://www.google.com/maps/@35.0826527,-107.5941102,3a,15y,89.2h,87.1t/data=!3m6!1e1!3m4!1sF0-kWJh_mWFAWcPq5zVM7g!2e0!7i13312!8i6656)
US 66hisgra/124: BIA30 -> PueRd_E (https://www.google.com/maps/@35.0858224,-107.5573357,3a,23.8y,91.9h,87.97t/data=!3m6!1e1!3m4!1s428WGvvBH3CV7sWcicXODg!2e0!7i13312!8i6656)
US 66hisgra/124: CR124 -> IntExt (https://www.google.com/maps/@35.0544754,-107.5242129,3a,16.2y,134.18h,87.59t/data=!3m6!1e1!3m4!1s51b0aNFpqZLTsD48TcScOw!2e0!7i13312!8i6656)
US 66hisgra/124: BIA22 -> CasaBlaRd (https://www.google.com/maps/@35.0516478,-107.4746735,3a,51.7y,117.97h,82.48t/data=!3m6!1e1!3m4!1swO4PqXl-IxGQ-tyllsG6vQ!2e0!7i13312!8i6656)
US 66hisgra: move I-40(114) west to the circle as NM124_E
124: add OldRt66Rd (https://www.google.com/maps/@35.0383587,-107.3737788,3a,29.4y,340.69h,81.57t/data=!3m6!1e1!3m4!1sE89fk6r_CmXF0fIrJlQqAA!2e0!7i13312!8i6656)
US 66hisgra: ISR53 -> BIA53? L53 (https://www.google.com/maps/@35.0139007,-107.3197756,3a,15.9y,50.95h,84.13t/data=!3m6!1e1!3m4!1s5grrB_imiCXplZ01wW_KIA!2e0!7i13312!8i6656) (L for Laguna (https://en.wikipedia.org/wiki/Laguna_Pueblo))?

US 66hissan/I-40blsan: US54_W -> US54_S (https://www.google.com/maps/@34.938176,-104.6940225,3a,53.6y,122.73h,84.98t/data=!3m6!1e1!3m4!1s8pGSrcYTBA2cV8FTAKOQvw!2e0!7i16384!8i8192)
US 54: add NM91 to match other routes

US 66hissfe: how does it go downtown? Given the maps on https://www.usends.com/santa-fe.html the actual historic route from the west appears to be Galisteo-SF-around the plaza-Old Santa Fe, but this is not completely followable in either direction. Eastbound can almost do it, but you need to turn before the plaza on Don Gaspar or loop after on Cathedral. Westbound is horrible; a sign points right on Old Santa Fe Trail just west of WatSt_E, but then you're forced to Palace at Washington. Are there even any signs west of downtown? If not, perhaps delete everything west of WatSt_E and add these (also EAlaSt -> AlaSt and PasPer_E -> PasPer):
SanFraSt http://www.openstreetmap.org/?lat=35.686978&lon=-105.938137
WatSt_W http://www.openstreetmap.org/?lat=35.686085&lon=-105.938367

466: OldPecTr -> OldPecTr_N
US 66hissfe: add a point at NM300 to match 466

US 66histuc/I-40bltuc/US 54bustuc: CamCor -> CorRd (https://www.google.com/maps/@35.1697879,-103.7479493,3a,15y,271.2h,87.96t/data=!3m6!1e1!3m4!1s3lrHwaOv3Ws5jIc4mHvSnQ!2e0!7i16384!8i8192)
US 66histuc/I-40bltuc: NM237 -> US54Bus_E?
US 66histuc/I-40bltuc: NM104 -> NM104/209
US 66histuc: GSJ at CRAG east of NM278
US 66histuc: QuayRdAd -> CRAD (Quay is the county name)
US 66histuc: GSJ at CRU west of NM469
US 66histuc: QuayRdM -> CRM
US 66histuc: QuayRdG -> CRG
US 66histuc: ToNM392 is a dead end that doesn't access 392
US 66histuc: do we have confirmation of signage east of I-40(335)? east of NM469 (the unpaved portion)?
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 30, 2020, 06:34:58 pm
Ohio
US 6hischa: the west end should be at the pavement change (https://www.google.com/maps/@41.5806745,-81.2281235,3a,71y,89.56h,85.9t/data=!3m6!1e1!3m4!1s_dxXjIZhtdgQHgWA22EUHg!2e0!7i16384!8i8192) at the city limits; the first sign can be seen ahead in the distance
US 20hisnor: PeruCenRd -> MainSt (https://www.google.com/maps/@41.2413403,-82.6934591,3a,18.8y,156.08h,90.64t/data=!3m6!1e1!3m4!1sMuXQ8-rVPG9TPhupJ6MCzQ!2e0!7i13312!8i6656)? it appears that Main becomes Peru Center at the city limits, but both are posted to be helpful
US 20hisnor: move US20_E east to the underpass
US 20hispai: ew, no touchy

Oklahoma
US 66hiscli: I-40(62) -> ToI-40(62)
US 66hiselk/I-40blelk: OK6_W -> OK6_N (https://www.google.com/maps/@35.407532,-99.475309,3a,47.9y,312.71h,89.34t/data=!3m6!1e1!3m4!1sUrceba3w3Wxnbdzb8CH9XQ!2e0!7i16384!8i8192), OK6_E -> OK6_S (https://www.google.com/maps/@35.4116589,-99.405156,3a,75y,111.67h,90.93t/data=!3m6!1e1!3m4!1s2YoTf38XNVmfPs-Kzb52Wg!2e0!7i16384!8i8192)
US 66hiselk/I-40blelk: AptEntRd -> ToCouClubBlvd and shift west
US 66hiselr: OK66 -> I-40BL_E since traffic on old 66 will continue on SH 66
US 66hiseri: continue west to the state line (https://www.google.com/maps/@35.2214588,-99.9982776,3a,42.7y,171.19h,54.85t/data=!3m6!1e1!3m4!1sA7YfCXfXl0oXvObDe0fytg!2e0!7i13312!8i6656) (where it meets TXSpr30)
I-40bleri: N1720 -> N1720_S
US 66hislko: MorRd -> OveDr (https://www.google.com/maps/@35.5077509,-97.6943276,3a,34y,275.91h,80.83t/data=!3m6!1e1!3m4!1s4y0XDIBTZkKILgdt-qnoZQ!2e0!7i13312!8i6656)_W, OveDr -> OveDr_E
US 66hismia: E0130 -> E0130_E
US 66hismia does not overlap US 69 between US69/10 and 1stAve. Move 1stAve slightly off and add a new point on both at CirDr where the overlap will begin.
US 66hismia/US 69: E0050 -> E0050_W (or E50Rd_W (https://www.google.com/maps/@36.9436191,-94.8647589,3a,33.6y,219.78h,85.69t/data=!3m6!1e1!3m4!1semxVhN6Cu464BWBpJn9HyA!2e0!7i13312!8i6656)?)
US 66hismia/US 69altbax: MainSt -> CR137 (https://www.google.com/maps/@36.9489627,-94.7878879,3a,22.6y,185.18h,81.93t/data=!3m6!1e1!3m4!1syr-kaWyZj6Y0U7rTIfS21Q!2e0!7i16384!8i8192)
US 66hismia: is this signed east of Commerce?

US 66hisntu: eastbound uses (from 10th) Detroit (https://www.google.com/maps/@36.1476358,-95.9848051,3a,28.1y,103.85h,87.5t/data=!3m6!1e1!3m4!1sn7_tATDQ5n7xy5cwY_XEtg!2e0!7i13312!8i6656)-2nd (https://www.google.com/maps/@36.1551024,-95.987761,3a,44.4y,13.93h,87.17t/data=!3m6!1e1!3m4!1sTYiriies_dL47MBns4T_iQ!2e0!7i13312!8i6656)-1st-Norfolk (https://www.google.com/maps/@36.1586002,-95.9787312,3a,19.9y,91.2h,86.6t/data=!3m6!1e1!3m4!1svgnvA9ZwWLCz6rK-h7PVcw!2e0!7i13312!8i6656)-2nd. Westbound uses 2nd-Madison-3rd (https://www.google.com/maps/@36.1571828,-95.9797859,3a,41y,223.27h,85.2t/data=!3m6!1e1!3m4!1sKKhvhYJcDPR7hI_jCV2Cyw!2e0!7i13312!8i6656)-Elgin (https://www.google.com/maps/@36.1552695,-95.9858062,3a,32.2y,277.77h,88.66t/data=!3m7!1e1!3m5!1sa52c6rZ6shkeiFYmqn3XRA!2e0!5s20071101T000000!7i3328!8i1664) (sign is long gone)-7th (https://www.google.com/maps/@36.1516983,-95.9845071,3a,15y,197.87h,88.28t/data=!3m7!1e1!3m5!1swYoPaZhWx7Rs_SbqtnZFLA!2e0!5s20071101T000000!7i13312!8i6656)-Cheyenne (https://www.google.com/maps/@36.1489707,-95.9908112,3a,35.8y,207.73h,86.85t/data=!3m6!1e1!3m4!1sZAI-hniT6YzkFcz-2Gi6rA!2e0!7i13312!8i6656) (to 11th). I'm not sure how to handle eastbound using Detroit from 10th; maybe we ignore this (it's signed 'to' anyway since it's not the actual old alignment, but so are other turns that aren't on it). Maybe like so:
11thSt http://www.openstreetmap.org/?lat=36.145967&lon=-95.989856
7thSt_W http://www.openstreetmap.org/?lat=36.148748&lon=-95.991422
7thSt_E http://www.openstreetmap.org/?lat=36.151005&lon=-95.984910
3rdSt_W http://www.openstreetmap.org/?lat=36.155289&lon=-95.987184
NorAve http://www.openstreetmap.org/?lat=36.157710&lon=-95.978531

US 66hisntu: I-244 -> DelAve, move HarAve south halfway to 1st Street
US 66hisntu: US66His_E -> 11thSt
US 66hisokl is in the wrong direction
US 66hisokl: I-235(2B) -> BroAve? I-235(2A) -> SanFeAve?
US 66hisokl: I-35(141) -> I-35
US 66hisokl/US 77: WEdmRd -> EdmRd
US 66hisokl/US 77: BouSt -> Blvd (https://www.google.com/maps/@35.6528938,-97.4780649,3a,41.4y,295.35h,93.87t/data=!3m6!1e1!3m4!1sQCNIJGDrbfzEt35O9jxZKg!2e0!7i13312!8i6656)
US 66histul: why the west end at 51stSt? if the westernmost sign is at 33rdAve, end it at the city limits
US 66histul: move I-244(1D) southwest to the overpass
US 66hisvin/US 60/US 69: ScrRd -> ScrSt (https://www.google.com/maps/@36.6277683,-95.1615647,3a,75y,62.75h,81.71t/data=!3m6!1e1!3m4!1sbjb_9oOPycoa41pXKYxg-A!2e0!7i16384!8i8192)
US 66hisvin: I-44(289) -> I-44

US 66hiswea: signage (https://www.google.com/maps/@35.5252021,-98.7125259,3a,41.9y,218.7h,86.95t/data=!3m6!1e1!3m4!1s6r0B6HrrZjbTp4pDBG9ImA!2e0!7i13312!8i6656) is a little different west of downtown. SWMainSt -> MainSt_W and replace OK54_N with:
OK54_N http://www.openstreetmap.org/?lat=35.524927&lon=-98.715656
SWMainSt_W http://www.openstreetmap.org/?lat=35.524927&lon=-98.712566
Also add RaiSt (not RaiAve (https://www.google.com/maps/@35.5249614,-98.7127146,3a,15.1y,208.24h,84.51t/data=!3m6!1e1!3m4!1sB8cmvtMY2jCT7roxs0kZlQ!2e0!7i13312!8i6656)) on 54.

US 66hiswea: I-40(88) -> OK58_N and move northwest, N2480 -> OK58_S, and I don't know what to do with 58med (it has a one-way pair per signage).
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 30, 2020, 09:07:15 pm
Oregon
US 30hiscas: I found one sign (https://zigzag.odot.state.or.us/uniquesig78ff0d392336a284c69037220217ce07902ac9825cdd667d43555eddf0570a01/uniquesig0/cf/dvl/images4//VideoImages/2019/002___Columbia%20River/Add/Device2/044950.jpg); it's very recent. Are we sure it exists west of I-84(47)? If so, could it use Forest Lane west of ForLn?
US 30hiscol: delete I-84(18); it ends at HistColRivHwy (https://www.google.com/maps/@45.5384358,-122.3751941,3a,55.5y,359.87h,85.36t/data=!3m6!1e1!3m4!1sK1DLkapshBKjyT5eXDnE0g!2e0!7i13312!8i6656) (and is signed 'to' (https://www.google.com/maps/@45.5435038,-122.3816105,3a,39.7y,226.88h,90.41t/data=!3m6!1e1!3m4!1sTWWLgCuPlQ8cMYu6qfnUPw!2e0!7i13312!8i6656) at I-84(18))
US 30hiscol: HistColRivHwy -> CroPoiHwy
US 30hiscol: StarkSt -> StaSt
US 30hiscol: BellRd -> BellRd_W, move MerRd just west to BellRd_E
US 30hiscol: *Fall -> *Fal
US 30hiscol: BriVeilFall -> BriVeil (https://www.google.com/maps/@45.5530903,-122.1833038,3a,15.1y,289.72h,84.4t/data=!3m6!1e1!3m4!1sfW-HuacwOyzIS-elMksjDg!2e0!7i13312!8i6656)?
US 30hiscol: there's nothing at OneFall (https://www.google.com/maps/@45.5898071,-122.0750617,3a,75y,233.37h,73.44t/data=!3m6!1e1!3m4!1sXorc7eVtYEtdwHkIr-R4dQ!2e0!7i13312!8i6656)
US 30hiscol: I-84(35) -> ToI-84(35) and move southwest
US 30hisrow/US 30: RocCreRd -> RockCreRd
US 30hisrow/US 30: RowCrst -> RowCre?
US 30hisrow: delete I-84(82)
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on January 30, 2020, 09:48:24 pm
Texas
US 66hisama: Why ArnRd and not DowRd or HopeRd? are there signs west of the turn at I-40BL_W? If there are none, maybe it'd be best to extend it to HillRd (https://www.google.com/maps/@35.1917827,-102.0282574,3a,24.5y,244.83h,89.58t/data=!3m6!1e1!3m4!1s7c1I4CRg16p7-xX2kujZ3w!2e0!7i13312!8i6656), where original 66 curved left under the railroad (remnant pavement? (https://www.google.com/maps/@35.1916482,-102.0275623,3a,41.5y,217.39h,82.6t/data=!3m6!1e1!3m4!1s3jGEuLD2QxfoVov0Q-85bw!2e0!7i13312!8i6656)).
US 66hisama/TXLp 279: GeoSt -> McMasSt (https://www.google.com/maps/@35.2114989,-101.865878,3a,75y,122.61h,92.93t/data=!3m6!1e1!3m4!1sPbwI5JfXakHpw9qI1yM3dg!2e0!7i13312!8i6656)
US 66hisama: does this sign in the background (https://www.google.com/maps/@35.2075135,-101.8357526,3a,15y,105.2h,88.85t/data=!3m6!1e1!3m4!1sOcBtT6iT2LUE0caGaGg6fQ!2e0!7i13312!8i6656) point straight or left on Fillmore? Fillmore was 66 from the beginning, so it probably points left, meaning delete US60_W and add something on Amarillo Boulevard between Fillmore and Pierce.
US 66hisama/I-40blama: missing GSJ at LakeSt west of TX136
US 66hisama/I-40blama: AveB -> BAve (https://www.google.com/maps/@35.2400587,-101.6844861,3a,15y,62.08h,87.38t/data=!3m6!1e1!3m4!1saacP1A7NyWutHTOXwd6QBA!2e0!7i13312!8i6656)

Washington
US 10hische: where is this signed? I can't find anything on GSV
US 10hisfre: presumably we have confirmation that this exists
US 10hisrit is not signed at RdU (https://www.google.com/maps/@47.0839172,-119.0449504,3a,45.4y,236.66h,84.66t/data=!3m6!1e1!3m4!1srAXf2JIuxH2qB8YxQmkTkg!2e0!7i16384!8i8192) (which is actually U Road), but is signed eastbound at the county line (https://www.google.com/maps/@47.0841904,-118.981626,3a,15y,134.33h,87.52t/data=!3m6!1e1!3m4!1sEi1AhQWacjdDu0_fzvOBSQ!2e0!7i16384!8i8192). So truncate it at a new Gra/Ada point.
US 10hisrit: LauRd barely exists (https://www.google.com/maps/@47.0814136,-118.726368,3a,57.4y,165.22h,86.83t/data=!3m6!1e1!3m4!1sGIE8BYKoo_oAeKT-xB_Myg!2e0!7i3328!8i1664)
US 10hisrit: this is not signed (https://www.google.com/maps/@47.1031511,-118.4943065,3a,16.8y,82.24h,87.87t/data=!3m6!1e1!3m4!1sqkK0lmvWeAN8PcHwKlMZ5Q!2e0!7i16384!8i8192) east of PahaPacRd_N (-> PahaPacRd). It needs to be split in two, restarting at I-90(220) (https://www.google.com/maps/@47.1105631,-118.397707,3a,20.3y,108.46h,86.63t/data=!3m6!1e1!3m4!1sJXGtxO7jHjrZvaYE2yNVPA!2e0!7i16384!8i8192).
US 10hisrit: I-90BL_E -> SchRd? I-90 BL isn't signed here
I-90blrit: move DanRd_E to the right place
US 10hisrit: NorHilRd -> NHilRd?
US 10hisrit: add DurRd southeast of I-90(231)
US 10hisrit needs field checking to see how far east it's signed in Sprague
US 99hisfed: truncate the south end to a new Pie/Kin point at the county line
US 99hisfed/WA 99: move 16thAve_S south
US 99hisfed/WA 99: 16thAve -> 16thAve_N
Title: Re: usaush: United States Historic US Routes
Post by: Bickendan on February 04, 2020, 03:06:12 pm
Oregon
US 30hiscas: I found one sign (https://zigzag.odot.state.or.us/uniquesig78ff0d392336a284c69037220217ce07902ac9825cdd667d43555eddf0570a01/uniquesig0/cf/dvl/images4//VideoImages/2019/002___Columbia%20River/Add/Device2/044950.jpg); it's very recent. Are we sure it exists west of I-84(47)? If so, could it use Forest Lane west of ForLn?
I'm going to need to field verify the route when I return from India; I saw that shield from I-84 but gmsv wasn't helpful.
Quote
US 30hiscol: delete I-84(18); it ends at HistColRivHwy (https://www.google.com/maps/@45.5384358,-122.3751941,3a,55.5y,359.87h,85.36t/data=!3m6!1e1!3m4!1sK1DLkapshBKjyT5eXDnE0g!2e0!7i13312!8i6656) (and is signed 'to' (https://www.google.com/maps/@45.5435038,-122.3816105,3a,39.7y,226.88h,90.41t/data=!3m6!1e1!3m4!1sTWWLgCuPlQ8cMYu6qfnUPw!2e0!7i13312!8i6656) at I-84(18))
If anything, I'm going to move the western terminus to the western exit 17 -
While US 30 doesn't peel off from I-84 until Cascade Locks, it is unsigned between 17 and 35, making US 30H defacto US 30. Furthermore, Hist Col Riv Hwy itself begins at 244th Ave (though from 244th to 257th isn't useful for us), and the US 30H shield at 257th and Frontage Rd is ambiguous enough (no 'to' assembly).
Quote
US 30hiscol: HistColRivHwy -> CroPoiHwy
US 30hiscol: StarkSt -> StaSt
US 30hiscol: BellRd -> BellRd_W, move MerRd just west to BellRd_E
US 30hiscol: *Fall -> *Fal
US 30hiscol: BriVeilFall -> BriVeil (https://www.google.com/maps/@45.5530903,-122.1833038,3a,15.1y,289.72h,84.4t/data=!3m6!1e1!3m4!1sfW-HuacwOyzIS-elMksjDg!2e0!7i13312!8i6656)?
US 30hiscol: there's nothing at OneFall (https://www.google.com/maps/@45.5898071,-122.0750617,3a,75y,233.37h,73.44t/data=!3m6!1e1!3m4!1sXorc7eVtYEtdwHkIr-R4dQ!2e0!7i13312!8i6656)
Without looking, that should be the Oneita Falls trailhead and should have parking nearby. Will double check that.
Quote
US 30hiscol: I-84(35) -> ToI-84(35) and move southwest
US 30hisrow/US 30: RocCreRd -> RockCreRd
US 30hisrow/US 30: RowCrst -> RowCre?
US 30hisrow: delete I-84(82)
Title: Re: usaush: United States Historic US Routes
Post by: Jim on March 12, 2020, 11:51:26 pm
Oregon
US 30hiscol: delete I-84(18); it ends at HistColRivHwy (https://www.google.com/maps/@45.5384358,-122.3751941,3a,55.5y,359.87h,85.36t/data=!3m6!1e1!3m4!1sK1DLkapshBKjyT5eXDnE0g!2e0!7i13312!8i6656) (and is signed 'to' (https://www.google.com/maps/@45.5435038,-122.3816105,3a,39.7y,226.88h,90.41t/data=!3m6!1e1!3m4!1sTWWLgCuPlQ8cMYu6qfnUPw!2e0!7i13312!8i6656) at I-84(18))

I drove this today, and can confirm the clear END sign at the bridge at point HistColRivHwy, well before I-84.  As a driver trying to clinch, I saw this sign and assumed it was "safe" to turn left across the bridge to drive into Troutdale.
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on May 21, 2020, 09:54:35 pm
Any information on this sign in Minnesota? https://www.usends.com/61.html says nothing more.
(http://www.usends.com/uploads/7/5/0/3/75032313/old61-2016-min_orig.jpg)
Title: Re: usaush: United States Historic US Routes
Post by: froggie on May 22, 2020, 07:39:37 am
^ Put up by Chisago County to mark the former routing.  Officially a county route.
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on May 22, 2020, 09:51:27 am
^ Put up by Chisago County to mark the former routing.  Officially a county route.
Which is different from the rest of this system how?
Title: Re: usaush: United States Historic US Routes
Post by: oscar on May 22, 2020, 10:19:15 am
^ Put up by Chisago County to mark the former routing.  Officially a county route.
Which is different from the rest of this system how?

"Old" rather than "Historic"? Maybe that shouldn't make a difference, but then other states like Maryland occasionally use "Old" banners on former routings with no historic significance.
;
Title: Re: usaush: United States Historic US Routes
Post by: osu-lsu on May 22, 2020, 07:16:23 pm
^ Put up by Chisago County to mark the former routing.  Officially a county route.
Which is different from the rest of this system how?

Routes considered for "US Historic Routes" have brown shields, or background, and have 'Historic' in the banner above the number.
(https://live.staticflickr.com/65535/48148451687_1a3036b07c_z.jpg)
Title: Re: usaush: United States Historic US Routes
Post by: Jim on June 24, 2020, 09:03:08 am
There's a label IA192 in ia.us006hiscou but we have no IA 192 in TM.
Title: Re: usaush: United States Historic US Routes
Post by: osu-lsu on June 24, 2020, 09:30:12 am
Look at any of your base maps for Council Bluffs, Iowa. Iowa 192 used to run through the heart of Council Bluff (as a N-S arterial) and whomever set up the routing for Historic US 6, had the western extent end at (the now former) routing of Iowa 192.
Yes, there is no Iowa 192 signed in Council Bluff. I don't recall seeing any signs for that road when I was in Council Bluff/Omaha, last year (doing Lincoln Hwy traveling).
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on June 24, 2020, 09:38:42 am
There's a label IA192 in ia.us006hiscou but we have no IA 192 in TM.
https://forum.travelmapping.net/index.php?topic=97.msg17639#msg17639
Title: Re: usaush: United States Historic US Routes
Post by: Bickendan on July 23, 2020, 03:58:46 am
Per my day trip today (yesterday):
OR US 30H Cascade Locks: (westbound) From Exit 51 (note: not signed from I-84 itself) to western Exit 44, with an overlap on mainline US 30 from Forest Dr to I-84(44_w).
OR US 30H Columbia River Gorge: signed as exiting I-84/US 30 at Exit 35, but signed along NE Frontage Rd. Ambiguous, considering routing along Frontage Rd to Exit 37, despite signage along I-84 (Frontage Rd serves Warrendale while waterfalls traffic exits at 35).
Title: Re: usaush: United States Historic US Routes
Post by: neroute2 on July 23, 2020, 10:02:19 am
For future checking: US 6 in Palmdale (not on Sierra Highway): https://www.aaroads.com/forum/index.php?topic=27290
Title: Re: usaush: United States Historic US Routes
Post by: the_spui_ninja on July 24, 2020, 11:25:39 am
Look at any of your base maps for Council Bluffs, Iowa. Iowa 192 used to run through the heart of Council Bluff (as a N-S arterial) and whomever set up the routing for Historic US 6, had the western extent end at (the now former) routing of Iowa 192.
Yes, there is no Iowa 192 signed in Council Bluff. I don't recall seeing any signs for that road when I was in Council Bluff/Omaha, last year (doing Lincoln Hwy traveling).
It died in the great 2016-ish Council Bluffs decommissioning where Iowa turned over the state-maintained roads in city limits to the city.
Title: Re: usaush: United States Historic US Routes
Post by: norheim on August 22, 2020, 03:49:36 pm
Historic US 10 is signed in George, Washington.