Template:MIint

Template documentation[view] [edit] [history] [purge]

This is a template for generating a junction list for a route article. To see this all in action, view the M-28 or the US 127 articles

Junction list usage

This is the basic syntax you need to get a complete junction table for roads that only have at-grade intersections. Just copy and paste the code below:

{{MIinttop}}
{{MIint
|county=
|cspan=
|location=
|lspan=
|type=
|mile=
|road=
|notes=}}
|}

...and fill in the variables! For more entries, use this:

{{MIint
|location=
|lspan=
|type=
|mile=
|road=
|notes=}}

Exit list usage

This is the basic syntax you need to get a complete junction table for roads that grade-separated interchanes. Just copy and paste the code below:

{{MIinttop|exit}}
{{MIint|exit
|county=
|cspan=
|location=
|lspan=
|type=
|mile=
|exit=
|road=
|notes=}}
|}

...and fill in the variables! For more entries, use this:

{{MIint|exit
|location=
|lspan=
|type=
|mile=
|exit=
|road=
|notes=}}

Parameters

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

• county: name of the county without wiki markup—the county is automatically linked by the template
• cspan: number of rows the county spans—if value=1, omit this parameter
• county_special: (replaces county) county where the junction is located—use for custom entries only. Full wiki markup is required.
• location: name of the location without wiki markup— the location is automatically linked by the template. Use "none" if the intersection is not in any named location.
• ctdab: (optional for use with location) further disambiguation by county
• location_special: (replaces location) location where the junction is located—use for custom entries only. Full wiki markup is required.
• lspan: number of rows the location spans—if value=1, omit this parameter
• type: use to specify a shading for that junction's row. The four permitted types are:
  • closed: for highways that are now closed to traffic
  • concur: for concurrencies
  • unbuilt: for unbuilt roadways
  • incomplete: for incomplete interchanges where all movements are not supported (Northbound exit and southbound entrance, etc.)
• mile: milepost of the junction. If unknown, leave blank. These display right-aligned to align the decimal points. Note: if using multiple sources for distance data, and the precision of decimal places differs, either round all data to the lowest level of precision or use nonbreaking space characters ( ) to pad the least precise data accordingly.
• exit: exit number for the junction. If unknown, leave blank. If the junction is not grade-separated, leave blank as well. If the exit is unnumbered along a highway that otherwise has numbered exits, use an em dash (—).
• road: road that the article route intersects at this junction. To generate the proper coding, use the {{jct}} template.
• notes: any notes regarding that junction.

Any parameter which is empty can be omitted.

See also

• {{MIinttop}}, a template that generates a MOS:RJL-compliant header for the junction list
• {{jctbridge}}, a template that creates bridge crossing entries.
• {{jctco}}, a template that creates a row for a county without junctions.
• {{jctbtm}}, a template that creates the MOS:RJL-complian table footer at the bottom of the table.

The above documentation is transcluded from Template:MIint/doc. (edit | history)
Editors can experiment in this template's sandbox (create | mirror) and testcases (create) pages.
Add categories to the /doc subpage. Subpages of this template.