User:Bunza

en-au This user is a native speaker of Australian English.

LE-1 This user's been known to screw up the occasional sentence and make the occasional typo, but is otherwise pretty accurate with regards to English.

ubx-1 This user is a userbox novice.

?met? This user prefers metric units and cannot figure out why Americans and Brits have such a hard time with them.

Sigma notation makes this user's head explode.

This user is a proud contributor to Uncyclopedia.

These templates act as a database to store route information:

• Template:TL Route Origin - stores one terminus
• Template:TL Route Destination - stores the other
• Template:TL Route Via - stores pathfinding info
• Template:TL Route Type - stores type of route (Local/BUZ/CityXpress etc.)
• Template:TL Route Op Hours - stores hours of operation

These auxilliary templates:

• Template:TL Route Operator - assigns operators to route numbers
• Template:TL Operator Link or Template:TL Operator Link Full - uses TL Route Operator to create abbreviated and full Wiki links for the operator
• Template:TL Region Name - assigns region names to route numbers
• Template:TL Region Colour - uses TL Region Name to assign a colour

are important in that they provide additional info required to display data.

All this info is fed into Template:TL Route Display + route number as parameter to produce a list version. eg. {{TL Route Display | 700}}

A sample table comprises of the above information, but is compiled using:

• Template:TL Route Display Table Header
• Template:TL Route Display Table Section Header + header as parameter
• Template:TL Route Display Table + route number as parameter
• Template:TL Route Display Table Note + note as parameter
• Template:TL Route Display Table Footer

This format of data storage means different ways of presenting the data can be developed, when the need arises. It also makes it incredibly easy to make Wikipedia-wide changes to formatting and information as, for example, at each station page dynamic templates for the connecting routes will replace the static text currently there.

To add additional routes, an entry needs to be placed into Origin, Destination (preferably in the order on the timetable), Via (eg. suburbs serviced) and Type (Local/BUZ/Link etc). Data on route operators and regions, including exceptions to the numbering plan (eg. Surfside 567) has already been entered.

Following that, an entry to display the data needs to be placed into the list and/or table.

• as it is, there is no capacity to put routes serviced by two companies, eg. 140/150 by BT and Park Ridge. It could be done by making special versions of the operator info, but is a tad messy as it involves creating a "new" operator for each pair that jointly run a route.
• I can't seem to find a way of being able to run a For Each loop so all routes entered are displayed automatically, so each route has to have itself added to the list and table manually by adding {{TL Route Display | 700}} or {{TL Route Display Table| 700}} respectively.