Misplaced Pages

:WikiProject U.S. Roads/Washington - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< Misplaced Pages:WikiProject U.S. Roads

This is an old revision of this page, as edited by SPUI (talk | contribs) at 06:18, 26 March 2006. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Revision as of 06:18, 26 March 2006 by SPUI (talk | contribs)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff) Shortcut
  • ]

To-do list for Misplaced Pages:WikiProject U.S. Roads/Washington: edit·history·watch·refresh· Updated 2021-10-11

  • Eliminate remaining articles below B-Class:
  • Remove references to Highways of Washington State, as it is not a reliable source.
    • There are 0 pages that have been identified as using HoWS as a source as of 17 January 2025.
    • Remember, these should be added as an external link, but not to be used as references.
  • Refresh older articles that were written before reliable access to local newspaper archives and the WSDOT Library.
  • Images:

Template:Portal US Roads Template:Project U.S. Roads

Title

WikiProject Washington State Highways

Scope

The purpose of this project is to clean up the Washington State Highway articles (Washington State Route articles) and make them conform to the same structure just like the California State Highways WikiProject.

Parentage

U.S. Roads

Similar WikiProjects

Participants

It is strongly recommended that {{Project U.S. Roads}} should go on all members' user pages.

Highways to include

To clarify what highways this WP will include: ALL Interstate, US, and state highways. However, multi-state US highways (2,12,95,97,101,195,197-technically) and multi-state Interstate hwys (5,82,90,205) get a {{routeboxint}} or a {{routeboxus}}. For these multi-state routes, under route description, make a sub-heading for WA and put the route description, state law, leg. history, etc. in there.

/Completion list

Structure

The best example of an article that follows this format is Washington State Route 525.

Articles should best start with a short description of the state highway. This description should say where the route begins and ends, as well as any discontinuities, as defined by law. Unique details about this route may be added, but use sparingly.

Route Description

A physical description of the route should be given here. Cities and communities the route traverses should be mentioned here, as well as segments of freeway.

History

The history of this route number should be discussed here.

State Law

Use the RCW for your highway. If your highway is a Spur, Alternate, or Business Route, and has no separate RCW entry use the same RCW number as the parent. If your Highway does not have an RCW entry, put "n/a" and try to figure out why it is referred to, but has to legal entry.

List of State Route RCW Entries

The description of the route as defined by state law should be quoted here. The quote must include the section of the RCW where the definition can be found. All descriptions should use the <pre><nowiki> markup.

See Washington State Route 525 for an example.

Below the code excerpt you should cite where you got the code, using the <font size=-2> markup.

External Links

This is where all external links should be placed. For those relating to the route, please include the following websites. Government or official links should go first. Road enthusiasts links should follow. Example: For Washington State Route 3, these links would be used:

]

External links to points of interests should also go here.

Sorry it's so messy, I ran out of time.

Naming of articles

All articles need to be named "Washington State Route " plus the number. "Washington State Highway " redirects need to be created as well.

General strategy and discussion forums

Templates

Infoboxes

{{Routeboxwa}}

Template:Routeboxwa

Examples

Template:Routeboxwa
Template:Routeboxwa

What these arguments do

Parameters:

  • previous_route: The route that numerically comes before the article route. (e.g. Route 81 precedes Route 82)
  • next_route: The route that numerically comes after the article route. (e.g. Route 83 follows 82)
  • previous_type: Interstate (for ALL interstates), Highway (for state highways), U.S. Highway (for US highways). This field specifies whether the previous route (for the browse box) .
  • next_type: Same as above except this field is for the next highway.
  • type: Same as above but this field is for the article route.
  • child: What is this highway a child of? (See List of Washington State Routes for help) Enter Primary for primary routes, WASR if the parent is a state route, Int if the parent is an Interstate, and US if the parent is a US Highway.
  • parent: If the route is a secondary route then enter what the parent is (like this: "101" if the parent is US-101). If you entered Primary above then you need to enter this parameter but leave the field empty; otherwise funny symbols will appear after Primary State Route.
  • article_route: The article route number.
  • section: The section of the RCW that describes the article route. (see above for details)
  • junction: The junctions and mile posts of the article route. See below for instructions on the table.
  • length_mi: The length of the route, in miles.
  • length_km: The length of the route, in kilometers.
  • cities : List of linked cities/towns that the route passes along, delimited using a HTML linebreak(>br>)
  • direction: The route's direction, either North-South or East-West.

What goes in the browse part

Example: For WA-3, US-2 is the previous route and WA-4 is the next route.

US Highways and Interstates are placed in numerical order with the state routes (including 3dis). Spurs are placed after their mainline route (for example, WA-16: previous route would be WA-15 and next route would be WA-16 Spur, and the spur's next route would be WA-17).

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 align=left>Milepost

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 MILE POST, 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 point along the article route (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 as a state highway) and that it meets the junction route at the given county 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 as defined by law and may include a route, a street, a city boundary, or a point of interest.

Background colors in any of the JUNCTION or MILE POST 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 milepost, 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. If this route number is in "regular" letters, then the shared alignment belongs to the article route. If the first entry is "bold" and the second "regular" or vise-versa the shared alignment is shared. ...merges with the junction route and shares alignment.
...alights from the junction route and continues.

How to do the county headings

For Pierce County:

{{routeboxwa/county|Pierce}}

This will produce:

Pierce County

Stub templates

{{Washington-State-Route-stub}}

Template:Washington-State-Route-stub

Other templates

{{Washington State Highway WikiProject}}

Template:Washington State Highway WikiProject

Categories

Use a sort key- for Washington State Route 3 the key would be: ] Only put state highways in here for consistency with all other states...

Same sort key

Same sort key

Includes all 3 categories above (If you put the highway article in one of the three categories above then it will automatically be classified into this category.)

Lists

Articles

Misplaced Pages articles on Washington State Highways

Resources

Categories:
Misplaced Pages:WikiProject U.S. Roads/Washington Add topic