Wikipedia:Manual of Style/Road junction lists

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 list form, is appropriate.

Using this style guide

As road design, jurisdiction and construction techniques vary significantly around the world, so do junctions and signing standards. While this document has been developed to provide a basis for a uniform presentation of road junction information, not all information is applicable to all roads in all regions. Thus, certain provisions of this guideline are noted as being for optional use. When creating or editing junction lists for a particular country or state, check with an appropriate road-related WikiProject for that region. The various projects may have adopted practices or preferences regarding some of the optional provisions presented below.

In some cases, there are different methods of doing the same thing. This guideline makes no preference of one system over another. Rather than needlessly editing back and forth, please follow the format of the first complete and compliant junction list on the article.

Summary lists

These should be formatted as a bulleted list consisting of the names of intersecting highways and locations.

Tables

Standard columns

Generally, 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. 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. These columns may be omitted entirely if there is not consensus on what subdivisions to use. The locations should be wikilinked. Examples of these column types are:
  • State subdivision: The subdivision of the country, state or province within which the junction lies. Title the column with an appropriate term—region, 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.
• Mile or km: The measured location of the junction. If no source is available, and the road uses a distance-based exit numbering system, then this column may be left out in favor of the exit number column. For lists in some geographic areas, other terminology may be used in accordance with alternate distance-measuring systems. The default practice is to use one column with one measurement system, but some situations may require both columns.
• 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".
• 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. This column may be split by carriageway or direction based on local signing practices.
• 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". If the Destinations column has been split into two columns by carriageway or direction, omit this column.

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.

Colors

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 or Destination column(s) 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 key

Color	Use	Notes
#d3d3d3	Closed	Previously complete and open, but now closed (temp. or perm.)
#ffdead	Unopened	Interchange 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

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 and generate a conversion key. This conversion key is required on all tables unless both miles and kilometers are listed on the table. Samples of this key are used in the examples section below.

• Example 1, no colors:

1.000 mi = 1.609 km; 1.000 km = 0.621 mi

• Example 2, colors:

1.000 mi = 1.609 km; 1.000 km = 0.621 mi

• Example 3, UK colors. Since the UK is currently using two distance columns, the conversion key is unnecessary.

1.000 mi = 1.609 km; 1.000 km = 0.621 mi

What to include

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 barrier 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 interchange 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.

If including geographical coordinates, use {{Coord}} for each set; and one instance of {{GeoGroupTemplate}} per page.

Highway link appearance

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

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."

• Example:
  M-28 east

Route markers

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

• 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.
  • Example: if the junction signage reads " Monroe Ave./Pittsford", then the exit should appear similar to " NY 31 (Monroe Avenue) – Pittsford" in the junction list.

Concurrencies

There are two methods for displaying concurrencies. A simple note may be placed in the notes column for the interchanges where the concurrency begins and ends, or a multi-column row can be used to mark the termini of the concurrency. Ideally, this multi-column row should span the Destinations and Notes columns, allowing the milepost and exit number to appear to the left.

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. See Interstate 77 in Virginia for an example in practice. To deal with this issue, any and all exit numbers for that interchange should be displayed.

Interchanges with multiple exits

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.

Examples

Below are eight examples of junction lists designed according to the above standards. Depicted are a section of the Interstate 75 summary article, a portion of Interstate 275 (Michigan), the lists for Ontario Highway 402, M5 motorway, and Oklahoma State Highway 88, and portions of A20 motorway (Netherlands) and the Tomei Expressway, respectively.

Interstate 75

• Interstate 595 in Davie, Florida
• Interstate 275 near Parrish, Florida
• Florida State Road 60 near Brandon, Florida
• Interstate 4 near Tampa, Florida
• Interstate 275 near Lutz, Florida
• Interstate 10 in Lake City, Florida

Interstate 275

Template:MIexittop Template:MIexit Template:MIexit Template:MIexit Template:MIexit |- |colspan=6 align=center|Rows omitted |- Template:MIexit Template:MIexit Template:MIexit Template:MIexit Template:MIexit Template:MIexit

1.000 mi = 1.609 km; 1.000 km = 0.621 mi

|- |}

Highway 402

Division	Location	km	Exit	Destinations	Notes
St. Clair River		0.00		I-69 west / I-94 west – Port Huron	Blue Water Bridge
Lambton	Point Edward	0.7	1	Front Street	Formerly Highway 40B
	Sarnia	1.1	2	Christina Street North	No eastbound exit
		3.0	3	County Road 29 (Indian Road)
		5.4	6	Highway 40 (Modeland Road)
		8.2	9	Airport Road
	Plympton-Wyoming	14.7	15	County Road 26 (Mandaumin Road)
		24.0	25	County Road 21 / County Road 30 (Oil Heritage Road) – Wyoming	Formerly Highway 21 south
	Warwick	33.3	34	Highway 21 north /  County Road 8 (Lambton Road) – Forest	Highway 21 was concurrent with Highway 402 west to Oil Heritage Road, prior to municipal downloading in 1997
		43.5	44	County Road 79 (Nauvoo Road) – Watford, Arkona	Formerly Highway 79
Middlesex	Adelaide-Metcalfe	54.6	56	County Road 6 (Kerwood Road) – Kerwood
		63.8	65	County Road 81 (Centre Road) – Parkhill, Strathroy	Formerly Highway 81
	Strathroy-Caradoc	68.1	69	County Road 39 (Hickory Drive) – Strathroy
		80.8	82	County Road 14 (Glendon Drive) – Mt. Brydges, Komoka
		84.3	86	County Road 2 (Longwoods Road) – Melbourne, Delaware	Formerly Highway 2
	London	96.6	98	Highway 4 – London, St. Thomas
		98.8	100	Wonderland Road	Ramps added to existing overpass, interchange opened in 1998
		102.5	103	Highway 401 east – Toronto	Eastbound exit and westbound entrance
