Wikipedia:WikiProject U.S. Interstate Highways

From Wikipedia, the free encyclopedia.

Jump to: navigation, search

Contents

Title

WikiProject U.S. Interstate Highways

Scope

To standardize the format of the Interstate highway articles.

Parentage

Wikipedia:WikiProject U.S. Roads

Descendant WikiProjects

No descendant WikiProjects have been defined.

Similar WikiProjects

Related WikiProjects

No related WikiProjects have been named.

Participants

Structure

All articles are to begin with a brief description of the route in general: mileage, etc.

Route description

The first state the interstate goes through

If this state is CA or WA then put the sections that that WP wants here. Otherwise describe the routing through this state.

Length

Make (or leave) a table that has the individual mileages for each state.

Cities

Make (or leave) the cities list... South to north and west to east please!

Intersections with other Interstates and other main roads

A bulleted list.

Spur routes

List any. Then put the 3di template in here.

Notes

Put all oddities, trivia, etc. here.

Sources

Put sources here

External links

Links having to do with entire interstate go here.

California (for example)

Put California related links here.

Naming articles

All articles are to be named "Interstate x". If more than one route of the same number exists (such as Interstate 405) then a disambiguation page needs to be placed at Interstate 405 and three pages need to be made called "Interstate 405 (California)", "Interstate 405 (Oregon)", and "Interstate 405 (Washington)". Exceptions to these rules will be listed below under naming exceptions.

Highways to include

Interstates 105CA, 205 CA, 305 CA, 405 CA, 505Ca, 605 CA, and 805CA are part of the California highway WP. Put the 3di tag on it but see the CA WP page for what to do with those highways. Interstates 405WA, 705 WA are part of the Washington highway WP. Interstates 205 OR/WA and 238 are part of this WP. Also Interstate 238 is a Primary interstate for purposes of this WP.

Goals

  1. See scope.

Tasks

Pending tasks for Wikipedia:WikiProject U.S. Interstate Highways:

edit - history - watch - purge
  • Fix the WP page to make it accurate.
  • Classify all articles with WP, 3di, and stub templates.
  • Work on the routebox.
  • Make sure all articles that already have routeboxes have correct ones.

General strategy and discussion forums

Templates

Routebox

{{Routeboxint}}

[[Image:{{{type2}}}{{{article_route}}}.png|100px]]
Interstate {{{article_route}}}
{{{type}}} Interstate

Length:

{{{length_mi}}} mi ({{{length_km}}} km)
Major cities/towns: {{{cities}}}
Established: {{{year_established}}}

{{Routeboxint/{{{route_type}}}dirsub|direction_a={{{direction_a}}}|direction_b={{{direction_b}}}|terminus_a={{{terminus_a}}}|terminus_b={{{terminus_b}}}}}

States traversed: {{{states}}}
{{{type3}}} JUNCTIONS
JUNCTION EXIT #

{{{junction}}}

Legend
  deleted (no longer in system)   unconstructed
  closed   crossing with no access
  begin/end concurrency, bold route is carried through
  a bold route on white background indicates termini.
BROWSE STATE HWYS
Prev Next
{{{browse}}}


Go to Template_talk:Routeboxint for a primer on how to use this routebox.

Example

Interstate 84
Primary Interstate

Length:

243 mi (391 km)
Major cities/towns: Scranton, PA

Hartford, CT

Established:
Direction: East-West
Western Terminus: Dunmore, PA at Interstate 81
Eastern Terminus: Sturbridge, MA at Interstate 90
States traversed: Pennsylvania

New York
Connecticut
Massachusetts

{{{type3}}} JUNCTIONS
JUNCTION EXIT #
I-81 PA 0
I-380 PA 4
I-86 NY 19 (4)
I-87 NY 36 (7)
I-684 NY 68 (20)
I-691 CT 41 (27)
I-91 CT 62 (51&52)
I-384 CT 66 (59)
I-291 CT 68 (61)
I-90 MA 7
Legend
  deleted (no longer in system)   unconstructed
  closed   crossing with no access
  begin/end concurrency, bold route is carried through
  a bold route on white background indicates termini.
BROWSE STATE HWYS
Prev Next


Junctions and Mile Posts Columns

To create these columns, simply add the following to the "junction" parameter:

<tr><td align=right>Junction route number and link to its article</td><td align=left>State abbreviation and milepost</td></tr>

