Template:Jctbridge/doc

This is a template for generating a bridge crossing entry in a junction list or exit list.

Usage
Complete variable list: 

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

For the above parameters, here's what you should fill in:
 * state: the state the intersection is at, do not use if cspan or lspan is specified for the row (use the state's postal abbreviation)
 * sspan: set to add a column for the state/province in a multi-state/provincial junction list. This uses the state or province's abbreviation to generate the link. This parameter needs to be set to the number of rows the state/province spans—if value=1, do not omit this parameter
 * state_special: (replaces state) state/province where the junction is located - use for custom entries only. Full wiki markup is required.
 * county: name of the county without wiki markup—the county is automatically linked by the template
 * county_special: (replaces county) county (or equivalent) where the junction is located - use for custom entries only. Full wiki markup is required.
 * cspan: number of rows the county spans—if value=1, omit this parameter
 * county_note: a note that appears in small text below the county—used primarily for California.
 * 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 location; this is often the case in states outside of the northeast.
 * location_special: (replaces location) location where the junction is located—use for custom entries only. Full wiki markup is required. Use this for a river or landmark that is located in a single county
 * area: (optional for use with location) used to disambiguate between town, city, village, etc.
 * ctdab: (optional for use with location) further disambiguation by county (Brighton in New York is an example where this tag would be used)
 * lspan: number of rows the location spans—if value=1, omit this parameter
 * river: the river or other landmark the bridge crosses if it forms a county or state boundary. This parameter requires full wiki markup, and the contents will span the county and location columns.
 * river_wide: set to yes if the river needs to span the state/province, county and location columns.
 * rspan: number of rows the river 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 crossings that are now closed to traffic
 * mplex or concur: for overlap or concurrency termini located at a bridge crossing.
 * unbuilt: for unbuilt crossings
 * incomplete: for crossings where all movements are not supported (a tunnel that's used for the northbound lanes only) or where one travel direction can't access a rest area
 * mile: milepost of the junction. If unknown, leave blank.
 * km: if the table uses kilometres instead of miles.
 * mile2 or km2: the second measurement if the location is in a range of miles or kilometres instead of one stated point.
 * line if the two measurements are on opposite sides of a state, provincial or national boundary, use this parameter to insert a instead of the dash and line break between the two numbers
 * bridge: the name of the bridge crossing, with full wiki markup if needed.
 * place: (interchangeable with ) the name of special feature, like a state line crossing or the transition point between a freeway and a surface highway, with full wiki markup if needed.
 * restarea: (interchangeable with ) the name of the rest area, with full wiki markup if needed.
 * tunnel: (interchangeable with ) the name of the tunnel crossing, with full wiki markup if needed.
 * bspan: spans the bridge, place, restarea or tunnel by the number of rows entered.

Any parameter which is empty can be omitted.

For regular exit lists, use "exit" as the first parameter before any other parameters. Doing so will force the name of the crossing to span the exit, destination and notes columns. This looks like: 

For exit lists that have old exit numbers displayed, use "old" as the first parameter before any other parameters. Doing so will force the name of the crossing to span the old exit, new exit, destination and notes columns. This looks like: 

If a freeway has named interchanges, like the Pennsylvania Turnpike, add  after either   or.