Just noticed today that the Route Log and Finder list was updated on January 27, 2016. There is a new URL as well at http://www.fhwa.dot.gov/planning/national_highway_system/interstate_highway_system/routefinder/index.cfm
I-41 is now included and I've noted mileage additions to I-69, I-73 and I-74. The I-69 suffixed routes now match the TxDOT Highway Designation Files, which reflected additions from this past fall.
Thanks for the note. Didn't see this, either.
(NY wins with 32 routes :D)
Noted that NC tweaked the mileages of a few routes including I-26, I-77, I-277, I-440 and I-495
The mileage for California's I-210 decreased, likely reflecting the portion that is now CA 57 south to the Kellogg Interchange.
I-22 mileage for Mississippi is added now.
The Maine figures for I-95/295/495 are still pre-2004.
I-181 is still referenced for Tennessee.
The I-465 Indiana mileage still includes what is I-865.
I-55 figures now also reference the overlaps with I-64 in IL and MO.
Quote from: Alex on February 02, 2016, 12:47:24 PM
I-22 mileage for Mississippi is added now.
However, no mileage for I-269 in either Mississippi or Tennessee.
Quote from: Alex on February 02, 2016, 12:47:24 PM
The mileage for California's I-210 decreased, likely reflecting the portion that is now CA 57 south to the Kellogg Interchange.
I wonder if they will ever extend I-210 along CA-210. I've seen it suggested elsewhere, can't remember where though.
The overlap between I-95 and I-495 over the Capital Beltway is not acknowledged in the route log, as the I-495 MD/VA mileage shown in the route log only covers about half of the beltway (a little more than 30 miles), and the I-95 DC mileage of 0.11 mile is only shown for I-95 even though it is signed for both I-95 and I-495. For whatever it's worth.
I verified/updated every active route on the Interstate Guide with the 2015 figures today.
Adding to what Andy wrote:
The Baltimore beltway mileage for I-695 still omits the "MD 695" portion to the south.
The I-49 mileage for LA was updated to include the new section north of Shreveport.
I-90's total for WI is still off.
Quote from: Alex on February 02, 2016, 11:44:58 PM
The Baltimore beltway mileage for I-695 still omits the "MD 695" portion to the south.
Which is apparently correct...FHWA has never added this piece. I-895 is also missing the non-Interstate piece south of I-695.
The Route Log lists I-80 in California as 199 miles, but it's actually closer to 205 miles long. Perhaps the section in City/County of San Francisco remains omitted? But "San Francisco" itself remains listed in the log, and the portion of I-80 between the Bay Bridge and US 101 was recently upgraded substantially and improved.
Quote from: Alex on February 02, 2016, 12:47:24 PM
I-181 is still referenced for Tennessee.
I-26 is listed at 31 miles in Tennessee, which gets you from the state line to just past US 321. Seems incorrect.
The I-181 length (8.4 miles) looks correct (before I-26 was extended), from I-81 to US 11W.
I wonder if the piece of I-86 east of I-81 is included. Binghamton is not listed in the cities.
Quote from: GrzrdHowever, no mileage for I-269 in either Mississippi or Tennessee.
Not surprising. Given how new the tiny section that opened is, TDOT and MDOT likely haven't updated their internal numbers yet.
Quote from: andy3175The overlap between I-95 and I-495 over the Capital Beltway is not acknowledged in the route log, as the I-495 MD/VA mileage shown in the route log only covers about half of the beltway (a little more than 30 miles), and the I-95 DC mileage of 0.11 mile is only shown for I-95 even though it is signed for both I-95 and I-495. For whatever it's worth.
FHWA doesn't officially consider the overlap to exist. To them, the eastern half is only I-95, not both routes. They've allowed VDOT and SHA to sign 495 for continuity purposes.
Quote from: Rothman on February 03, 2016, 12:48:21 AM
I wonder if the piece of I-86 east of I-81 is included. Binghamton is not listed in the cities.
FWIW, the figure for I-86 in NY was unchanged from the 2014 log.
Quote from: mvak36 on February 02, 2016, 02:09:53 PM
Quote from: Alex on February 02, 2016, 12:47:24 PM
The mileage for California's I-210 decreased, likely reflecting the portion that is now CA 57 south to the Kellogg Interchange.
I wonder if they will ever extend I-210 along CA-210. I've seen it suggested elsewhere, can't remember where though.
I think the answer to that is the same as when they'll extend I-15 along CA 15, or change CA 905 to I-905: Probably not in our lifetimes, but eventually.
Quote from: andy3175 on February 02, 2016, 11:56:46 PM
The Route Log lists I-80 in California as 199 miles, but it's actually closer to 205 miles long. Perhaps the section in City/County of San Francisco remains omitted? But "San Francisco" itself remains listed in the log, and the portion of I-80 between the Bay Bridge and US 101 was recently upgraded substantially and improved.
similarly, Philadelphia is listed for I-295; a route doesn't need to enter the city/county/state proper to serve the metro area.
There is no Bangor in Maryland.
Quote from: cpzilliacus on February 03, 2016, 12:18:57 PM
There is no Bangor in Maryland.
Speaking of Maryland, the distance for I-195 was shortened from 4.71 to 4.35.
Quote from: andy3175 on February 02, 2016, 11:56:46 PM
The Route Log lists I-80 in California as 199 miles, but it's actually closer to 205 miles long. Perhaps the section in City/County of San Francisco remains omitted? But "San Francisco" itself remains listed in the log, and the portion of I-80 between the Bay Bridge and US 101 was recently upgraded substantially and improved.
The San Francisco Skyway west of 480 was removed from the official Interstate system 1968 IIRC (and I recall it was part of California trying to get more chargeable mileage for the Century Freeway/105) Having said that, I would say 95% of the improvements have taken place from 5th Street eastward at most (along the old US 40/50 ramps that are the original west terminus of the Bay Bridge) along where the old 480 junction used to be; the section of freeway between 101 and 5th is pretty unchanged from its 1950s origins and I don't think has ever been widened or realigned.
Quote from: andy3175 on February 02, 2016, 11:56:46 PM
The Route Log lists I-80 in California as 199 miles, but it's actually closer to 205 miles long. Perhaps the section in City/County of San Francisco remains omitted? But "San Francisco" itself remains listed in the log, and the portion of I-80 between the Bay Bridge and US 101 was recently upgraded substantially and improved.
As far as FHWA is concerned, I-80 ends at the west end of the Bay Bridge. The early 1950s proposal was for a western extension of I-80 to the Central Freeway, then west along the Fell/Oak panhandle of Golden Gate Park, then ending at an interchange with the Park Presidio Freeway which would have replaced Park Presidio Boulevard. That proposal is what California mileage is based on, although not the exit numbers.
This is a good starting point for the confusing history: http://www.cahighways.org/maps-sf-fwy.html
I'm not sure what the definition of "serving major cities" is. It lists I-275 as serving both Ann Arbor & Detroit. Seems a bit of a stretch.
Also, it says Detroit is served by I-295. Definite mistake there.
Monroe, MI served by I-74. I think they meant I-75.
It lists Toledo, OH as served by I-80, but not I-90.
And if Ann Arbor & Detroit proper can be served by I-275, shouldn't I-80 & I-90, I-475 (OH) & I-280 be considered as serving Monroe, MI?
Quote from: JCinSummerfield on February 03, 2016, 01:17:31 PM
And if Ann Arbor & Detroit proper can be served by I-275, shouldn't I-80 & I-90, I-475 (OH) & I-280 be considered as serving Monroe, MI?
No.
The definition of an anal roadgeek: someone who doesn't think I-275 can serve Detroit unless I-80/90 serves Monroe.
Quote from: kkt on February 03, 2016, 12:48:38 PM
Quote from: andy3175 on February 02, 2016, 11:56:46 PM
The Route Log lists I-80 in California as 199 miles, but it's actually closer to 205 miles long. Perhaps the section in City/County of San Francisco remains omitted? But "San Francisco" itself remains listed in the log, and the portion of I-80 between the Bay Bridge and US 101 was recently upgraded substantially and improved.
As far as FHWA is concerned, I-80 ends at the west end of the Bay Bridge. The early 1950s proposal was for a western extension of I-80 to the Central Freeway, then west along the Fell/Oak panhandle of Golden Gate Park, then ending at an interchange with the Park Presidio Freeway which would have replaced Park Presidio Boulevard. That proposal is what California mileage is based on, although not the exit numbers.
Hm, Google Maps shows 203 miles from the 101/80 split at the Central Freeway east to the Nevada border - which is pretty close to the California mileage listed above, without having to include the unbuilt Western Freeway (or the existing Central Freeway segment that was I-80/US 101 from the late 1950s to 1968).
They updated the mileage for I-73 and I-99 in the logs, but not on their list of Shortest Interstates in the 'Miscellaneous Interstate Facts' on the main page (listed as updated 1/28/16), which still lists I-73 as the shortest 2di with 12.27 miles and I-99 as the third at 55 miles. As the log states, I-73 is now 80.85 miles long. The top honor should go to I-97 at 17.62.
Also, the I-74 listing for NC, though revised, is still wrong. The total mileage for I-74 signed freeways is around 125, though they list it as 72.12. The route runs with I-73 from Exit 25 to Exit 80, or 55 miles, they only list a 16.26 mile concurrency, nor do they list its running with I-77 for about 5 miles.
I can understand not including the overlap with I-77. It ends at the state line and the overlap is essentially useless. Does NC honestly believe that states other than themselves have any interest in building I-74?
Apparently, Dillon is the only "major city" served by I-95 in South Carolina. Florence is larger and more of a regional hub in the Pee-Dee region so the choice of Dillon seem strange there.
While considering major cities served by interstates, we should add Evansville to the list of those served by I-69 in Indiana. The table lists cities as small as Gas City and Washington among those served, but omits E-ville. I suppose it was left off when I-69 stopped at I-64, but that's no longer the case.
I-41's concurrency mileage does not reflect the concurrency along US 41.
It shouldn't. It only lists overlaps with other interstates.
Quote from: mvak36 on February 02, 2016, 02:09:53 PM
Quote from: Alex on February 02, 2016, 12:47:24 PM
The mileage for California's I-210 decreased, likely reflecting the portion that is now CA 57 south to the Kellogg Interchange.
I wonder if they will ever extend I-210 along CA-210. I've seen it suggested elsewhere, can't remember where though.
If you go by the new BGS that is on I-10 West just east (1-2 miles) of the I-210 (CA-210) exit then the whole thing is already I-210
This one?
https://goo.gl/maps/j5qR4HvTkW12
Quote from: TheStranger on February 03, 2016, 12:33:07 PM
Quote from: andy3175 on February 02, 2016, 11:56:46 PM
The Route Log lists I-80 in California as 199 miles, but it's actually closer to 205 miles long. Perhaps the section in City/County of San Francisco remains omitted? But "San Francisco" itself remains listed in the log, and the portion of I-80 between the Bay Bridge and US 101 was recently upgraded substantially and improved.
The San Francisco Skyway west of 480 was removed from the official Interstate system 1968 IIRC (and I recall it was part of California trying to get more chargeable mileage for the Century Freeway/105) Having said that, I would say 95% of the improvements have taken place from 5th Street eastward at most (along the old US 40/50 ramps that are the original west terminus of the Bay Bridge) along where the old 480 junction used to be; the section of freeway between 101 and 5th is pretty unchanged from its 1950s origins and I don't think has ever been widened or realigned.
Is the San Francisco Skyway 6 miles long? I'm trying to understand how I-80 is 205 miles, yet the route log lists only 199. Your explanation may account for two or three miles, not the full six differential. Perhaps this has something to do with I-80's realignment many years ago in Sacramento as well?
Quote from: TheStranger on February 03, 2016, 02:22:18 PM
Quote from: kkt on February 03, 2016, 12:48:38 PM
Quote from: andy3175 on February 02, 2016, 11:56:46 PM
The Route Log lists I-80 in California as 199 miles, but it's actually closer to 205 miles long. Perhaps the section in City/County of San Francisco remains omitted? But "San Francisco" itself remains listed in the log, and the portion of I-80 between the Bay Bridge and US 101 was recently upgraded substantially and improved.
As far as FHWA is concerned, I-80 ends at the west end of the Bay Bridge. The early 1950s proposal was for a western extension of I-80 to the Central Freeway, then west along the Fell/Oak panhandle of Golden Gate Park, then ending at an interchange with the Park Presidio Freeway which would have replaced Park Presidio Boulevard. That proposal is what California mileage is based on, although not the exit numbers.
Hm, Google Maps shows 203 miles from the 101/80 split at the Central Freeway east to the Nevada border - which is pretty close to the California mileage listed above, without having to include the unbuilt Western Freeway (or the existing Central Freeway segment that was I-80/US 101 from the late 1950s to 1968).
I looked at this too and arrived at a bit more, closer to 205. Wikipedia lists 205.07 (https://en.wikipedia.org/wiki/Interstate_80_in_California), which references CalNexus (http://www.dot.ca.gov/hq/traffops/engineering/calnexus/pdf/80.pdf).
So what is the total current official mileage of the Interstate system? I did not see it listed but admittedly I did not have time to read the entire thing.
I find it interesting that I-35W and 35E are labeled as such, but I-69W, 69C and 69E are labeled 69 West, 69 Central and 69 East.
Quote from: Bickendan on February 05, 2016, 02:32:49 AM
I find it interesting that I-35W and 35E are labeled as such, but I-69W, 69C and 69E are labeled 69 West, 69 Central and 69 East.
Technically that's what they're called by the TxDOT Minute Order and ISTEA Section 1105, as amended.
Quote from: andy3175 on February 04, 2016, 12:01:38 AM
Is the San Francisco Skyway 6 miles long? I'm trying to understand how I-80 is 205 miles, yet the route log lists only 199. Your explanation may account for two or three miles, not the full six differential. Perhaps this has something to do with I-80's realignment many years ago in Sacramento as well?
Saw your followup post. To clarify what the Skyway is...it's 80 between US 101 and the old 480 junction (today's Fremont Street exit westbound) which was built as US 40 and US 50 in the early 1950s.
Google Maps shows a 1.6 mile length for that segment, from the 101/80 split northbound at the Central Freeway to the beginning of the double-decker portion of the Bay Bridge.
So now I do wonder if the 80 realignment through Sacramento affected the calculations somewhere.
Quote from: TheStranger on February 05, 2016, 12:46:03 PM
Quote from: andy3175 on February 04, 2016, 12:01:38 AM
Is the San Francisco Skyway 6 miles long? I'm trying to understand how I-80 is 205 miles, yet the route log lists only 199. Your explanation may account for two or three miles, not the full six differential. Perhaps this has something to do with I-80's realignment many years ago in Sacramento as well?
Saw your followup post. To clarify what the Skyway is...it's 80 between US 101 and the old 480 junction (today's Fremont Street exit westbound) which was built as US 40 and US 50 in the early 1950s.
Google Maps shows a 1.6 mile length for that segment, from the 101/80 split northbound at the Central Freeway to the beginning of the double-decker portion of the Bay Bridge.
So now I do wonder if the 80 realignment through Sacramento affected the calculations somewhere.
The Goog calls it 18.5 miles from the ends of I-80 business. There seems to be more here.
Quote from: noelbotevera on February 05, 2016, 03:22:34 PM
Quote from: TheStranger on February 05, 2016, 12:46:03 PM
Quote from: andy3175 on February 04, 2016, 12:01:38 AM
Is the San Francisco Skyway 6 miles long? I'm trying to understand how I-80 is 205 miles, yet the route log lists only 199. Your explanation may account for two or three miles, not the full six differential. Perhaps this has something to do with I-80's realignment many years ago in Sacramento as well?
Saw your followup post. To clarify what the Skyway is...it's 80 between US 101 and the old 480 junction (today's Fremont Street exit westbound) which was built as US 40 and US 50 in the early 1950s.
Google Maps shows a 1.6 mile length for that segment, from the 101/80 split northbound at the Central Freeway to the beginning of the double-decker portion of the Bay Bridge.
So now I do wonder if the 80 realignment through Sacramento affected the calculations somewhere.
The Goog calls it 18.5 miles from the ends of I-80 business. There seems to be more here.
Park-Presidio Blvd. and Fulton St. (the north edge of Golden Gate Park) to I-80 and Fremont St. is 5.6 miles according to Google Maps, via Fell St. and 101.
Quote from: NE2 on February 03, 2016, 01:28:19 PM
Quote from: JCinSummerfield on February 03, 2016, 01:17:31 PM
And if Ann Arbor & Detroit proper can be served by I-275, shouldn't I-80 & I-90, I-475 (OH) & I-280 be considered as serving Monroe, MI?
No.
The definition of an anal roadgeek: someone who doesn't think I-275 can serve Detroit unless I-80/90 serves Monroe.
Has anybody ever told you your mouth needs a tether? If I had to lay money down, I'd bet there would be plenty that have.