To add more routes, simply copy and paste this code into the "junction" parameter as many times as needed. The code will in turn form two columns: The right column, titled EXIT #, which gives the status of the article route according to its legal definition; and the left column, titled JUNCTION, which gives the status of the junction route it meets. The right column lists the exit number along the article route (in the STATE it currently traverses, in miles) where it meets the junction route. Generally, if the right column is white, it means that the article route physically exists (it is constructed, traversable, state-maintained and signed) and that it meets the junction route at the given state and milepost. The left column lists the junction routes. If the left column is white, it means that the respective junction route physically meets the article route at an interchange. Also, junction routes in bold denote the start, discontinuities, and the end of the route and may include a route, a street, a city boundary, or a point of interest.

Background colors in any of the JUNCTION or Exit # columns' boxes designates a different status of the junction route or the article route, respectively. In this case, either the junction route or article route does not meet the other at the given exit number, for a variety of reasons. These background colors should be added in the "td" section of the tables (Example: <td align=left bgcolor=#d3d3d3>). The following is the key:

Web Colors Junction route... Article route at this milepost...
lightgrey #d3d3d3 ...is deleted. ...is deleted.
plum #dda0dd ...is unconstructed. ...is unconstructed.
lightyellow #ffffe0 ...is closed to traffic. ...is closed traffic.
navajowhite #ffdead ...does not have an interchange with the article route. ...does not have an interchange with junction route.
paleturquoise #afeeee ...shares alignment with the article route. If this route number is in bold letters, then the shared alignment belongs the junction route, making the article route discontinuous. If this route number is in "regular" letters, then the shared alignment belongs to the article route, making the junction route discontinuous. ...merges with the junction route and shares alignment.
...alights from the junction route and continues.

Note: Only major junctions go into the Interstate routebox... these would be other Interstates, terminii, state lines, and weird things (turnpikes, etc). For transcontinental interstates with several junctions you may need to have 2di junctions only (plus the terminii of course) and delete the 3di junctions and the state lines).

Also note: 3dis have more lenient rules because of their shorter nature. Junctions with state roads may be added, within reason. Again, the goal is to keep the length of the routebox shorter than the length of the page on a 1024 x 768 layout.

Optional Terminology for Junction Columns

Junction box colors may not always indicate with clarity the status and layout of a junction. Occasionally, and if space permits, tags will be necessary to clarify what exactly is happening at a given junction.

  • West, East, North, or South — indicates that this interchange is with a highway that, under normal circumstances, would pass through the interchange, but at this interchange only one given direction is available.
    • Example: Interstate 294 at its northern end. The first junction traveling southbound is the choice between Interstate 294 south, or Interstate 94 east (west implies a U-turn!). Therefore an acceptable junction box is:
I-94 East Mile 53.5
  • Should the above rule indicate that the highway runs concurrent with the parent, mark it with the color #afeeee and if it's not obvious as to which direction the concurrency runs, state the direction the concurrent highway travels away from the parent.
    • Example: Interstate 80/94 in Indiana is concurrent with U.S. 41, a North-South U.S. Highway, for a mile. Therefore, if a junction box were to be made for this, it would look like this, with more correct mileposts:
...some exits further west here...
U.S. 41 North Mile 3.0
U.S. 41 South Mile 4.0
...some exits further east here...
  • Example 2: Interstate 290 runs, and is marked, east/west. U.S. 20 also runs east/west, and is concurrent on I-290 between miles 12 and 13. It is also not a wrong-way multiplex. A correct junction box for this is as follows:
U.S. 20 Mile 12.0
U.S. 20 Mile 13.0
Combining the two rows is also acceptable.
  • WB Only, EB Only, etc. — In a perfect world, all interchanges would be full. Unfortunately, this is rarely the case, and so if an isolated intersection is partial, mark in which direction the exit ramps are located with these tags. Example: East-West Interstate X and North-South Interstate Y meet at a point, but only eastbound traffic can access Y. Therefore, this should be marked EB Only.
  • Onramp Only or Entrance Only — indicates that this is an interchange, but there are no exits from the parent Interstate. Should this be the case, it can be marked Onramp Only. If there's only one onramp (or roughly 1/8th of a full Interchange), it may be marked WB Onramp Only or EB Onramp Only, etc. Example: Due to space issues, an interchange at Interstate 294 and U.S. 20 contains no exits to U.S. 20, and no onramps to SB I-294. Therefore, it can be marked:
