Talk:U.S. Route 6

From Wikipedia, the free encyclopedia

U.S. Route 6 is part of WikiProject Ohio, which collaborates on Ohio-related subjects on Wikipedia. If you would like to participate, you can edit the article attached to this page, or visit the project page, where you can join the project and/or contribute to current discussions.
Start This article has been rated as Start-class on the quality scale.
??? This article has not yet received a rating on the importance scale.

Please rate this article, and then leave comments here to explain the ratings and/or to identify the strengths and weaknesses of the article.

This article is within the scope of the U.S. Roads WikiProject, an attempt to build a comprehensive and detailed guide to roads in the United States. If you would like to participate, you can edit the article attached to this page, or visit the project page, where you can join the project and/or contribute to the discussion.
Topics U.S. Highways U.S. auto trails Nevada State Routes Utah State Highways Iowa State Highways Indiana State Roads Ohio State Highways
Start This article has been rated as Start-Class on the quality scale. (add assessment comments)
Mid This article has been rated as Mid-importance on the importance scale.
The map in this article is maintained by the Maps task force.
To-do list for U.S. Route 6:

Here are some tasks you can do:

    Contents

    [edit] Nevada milage

    I guess US-6 travels several hundred miles across Nevada, but that's not reflected in the milage box in the article. Where can we find accurage milage info to reflect that? -- Finlay McWalter | Talk 23:39, 11 October 2005 (UTC)

    [edit] Colorado is COMPLICATED!

    On and off, and on and off, and on again, U.S. Highway 6 is driving me nuts trying to write the junctions in Colorado. Interstate 70, U.S. Highway 25, Interstate 76, not to mention where in the world U.S. 6 is in Denver apart from its freeway section. Massive discontinuities are too much for my brain to process! So I did some research, and found this site for U.S. 6 within Colorado: http://www.mesalek.com/colo/us6.html. Please, HELP ME!!!! California, where I'm from, is actually much easier than this! --Geopgeop 13:15, 9 December 2005 (UTC) P.S. Sorry, the stress...

    It looks like US 6 is unsigned whenever it overlaps with an Interstate highway. I took a look at the Colorado DOT website and from what I understand, US 6 is something like this:
    • Utah state line
    • Mile 0.00-11.21: on I-70
    • Mile 11.21-26.00: Section "A" (Mack, Fruita, Grand Junction)
    • Mile 26.00-30.27: on I-70 Business
    • Mile 30.27-34.38: Section "B" (Grand Junction)
    • Mile 34.38-37.50: on I-70 Business

    th*Mile 37.50-45.82: Section "C" (Grand Junction, Palisade)

    • Mile 45.82-65.41: on I-70
    • Mile 65.41-75.42: Section "M" (Parachute) [on I-70 frontage road]
    • Mile 75.42-88.61: on I-70
    • Mile 88.61-91.00: Section "L" (Rifle)
    • Mile 91.00-92.00: On CO 13
    • Mile 92.00-110.80: Section "D" (Rifle, Silt City, Newcastle)
    • Mile 110.80-142.00: on I-70
    • Mile 142.00-174.54: Section "E" (Gypsum, Eagle, Avon)
    • Mile 174.54-208.66: on I-70
    • Mile 208.66-229.33: Section "F" (Silverthorne, Dillon)
    • Mile 229.33-257.08: on I-70
    • Mile 257.08-284.48: Section "G" (Golden, Lakewood, Denver)
    • Mile 284.48-291.08: on I-25 and I-70
    • Mile 291.08-296.00: Section "H" (Commerce, Denver)
    • Mile 296.00-343.72: on I-76
    • Mile 343.72-346.70: Section "I" (Wiggins)
    • Mile 346.70-371.69: on I-76
    • Mile 371.69-467.28: Section "J" (Hillrose, Merino, Sterling, Fleming, Haxtun, Paoli, Holyoke)
    • Nebraska state line

    Here's an junction/interchange list US and interstate highways. This excludes junctions when US 6 is multiplexed with I-70 or I-76.

    • 0.00 [I-70/US 6/US 50]
    • 11.21 I-70/US 50 (end multiplex)
    • 26.00 I-70; US 50 (begin multiplex)
    • 30.27 US 50 (end multiplex)
    • 45.82 I-70
    • 65.41 I-70?
    • 75.42 I-70?
    • 88.61 I-70
    • 110.80 I-70
    • 142.00 I-70
    • 174.54 I-70; US 24
    • 208.66 I-70
    • 229.33 I-70
    • ??? US 40 (begin multiplex)
    • 257.18 I-70; US 40 (end multiplex)
    • 275.13 US 40
    • 275.65 I-70 (partial interchange)
    • 284.48 I-25/US 87/US 85 (begin multiplex 85,87)
    • ??? US 287
    • ??? I-25/US 87 (end multiplex 87); I-70
    • 291.08 I-70
    • 292.72 I-270/US 36
    • 296.00 I-76
    • ??? US 85 (end multiplex 85)
    • 343.72 I-76
    • 346.70 I-76; US 34 (begin multiplex)
    • ??? US 34 (end multiplex)
    • 371.69 I-76 / To US 34
    • 404.64 US 138
    • 406.39 I-76
    • 454.06 US 385
    • 467.28 [US 6]

    Polaron 17:37, 9 December 2005 (UTC)

    Wow... yuck. Well I'll start by trying to consolidate these two lists and trying to make sense out of them below:

    • 0.00 Utah state line
    • Mile 0.00-11.21: on I-70
    • 11.21 I-70/US 50 (end multiplex)
    • Mile 11.21-26.00: Section "A" (Mack, Fruita, Grand Junction)
    • 26.00 I-70; US 50 (begin multiplex)
    • Mile 26.00-30.27: on I-70 Business
    • 30.27 US 50 (end multiplex)
    • Mile 30.27-34.38: Section "B" (Grand Junction)
    • Mile 34.38-37.50: on I-70 Business
    • Mile 37.50-45.82: Section "C" (Grand Junction, Palisade)
    • 45.82 I-70 (begin multiplex)
    • Mile 45.82-65.41: on I-70
    • 65.41 I-70 (end multiplex)
    • Mile 65.41-75.42: Section "M" (Parachute) [on I-70 frontage road]
    • 75.42 I-70 (begin multiplex)
    • Mile 75.42-88.61: on I-70
    • 88.61 I-70 (end multiplex)
    • Mile 88.61-91.00: Section "L" (Rifle)
    • Mile 91.00-92.00: On CO 13
    • Mile 92.00-110.80: Section "D" (Rifle, Silt City, Newcastle)
    • 110.80 I-70 (begin multiplex)
    • Mile 110.80-142.00: on I-70
    • 142.00 I-70 (end multiplex)
    • Mile 142.00-174.54: Section "E" (Gypsum, Eagle, Avon)
    • 174.54 I-70; US 24 (begin multiplex)
    • Mile 174.54-208.66: on I-70
    • 208.66 I-70 (end multiplex)
    • Mile 208.66-229.33: Section "F" (Silverthorne, Dillon)
    • 229.33 I-70 (begin multiplex)
    • Mile 229.33-257.08: on I-70
    • ??? US 40 (begin multiplex)
    • 257.18 I-70; US 40 (end multiplex)
    • Mile 257.08-284.48: Section "G" (Golden, Lakewood, Denver)
    • 275.13 US 40
    • 275.65 I-70 (partial interchange)
    • 284.48 I-25/US 87/US 85 (begin multiplex 85,87)
    • Mile 284.48-291.08: on I-25 and I-70
    • ??? US 287
    • ??? I-25/US 87 (end multiplex 87); I-70
    • 291.08 I-70
    • Mile 291.08-296.00: Section "H" (Commerce, Denver)
    • 292.72 I-270/US 36
    • 296.00 I-76 (begin multiplex)
    • Mile 296.00-343.72: on I-76
    • ??? US 85 (end multiplex 85)
    • 343.72 I-76 (end multiplex)
    • Mile 343.72-346.70: Section "I" (Wiggins)
    • 346.70 I-76; US 34 (begin multiplex)
    • Mile 346.70-371.69: on I-76
    • ??? US 34 (end multiplex)
    • 371.69 I-76 / To US 34
    • 404.64 US 138
    • 406.39 I-76
    • 454.06 US 385
    • 467.28 [US 6]
    • Mile 371.69-467.28: Section "J" (Hillrose, Merino, Sterling, Fleming, Haxtun, Paoli, Holyoke)
    • Nebraska state line

    --Rschen7754 (talk - contribs) 07:38, 10 December 2005 (UTC)


    So how would we put the junctions in the routebox? I would assume maybe giving the first and last instances of each U.S. and Interstate highway in each state? Should we even note concurrency in Colorado? I'd be happy if U.S. 6 was continuously concurrent through the state, but to be real, look at all of the breaks in between! I do want to stick with consistency here... (sigh) --Geopgeop 12:38, 23 December 2005 (UTC)

    I'm tempted to just throw out all of the U.S. Highways. The routebox will be long enough anyway. --Rschen7754 (talk - contribs) 18:48, 23 December 2005 (UTC)

    [edit] Heh, all that work done...

    After all that research on the junctions... sigh...

    Oh, yeah, next order of business for this article: consolidate the browseboxes for all the states into one, like with the Interstate highway articles. While California has the correct box, it should be in the bottom along with all the other states, like where Massachusetts should be as well. --Geopgeop 13:34, 16 March 2006 (UTC)

    [edit] Suburbs of Boston?

    I would like to know exactly which towns US-6 passes through that could be considered "suburbs" of Boston. I used to live in Cape Cod, and to most, the nearest town that could be even remotely considered a "suburb" of Boston is Plymouth (and that's stretching it), and US-6 does not pass through it. Wareham and points west are more properly considered to be either rural or suburbs of New Bedford. So why the revert of my deletion of "Boston" for the list of suburbs that US-6 goes through, because US-6 does not go through any of Boston's suburbs, or any town that could even remotely be though of by locals as such? (EmiOfBrie 16:38, 19 March 2006 (UTC))

    Plymouth county is considered part of the census definition of the Boston metropolitan area (MSA). US 6 passes through the towns of Mattapoisett, Marion, and Wareham. However, in a more logical metro area definition using town boundaries (NECTA), Mattapoisett is included in New Bedford while Marion and Wareham are included in Barnstable Town (Cape Cod). I have changed back to your version since the statement about passing through Boston outer suburbs is stretching it at best. Polaron 02:45, 20 March 2006 (UTC)

    [edit] Roosevelt Highway

    Greeley to Provincetown along US 6, maybe extended to Long Beach with US 6 --SPUI (T - C) 11:43, 27 May 2006 (UTC)

    [edit] Routes replaced

    [edit] My $.02 on the junctions list (also to make a few corrections

    First, What constitutes a major junction? From the route box it appears only interstate highways, but list any other US highways that happen to be in the vicinity. Is this correct?

    In either case, I sympathize with all who contributed on the junction box. There are so many multiplexes that trying to decide where US6 intersects US-50 (they touch 4 times, Ely, Delta, Green River, Grand Junction) or I-70 (they touch 7 times, Green River, Grand Junction, palasade, near Eisenhower Tunnel (twice), near Idaho Springs and Denver) is a mess. I would argue that the major intersection of US6 and I-70 is not Denver, but Green River. At Denver, US6 is mearly a local commuter traffic interchange. Most long distance drivers would be most concerned about the split at Green River. I changed the route box to reflect this. If I missed the point, sorry, please inform and correct. Also, shouldn't the US-95 junction at Tonopah, NV be included? I know this is not an interstate junction, but its the only junction for hundreds of miles and if you miss it, woe be unto you (and your gas tank). Davemeistermoab 02:46, 7 July 2006 (UTC)

    I brought this up on the U.S. Highway Project page and haven't got a response yet. I've been doing the junctions on the infoboxes. I'm using ArcGIS to find the junctions and then trying to label them as the nearest city. It becomes tricky as you say when a particular route intersects or multiplexes with another (or three) multiple times. My method has been to list junctions near major cities unless it's a junction with a major thoroughfare, such as an Interstate ending in a 0 or 5 (general rule) or one of the U.S. Routes ending in 0 or 1. As far as the junction with U.S. 95, the project mentions to keep the junction lists small, 10 or less, so some need to be cut out, in that case I try to adhere to the standard I mentioned. I also list junctions as you would encounter them driving west to east or south to north as that's the standard listing method of the U.S. Highways Project. Stratosphere 02:54, 7 July 2006 (UTC)
    We should probably not include junctions with "parallel" routes such as I-70, I-76, I-80, I-84, US 50, etc. For these cross-country routes, one possible option would be to do what is done for similar cross-country Interstate Highways -- use only junction with Interstate highways ending in 5 for east/west routes. Polaron | Talk 03:27, 7 July 2006 (UTC)
    Yeah, that's pretty much the method I've been following so far. Stratosphere 03:32, 7 July 2006 (UTC)

    In this case I looked at a map and chose a number of roughly evenly-spaced large cities, and added I-15 to even it out. --SPUI (T - C) 10:04, 7 July 2006 (UTC)

    [edit] Some Cleanup is in order

    IMO this article needs some help. Here are some proposals:

    • Move all of the new york section to a sub page and link (similar to the Penn. section)
    • Merge the "miscelenia" and Mass. sections. Everything in Miscelenia is mass. related anyways.
    • Delete the entire Releted Routes section. IMO this adds no value. Most of this section is listing interstates that have largely replaced US 6 but are not numerically related to US 6. In addition if this section were to list EVERY instance where US 6 is supplanded or spured from an interstate the list would be HUGE, there are 20+ such instances in Colorado alone (in the western US, this is a common practice). So IMO this section is both incomplete and not adding value
    • Similarly purge most of the content in the Oddities section or move to the states section, clean up what's left. This section contains a lot of irrelevent points (IMO). For example, hundreds of US routes lack an End marker at a terminus. Not newsworthy. Route violations abound, not newsworthy. It is mentioned that the eatern terminal of US 6 is not its most eastern point and its western terminous is not its most western point in 2 scattered bullet points. Should be combined into 1.
    • Major Intersections is redundant with the route box

    Any objections to what I propose? If nobody objects I'll start to work on it in my spare time

    Davemeistermoab 07:46, 16 December 2006 (UTC)

    Most of what you said parallels the current guidelines at WP:USH, so I have no objections. --TMF Let's Go Mets - Stats 15:29, 16 December 2006 (UTC)

    O.K. I did round 1. One thing that amazed me is how much redundant content there was. Almost like people added content not knowing it was already present in another section. I tried to combine all redundant content and place it in the "best" spot. Davemeistermoab 05:30, 20 December 2006 (UTC)

    [edit] Anybody know what this section is supposed to say...

    The following text was recently added to the California section. I'm not sure of the authors intent, nor am I even sure what this says. Anybody have any ides? Does this belong in the article? Aside from the mention of California State Route 11 this text adds nothing new from what I can tell.

    [edit] Alt US 6 Arroyo Sections

    The US 6 was mainly once used in sections of Harbor and Pasadena Freeways, including Arroyo Parkway from 1940s to 1964 then it was decommissioned to State Route 11 (to avoid conflicts with other segments) and became California State Route 110 and Interstate 110 in 1981.


    Here's my best guess at cleaning this up Davemeistermoab 04:23, 10 April 2007 (UTC)

    [edit] History notes

    Obviously the detailed history should go in the state articles. Here are some general notes. --NE2 00:49, 11 July 2007 (UTC)

    • Midland Trail, Los Angeles, CA to Ely, NV
    • Pikes Peak Ocean to Ocean Highway, Price, UT to Red Cliff, CO
    • Detroit-Lincoln-Denver Highway, Denver, CO to Joliet, IL (DLD went via the Lincoln Highway to South Bend, and then northeast to Paw Paw and east to Detroit)
    • Toledo-Chicago Pike, Ligonier, IN to Bryan, OH
    • Shore Road, Fremont, OH to Cleveland, OH
    • Yellowstone Trail, Sandusky, OH to Cleveland, OH
    • Roosevelt Highway, Erie, PA (via later US 6N) to Port Jervis, NY
    • Bridge Route, Monroe, NY? to Brewster, NY?
    State highway numbers
    • CA: no signed routes
    • NV: 3, 4, 14
    • UT: see Talk:U.S. Route 50
    • CO: 4, 78, 91, 2 (roughly, including US 38 from Greeley), 14
    • NE: 7
    • IA: 2, 7
    • IL: 7, 18 (US 32 to Chicago), no number east of Joliet
    • IN: no number west of Ligonier, 17
    • OH: 2, 34, 12, 85
    • PA: no number for new alignment, 7 (including later US 6N)
    • NY: no number west of Middletown, 17, 37; 50 (later US 6N)
    • CT: 119, 3, 130, 350, 113, 3, 109, 315, 3
    • RI: 3
    • MA: 3, 6, 28?, 3

    [edit] long distance mileage sign

    [edit] Pictures for US 6 article

    I've been thinking that this article needs some pictures for quite some time. Ironically, somebody just posted one. How many is too many? On the article for Loveland Pass, U.S. Route 50 in Utah, and Glenwood Canyon have pictures that could be used. How many is too many? I look at Interstate 70 and think that is overkill. Would adding those 2 be appropriate? Davemeistermoab 20:48, 27 October 2007 (UTC)

    I don't think the pics on I-70 are overkill, honestly. The image layout, however, was poor, as all the pics were stacked to the right. I fixed it so that the pics alternate as they go down the page. Regarding this page...I'm not sure if they should be used (since I don't see the connection between them and US 6 at first glance), but maybe I'm missing something. --TMF Let's Go Mets - Stats 01:22, 28 October 2007 (UTC)
    Glenwood Canyon and Loveland Pass Carry US 6 over and through the Rocky Mountains. US 6 is clearly visible in one of the pictures for Loveland Pass. And a significant portion of US 6 is multiplexed with US 50 in Utah. That's the connection. 17.255.242.234 03:05, 28 October 2007 (UTC)
    If you think the pictures will help the article, then by all means add them. If they're appropriate, they won't be removed in all likelihood. --TMF Let's Go Mets - Stats 03:30, 28 October 2007 (UTC)
    I'll go through my photo album first. I prefer original pictures to "me too" photos. But if I can't find anything, I'll link to those photos. On my last trip to Utah, I tried to take pictures of Soldier Summit, Utah (also along US 6) but none I thought good enough for wikipedia. Got an good one of fall colors and a train going up the Gilluly Loops (swichbacks on the tracks leading up to soldier summit) but it was from far enough away I'd have to draw arrows on the picture =-) Davemeistermoab 01:28, 30 October 2007 (UTC)

    You can always place them in commons:Category:U.S. Route 6 and add commons=category to the infobox. --NE2 21:26, 30 October 2007 (UTC)