Wikipedia:WikiProject Australian Roads/Standards/Australian road junction lists

All road junction lists should comply with the Manual of Style for Road junction lists (MOS:RJL). This project standard expands on that guideline to provide specific advice for Australian roads. In the case of a conflict, refer to the MOS:RJL guideline.

What to include
The rows included in a junction list table varies depending on the type and length of road. A 500m street can have all its junctions listed, but that is not practical for a 500km rural highway. Therefore:
 * For short streets, include every junction
 * For arterial roads, include intersections controlled by traffic lights or large roundabouts (or both)
 * For freeway-standard roads and, in urban areas, limited access highways, include all junctions
 * For rural highways, include state-controlled highways and main roads. Other major roads can be included if the list would otherwise be very short.
 * For all roads:
 * Include the start and end points
 * Include all grade separated junctions
 * Include all junctions with roads allocated a (numeric or alphanumeric) State Route, National Route, or National Highway
 * Junctions where a turn is required to stay on the road may be included, if it will not make the list too long. This should be decided on a case-by-case basis, based on consensus at individual articles.
 * Include all junctions or points where the route number changes
 * Junctions or points where the road name changes (such as a highway that takes on another name within a particular town) may be included, if it will not make the list too long. This should be decided on a case-by-case basis, based on consensus at individual articles.
 * Additionally:
 * Include bridges over significant/notable rivers or other features
 * Include tunnels
 * Include state/territory border crossings
 * Do not include crossings with other roads if there is no connection between the roads (such as a flyover bridge without any connecting ramps)
 * Do not include private driveways or roads, such as university or shopping centre access roads (these can be included in the notes column, if they occur at an intersection that otherwise meets the criteria for listing)

What goes in each column
A typical table will have the following columns: LGA (or District), Location, km, Mile, Destinations, Notes. Additional columns may be used, if needed: State (or State/Territory), Exit number, Old Exit number. If the value in a table cell applies to multiple rows, that cell should span those rows.
 * For interstate routes, the State or State/Territory column has the state or territory name, wikilinked to its article
 * For the LGA column, the local government area is wikilinked. The official name may be truncated to exclude prefixes or suffixes such as "Shire of ..." or "... Shire".
 * In the ACT, District replaces LGA
 * For roads within a single area, a sentence above table should be used instead of this column, in the form of "The entire road is in ..."
 * For the Location column, the suburb or locality or other location is wikilinked (or redlinked if the article does not yet exist)
 * For the km column, the distance to the junction is listed. This can be in the form of a single value, or a range of two values.
 * The Mile column is automatically calculated from the km column
 * An exit number column can be included, if the relevant road authority publicly numbers exits
 * An old exit number column can be included, if the exit numbers have changed
 * An interchange name column can be included, if many interchanges have an official name, or are commonly known by a name (if only a few interchanges do so, then note the name in the notes column)
 * The Destinations column lists intersecting roads, and destinations that can be reached by turning onto those roads - the sort of information that would be seen on a big green directional sign. The general pattern is "[route marker graphic] Name of Road (Route as text) – Destinations".
 * For multiple roads, this can be combined into one line as "[route marker graphics] First Road (First Route) direction / Second Road (Second Route) direction – Destinations". Remember, directions such as north are not proper nouns, and do not take capital letters (unless part of a road name).
 * Alternatively, a separate line can be used for each road, with each line following the general pattern
 * Do not use parentheses around any destinations. The meaning of parentheses may vary from country to country, so if the information indicated by them is important, include an explanation in the notes.
 * The Notes column should contain any relevant notes, such as a junction type (at-grade or grade-separated) that is an exception to the majority on the road. If a background colour is used for a row, the note should explain why the colour was used.
 * Bridges and tunnels should span both the destination and notes column. If a river is crossed, then the river can be used as the location. This cell should span multiple columns if the river is also a boundary between LGAs or states.

Other issues

 * If a junction is at the edge of multiple LGAs or locations, then all the LGAs or locations should appear in the relevant column. The boundary (or tripoint, quadripoint, or other multipoint) should be explicitly stated in the form of "LGA1–LGA2 boundary" or "location1–location2–location3 tripoint".
 * Do not split tables, unless a road/route has a spur section. A multi-column cell should note any gaps in the road/route (use jctgap). For interstate roads/routes, use a single table with a "State" or "State/Territory" column.
 * The direction of the table from top to bottom should be the same as the direction used in the article prose. If chainages or SLK (straight line kilometre) values are known, the numbers should increase from 0 upwards. Otherwise, if this information is not available, it is up to editors' discretion/consensus at individual articles – the following advice may be used in deciding direction:
 * If possible, go from smaller house/street numbers to larger ones; or
 * Follow the direction from a larger city/town/settlement to a smaller city/town/settlement; or
 * If the road may be extended from one end, start at the other end; or
 * If the road is gazetted as from " to via " or similar, this direction can also be used; or
 * Just retain the direction the first editor chooses (until a reliable source can found that either agrees or disagrees with that direction)
 * Use of background colours, as specified at MOS:RJL, is recommended. In the case of a colour conflict, where multiple colours could be used, it is up to editors' discretion/consensus at individual articles
 * If concurrencies occur various approaches may help the situation for deciding shield order:
 * List/Display the higher "rank" routes first
 * M > A > B > C
 * NH > NR > SR
 * All standard routes > All Tourist Drives
 * Non-numbered Tourist Drives > Numbered Tourist Drives
 * All standard routes + Tourist Drives > Other signage
 * As signposted on route
 * Majority route of length of road first
 * For the WP:ACCESS requirements for shielding use an ordering system from above - It is currently considered optional to also add the road number as the last number (usage should be consistent across an article though).
 * Some oddball cases may not be fully covered, or not be able to follow this standard exactly. In such cases, it is probably best to seek consensus on either the article talk page or project talk page
 * Verifiability is important! As a bare minimum, the "km" column should have a reference (if Google maps was used, the template Google maps can help). Official sources that may help with some or all of the columns are listed in the project's resources department (WP:AURD/R). There are "pre-cited" templates available for some states.