NB Onramp Only
U.S. 20
(milepost)
  • Full Northern Access Only, Full Southern Access Only, etc. — use sparingly please. A variation of WB Only, but used to indicate that the general traffic flow is towards and from a direction, to the point that the interchanges are direction-centered. Example: The great majority of interchanges on Interstate 294 "point" towards the airport, but some are full interchanges split across two major east-west roads. In either case, use these tags to mark such "half interchanges".
Full Northern Access Only
IL 19
(milepost #)
If a common inbound/outbound point can be established (a city, for example), IB On / OB Off Only terminology can be used. If that point lies on the Interstate itself, a common inbound/outbound point cannot be established, so either use Full Northern Access Only or do not tag at all.

Stub templates

{{Interstate-stub}} (Got changed from {{Interstate Highway Stub}}.)

This article relating to U.S. Interstate Highways is a stub. Please support the U.S. Interstate Highway WikiProject and help Wikipedia by expanding the stub.

{{cleanupint}} (Next step up from a stub, use what links here to see what articles are classified here)

This Interstate Highway article needs to be cleaned up to conform to both a higher standard of article quality and accepted design standards outlined in the WikiProject U.S. Interstate Highways. After the article has been cleaned up, you may remove this message. For help, see Wikipedia:How to edit a page, the Category:Wikipedia help, and the project page.

Other templates

This article is part of the U.S. Interstate Highway WikiProject, an attempt to build a comprehensive and detailed guide to interstate highways in the US. 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.


Goes on talk page of each article.

Three-digit Interstates from Interstate 5
I-105 California - Oregon
I-205 California - Oregon/Washington
I-305 California
I-405 California - Oregon - Washington
I-505 California
I-605 California
I-705 Washington
I-805 California
past/
future
I-305: Oregon - I-505: Oregon - I-605: Washington - I-905: California


Goes on each primary highway (exept 76, 84, 86, and 88) that has 3dis, and also goes on each secondary highway. (For Interstate 10 use {{3di|10}}etc.

Three-digit Interstates from Interstate 84
I-384 Connecticut
I-684 New York


Same use as Template:3di. Use this for Interstates 76, 84, 86, and 88 (east and west for all). Example: Use {{3di2|84|east}} for the I-84 in the east. If the box is empty (or incomplete or inaccurate), then create (edit) Template:3di 84 (east). The format for Template:3di xx (xxxx) is the same as the format for Template:3di xx.

Primary Interstate Highways Interstate Highway marker
4 5 8 10 12 15 16 17
19 20 22 24 25 26 27 29
30 35 37 39 40 43 44 45
49 55 57 59 64 65 66 68
69 70 71 72 73 74 75 76 (W)
76 (E) 77 78 79 80 81 82 83
84 (W) 84 (E) 85 86 (W) 86 (E) 87 88 (W) 88 (E)
89 90 91 93 94 95 96 97
99 238 H-1 H-2 H-3
Unsigned Interstate Highways
A-1 A-2 A-3 A-4 PRI-1 PRI-2 PRI-3
Lists
Two-digit Interstates - Three-digit Interstates
Gaps in Interstates - Intrastate Interstates
Interstate standards - Proposed Interstates


Goes on every article on a primary highway.

Categories

All primary interstate highways go here with a 2 digit sort code (08 for I-8, 85 for I-85, etc.)
All interstates that run through that state go here. For 2dis, use a 2 digit sort code as above. For 3dis, follow this example: 05-7 for I-705. 25-8 for I-825.
All 3dis go here with the 05-2 sort key (for example).

Lists

Naming exceptions

Alaska, Puerto Rico

All of these interstates are listed under Interstate Highways in Alaska or Interstate Highways in Puerto Rico.

2-state 3dis

All should be named "Interstate 205 (Oregon-Washington)" for example. The only 3-state 3di is I-275 in Ohio, Kentucky, and Indiana.... any suggestions for naming that one? uese all 3? Interstate 295 (Delaware-New Jersey-Pennsylvania)

Suggestion for the I-275 Cincinnati Bypass: Interstate 275 (Cincinnati Bypass)

Perhaps best to move this to the talk page. I disagree with the use of anything but state names, because then it becomes nonstandardised (perhaps a redirect is OK though) --Chris 23:57, 21 November 2005 (UTC)
Personal tools