1.000 mi = 1.609 km; 1.000 km = 0.621 mi

M5 motorway

M5 Motorway
mile	km	Northbound exits (B Carriageway)	Junction	Southbound exits (A Carriageway)
0.0	0.0	The North West, Wolverhampton, Birmingham (north & east), Walsall M6	M6, J8	Start of motorway
2.7	4.4	West Bromwich, Birmingham (north west) A41	J1	West Bromwich, Birmingham (north west) A41
5.4	8.7	Dudley, Wolverhampton, Birmingham (west) A4123	J2	Dudley, Wolverhampton, Birmingham (west) A4123
8.2	13.3	Birmingham (south west & central) A456	J3	Kidderminster A456
		Frankley Services	Services	Frankley Services
14.8	23.8	Birmingham (south) A38 Stourbridge A491	J4	Bromsgrove A38 Stourbridge A491
16.3	26.3	NEC, Birmingham Airport, Redditch M42, London (M40, M1)	J4a	Birmingham (south & east), Redditch M42, London (M40)
21.6	34.9	Droitwich Spa, Bromsgrove A38	J5	Droitwich Spa A38
		Worcester (north), Kidderminster A449	J6	Worcester (north) A449 Evesham A4538
		Worcester (south) A44	J7	Worcester (south) A44
		Strensham services	Services	Strensham services
39.8	64.2	South Wales, Ross-on-Wye M50	J8	South Wales, Ross M50
44.0	70.9	Tewkesbury A438 Evesham A46	J9	Tewkesbury A438 Evesham A46
48.0	77.4	No access	J10	Cheltenham A4019
51.2	82.6	Cheltenham, Gloucester (north), Gloucestershire Airport A40	J11	Cheltenham, Gloucester (north), Gloucestershire Airport A40
53.6	86.4	Gloucester, Cirencester (east) A417	J11a	London, Cirencester A417
		Gloucestershire Gateway Services	Services	Gloucestershire Gateway Services
60.3	97.3	Gloucester (south) (A38)	J12	Gloucester (south) (A38)
Rows omitted
157.6	254.2	Exeter A379 Sidmouth, Exmouth (A3052) A376 Exeter services	J30 Services	Exeter A379 Sidmouth, Exmouth A376 Exeter services
		Start of motorway	J31	Bodmin, Okehampton A30
		Bodmin, Okehampton A30 Non-motorway traffic		Road becomes A38 from/to Plymouth and Torquay
Data from driver location signs are used to provide distance and carriageway identifier information
1.000 mi = 1.609 km; 1.000 km = 0.621 mi

Coordinate list

SH-88

The entire route is in Rogers County.

Location	mi	km	Destinations	Notes
Inola	0.0	0.0	Commercial St.	Southern terminus
​	0.9	1.4	US 412	Partial cloverleaf interchange
Claremore	13.0	20.9	SH-66	Southern end of SH-66 concurrency
	13.1	21.1	SH-20	Southern end of SH-20 concurrency
	13.2	21.2	SH-66	Northern end of SH-66 concurrency
	14.0	22.5	SH-20	Northern end of SH-20 concurrency
Oologah	26.0	41.8	US 169	Northern terminus
1.000 mi = 1.609 km; 1.000 km = 0.621 mi

A20 motorway (Netherlands)

The entire route is in South Holland.

Municipality	km	Exit	Name	Roads	Notes
Westland	10		Naaldwijk	N223	Continues as road N213 to Westland.
	12	6	Maasdijk	N220
Maassluis	17	7	Maassluis
Vlaardingen	21	8	Vlaardingen-West
	22	9	Vlaardingen
Schiedam	23		Interchange Kethelplein	A4
	24	10	Schiedam-Noord		Noord means north
	26	11	Schiedam
Rotterdam	27	12	Spaanse Polder
	29	13	Overschie / Interch. Kleinpolderplein	A13
	31	14	Centrum		Centrum means center
	32	15	Crooswijk		Eastbound exit and westbound entrance
	35		Interchange Terbregseplein	A16
	38	16	Prins Alexander
Nieuwerkerk a/d IJssel	43	17	Nieuwerkerk aan den IJssel	N219
Moordrecht	46	18	Moordrecht
Gouda	49		Interchange Gouwe	A12
1.000 mi = 1.609 km; 1.000 km = 0.621 mi

Tomei Expressway

Prefecture	Municipality	km	Exit	Int. name	Destinations	Notes
Continues as Shuto Expressway Route 3
Tokyo	Setagaya	0.0	1	Tokyo	Kanpachi-dori (Prefectural Route 311) - Tokyo, Setagaya
Kanagawa	Kawasaki	7.6	3	Tomei Kawasaki	Kawasaki, Noborito, Tama
	Yokohama	13.3	3-1	Yokohama Aoba	National Route 246 - Yokohama Aoba, Ichigao
		19.7	4	Yokohama-Machida	National Route 16 / National Route 246 - Yokohama, Machida
	Atsugi	35.0	5	Atsugi	National Route 129 / National Route 171 - Atsugi, Hiratsuka, Odawara
	Hadano	50.1	5-1	Hadano-Nakai	Hadanoninomiya Route (Prefectural Route 71) - Hadano, Nakai
	Oi-machi	57.9	6	Oi-Matsuda	National Route 246 / National Route 255 - Oi, Matsuda, Odawara
Shizuoka	Gotemba	83.7	7	Gotemba	National Route 138, Hakone-Gotemba Route - Gotemba, Hakone, Yamanakako
1.000 mi = 1.609 km; 1.000 km = 0.621 mi