Template:Jct/doc

< Template:Jct

This is the basic syntax you need to get a junction listing for a highway article's exit list or interchange list, just place this in the appropriate place in the exit list table and fill in the variables. Note that this is a complete list of every variable that can be used with {{jct}} and that many are unnecessary in most cases. Variables that are empty can be omitted. This template currently only supports up to 4 routes per junction list.

Usage

{{jct|country=|state=|1|2|3|4|5|6|7|8
  |dir1=|dir2=|dir3=|dir4=
  |to1=|to2=|to3=|to4=
  |name1=|name2=|name3=|name4=
  |road=
  |city1=|city2=|city3=|city4=}}

For the above parameters here's what you should fill in:

  • country: the ISO 3166-1 alpha-3 code of the country that the route is in. Use this list to find the correct code for the country. These countries have had the necessary subtemplates set up; see that page for instructions on how to set up new countries. If the route is located in the United States or Canada and the route is located within one state or province the in is possible to use state without setting the country. Accepted values for state are as follows:
  • state: or province: two-letter abbreviation, state/province (USA & CAN only) that the article route is located in
  • 1, 3, 5, 7: the type of route, this parameter replaces the number, i.e. it should not be 1=I, just simply I
For American routes, see this page.
For Canadian routes, the following designations are supported:
  • AB (Alberta) - Hwy (primary and secondary provincial highways)
  • ON (Ontario) - Highway (provincial highway, all types), RR (Regional Road, must supply a county argument for region)
  • QC (Quebec) - Route (standard route), A (Autoroute)
  • MB (Manitoba) - Hwy (primary provincial highway, secondary not supported)
  • NB (New Brunswick) - Route (NOTE: Not all routes have shield graphics at present.)
  • NS (Nova Scotia) - Trunk (trunk route), Hwy (highway), Route (other route)
  • All provinces - TCH (Trans-Canada Highway)
For United Kingdom routes:
  • M = Motorway
  • A = A roads
For A roads that have a motorway segment, example: A1(M), use M as the route type and the A1 as the number
Not all A roads have an svg shield. Use a lowercase a to show a png shield.
  • 2, 4, 6, 8: the route number for the preceding route type, this parameter replaces the number, i.e. it should not be 2=10, just simply 10
  • dir1, dir2, dir3, dir4: road direction if the exit only leads to a particular direction rather than both, for example Interstate 10 east
  • to1, to2, to3, to4: inputs a To before a route
  • name1, name2, name3, name4: road name if the highway has a common name as well as a route number
  • road: adds road names, separate multiple roads by a forward slash(/).
  • city1, city2, city3, city4: the cities listed on the exit's guide signs, i.e. control cities. The template will automatically put the city in the following format: [[city1, state|city1]]. In the event a destination city is located outside of the state the route is in, or the city needs additional disambiguation by area or county, use the location parameter(s).
  • location1, location2, location3, location4: other locations listed on the exit's guide signs, i.e. control cities. These parameters are mutually exclusive with their corresponding city# parameters. In other words, do not use city1 and location1; use city1 and location2. The template will display the input at the appropriate location in the list, using whatever formatting is used in the parmeter.
  • Other parameters include county1-4, for disambiguating county routes, noshield1-4, for not showing a shield, nolink1-4, for not linking to a minor route that will never have an article, and dab1-4, for disambiguating a route (like Minnesota State Highway 62 (east) or an Interstate business route; business routes that need separate banners on top are currently supported in all U.S. states where the banners are actually used in the field.
  • There are also noshield and nolink params to hide all shields or all links.
  • extra: currently supports adding the MUTCD intermodal icon for an airport, bus terminal, car ferry, passenger rail or light rail station appear after any and all route markers but before the rest of the output using airport, bus, ferry, rail or light-rail respectively.

Examples

{{jct|state=TX|I|35|city1=Dallas|city2=San Antonio}}
Lua error in Module:Jct at line 204: attempt to concatenate local 'link' (a boolean value).

{{jct|state=FL|FL|A1A|city1=Miami|city2=Jacksonville}}
Lua error in Module:Jct at line 204: attempt to concatenate local 'link' (a boolean value).

{{jct|state=NY|NY|31|name1=Monroe Avenue|city1=Pittsford|areadab1=village}}
Lua error in Module:Jct at line 204: attempt to concatenate local 'link' (a boolean value).

{{jct|state=NY|NY|100|NY|119|name2=Tarrytown Road}}
Lua error in Module:Jct at line 204: attempt to concatenate local 'link' (a boolean value).

{{jct|state=TX|US-Bus|90|dab1=Houston|SH|80}}
Lua error in Module:Jct at line 204: attempt to concatenate local 'link' (a boolean value).

{{jct|state=MI|I|75|city1=Saginaw|location2=[[Mackinac Bridge]]}}
Lua error in Module:Jct at line 204: attempt to concatenate local 'link' (a boolean value).

{{jct|state=MI|M|37|name1=Broadmoor Avenue|city1=Grand Rapids|city2=Hastings|location3=[[Gerald R. Ford International Airport]]|extra=airport}}
Lua error in Module:Jct at line 204: attempt to concatenate local 'link' (a boolean value).

Related pages

{{roadlink}}, a similar template that produces road links without route marker images