Any US City with two US routes in them, that do not physically touch?
I can give you St. Petersburg, FL which has both US 19 and US 92 where both routes do not intersect. In fact US 19 and US 92 are the city's only US routes in its case. One going E-W while the other N-S and do not junction. In this scenario you not only have two different running US routes, but you have a major city where both of its only routes do not meet as well.
Are there any other cities proper that have at least two routes in its corporation that do not meet?
Do overpasses or instances where they cross over one another with no ramps count? If so, US 206 and US 1 in Trenton NJ.
https://www.google.com/maps/@40.2170436,-74.7603161,15z
Nice find though, but they do somewhat connect near the Brunswick Circle as US 1 comes close to it there within a half a mile using Strawberry Street. Plus Business US 1 does junction with US 206 inside the circle and I would say that it is a loop off its parent.
Louisville. US 42 and US 31W. Also US 42 and US 150.
Frankfort. US 127 and US 460.
Cincinnati. US 22 and US 50.
I don't think US 40 and US 50 touch in St. Louis.
In Asheville, US 25A avoids most of the other US routes in that city.
US 50 does not even enter the City of St. Louis according to Google Maps.
I believe US-29 and US-50 never meet in the District of Columbia. US-1 touches both of them within the District, but I believe they never touch each other.
Some Louisiana examples:
US 71 and US 171 in Shreveport (ugh)
US 63 and US 80 in Ruston
US 11 and US 61 in New Orleans (not anymore)
Quote from: 1995hoo on May 19, 2014, 09:01:14 PM
I believe US-29 and US-50 never meet in the District of Columbia. US-1 touches both of them within the District, but I believe they never touch each other.
This one is a great find, as US 29 and US 50 do not touch at all. They actually intersect miles away in Fairfax, VA, but you can include Arlington, VA as well for both of these routes do enter that without touching as well.
In Atlanta, US 23 does not meet either US 19 or US 41.
I don't believe US-60 intersects either US-33 or US-250 in Richmond. They come within 1000 feet though.
Also US 69 and US 271 in Tyler, TX, the only 2 in that city.
In Dallas truncation a caused a lot of these:
US 80 and All US routes there except 67 and it's hidden there.
US 75 and US 77
US 175 and all other US routes in Dallas
In Fort Worth US 81 and US 377
In Jacksonville, TX, US 79 and US 175
Quote from: Thing 342 on May 19, 2014, 09:19:30 PM
I don't believe US-60 intersects either US-33 or US-250 in Richmond. They come within 1000 feet though.
I do think they did at one time for US 60 and 250. I am not sure about that one, but some of our VA experts on here would know for sure.
Boston has three routes that don't touch. US-1, US-3, and US-20 never touch each other at all.
Quote from: hbelkins on May 19, 2014, 08:40:31 PM
I don't think US 40 and US 50 touch in St. Louis.
They don't meet in Kansas City, either. Interestingly, but not surprisingly, they touched at one point in time in both cities.
US-6 and US-67 don't intersect each other in Davenport, but they do farther east in Bettendorf. (Come to think of it, 67 doesn't meet US-61 in Davenport anymore, either, just Business 61.)
In Chicago, US-14 doesn't make it quite far enough to intersect US-12 or US-20. However, it meets 12 in Des Plaines.
Quote from: Zeffy on May 19, 2014, 08:28:06 PM
Do overpasses or instances where they cross over one another with no ramps count?
I don't think they should, but US-6 and US-218 miss each other in Coralville, IA for that reason.
Quote from: roadman65 on May 19, 2014, 09:16:12 PM
Quote from: 1995hoo on May 19, 2014, 09:01:14 PM
I believe US-29 and US-50 never meet in the District of Columbia. US-1 touches both of them within the District, but I believe they never touch each other.
This one is a great find, as US 29 and US 50 do not touch at all. They actually intersect miles away in Fairfax, VA, but you can include Arlington, VA as well for both of these routes do enter that without touching as well.
Good point. I didn't think of Arlington because it's a county rather than a city, but it is interesting that this happens for the same two routes in two adjacent jurisdictions.
Following further on the point, US-1 also passes through Arlington County and does not touch either US-29 or US-50 while there (it runs up through Crystal City and over the 14th Street Bridge into DC).
In Indianapolis, US 136 never touches any other US Highway, because all the other highways have been rerouted around the 465 beltway while it instead terminates at 465.
Do US 301 and 401 meet in Fayetteville anymore?
Atlantic City: US 30 and US 40/322 (if we permit concurrencies).
US 14A and US 385 in Deadwood.
Quote from: roadman65 on May 19, 2014, 09:33:32 PM
Quote from: Thing 342 on May 19, 2014, 09:19:30 PM
I don't believe US-60 intersects either US-33 or US-250 in Richmond. They come within 1000 feet though.
I do think they did at one time for US 60 and 250. I am not sure about that one, but some of our VA experts on here would know for sure.
US 250 ended at US 60 until 2003.
US 33 also does not touch US 1, US 301, or US 360
Mapmikey
Quote from: Takumi on May 19, 2014, 11:30:45 PM
Do US 301 and 401 meet in Fayetteville anymore?
They stopped doing so when 301 Business was decommissioned about 1975...
Mapmikey
US 6 and US 275 parallel each other for many miles in Omaha and Council Bluffs without meeting, until US 6 turns south at 204th St. and intersects US 275 somewhere in western Douglas County, although whether that's Omaha at that point is debatable.
If overpasses count, US 6 and US 34 avoid each other in Lincoln.
I may be mistaken, but in Joliet, Illinois, I believe US 30 and US 52 avoid each other.
Indianapolis: US 136 does not touch US 31, 36, 40, 52, or 421
Hammond/Gary/Lake Station: US 6 does not touch US 12 or 20
Michigan City: US 12 does not touch US 20 or 421 (US 35 never touched US 421 but it has been truncated outside the city limits, also US 12 used to touch US 421 before 421 was truncated)
Chicago: US 41 and 45 don't cross.
US 20 and 26 never touch in Idaho Falls, nor do 20/26 and 30 in Meridian
Saint Paul: 52 & 61
US 271 and US 69 in Tyler, TX
US 202 and 13 in Wilmington DE
US 221 and US 460 Lynchburg VA (but 221 does end at Bus US 460)
A couple honorable mentions for being so close:
US 301 and 13 in Delaware. US 13 gets close but doesn't enter Middletown.
US 11/15 and US 22 but 11/15 doesn't enter Harrisburg PA
1934-1965: US-66 and US-466 come within not much more than one US-91 bridge in Barstow, but never touch.
This almost happens in East Hartford, CT. US Route 6 is concurrent with I-84 there. I-84/US 6 pass over US Route 5 (Main Street). There is one lone on ramp from US 5 north to I-84/US 6 West. US Route 44 is a short distance north of this, but that and US 6 do run concurrent in two spots.
Maybe New Haven could count? I don't think US Routes 1 and 5 ever touch. They're both definitely within the New Haven city limits.
US 27 and US 41 in Miami, FL.
US 301 and US 41 in Tampa, FL.
Quote from: Zeffy on May 20, 2014, 11:54:45 AM
US 27 and US 1 in Miami, FL. US 41 also does not touch US 27 either, but does touch US 1.
US 301 and US 41 in Tampa, FL.
US 27 ends at US 1 - http://goo.gl/maps/FhZ2o
Mapmikey
Quote from: Mapmikey on May 20, 2014, 12:00:10 PM
US 27 ends at US 1 - http://goo.gl/maps/FhZ2o
Mapmikey
Oh shoot, I didn't see US 27 continue on NE 36th Street...
Quote from: Zeffy on May 20, 2014, 11:54:45 AM
US 27 and US 41 in Miami, FL.
US 301 and US 41 in Tampa, FL.
US 1 does indeed connect the two routes via US 1.
In Detroit, US-12 doesn't connect with US-10, US-16 or US-25 ... :eyebrow: never mind...
Does US 136 end in Indianapolis proper or in Speedway? (yes, completely pedantic and I don't know the exact answer)
Quote from: PurdueBill on May 20, 2014, 02:03:13 PM
Does US 136 end in Indianapolis proper or in Speedway? (yes, completely pedantic and I don't know the exact answer)
Now that they have reconfigured the 465/74/136 interchange, 136 ends right at Speedway's city limits instead of inside Speedway, but in any case, Indy's city limits continue out a couple miles west of there so 136 does go through Indy.
That's what I speculated. I know it used to technically turn left (unsigned) to meet I-74, but that isn't possible anymore. I know that Indy legally is west of Speedway too but just wondered when US 136 came up above as to what they define the end as now. It definitely did (and still does) enter/pass thru Indy without meeting 52 and friends.
US-52 comes within a mile of US-30 in Joliet, Illinois, but does not meet and does not cross. They wait until the middle of nowhere near Amboy, Illinois for that.
Due to the "unique shape" of Chesapeake, VA, US 17 does not meet US 58 within the city, though they do end up meeting in the neighboring city of Portsmouth.
Edited to add: In another of its neighbors, the city of Suffolk, VA, not only do those two routes not meet again, but US 17 meets none of US 13, US 58, and US 460.
Montgomery, AL: US 31 doesn't junction either US 231 or 331.
Gadsden, AL: US 11 doesn't junction US 411.
Allentown, PA: US 222 and US 22
Ebensburg, PA: US 422 and US 22
Chattanooga, TN: US 76 and US 74, US 27 and US 74, US 41 and US 74, US 72 and US 74.
Close: Hammonton has US 206 end at US30 with NJ54 connecting via the town of Folsom.
US 75 and US 169 in Tulsa.
Quote from: KEVIN_224 on May 20, 2014, 11:39:58 AM
This almost happens in East Hartford, CT. US Route 6 is concurrent with I-84 there. I-84/US 6 pass over US Route 5 (Main Street). There is one lone on ramp from US 5 north to I-84/US 6 West. US Route 44 is a short distance north of this, but that and US 6 do run concurrent in two spots.
Maybe New Haven could count? I don't think US Routes 1 and 5 ever touch. They're both definitely within the New Haven city limits.
Yes in New Haven. US 5 used to end at US 1, but now officially ends at I-91 Exit 4 on State St. Also, US 5 and US 20 barely meet as US 20 overpasses it in West Springfield. And US 6 overpasses US 1 as it's duplexed with I-95 for one exit in Providence. And US 30 and US 40 both end in Atlantic City blocks apart.
US 26 and US 30 do not connect in Portland OR.
Rick
Quote from: KEVIN_224 on May 20, 2014, 11:39:58 AM
Maybe New Haven could count? I don't think US Routes 1 and 5 ever touch. They're both definitely within the New Haven city limits.
They don't, the south end of US 5 is at I-91 exit 5. It
used to continue down State Street to end at US 1, but maintenance of that was turned back to the city of New Haven decades ago and so the designation was truncated.
If we interpret "city" to mean the strict boundaries of any municipality, then for Connecticut we also have:
- US 5 does not intersect US 6/44 in Hartford
- US 6 does not intersect US 44 in West Hartford
- US 6 does not intersect US 44 in Coventry
- US 6 does not intersect US 44 in Mansfield
- US 7 does not intersect US 44 in Salisbury
- US 202 does not intersect US 44 in New Hartford
Houston, US290 and US90. US59 and US90
In St. Joseph, Missouri, US 169 never intersects US 59.
Knoxville: US 129 does not meet US 25W, nor does it meet US 441. Technically, 129 and 441 do not meet 11E and 11W either. I know 441 meets 11 but I'm not positive about 129.
Bristol, Va.: US 58 does not meet US 11E or 11W. It does meet 11, however.
US 51 & 61 go through Memphis and don't touch.
Quote from: Charles2 on May 20, 2014, 04:45:16 PM
Montgomery, AL: US 31 doesn't junction either US 231 or 331.
Gadsden, AL: US 11 doesn't junction US 411.
Come to think about it, US 231 and 331 don't junction in Montgomery, either.
And...if one considers all of Jefferson County, Alabama as Birmingham, US 411 doesn't junction US 11, 31 or 280.
US 45 and US 90 in Mobile, AL
US 43 and US 98 in Moblie
Quote from: golden eagle on May 21, 2014, 08:03:57 PM
US 51 & 61 go through Memphis and don't touch.
Speaking of Memphis, 72 and 78 don't either.
271 and 64 here in Fort Smith (though the DID once upon a time). It's signed at 64, but doesn't officially begin until a couple miles south
Now would 71/271 count since it's Business 71? :hmmm:
Not a big city, but Portsmouth NH, US 4 ends at US 1 Bypass, about one mile west of US 1.
Are there any that bounce of each other without crossing or running together?
Quote from: Beeper1 on May 19, 2014, 09:56:12 PM
Boston has three routes that don't touch. US-1, US-3, and US-20 never touch each other at all.
US 3 never enters Boston.
When US 104 existed and US 15 entered Rochester, they never touched in that city–and even as I write this, I'm doubting myself, since I know US 104 did pass through downtown at one point, where it may have intersected US 15 during the first year or two of both routes' existence.
Do "used-to-be"s count? In Toledo, OH, US-223 never touched US-20.
US-223 used to follow Monroe St. (now OH-51) all the way to the end downtown, then followed Summit St. (now OH-65) north at least as far as the Craig Memorial Bridge. Sometime in the 80s, the US-223 designation was cut back to the US-23/Monroe St. interchange in Sylvania.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.usends.com%2F20-29%2F223%2Fend223e.jpg&hash=2c9d533099cff75bd18989f8bd5fa13251b03238)
Yet in the late '70s, US-223 was rerouted from a point east of Blissfield, MI, to meet US-23 for a (useless?) multiplex down to the Monroe St. exit. I think this was done to keep through traffic out of downtown Sylvania.
US 202 and US 13 in Wilmington, although they and US 40 do meet in Wilmington Manor.
US 6 and US 20 never touch, but they get very close. They are both in Gary IN and possibly several other nearby towns.
US 6 and 20 touch each other in Ohio it appears and are even multiplexed together in the Cleveland area, unless you were just talking about the Indiana area, in which case never mind.
US 23 and US 41 don't intersect in Macon, GA. Nor do Alternate US 129 and US 41.
US 41 and US 129 in Warner Robins, GA. They do multiplex for a few miles in Macon, however.
US 64 and US 70/US 79 don't meet in Arlington or Lakeland, TN, although they do meet (and multiplex) further west in Memphis and Bartlett.
Quote from: Duke87 on May 21, 2014, 12:14:05 AM
Quote from: KEVIN_224 on May 20, 2014, 11:39:58 AM
Maybe New Haven could count? I don't think US Routes 1 and 5 ever touch. They're both definitely within the New Haven city limits.
They don't, the south end of US 5 is at I-91 exit 5. It used to continue down State Street to end at US 1, but maintenance of that was turned back to the city of New Haven decades ago and so the designation was truncated.
If we interpret "city" to mean the strict boundaries of any municipality, then for Connecticut we also have:
- US 5 does not intersect US 6/44 in Hartford
- US 6 does not intersect US 44 in West Hartford
- US 6 does not intersect US 44 in Coventry
- US 6 does not intersect US 44 in Mansfield
- US 7 does not intersect US 44 in Salisbury
- US 202 does not intersect US 44 in New Hartford
Couple of others in MA (other than the Boston ones)
US 5 and US 20 do not intersect in Springfield
US 6 and US 44 do not intersect in Seekonk
A few past situations in LA:
- The old US 101A briefly passed through town via the Harbor Gateway neighborhood (essentially, the strip of land along Figueroa/110), while it intersected US 66 in Santa Monica!
- After the construction of the Golden State Freeway, but pre-1964, US 99 bypassed downtown LA via I-5 and I-10, thus avoiding US 101 (which remained, then as now, along the Santa Ana Freeway). (This might have also been true in the past when 99 did not enter downtown but instead headed east from the San Fernando Valley towards Pasadena, depending on how older maps are interpreted)
- US 60 never touched US 6 in downtown LA, despite being less than a mile apart via US 101. (US 70 was signed as far west as the Four-Level...as a likely implied TO from 101 south, still more noted than 60 ever was from that spot)
Quote from: Perfxion on May 21, 2014, 06:34:45 AM
Houston, US290 and US90. US59 and US90
US 290 & US 90, yes - get close without a true intersection, but US 59 & US 90 actually intersect downtown.
Quote from: US81 on May 24, 2014, 06:58:49 AM
Quote from: Perfxion on May 21, 2014, 06:34:45 AM
Houston, US290 and US90. US59 and US90
US 290 & US 90, yes - get close without a true intersection, but US 59 & US 90 actually intersect downtown.
I assume he meant US 59 and US 290, which don't intersect.
Quote from: texaskdog on May 23, 2014, 05:23:48 PM
Are there any that bounce of each other without crossing or running together?
US 61 and 67 in Davenport is the closest I can think of. 61 comes in from the west and leaves to the north, and 67 comes in from the south and leaves in the east without touching 61.
Oh wait, did you mean like US 14 and IL 58 at the corner of Dempster and Waukegan in the northern suburbs of Chicago? (Google map (https://www.google.com/maps/@42.0416978,-87.7968623,17z)) I can't think of any of those with two US routes off the top of my head.
Quote from: 1995hooI believe US-29 and US-50 never meet in the District of Columbia. US-1 touches both of them within the District, but I believe they never touch each other.
Quote from: texaskdogAre there any that bounce of each other without crossing or running together?
Officially, US 1 and US 29 do not touch in DC, as 29 turns at 7th and Rhode Island Ave NW while US 1 turns at 6th and Rhode Island NW.
UNofficially, as traffic cannot legally turn left from eastbound Rhode Island Ave to northbound 7th St NW, northbound US 29 traffic must continue to 6th and Rhode Island NW to turn, so technically US 1 and northbound US 29 (but not southbound) do a "bump".
US 51 and 14 do not intersect in Madison, though a jump-over is possible at US 12/18. (14 and 51 intersect on the outskirts of Janesville). This is the only one I know of in WI.
Because it only passes through the very southern tip of Denver, U.S. 285 never intersects U.S. 6, 36, 40 or 287.
Quote from: hbelkins on May 22, 2014, 07:26:43 PM
Quote from: golden eagle on May 21, 2014, 08:03:57 PM
US 51 & 61 go through Memphis and don't touch.
Speaking of Memphis, 72 and 78 don't either.
78 also doesn't touch 61 and 70.
Quote from: 1995hoo on May 19, 2014, 09:01:14 PM
I believe US-29 and US-50 never meet in the District of Columbia. US-1 touches both of them within the District, but I believe they never touch each other.
U.S. 1 and U.S. 29 do not touch each other. They come within a block of a touch on Rhode Island Avenue, but they never share a multiplex.
Quote from: golden eagle on May 25, 2014, 11:50:29 AM
78 also doesn't touch 61 and 70.
Pretty sure 78 on MLK/ex-Linden ends at 70 (and 64 and 79) at the 2nd/3rd couplet downtown in Memphis. Not that it's easy to follow using signage.
78 does miss 61 though, and 72 as mentioned above. 72 also misses 61.
A few more: US 278 and US 78 never intersect in Tupelo.
US 51 (which supposedly follows I-55 here) never intersects US 80 in Jackson, and just passes over it without an interchange in Flowood. US 80 and US 49 both enter Pearl but miss intersecting by a few dozen yards these days (they do intersect in west Jackson near the mall).
Quote from: lordsutch on May 25, 2014, 06:59:27 PM
Quote from: golden eagle on May 25, 2014, 11:50:29 AM
78 also doesn't touch 61 and 70.
Pretty sure 78 on MLK/ex-Linden ends at 70 (and 64 and 79) at the 2nd/3rd couplet downtown in Memphis. Not that it's easy to follow using signage.
78 does miss 61 though, and 72 as mentioned above. 72 also misses 61.
A few more: US 278 and US 78 never intersect in Tupelo.
US 51 (which supposedly follows I-55 here) never intersects US 80 in Jackson, and just passes over it without an interchange in Flowood. US 80 and US 49 both enter Pearl but miss intersecting by a few dozen yards these days (they do intersect in west Jackson near the mall).
If memory serves correct, there is a bridge plaque on NB I-55 at Crump Blvd that says US 78.
Quote from: US71 on May 25, 2014, 09:20:20 PM
If memory serves correct, there is a bridge plaque on NB I-55 at Crump Blvd that says US 78.
That's true, but I am pretty sure it's a mistake by TDOT. US 78 isn't actually signed anywhere on that part of Crump.
Looking at http://www.tdot.state.tn.us/Maps/city/Memphis%20DT.PDF, it appears US 78 crosses US 64, 70, and 79 (and SR 1) at the intersection of MLK and Danny Thomas, and continues west to end at the 2nd/3rd couplet, which is State Secondary 14, concurrent with SSR 278. I don't see any US 78 shields on the map on Crump near I-55. (There is a short section of 78 on Crump near I-240/69 however.)
If we're lucky the signage plans for the 55/Crump/Riverside rebuild will clarify things one way or another, but TDOT's signage of state and US highways in Memphis, particularly state secondaries, has always been fairly poor.
US 1 and 441 don't meet in Ft. Lauderdale, Hollywood or Miami.
Quote from: froggie on May 24, 2014, 10:09:10 PM
UNofficially, as traffic cannot legally turn left from eastbound Rhode Island Ave to northbound 7th St NW, northbound US 29 traffic must continue to 6th and Rhode Island NW to turn, so technically US 1 and northbound US 29 (but not southbound) do a "bump".
I have seen that happen elsewhere in D.C., where a numbered U.S. highway makes a left turn, but DDOT or its predecessor agency (DCDPW) puts up a sign to deny the turn (often at the request of a member of the D.C. Council or an Advisory Neighborhood Commission (ANC)). I am going to point this error out to one of my DDOT contacts after I have had a chance to go by there and take some current photographs (GSV exactly confirms what you say above).
One similar error that immediately comes to mind is U.S. 1 southbound, which used to make a left turn from westbound Constitution Avenue, N.W. onto southbound 14th Street to head in the direction of the 14th Street Bridge. The NO LEFT TURN signs were installed, and then the mistake was pointed out to DCDPW (this happened long before DDOT was established), which had to go to a lot of trouble to provide for a (legal) left turn onto 15th Street, N.W. (National Park Service maintenance), including truck traffic. It was eventually remediated at great expense, and to this day, all U.S. 1 traffic (except taxicabs and buses) must turn at 15th Street, then make a left and then a right to reach 14th Street.
Quote from: cpzilliacus on May 26, 2014, 12:56:53 AM
Quote from: froggie on May 24, 2014, 10:09:10 PM
UNofficially, as traffic cannot legally turn left from eastbound Rhode Island Ave to northbound 7th St NW, northbound US 29 traffic must continue to 6th and Rhode Island NW to turn, so technically US 1 and northbound US 29 (but not southbound) do a "bump".
I have seen that happen elsewhere in D.C., where a numbered U.S. highway makes a left turn, but DDOT or its predecessor agency (DCDPW) puts up a sign to deny the turn (often at the request of a member of the D.C. Council or an Advisory Neighborhood Commission (ANC)). I am going to point this error out to one of my DDOT contacts after I have had a chance to go by there and take some current photographs (GSV exactly confirms what you say above).
One similar error that immediately comes to mind is U.S. 1 southbound, which used to make a left turn from westbound Constitution Avenue, N.W. onto southbound 14th Street to head in the direction of the 14th Street Bridge. The NO LEFT TURN signs were installed, and then the mistake was pointed out to DCDPW (this happened long before DDOT was established), which had to go to a lot of trouble to provide for a (legal) left turn onto 15th Street, N.W. (National Park Service maintenance), including truck traffic. It was eventually remediated at great expense, and to this day, all U.S. 1 traffic (except taxicabs and buses) must turn at 15th Street, then make a left and then a right to reach 14th Street.
DC has the most convoluted routings for their US highways. And poor signage.
How about routing US 50 from the TR Bridge to Indepedence to Maine to I-395 north and then continuing on New York Avenue?
How about routing US 1 from the 14th St Bridge along I-395 north to New York Ave (to M) to N Captiol to Rhode Island?
US 29 is harder. K Street is terrible. In Arlington, US 29 becomes the routing for I-66 traffic for those who cannot use I-66 (Non-HOV, trucks etc.). So have US 29 join I-66 at Rosslyn and then continue along US 50's routing and then following US 1's routing to North Capitol to New Hampshire to Columbia Pike.
My point is that following the US routings would get you stuck in the heart of Downtown DC. It should be a through routing.
QuoteMy point is that following the US routings would get you stuck in the heart of Downtown DC. It should be a through routing.
With the exception of multijurisdictional-295, NOBODY who's sane takes a through routing through DC, regardless of which streets a given route follows.
Could DC clarify/simplify the routings of 1/29/50 through the city? Sure. Should it be a priority? No.
Quote from: froggie on May 27, 2014, 10:13:15 AM
QuoteMy point is that following the US routings would get you stuck in the heart of Downtown DC. It should be a through routing.
With the exception of multijurisdictional-295, NOBODY who's sane takes a through routing through DC, regardless of which streets a given route follows.
Could DC clarify/simplify the routings of 1/29/50 through the city? Sure. Should it be a priority? No.
Ordinarily yes. But now, we also have the I-695 connection that may make for some more useful routings during certain times of the day. Especially, if you're starting or ending at an inner suburb.
I-695 is a great connector from Virginia (via I-395 or I-66->Independence->Maine->I-395) to 295 towards Baltimore or Annapolis.
The Beltway isn't always better. The American Legion Bridge going northbound in the afternoon is probably worse than the Virginia-DC bridges. The Eastern Beltway is terrible when there is a football game at FedEx Field.
QuoteThe Eastern Beltway is terrible when there is a football game at FedEx Field.
Which, barring playoffs, only happens 8 times a year.
Quote from: mrsman on June 01, 2014, 08:08:51 PM
.... The Eastern Beltway is terrible when there is a football game at FedEx Field.
In some ways it's worse when there's a non-Redskins event, whether college football, soccer, or a concert, doesn't really matter what. There are always enough people unfamiliar with the venue and the routes to and from it that it messes things up big-time. I remember a few years ago when Paul McCartney took the stage some two hours late simply because so many people were still stuck in traffic on the Beltway.
BTW, froggie says eight times, but the Redskins play at home at least 10 times a year if you count preseason. While those games draw smaller crowds, they have a potential for bigger traffic issues because they're usually on Thursday or Friday nights instead of Sunday afternoons.
Quote from: froggie on June 01, 2014, 09:07:23 PM
QuoteThe Eastern Beltway is terrible when there is a football game at FedEx Field.
Which, barring playoffs, only happens 8 times a year.
Fortunately, the Redskins have reached a compromise with the community, in which they no longer reach the playoffs.
In Baltimore, US 1 and US 40 (as routed) do not touch. US 1 crosses over US 40 in the Franklin-Mulberry Corridor when it is routed onto the former I-170.
However, since the eastbound I-170 portion is closed, all US 40 traffic is detoured onto W Mulberry Street, which does intersect with US 1.
Quote from: jp the roadgeek on May 20, 2014, 11:32:20 PMAnd US 30 and US 40 both end in Atlantic City blocks apart.
Not to mention 322, which enters overlapped with (and ends with) 40.