User:Imzadi1979/Sandbox66
This style guide provides the foundation for creating, editing and maintaining road junction lists across Wikipedia articles. Most road articles should use a table to indicate junctions. There are cases, such as a major transcontinental highway with parent and section-detail articles, where only a partial junction list, in a bulleted list form, is appropriate.
Summary lists
[edit]These should be formatted as a bulleted list consisting of the names of intersecting highways and locations.
Tables
[edit]Standard columns
[edit]The following columns should appear from left to right in the following order:
- Geographic columns should be used to orient the location of a junction along the path of the roadway. These will vary based on the country that the highway is in, and may not be applicable in all countries. The left-most column should cover the most general geographic entity while the right-most column covers the most specific locations. These should be formatted so one cell expands across the rows for all junctions within a geographic entity. If the roadway only passes through one geographic location, the column(s) should be omitted and a note placed above the top of the column. The locations should be wikilinked. Examples of these column types are:
- Country: for an international highway.
- National subdivision: The top-level subdivsion of a nation, such as a state in the US or Germany or a province in Canada.
- State subdivision: The subdivision of the country, state or province within which the junction lies. Title the column with an appropriate term—region, division, county, district, prefecture, parish (as in Louisiana), borough (as in Alaska), or equivalent.
- Location: The municipality or equivalent within which the junction lies, whether it be a town, city, or village. If the location is indeterminable, or if the junction lies in unincorporated territory, this should be left blank. If the route passes through an independent city or a consolidated city-county, do not repeat the location in both columns, instead have an entry which spans both columns.
- Distance columns: The measured location of the junction should be listed in the first column with a second column giving a converted value. For lists in some geographic areas, other terminology may be used in accordance with alternate distance-measuring systems, and a converted value may not be a useful or practical option.
- Exit or Junction: This column is for use on grade-separated roadways that have numbered interchanges. The column lists the number of the exit/junction. If old and new numbers exist, these should be presented as two columns, "Old" and "New". If the exits or junctions along a grade-separated roadway are not numbered, omit the column and place a note above the table to that effect
- Interchange name: This column should follow the exit/junction column for highway systems which have named interchanges. Use only if the interchange names are in common usage in the region and are not purely ceremonial names.
- Destinations: Locations and roads as presented on guide signs for the junction. Other locations should not be listed unless that location is extremely notable and well known; an entry in the notes column such as "Serves Missouri State University" can be used. Routes not indicated on the guide signs may be included in parentheses.
- Notes: Any additional notes about the interchange or terminus, such as the design of an interchange, special circumstances such as missing ramps, concurrency termini, opening date, or additional locations that do not merit inclusion in "Destinations".
To comply with MOS:ACCESS, and promote accessibility on the part of our readers who use assistive technology like screen readers, tables or the templates used to create tables should use: !scope=col|<column name> as the code to create column headers. Footnotes that cover the data in a column can be added in the header for a column, or grouped together in the table footer as appropriate.
Colors
[edit]The use of colored backgrounds in the table is optional. If a list includes backgrounds, a key below the table must be included. Color should not be the only method to impart the information. For the benefit of colorblind readers or persons using screen readers, the Notes column must include the information. The following table lists the standardized colors with standardized meanings. Additional colors may be used to supplement the standard colors below. These colors must be compliant with this guideline and WP:COLOR, and they must be included in the key below the table.
| Color | Use | Notes |
|---|---|---|
| #d3d3d3 | Closed | Previously complete and open, but now closed (temp. or perm.) |
| #ffdead | Unopened | Junction being constructed, not yet open to traffic |
| #ffdddd | Incomplete access | Some ramps/movements missing |
| #ddffdd | Concurrency terminus | |
| UK specific colors | ||
| #0079c1 | Motorways | Uses white text in the table; used for table headers and classification transitions |
| #00703c | Primary road | Uses yellow text (color #ffd200) in the table; used for table headers and classification transitions |
| white | Secondary road | Used for table headers and classification transitions |
Table footers
[edit]A standardized color key template has been implemented with {{legendRJL}}. A second footer, without a color key, can be generated with {{jctbtm}}. Both templates close the wikitable syntax. If the table requires an additional key or grouped references in the footer, these can be implemented in the templates.
What to include
[edit]The following items should be included or excluded in tables on grade-separated highways.
- Include
- All grade-separated interchanges, without exception
- Concurrencies
- Toll barriers, major water bodies, bridges and tunnels, if possible, wikilink to the article on the bridge or tunnel concerned. These should be represented with a multi-column row. Ideally this should span the Exit/Junction, Destinations and Notes columns, allowing the distance where the featured is located to appear to the left.
- Service areas; if multiple exist, limit those displayed to those of historical or other significance or notability. These should span the Exit/Junction, Destinations and Notes columns as above.
- Exclude
- Crossings with other highways where no direct connection between the highways exists
- Proposed or future interchanges that have not reached the construction phase. Do not add future exit numbers without a reliable source such as signing plans.
Highway link appearance
[edit]When linking to highways, a commonly used abbreviation should be used for the displayed text for the link. For instance: I-59, A1 rather than Interstate 59 or A1 road (Great Britain) respectively.
Text appearance
[edit]Text in the tables must comply with other provisions of the MoS, specifically regarding boldface, italics and ALLCAPS. Directional junctions should be formatted in the following pattern: "(route marker) (link to road article) (direction)". Directions must be entirely lowercase per Wikipedia:Manual of Style#Directions and regions: "Directions such as north are not proper nouns and do not take capitals." Per MOS:CAPS, ALL CAPS should be re-rendered into another sentence case unless it is used for an acronym or abbreviation.
- Example:
M-28 east
Do not abbreviate street names like "Street" or "Drive" as "St." or "Dr." as these abbreviations may be confused for other words. ("St." is also the abbreviation for "Saint" and "Dr." is also the abbreviation for "Doctor".)
Route markers
[edit]If route marker graphics are used, generally, they should have a height of 20–25px. They should always appear at the beginning of the line, per Wikipedia:Manual of Style (icons)#Do not use icons in general article prose: "Icons should not be used in the article body...This breaks up the continuity of the text, distracting the reader." Use of marker images should be limited to the Destinations column(s) only.
Special-case scenarios
[edit]- Some exits may have the same number for different interchanges. Some exits may have different numbers for the same interchange. In each case though, the list should be broken up by exit number, not by interchange, to maintain a consistent appearance.
- Junctions with signage that lists both the road name(s) and the route number should have both included in the exit list. If multiple names are given, every name should be listed. See the example for how to format these entries.
Concurrencies
[edit]A simple note may be placed in the notes column for the interchanges where the concurrency begins and ends.
In some cases, a concurrency between two freeways can cause the exits along one freeway to "adopt" the exit numbering system of the other for the length of the concurrency, then revert back to the original numbering system after the concurrency. Notes should be used in the table to that effect, and all exit numbers for a single interchange should be given.
Interchanges with multiple exits
[edit]If there are two exits in an interchange, one for each direction of the crossing road, they should generally be combined into one row, unless this would complicate matters. If the two exits have different numbers, that should be noted in the notes column, for example "signed as exits 1A (north) and 1B (south) eastbound", in a case where only the eastbound freeway has the split.
If two interchanges with different roads have the same number with different lettered suffixes, they generally should not be combined.