Template:PHLint/doc

From Wikipedia, the free encyclopedia

This template creates an exit or intersection listing for a Manual of Style-compliant table for a Philippines road article. It is a member of {{Jctint}} suite of templates, and it is intended to be used on newer Philippine highway articles and replace existing Philippine road intersection/exit lists using nonstandard tables.

Usage[edit]

This is a basic syntax for a complete intersection/exit table. Just copy and paste this code below:

{{PHLinttop}}
{{PHLint
|province=
|pspan=
|location=
|lspan=
|type=
|km=
|road=
|notes=
}}
{{Jctbtm}}

and fill up the parameters. For more entries, use this:

{{PHLint
|province=
|pspan=
|location=
|lspan=
|type=
|km=
|road=
|notes=
}}

Roads through multiple regions[edit]

For roads on more than one region, like expressways and national roads, copy and paste this code below:

{{PHLinttop}}
{{PHLint
|region=
|rspan=
|province=
|pspan=
|location=
|lspan=
|type=
|km=
|road=
|notes=
}}
{{Jctbtm}}

For more entries, use this:

{{PHLint
|region=
|rspan=
|province=
|pspan=
|location=
|lspan=
|type=
|km=
|road=
|notes=
}}

Roads through one region[edit]

For roads within one region, copy and paste this code below:

{{PHLinttop}}
{{PHLint
|province=
|pspan=
|location=
|lspan=
|type=
|km=
|road=
|notes=
}}
{{Jctbtm}}

For more entries, use this:

{{PHLint
|province=
|pspan=
|location=
|lspan=
|type=
|km=
|road=
|notes=
}}

Roads within a province, highly urbanized city (e.g. in Metro Manila), independent component city, or both[edit]

For roads within one province, like national roads within a province, copy and paste this code below:

{{PHLinttop|noprovince=yes}}
|location=
|lspan=
|type=
|km=
|road=
|notes=
}}
{{Jctbtm}}

For more entries, use this:

{{PHLint|noprovince=yes
|location=
|lspan=
|type=
|km=
|road=
|notes=
}}


If the road passes through or lies within an independent city or highly urbanized city (including those in Metro Manila), copy and paste this code below:

{{PHLinttop}}
{{PHLint
|hucicc=
|lspan=
|type=
|km=
|road=
|notes=
}}
{{Jctbtm}}

For more entries, use this:

{{PHLint
|hucicc=
|lspan=
|type=
|km=
|road=
|notes=
}}

But, if the independent city or highly urbanized city lies within a province and the road passes through it where the independent city or highly urbanized city is located (geographically), include the province column:


{{PHLinttop}}
{{PHLint
|province=
|pspan=
|location=
|lspan=
|type=
|km=
|road=
|notes=
}}
{{Jctbtm}}

For more entries, use this:

{{PHLint
|province=
|pspan=
|location=
|lspan=
|type=
|km=
|road=
|notes=
}}

Parameters[edit]

  • region: name of the region where the junction is located. This is automatically wikilinked and does not need further markup. It supports common names and abbreviations of any region of the Philippines.
    • region_special: (replaces region) use for custom entries only. Full wiki markup is required.
  • province: name of the province where the junction is located without wiki markup — the province is automatically linked by the template.
    • pspan: number of rows the province spans — if value=1, omit this parameter
    • province_special: (replaces province) use for custom entries only. Full wiki markup is required.
  • location: name of the location where the junction is located without wiki markup — the location is automatically linked by the template.
    • lspan: number of rows the location spans. If value=1, omit this parameter. Ignored when |location=none or |location= .
    • location_special: (replaces location) use for custom entries only. Full wiki markup is required. Ignored when |location= is set.
    • provdab: (optional for use with location) used to disambiguate between municipalities, cities, barangays, etc.
  • hucicc: highly urbanized city or independent component city where the junction is located without wiki markup. Set to "yes" if the location in "location" is a highly urbanized city or independent component city. Specific cities are linked automatically by the template.
    • hucicc_special: (replaces location and hucicc) use for custom entries only. Full wiki markup is required.
  • type: use to specify a shading for that junction's row. The permitted types are:
    • closed: for highway junctions that are now closed to traffic
    • mplex or concur: for overlaps or concurrencies
    • unbuilt: for unbuilt roadway junctions/interchanges
    • incomplete: for incomplete intersections/interchanges where all movements are not supported (Northbound exit and southbound entrance, etc.). May apply to service areas for only one direction of the highway
    • etc or toll: for intersections/interchanges that involve a toll; on toll roads this could be for intersections/interchanges where only electronic toll collection is offered, or toll plazas/barriers.
    • trans: use to specify point at which a highway transitions from one designation to another. Only applicable to named roads that follow several route numbers (e.g. MacArthur Highway, which follows routes N1 and N2)
  • km: Distance in kilometers, marked by stones or signage, from Kilometer Zero in Rizal Park or Other similar points outsize Luzon, Samar, Leyte and Mindanao. If unknown, leave blank.
    • km2: Use this for the end distance of a segment of a national within a city or municipality, or the ends distance of a bridge or viaduct. Should be used with starting distance (km:) from Rizal Park, or other designated locations in other islands other than those part of N1.
    • uspan: Use this for the distance to span multiple rows. Useful for start and end distances of national roads within a city or municipality.
  • exit: exit number of the junction. If the junction is not a numbered exit, leave blank; if an exit is unnumbered, either leave blank or insert an em dash (—) as desired.
  • name: Used for exit names in expressways, or common junction names in some national roads.
  • road: road that the article route intersects at this junction. To generate the proper coding, use the {{jct}} template. May accommodate only destinations, in cases where routes or road names are not signed.
  • notes: any notes regarding that junction. This must include an explanation for any usage of the type-generated shading.
    • nspan: number of rows the notes span. If value=1, omit this parameter.

Any parameter which is empty can be omitted.