GRFSpecs - User contributions [en-gb]

TracktypeLabels

2023-11-12T18:31:06Z

Revenge of kiothedev: Made some improvements(?)

== Labels for rail types, road types and tram type ==
All track types are identified via 4-byte labels.
The labels are unique within their type, but it is common that rail types and tram types use the same label for similar types.

Vehicles can check for their track type on a tile, but they only have access to their own type: On a level-crossing with all three tracks (rail, road, tram) trains can only check rail types, buses/trucks can only check road types, and trams can only check tram types.

=== Rail vs. tram ===
Rail and tram are very different wrt. game-play, but both are kind of rails.
To unify labels, rail and tram should use the same labels, if the tracks are similar.
* RAIL for unelectrified rail and tram.
* ELRL for electrified rail and tram.
* FNCY for fancy-powered rail and tram.

== Default labels ==

=== Rail type ===
These labels are used for the trains and tracks in the base game, as well as for train sets that are not rail-type-aware. Consequently, track NewGRFs should always override their properties, or at least make their tracks compatible to them.

{| class="wikitable"
|-
!'''Label'''
!'''Rail Type'''
|-
|RAIL
|Normal rail
|-
|ELRL
|electrified rail
|-
|MONO
|Monorail tracks
|-
|MGLV
|Maglev tracks
|}

=== Road types ===
By default there is only a single road type defined:
{| class="wikitable"
|-
!'''Label'''
!'''Road Type'''
|-
|ROAD
|Normal road
|}
However, if a NewGRF requires electrified "ELRD", an Action0 is sufficient to add this type and make it use the default road-ground and catenary sprites.

=== Tram types ===
By default there is only a single tram type defined:
{| class="wikitable"
|-
!'''Label'''
!'''Tram Type'''
|-
|ELRL
|Electrified rail
|}
However, if a NewGRF requires unelectrified "RAIL", an Action0 is sufficient to add this type and make it use the default tram-ground sprites.

Note: Please use the same label for tram types which already exist as rail types.

== Standardized Railtype Scheme ==
Several members of the TT Forums have collaborated to define a rail type label scheme that allows for compatibility between train and track sets by different authors. At the same time it allows fancy stuff like axle weight limits, speed limits, different track and electrification types, etc. See [[Standardized Railtype Scheme]].

The Standardized Railtype Scheme is not mandatory, and authors providing both trains and railtypes may have valid reasons to use labels outside the scheme. The Standardized Scheme cannot cover all possible cases, by design, as it would be too complex.

However even when using custom labels, it may be worth using Standardized Railtype labels:
* as fallbacks for trains when the custom label is not available (via NML railtypetable fallback lists)
* as alternates handled by a railtype with a custom label (via NML alternative_railtype_list or NFO prop 1D)
This will provide wider compatibility with other train and railtype grfs.

=== Non-standard railtype labels ===

The following labels were defined before the Standardized Railtype Scheme existed. Using these or not is at the discretion of individual grf authors, but generally, if an equivalent label exists in the Standardized Railtype Scheme, it's better to use that.

{| class="mw-collapsible mw-collapsed wikitable"
|-
! scope="col" | '''Label'''
! scope="col" | '''Rail Type'''
! scope="col" | '''Notes'''
|-
|_040
|speed limit 40 km/h
|Slowrails, SwedishRails
|-
|_080
|speed limit 80 km/h
|Slowrails, SwedishRails
|-
|E040
|speed limit 40 km/h, with catenary
|Slowrails, SwedishRails
|-
|E080
|speed limit 80 km/h, with catenary
|Slowrails, SwedishRails
|-
|3RDR
|Tracks with third rail
|MetroTracks, NuTracks, UK Railway Set tracks, Japanese Track Set
|-
|3RDC
|Tracks with third rail and catenary
|MetroTracks, NuTracks, UK Railway Set tracks, Japanese Track Set
|-
|RLOW
|Low speed tracks
|NuTracks, SwedishRails, Japanese Track Set
|-
|ELOW
|Low speed tracks with catenary
|NuTracks, SwedishRails, Japanese Track Set
|-
|3LOW
|Low speed tracks with 3rd rail
|NuTracks,
|-
|CLOW
|Low speed tracks, 3rd rail and catenary
|NuTracks
|-
|RMED
|Medium speed tracks
|NuTracks, SwedishRails
|-
|EMED
|Medium speed tracks with catenary
|NuTracks, SwedishRails
|-
|3MED
|Medium speed tracks with 3rd rail
|NuTracks
|-
|CMED
|Medium speed tracks, 3rd rail and catenary
|NuTracks
|-
|RHIG
|High speed tracks
|NuTracks, SwedishRails, Japanese Track Set
|-
|EHIG
|High speed tracks with catenary
|NuTracks, SwedishRails, Japanese Track Set
|-
|HSTR
|Very high speed tracks with catenary
|NuTracks, SwedishRails, Japanese Track Set
|-
|NGRL
|Narrow gauge tracks
|Narrow Gauge Track Types, Japanese Track Set
|-
|ELNG
|Narrow gauge tracks with catenary
|Narrow Gauge Track Types, Japanese Track Set
|-
|PLAN
|Planning tracks (blue dotted lines)
|NuTracks
|-
|MTRO
|Metro tracks
|NuTracks
|-
|MTRC
|Metro tracks with concrete edges
|NuTracks
|-
|MTRS
|Metro tracks with suburban buildings on top
|NuTracks
|-
|MTRU
|Metro tracks with 'downtown' buildings on top
|NuTracks
|-
|MTRT
|Metro tracks with plain landscape on top
|NuTracks
|-
|DBNN
|branch line
|DBRails
|-
|DBNE
|branch line, electrified
|DBRails
|-
|DBHN
|main line
|DBRails
|-
|DBHE
|main line, electrified
|DBRails
|-
|DBHS
|high speed line electrified (NBS)
|DBRails
|-
|TRPD
|transrapid track
|Transrapid track type
|-
|NLOW
|Low speed narrow gauge tracks
|Japanese Track Set
|-
|ENLW
|Low speed narrow gauge tracks with catenary
|Japanese Track Set
|-
|ENHI
|Modern narrow gauge tracks with catenary
|Japanese Track Set
|-
|RLA0
|Broad (1520 mm) gauge unelectrified tracks. Speed limit 60 km/h
|xUSSR train set
|-
|RLA1
|Broad (1520 mm) gauge unelectrified tracks. Speed limit 100 km/h
|xUSSR train set
|-
|RLA2
|Broad (1520 mm) gauge unelectrified tracks. Speed limit 140 km/h
|xUSSR train set
|-
|RLA3
|Broad (1520 mm) gauge unelectrified tracks. Speed limit 250 km/h
|xUSSR train set
|-
|ERd0
|Broad (1520 mm) gauge tracks with generic DC catenary 1,5kV. Speed limit 60 km/h
|xUSSR train set
|-
|ERd1
|Broad (1520 mm) gauge tracks with generic DC catenary 1,5kV. Speed limit 100 km/h
|xUSSR train set
|-
|ERd2
|Broad (1520 mm) gauge tracks with generic DC catenary 1,5kV. Speed limit 140 km/h
|xUSSR train set add-on
|-
|ERd3
|Broad (1520 mm) gauge tracks with generic DC catenary 1,5kV. Speed limit 250 km/h
|xUSSR train set add-on
|-
|ERD1
|Broad (1520 mm) gauge tracks with generic DC catenary 3kV. Speed limit 100 km/h
|xUSSR train set
|-
|ERD2
|Broad (1520 mm) gauge tracks with generic DC catenary 3kV. Speed limit 140 km/h
|xUSSR train set
|-
|ERD3
|Broad (1520 mm) gauge tracks with generic DC catenary 3kV. Speed limit 250 km/h
|xUSSR train set
|-
|ERA1
|Broad (1520 mm) gauge tracks with generic AC catenary 25kV. Speed limit 100 km/h
|xUSSR train set
|-
|ERA2
|Broad (1520 mm) gauge tracks with generic AC catenary 25kV. Speed limit 140 km/h
|xUSSR train set
|-
|ERA3
|Broad (1520 mm) gauge tracks with generic AC catenary 25kV. Speed limit 250 km/h
|xUSSR train set
|-
|ERA4
|Broad (1520 mm) gauge tracks with generic AC catenary 25kV. No speed limit
|xUSSR train set
|-
|ERa0
|Broad (1520 mm) gauge tracks with generic AC catenary 15kV. Speed limit 60 km/h
|xUSSR train set
|-
|ERa1
|Broad (1520 mm) gauge tracks with generic AC catenary 15kV. Speed limit 100 km/h
|xUSSR train set add-on
|-
|ERa2
|Broad (1520 mm) gauge tracks with generic AC catenary 15kV. Speed limit 140 km/h
|xUSSR train set add-on
|-
|ERa3
|Broad (1520 mm) gauge tracks with generic AC catenary 15kV. Speed limit 250 km/h
|xUSSR train set add-on
|-
|ERa4
|Broad (1520 mm) gauge tracks with generic AC catenary 15kV. No speed limit
|xUSSR train set add-on
|-
|ER2D
|Broad (1520 mm) gauge tracks with DC 1,5kV / 3kV catenary. Speed limit 100 km/h
|xUSSR train set
|-
|ER2S
|Broad (1520 mm) gauge tracks with AC 25kV / DC 3kV catenary. Speed limit 120 km/h
|xUSSR train set
|-
|ER2s
|Broad (1520 mm) gauge tracks with AC 25kV / DC 1,5kV catenary. Speed limit 120 km/h
|xUSSR train set add-on
|-
|ER3a
|Broad (1520 mm) gauge tracks with AC 25kV / 15kV / DC 1,5kV catenary. Speed limit 120 km/h
|xUSSR train set add-on
|-
|ER3D
|Broad (1520 mm) gauge tracks with AC 25kV / DC 3kV / 1,5kV catenary. Speed limit 120 km/h
|xUSSR train set add-on
|-
|ER4S
|Broad (1520 mm) gauge tracks with AC 25kV / 15kV / DC 3kV / 1,5kV catenary. Speed limit 120 km/h
|xUSSR train set add-on
|-
|WWAY
|Wagonway
|Early Rails set
|-
|WGWY
|Wagonway
|Recycled Tracktype Set
|-
|LTRL
|Light Rails
|Early Rails set
|-
|LIHT
|Light Rails
|Recycled Tracktype Set
|-
|TYTX
|ToyTrax
|ToyTrax
|-
|ELTX
|ElecTrax
|ToyTrax
|-
|DPRK
|North Korean Urban Ground
|Trackless Trackset
|-
|JPU1
|Japanese Urban Ground
|Trackless Trackset
|-
|ISR1
|Industrial Stations Renewal Ground
|Trackless Trackset
|-
|ISR2
|CHIPS Dirt Ground
|Trackless Trackset
|-
|ISR3
|CHIPS Asphalt Ground
|Trackless Trackset
|-
|ISR4
|CHIPS Cobblestone Ground
|Trackless Trackset
|}

== Standardized Roadtype Scheme ==
Same story as the railtype one, also covers trams. See [[Standardized Roadtype Scheme]]

=== Non-standard roadtype labels ===

The following labels were defined before the Standardized Roadtype Scheme existed, but after alternative_roadtype_list and alternative_tramtype_list existed (meaning compatibility options allowed for quicker proliferation. Using these or not is at the discretion of individual grf authors, but generally, if an equivalent label exists in the Standardized Roadtype Scheme, it's better to use that. Ditto for tramtypes, but note that a label can be used twice, once for a roadtype and once for a tramtype.

==== Non-standard roadtypes ====
{| class="mw-collapsible mw-collapsed wikitable"
|-
! scope="col" | '''Label'''
! scope="col" | '''Road Type'''
! scope="col" | '''Notes'''
|-
|_TRD
|Town Roads
|Ufiby's U&ReRMM (1st version only)
|}

==== Non-standard tramtypes ====
{| class="mw-collapsible mw-collapsed wikitable"
|-
! scope="col" | '''Label'''
! scope="col" | '''Road Type'''
! scope="col" | '''Notes'''
|-
|N/A
|N/A
|Please fill this list with entries!
|}

TracktypeLabels

2023-11-12T17:44:39Z

Revenge of kiothedev: /* Non-standard railtype labels */

== Labels for rail types, road types and tram type ==
All track types are identified via 4-byte labels.
The labels are unique within their type, but it is common that rail types and tram types use the same label for similar types.

Vehicles can check for their track type on a tile, but they only have access to their own type: On a level-crossing with all three tracks (rail, road, tram) trains can only check rail types, buses/trucks can only check road types, and trams can only check tram types.

=== Rail vs. tram ===
Rail and tram are very different wrt. game-play, but both are kind of rails.
To unify labels, rail and tram should use the same labels, if the tracks are similar.
* RAIL for unelectrified rail and tram.
* ELRL for electrified rail and tram.
* FNCY for fancy-powered rail and tram.

== Default labels ==

=== Rail type ===
These labels are used for the trains and tracks in the base game, as well as for train sets that are not rail-type-aware. Consequently, track NewGRFs should always override their properties, or at least make their tracks compatible to them.

{| class="wikitable"
|-
!'''Label'''
!'''Rail Type'''
|-
|RAIL
|Normal rail
|-
|ELRL
|electrified rail
|-
|MONO
|Monorail tracks
|-
|MGLV
|Maglev tracks
|}

=== Road types ===
By default there is only a single road type defined:
{| class="wikitable"
|-
!'''Label'''
!'''Road Type'''
|-
|ROAD
|Normal road
|}
However, if a NewGRF requires electrified "ELRD", an Action0 is sufficient to add this type and make it use the default road-ground and catenary sprites.

=== Tram types ===
By default there is only a single tram type defined:
{| class="wikitable"
|-
!'''Label'''
!'''Tram Type'''
|-
|ELRL
|Electrified rail
|}
However, if a NewGRF requires unelectrified "RAIL", an Action0 is sufficient to add this type and make it use the default tram-ground sprites.

Note: Please use the same label for tram types which already exist as rail types.

== Standardized Railtype Scheme ==
Several members of the TT Forums have collaborated to define a rail type label scheme that allows for compatibility between train and track sets by different authors. At the same time it allows fancy stuff like axle weight limits, speed limits, different track and electrification types, etc. See [[Standardized Railtype Scheme]].

The Standardized Railtype Scheme is not mandatory, and authors providing both trains and railtypes may have valid reasons to use labels outside the scheme. The Standardized Scheme cannot cover all possible cases, by design, as it would be too complex.

However even when using custom labels, it may be worth using Standardized Railtype labels:
* as fallbacks for trains when the custom label is not available (via NML railtypetable fallback lists)
* as alternates handled by a railtype with a custom label (via NML alternative_railtype_list or NFO prop 1D)
This will provide wider compatibility with other train and railtype grfs.

== Standardized Roadtype Scheme ==
Same story as the railtype one, also covers trams. See [[Standardized Roadtype Scheme]]

== Non-standard railtype labels ==

The following labels were defined before the Standardized Railtype Scheme existed. Using these or not is at the discretion of individual grf authors, but generally, if an equivalent label exists in the Standardized Railtype Scheme, it's better to use that.

{| class="wikitable"
|-
!'''Label'''
!'''Rail Type'''
!'''Notes'''
|-
|_040
|speed limit 40 km/h
|Slowrails, SwedishRails
|-
|_080
|speed limit 80 km/h
|Slowrails, SwedishRails
|-
|E040
|speed limit 40 km/h, with catenary
|Slowrails, SwedishRails
|-
|E080
|speed limit 80 km/h, with catenary
|Slowrails, SwedishRails
|-
|3RDR
|Tracks with third rail
|MetroTracks, NuTracks, UK Railway Set tracks, Japanese Track Set
|-
|3RDC
|Tracks with third rail and catenary
|MetroTracks, NuTracks, UK Railway Set tracks, Japanese Track Set
|-
|RLOW
|Low speed tracks
|NuTracks, SwedishRails, Japanese Track Set
|-
|ELOW
|Low speed tracks with catenary
|NuTracks, SwedishRails, Japanese Track Set
|-
|3LOW
|Low speed tracks with 3rd rail
|NuTracks,
|-
|CLOW
|Low speed tracks, 3rd rail and catenary
|NuTracks
|-
|RMED
|Medium speed tracks
|NuTracks, SwedishRails
|-
|EMED
|Medium speed tracks with catenary
|NuTracks, SwedishRails
|-
|3MED
|Medium speed tracks with 3rd rail
|NuTracks
|-
|CMED
|Medium speed tracks, 3rd rail and catenary
|NuTracks
|-
|RHIG
|High speed tracks
|NuTracks, SwedishRails, Japanese Track Set
|-
|EHIG
|High speed tracks with catenary
|NuTracks, SwedishRails, Japanese Track Set
|-
|HSTR
|Very high speed tracks with catenary
|NuTracks, SwedishRails, Japanese Track Set
|-
|NGRL
|Narrow gauge tracks
|Narrow Gauge Track Types, Japanese Track Set
|-
|ELNG
|Narrow gauge tracks with catenary
|Narrow Gauge Track Types, Japanese Track Set
|-
|PLAN
|Planning tracks (blue dotted lines)
|NuTracks
|-
|MTRO
|Metro tracks
|NuTracks
|-
|MTRC
|Metro tracks with concrete edges
|NuTracks
|-
|MTRS
|Metro tracks with suburban buildings on top
|NuTracks
|-
|MTRU
|Metro tracks with 'downtown' buildings on top
|NuTracks
|-
|MTRT
|Metro tracks with plain landscape on top
|NuTracks
|-
|DBNN
|branch line
|DBRails
|-
|DBNE
|branch line, electrified
|DBRails
|-
|DBHN
|main line
|DBRails
|-
|DBHE
|main line, electrified
|DBRails
|-
|DBHS
|high speed line electrified (NBS)
|DBRails
|-
|TRPD
|transrapid track
|Transrapid track type
|-
|NLOW
|Low speed narrow gauge tracks
|Japanese Track Set
|-
|ENLW
|Low speed narrow gauge tracks with catenary
|Japanese Track Set
|-
|ENHI
|Modern narrow gauge tracks with catenary
|Japanese Track Set
|-
|RLA0
|Broad (1520 mm) gauge unelectrified tracks. Speed limit 60 km/h
|xUSSR train set
|-
|RLA1
|Broad (1520 mm) gauge unelectrified tracks. Speed limit 100 km/h
|xUSSR train set
|-
|RLA2
|Broad (1520 mm) gauge unelectrified tracks. Speed limit 140 km/h
|xUSSR train set
|-
|RLA3
|Broad (1520 mm) gauge unelectrified tracks. Speed limit 250 km/h
|xUSSR train set
|-
|ERd0
|Broad (1520 mm) gauge tracks with generic DC catenary 1,5kV. Speed limit 60 km/h
|xUSSR train set
|-
|ERd1
|Broad (1520 mm) gauge tracks with generic DC catenary 1,5kV. Speed limit 100 km/h
|xUSSR train set
|-
|ERd2
|Broad (1520 mm) gauge tracks with generic DC catenary 1,5kV. Speed limit 140 km/h
|xUSSR train set add-on
|-
|ERd3
|Broad (1520 mm) gauge tracks with generic DC catenary 1,5kV. Speed limit 250 km/h
|xUSSR train set add-on
|-
|ERD1
|Broad (1520 mm) gauge tracks with generic DC catenary 3kV. Speed limit 100 km/h
|xUSSR train set
|-
|ERD2
|Broad (1520 mm) gauge tracks with generic DC catenary 3kV. Speed limit 140 km/h
|xUSSR train set
|-
|ERD3
|Broad (1520 mm) gauge tracks with generic DC catenary 3kV. Speed limit 250 km/h
|xUSSR train set
|-
|ERA1
|Broad (1520 mm) gauge tracks with generic AC catenary 25kV. Speed limit 100 km/h
|xUSSR train set
|-
|ERA2
|Broad (1520 mm) gauge tracks with generic AC catenary 25kV. Speed limit 140 km/h
|xUSSR train set
|-
|ERA3
|Broad (1520 mm) gauge tracks with generic AC catenary 25kV. Speed limit 250 km/h
|xUSSR train set
|-
|ERA4
|Broad (1520 mm) gauge tracks with generic AC catenary 25kV. No speed limit
|xUSSR train set
|-
|ERa0
|Broad (1520 mm) gauge tracks with generic AC catenary 15kV. Speed limit 60 km/h
|xUSSR train set
|-
|ERa1
|Broad (1520 mm) gauge tracks with generic AC catenary 15kV. Speed limit 100 km/h
|xUSSR train set add-on
|-
|ERa2
|Broad (1520 mm) gauge tracks with generic AC catenary 15kV. Speed limit 140 km/h
|xUSSR train set add-on
|-
|ERa3
|Broad (1520 mm) gauge tracks with generic AC catenary 15kV. Speed limit 250 km/h
|xUSSR train set add-on
|-
|ERa4
|Broad (1520 mm) gauge tracks with generic AC catenary 15kV. No speed limit
|xUSSR train set add-on
|-
|ER2D
|Broad (1520 mm) gauge tracks with DC 1,5kV / 3kV catenary. Speed limit 100 km/h
|xUSSR train set
|-
|ER2S
|Broad (1520 mm) gauge tracks with AC 25kV / DC 3kV catenary. Speed limit 120 km/h
|xUSSR train set
|-
|ER2s
|Broad (1520 mm) gauge tracks with AC 25kV / DC 1,5kV catenary. Speed limit 120 km/h
|xUSSR train set add-on
|-
|ER3a
|Broad (1520 mm) gauge tracks with AC 25kV / 15kV / DC 1,5kV catenary. Speed limit 120 km/h
|xUSSR train set add-on
|-
|ER3D
|Broad (1520 mm) gauge tracks with AC 25kV / DC 3kV / 1,5kV catenary. Speed limit 120 km/h
|xUSSR train set add-on
|-
|ER4S
|Broad (1520 mm) gauge tracks with AC 25kV / 15kV / DC 3kV / 1,5kV catenary. Speed limit 120 km/h
|xUSSR train set add-on
|-
|WWAY
|Wagonway
|Early Rails set
|-
|WGWY
|Wagonway
|Recycled Tracktype Set
|-
|LTRL
|Light Rails
|Early Rails set
|-
|LIHT
|Light Rails
|Recycled Tracktype Set
|-
|TYTX
|ToyTrax
|ToyTrax
|-
|ELTX
|ElecTrax
|ToyTrax
|-
|DPRK
|North Korean Urban Ground
|Trackless Trackset
|-
|JPU1
|Japanese Urban Ground
|Trackless Trackset
|-
|ISR1
|Industrial Stations Renewal Ground
|Trackless Trackset
|-
|ISR2
|CHIPS Dirt Ground
|Trackless Trackset
|-
|ISR3
|CHIPS Asphalt Ground
|Trackless Trackset
|-
|ISR4
|CHIPS Cobblestone Ground
|Trackless Trackset
|}

Standardized Railtype Scheme

2023-11-12T17:09:24Z

Revenge of kiothedev: /* Possible additions */

This railtype label scheme aims to bring order to the uncontrolled growth of railtype labels. It groups the rail types into what matters from a technical perspective. The scheme provides a standardized way of defining railtype labels, based on track gauge and type, speed class, allowable axle weight and electrification type.

It is the explicit intent of this scheme to decouple track sets from vehicle sets to facilitate easy mixing. This way the player can select a track set of choice to go with a train set of choice. It allows the player to play with or without axle load classes, or with or without speed limit classes, simply by loading a track set that does or does not provide these features. In some cases it will also be possible to combine niche track sets, for instance a standard gauge track set with a narrow gauge and a metro track set.

== The Label Scheme ==
A railtype label consists of four characters. In this scheme, each position has a different purpose:
# Track gauge and type class (e.g. standard gauge rail, narrow gauge rail, monorail)
# Speed limit class
# Axle load class (maximum allowed axle weight for this track)
# Energy source type class

In the next sections, each of the four positions will be explained.

=== Track gauge and type class [X***] ===
The first position in the railtype label defines track gauge and/or track type class. The following classes are currently defined:

{|
! !!Track type/gauge
|-
|S ||Standard gauge rail
|-
|B ||Broad gauge rail
|-
|N ||Narrow gauge rail
|-
|n ||Secondary narrow gauge rail (e.g. when providing both metre and cape gauge, always use N in case of just one type of narrow gauge)
|-
|D ||Dual gauge rail, standard/broad gauge
|-
|d ||Dual gauge rail, standard/narrow gauge
|-
|M ||Monorail
|-
|L ||Magnetic Levitation
|}

=== Speed limit class [*X**] ===
The second position in the railtype label defines the speed limit class. These classes do not map to a fixed numeric value, but are used to define an internal speed limit order for the track set. This means that if your track set has two different speed limits for track types that are otherwise identical, you'll use letters A and B here. In case of three different speed limits, use A, B and C. In case your track set does not employ speed limits, always use A. Train sets do not care about the speed limit, and will always set the lowest speed class, i.e. A.

This gives for instance the following options:

<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||no speed limits
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||high speed
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||medium speed
|-
|C ||high speed
|}
</div>
<div style="float:left;">
 etc. 
</div>
</div>
<div style="clear:left;"></div>

The speed limit class may also be used for some advanced features of the label scheme, like specialized track types and eyecandy purposes. Be careful not to break the compatibility with other sets when using the speed limit class for these purposes.

An example of a special use is rack rail. In the French set it is used to give rack rail engines a higher speed and TE than normal rail engines when used on rack rail. When defining trains with a special speed limit class, always allow a fallback to speed limit class A via the railtype table.

An example of eyecandy use are urban tracks. These are a variation of regular tracks, but with concrete ground tiles to better match the urban environment. Train sets must not define vehicles for eyecandy classes. If you think you have special vehicles that should only run on the eyecandy class, it is ''not'' eyecandy but a separate track gauge/type.

The following special and eyecandy classes have been defined so far:

{|
! !!Description !!Type !!Used by
|-
|A-H ||speed limits ||colspan="2"|reserved
|-
|R ||rack rail ||special ||French Set Rails
|-
|S ||subterranean ||eyecandy ||Metro Track Set
|-
|U ||urban ||eyecandy ||Metro Track Set
|-
|g ||ground tile for 45° angles ||eyecandy ||(none yet)
|}

=== Axle load class [**X*] ===
The third position defines the axle weight limit. Heavy trains cannot run on tracks with a low axle weight limit; these trains need more expensive tracks with a heigher weight limit. There are five axle load classes '''A''' through '''E'''. '''A''' is for the lowest axle load limit, '''E''' for the highest. The exact axle load attached to each class is relative to the track gauge/type and trains in the set.

A train set should set the appropriate axle weight for each train via the railtype label, as to make the set work with track sets that do provide tracks with different weight limits, even if you don't care about it for your trainset. Split all vehicles of a certain track gauge/type into five groups of similar axle weight. The group with the lowest axle weights will get class '''A''', the second lowest class '''B''', etc. up to the group with the highest axle weights which will get class '''E'''. Do the same for the other track gauge/types if your train set has those.

A track set does not have to provide a dedicated track type for each axle weight limit. A track set that does not provide a dedicated track for each axle load class, must make sure to map all undefined axle load classes to a real railtype using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]]. This way a train set can rely on all labels for all axle load classes being available. Example: if you only want to provide 2 axle load classes for standard gauge unelectrified with no speed limits, you can map SA'''A'''N + SA'''B'''N to SA'''C'''N and SA'''D'''N to SA'''E'''N if the cost difference between the two railtypes is high, or SA'''A'''N to SA'''B'''N and SA'''C'''N + SA'''D'''N to SA'''E'''N if the cost difference is low.

If you don't want to provide any axle load classes in your track set, it doesn't really matter what axle load class you choose for the track, as you'll be mapping all other classes to this track anyways. But the lowest or highest class are the obvious choice. Example: if your track set only provides narrow gauge unelectrified track with no speed limits and no axle load limits, you may use NA'''A'''N for the track label, and provide NA'''B'''N, NA'''C'''N, NA'''D'''N, NA'''E'''N in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

If you need more than five axle load class, you may use lowercase letters for very low axle loads and continue the uppercase letters for very high axle loads. Be advised that your train set may not assume the existance of any other class than '''A''' through '''E''', so when the range make sure to program your railtype table such that trains with such a class will fall back to class '''A''' or '''E'''. If you make a track set with an extended range, be aware that not all train sets will define trains for these tracks. In general: only do this in case of a train set with a matching track set.

For the lowercase letters, '''b''' is lower than '''a''', so for increasing axle load limits: b < a < A < B < C etc.

Note that the axle load classes never map to a specific weight in tonnes. For that reason it does not make sense to add a numeric value for the axle load to the name of a track type or in the extended purchase info of a train. Instead use the relative expressions 'very low', 'low', 'medium', 'high' and 'very high' or use the class letters directly.

=== Energy source type class [***X] ===
The last position defines the energy source type class. This is split in generic energy source types like overhead wires and third rail and specialized types like alternating and direct current.

A track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

A vehicle set that uses specialized types should define a generic type as fallback, via the railtype table. If such a fallback is omitted, please note that certain vehicles may be unavailable depending on track set loaded.

{|
! !!Generic energy type classes
|-
|N ||no electrification
|-
|E ||overhead wires/catenary electrification
|-
|3 ||3rd rail electrification
|}

{|
! !!Specialized energy type classes !!Vehicle set fallback
|-
|Z ||3rd rail and catenary electrification || 3 or E
|-
|4 ||4th rail electrification || 3
|-
|Y ||4th rail and catenary electrification || 4 or E
|-
|T ||[http://en.wikipedia.org/wiki/Three-phase_AC_railway_electrification three phase AC electrification] || E
|-
| colspan="3" |  
|-
|D ||DC catenary electrification || E
|-
|d ||low voltage DC catenary electrification (only when D also used in set) || First A then E
|-
|A ||AC catenary electrification || E
|-
|a ||low voltage AC catenary electrification (only when A also used in set) || First A then E
|}

If you want multi-voltage/current vehicles in your set (i.e. a train that can run on both AC and DC current), you have to define a dedicated railtype for those vehicles. Without the railtype, it's not possible to define vehicles with this property. If you only have vehicles that can run on either one type of voltage/current or on all types of voltage/current (e.g. a 2-system if you only have '''A''' and '''D''' tracks, or a 4-system in case of all '''A''', '''a''', '''D''' and '''d'''), then use the generic class '''E''' for vehicles that should be able to run on all different voltage/currents. Also the track set needs to have one at least one railtype with class '''E''' defined.

Note that if you want more than one type of multi-voltage/current, you'll quickly get a combinatory explosion of railtype labels, so plan carefully or do not attempt it. For every different multi-voltage/current vehicle type a dedicated railtype is needed. If you want all possible combinations, then you need to define an additional 8 classes. It is not recommended to make your train/track set this complicated.

Example approach for a 4-system set, with trains that can run on either one or all systems:
* '''E''': generic catenary-powered electric engines. "universal" [4-system] if any of '''D'''/'''d'''/'''A'''/'''a''' are defined.
* '''A''': generic AC catenary electric engines. 25kV only if '''a''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''A''';
* '''a''': 15kV AC catenary electric engines. Only defined if '''A''' also defined. Vehicle sets should use '''A''' and '''E''' as fallback, if defining an engine for '''a''';
* '''D''': generic DC catenary electric engines. 3kV if '''d''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''D''';
* '''d''': 1.5kV DC catenary electric engines. Only defined if '''D''' also defined. Vehicle sets should use '''D''' and '''E''' as fallback, if defining an engine for '''d'''.
For a 2-system set, you can simply drop '''a''' and '''d'''.

=== Standard labels: RAIL, ELRL, MONO, MGLV ===
It's not possible to undefine the standard railtypes RAIL, ELRL, MONO and MGLV. The game will always add those if there are vehicles defined for these track types. As a result, for a track set it's best not to ignore those standard labels, but rather work with them and define them in the set. If your track set does not have monorail or maglev tracks, there of course is no need to define those. But if your track set defines anything that resembles unelectrified or electrified rail, you should use the RAIL and ELRL labels. Matching labels from the above scheme will then be defined in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

As vehicles from NewGRFs that do not use explicit railtypes will end up on these standard railtypes, you should use RAIL instead of whatever type could be regarded as the most commonly used unelectrified type, ELRL instead of the most commonly used electrified type and so on. The label according to this scheme is then set as an alternate.

== Summary for track sets ==
This section summarizes the above for track sets.

; [X***] Track gauge and type class
* Define at least one track type for every track gauge/type class you want in your set.
* If you only provide tracks for one gauge/type, consider leaving some free railtypes so a player can load an additional set for some other type.
; [*X**] Speed limit class
* Make sure class A is always available, either directly or via an alternate label.
* Use only class A if you don't want speed limits;
* With speed limits, A is the lowest speed limit. Continue with B, C, etc. for increasing speed limits;
* The speed class can also be used to implement additional eye-candy track types, use letters higher in the alphabet for this.
; [**X*] Axle load class
* Always define all classes A through E for every track type class / electrification combination, either:
** Directly via a real railtype definition;
** Indirectly via the alternate rail type label list, property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].
* Extend the predefined classes only if you also provide a train set that makes use of these.
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via property 1D.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Always define the standard labels when possible, instead of what would be the equivalent of the standard label in this scheme.
* Map the equivalent labels from this scheme to the standard labels using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

Or, put differently, for each gauge/type, select one or more energy source types. For each type/energy combination provide all axle load classes for the speed class "A", either as a real type or as an alternate of another type. Provide more types with a different speed letter if you want to provide several different speeds or other eye-candy tracks.

== Summary for train sets ==
This section summarizes the above for train sets.

; [X***] Track gauge and type class
* Use the track type class that matches the vehicle;
* Define a fallback type via the railtype table in case you want the vehicle to be available on a different track if no matching track set is loaded.
** Specialized subtypes like "n" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "N").
; [*X**] Speed limit class
* Always use class A for every vehicle.
; [**X*] Axle load class
* Use all classes A through E according to the maximum axle weight of the vehicle.
* Extend the predefined classes only if you also provide a track set that makes use of these;
** When extending the predefined classes A through E, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Define a fallback type to the standard labels via the railtype table in case you want the vehicle to be available on the standard tracks if no matching track set is loaded.

Be as specific as you want when selecting the railtype, it is the job of the track set to select a playable, reduced subset out of all possible type combinations.

== In case you're not convinced by this scheme ==
Adopting this scheme gives the player freedom to use any track set in combination with any train set that follow the scheme.

This means that you can make your train set compatible with track sets that provide axle load classes, and track sets that provide speed limits, and at the same time with track sets that provide none of this. This way, the player can decide to play with or without axle load classes, or with or without speed limits, simply by loading a track set that does or does not provide these features.

And for your track set, it means that you can make it as simple or as complicated as you want (within the 64 track type limit), while not having to worry about compatibility with train sets.

Still not convinced? Feel free to use railtype labels of your own, but know that you will likely come to regret that at some point in the future.

==Forum topic==
If you want to discuss the standardized railtype scheme or have any questions about it, you can visit [http://www.tt-forums.net/viewtopic.php?t=59379 the forum topic].

=="Innsbruck 2022 Convention" for partial compliance==

This is really esoteric, but eh. It was the product of long discussion / debate / argument / reasoning between grf authors.

1. The Standardized Railtype Scheme '''is a useful tool''' for providing reliable compatibility between train grfs and railtype grfs.

2. The '''axle load class''' in the scheme presents a number of issues for compliance.

2.1. Over 10 years since the scheme was standardised, not many train grfs implement multiple axle load classes '''as required by the scheme'''. Known examples that '''do''' comply include Dutch Train Set, French Narrow Gauge Trains, and Finnish Trains.

2.2. Elements of the axle load rules have proven hard to interpret. For example:

* is it compliant to use ''fewer'' than 5 classes in a train grf? There is a lack of consensus on this.
* axle load is only one of many factors that govern whether a vehicle is compatible with a route, for example loading gauge, minimum curve, signalling types etc

2.3. Meanwhile ''multiple existing train grfs use class ''A'' for the axle load for all trains'' (except where relying on default railtypes such as RAIL and ELRL).

'''3. The Innsbruck 2022 Convention uses class ''A'' for axle load for '''all''' trains in a train grf (except where relying on default railtypes such as RAIL and ELRL).'''

This is '''not''' fully compliant with the Standardized Railtype Scheme and does not claim to be.

However train grfs using the Innsbruck 2022 Convention are ''broadly compatible'' with railtype grfs using the Standardized Railtype Scheme.

Obligatory XKCD link about 'standards': https://xkcd.com/927/

===Known issues===

Known problems are that trains using only class 'A' may limit the ability of railtype grf authors to achieve their design goals for separating railtypes by axle load.
But on reflection, it can be seen that a train grf might not be able to provide a broad enough range of vehicles to cover at least 5 axle load classes.

3.1. The Innsbruck 2022 Convention is '''not''' appropriate for train grf authors who wish to provide more than one axle load class.

3.2. The Innsbruck 2022 Convention treats the meaning of class ''A'' as ''undefined'', ''ignored'' or ''compatible with most restricted railtype'' for axle load.

Axle load class ''A'' '''cannot''' be safely interpreted as ''universal'' because from the perspective of a railtype grf ''A'' is ''most restricted railtype'', where ''universal'' is better represented as ''least restricted railtype''. Depending how many axle load classes are in use by the railtype grf, this could be class ''B'', ''C'', ''D'', ''E'' etc. To illustrate this issue, take the following scenario

* railtype grf defines axle loads ''A'' to ''E''. In this case the railtype grf author intends that ''A'' is compatible with the smallest range of vehicles, ''E'' is compatible with the largest range of vehicles, and ''B'', ''C'' and ''D'' are compatible with some intermediate ranges of vehicles
* but the vehicle grf author has defined all vehicles to be axle load ''A'' in an attempt to express this vehicle is ''universal''. The result in the game is that an identical range of vehicles will be compatible with railtypes ''A'' to ''E''.

This is clearly '''not''' the intended outcome of the railtype author. But nor is it clear within the spec that the vehicle author has particularly done anything wrong.

It ''would'' be possible to use railtype availability testing to adjust the vehicle property 05 (track_type) to fit the highest defined axle load (''E'' in this example case), but this is not insignificant work, and it's unlikely to be widely adopted by vehicle grf authors. Nor would this solution achieve ''universal'' as all vehicles in vehicle grf then would be incompatible with types ''A'' through ''D''.

3.3. When the Innsbruck 2022 Convention is used, this '''does not prevent''' a train grf being extended in some future release to achieve full compliance with Standardized Railtype Scheme. ''That choice remains with train grf authors''.

3.4. If 2012 could be revisited, providing an optional ''_'' axle load class in the Standardized Railtype Scheme for ''undefined'' would have been preferable, but as of 2022, ''A'' is already widely used for this purpose, and time travel is not known to be possible.

==Possible additions==

{|
! !!Track type/gauge
|-
|B ||Broad gauge rail (Also used by "ultra-broad" fictional tracktype; As broad gauge is a rare tracktype, it may still be feasible to cement B and b as broad gauges of two differing sizes)
|-
|b ||Broad gauge rail (Originally assigned to uppercase B; As broad gauge is a rare tracktype, it may still be feasible to cement B and b as broad gauges of two differing sizes)
|-
|s ||Multiple gauge rail, ultrabroad/broad/standard/narrow/secondary narrow gauge
|-
|6 ||600mm, formerly labelled "NG60" before standardization
|-
|m ||Minimum gauge rail; [https://en.wikipedia.org/wiki/Minimum-gauge_railway 15 in (381 mm), 400 mm (15+3⁄4 in), 16 in (406 mm), 18 in (457 mm), 19 in (483 mm), 500 mm (19+3⁄4 in) or 20 in (508 mm)]
|-
|-
|0 ||(A number zero, not a letter "Oh") No track, eyecandy-use only
|}

It might be prefered to instead use keep "B" for current broad gauge and instead using lovercase "b" for the new ultra-broad gauge. This wouldn't be to different from narrow gauge since the lesser used ones are lowercase and fallback to the uppercase ones.

{|
! !!Electrification !!Fallback
|-
|t ||"Universal custom tunnel" (for electrified sub-surface rail tunnels) ||E (mandatory)
|}

Standardized Railtype Scheme

2023-11-12T17:05:13Z

Revenge of kiothedev: /* Possible additions */

This railtype label scheme aims to bring order to the uncontrolled growth of railtype labels. It groups the rail types into what matters from a technical perspective. The scheme provides a standardized way of defining railtype labels, based on track gauge and type, speed class, allowable axle weight and electrification type.

It is the explicit intent of this scheme to decouple track sets from vehicle sets to facilitate easy mixing. This way the player can select a track set of choice to go with a train set of choice. It allows the player to play with or without axle load classes, or with or without speed limit classes, simply by loading a track set that does or does not provide these features. In some cases it will also be possible to combine niche track sets, for instance a standard gauge track set with a narrow gauge and a metro track set.

== The Label Scheme ==
A railtype label consists of four characters. In this scheme, each position has a different purpose:
# Track gauge and type class (e.g. standard gauge rail, narrow gauge rail, monorail)
# Speed limit class
# Axle load class (maximum allowed axle weight for this track)
# Energy source type class

In the next sections, each of the four positions will be explained.

=== Track gauge and type class [X***] ===
The first position in the railtype label defines track gauge and/or track type class. The following classes are currently defined:

{|
! !!Track type/gauge
|-
|S ||Standard gauge rail
|-
|B ||Broad gauge rail
|-
|N ||Narrow gauge rail
|-
|n ||Secondary narrow gauge rail (e.g. when providing both metre and cape gauge, always use N in case of just one type of narrow gauge)
|-
|D ||Dual gauge rail, standard/broad gauge
|-
|d ||Dual gauge rail, standard/narrow gauge
|-
|M ||Monorail
|-
|L ||Magnetic Levitation
|}

=== Speed limit class [*X**] ===
The second position in the railtype label defines the speed limit class. These classes do not map to a fixed numeric value, but are used to define an internal speed limit order for the track set. This means that if your track set has two different speed limits for track types that are otherwise identical, you'll use letters A and B here. In case of three different speed limits, use A, B and C. In case your track set does not employ speed limits, always use A. Train sets do not care about the speed limit, and will always set the lowest speed class, i.e. A.

This gives for instance the following options:

<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||no speed limits
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||high speed
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||medium speed
|-
|C ||high speed
|}
</div>
<div style="float:left;">
 etc. 
</div>
</div>
<div style="clear:left;"></div>

The speed limit class may also be used for some advanced features of the label scheme, like specialized track types and eyecandy purposes. Be careful not to break the compatibility with other sets when using the speed limit class for these purposes.

An example of a special use is rack rail. In the French set it is used to give rack rail engines a higher speed and TE than normal rail engines when used on rack rail. When defining trains with a special speed limit class, always allow a fallback to speed limit class A via the railtype table.

An example of eyecandy use are urban tracks. These are a variation of regular tracks, but with concrete ground tiles to better match the urban environment. Train sets must not define vehicles for eyecandy classes. If you think you have special vehicles that should only run on the eyecandy class, it is ''not'' eyecandy but a separate track gauge/type.

The following special and eyecandy classes have been defined so far:

{|
! !!Description !!Type !!Used by
|-
|A-H ||speed limits ||colspan="2"|reserved
|-
|R ||rack rail ||special ||French Set Rails
|-
|S ||subterranean ||eyecandy ||Metro Track Set
|-
|U ||urban ||eyecandy ||Metro Track Set
|-
|g ||ground tile for 45° angles ||eyecandy ||(none yet)
|}

=== Axle load class [**X*] ===
The third position defines the axle weight limit. Heavy trains cannot run on tracks with a low axle weight limit; these trains need more expensive tracks with a heigher weight limit. There are five axle load classes '''A''' through '''E'''. '''A''' is for the lowest axle load limit, '''E''' for the highest. The exact axle load attached to each class is relative to the track gauge/type and trains in the set.

A train set should set the appropriate axle weight for each train via the railtype label, as to make the set work with track sets that do provide tracks with different weight limits, even if you don't care about it for your trainset. Split all vehicles of a certain track gauge/type into five groups of similar axle weight. The group with the lowest axle weights will get class '''A''', the second lowest class '''B''', etc. up to the group with the highest axle weights which will get class '''E'''. Do the same for the other track gauge/types if your train set has those.

A track set does not have to provide a dedicated track type for each axle weight limit. A track set that does not provide a dedicated track for each axle load class, must make sure to map all undefined axle load classes to a real railtype using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]]. This way a train set can rely on all labels for all axle load classes being available. Example: if you only want to provide 2 axle load classes for standard gauge unelectrified with no speed limits, you can map SA'''A'''N + SA'''B'''N to SA'''C'''N and SA'''D'''N to SA'''E'''N if the cost difference between the two railtypes is high, or SA'''A'''N to SA'''B'''N and SA'''C'''N + SA'''D'''N to SA'''E'''N if the cost difference is low.

If you don't want to provide any axle load classes in your track set, it doesn't really matter what axle load class you choose for the track, as you'll be mapping all other classes to this track anyways. But the lowest or highest class are the obvious choice. Example: if your track set only provides narrow gauge unelectrified track with no speed limits and no axle load limits, you may use NA'''A'''N for the track label, and provide NA'''B'''N, NA'''C'''N, NA'''D'''N, NA'''E'''N in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

If you need more than five axle load class, you may use lowercase letters for very low axle loads and continue the uppercase letters for very high axle loads. Be advised that your train set may not assume the existance of any other class than '''A''' through '''E''', so when the range make sure to program your railtype table such that trains with such a class will fall back to class '''A''' or '''E'''. If you make a track set with an extended range, be aware that not all train sets will define trains for these tracks. In general: only do this in case of a train set with a matching track set.

For the lowercase letters, '''b''' is lower than '''a''', so for increasing axle load limits: b < a < A < B < C etc.

Note that the axle load classes never map to a specific weight in tonnes. For that reason it does not make sense to add a numeric value for the axle load to the name of a track type or in the extended purchase info of a train. Instead use the relative expressions 'very low', 'low', 'medium', 'high' and 'very high' or use the class letters directly.

=== Energy source type class [***X] ===
The last position defines the energy source type class. This is split in generic energy source types like overhead wires and third rail and specialized types like alternating and direct current.

A track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

A vehicle set that uses specialized types should define a generic type as fallback, via the railtype table. If such a fallback is omitted, please note that certain vehicles may be unavailable depending on track set loaded.

{|
! !!Generic energy type classes
|-
|N ||no electrification
|-
|E ||overhead wires/catenary electrification
|-
|3 ||3rd rail electrification
|}

{|
! !!Specialized energy type classes !!Vehicle set fallback
|-
|Z ||3rd rail and catenary electrification || 3 or E
|-
|4 ||4th rail electrification || 3
|-
|Y ||4th rail and catenary electrification || 4 or E
|-
|T ||[http://en.wikipedia.org/wiki/Three-phase_AC_railway_electrification three phase AC electrification] || E
|-
| colspan="3" |  
|-
|D ||DC catenary electrification || E
|-
|d ||low voltage DC catenary electrification (only when D also used in set) || First A then E
|-
|A ||AC catenary electrification || E
|-
|a ||low voltage AC catenary electrification (only when A also used in set) || First A then E
|}

If you want multi-voltage/current vehicles in your set (i.e. a train that can run on both AC and DC current), you have to define a dedicated railtype for those vehicles. Without the railtype, it's not possible to define vehicles with this property. If you only have vehicles that can run on either one type of voltage/current or on all types of voltage/current (e.g. a 2-system if you only have '''A''' and '''D''' tracks, or a 4-system in case of all '''A''', '''a''', '''D''' and '''d'''), then use the generic class '''E''' for vehicles that should be able to run on all different voltage/currents. Also the track set needs to have one at least one railtype with class '''E''' defined.

Note that if you want more than one type of multi-voltage/current, you'll quickly get a combinatory explosion of railtype labels, so plan carefully or do not attempt it. For every different multi-voltage/current vehicle type a dedicated railtype is needed. If you want all possible combinations, then you need to define an additional 8 classes. It is not recommended to make your train/track set this complicated.

Example approach for a 4-system set, with trains that can run on either one or all systems:
* '''E''': generic catenary-powered electric engines. "universal" [4-system] if any of '''D'''/'''d'''/'''A'''/'''a''' are defined.
* '''A''': generic AC catenary electric engines. 25kV only if '''a''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''A''';
* '''a''': 15kV AC catenary electric engines. Only defined if '''A''' also defined. Vehicle sets should use '''A''' and '''E''' as fallback, if defining an engine for '''a''';
* '''D''': generic DC catenary electric engines. 3kV if '''d''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''D''';
* '''d''': 1.5kV DC catenary electric engines. Only defined if '''D''' also defined. Vehicle sets should use '''D''' and '''E''' as fallback, if defining an engine for '''d'''.
For a 2-system set, you can simply drop '''a''' and '''d'''.

=== Standard labels: RAIL, ELRL, MONO, MGLV ===
It's not possible to undefine the standard railtypes RAIL, ELRL, MONO and MGLV. The game will always add those if there are vehicles defined for these track types. As a result, for a track set it's best not to ignore those standard labels, but rather work with them and define them in the set. If your track set does not have monorail or maglev tracks, there of course is no need to define those. But if your track set defines anything that resembles unelectrified or electrified rail, you should use the RAIL and ELRL labels. Matching labels from the above scheme will then be defined in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

As vehicles from NewGRFs that do not use explicit railtypes will end up on these standard railtypes, you should use RAIL instead of whatever type could be regarded as the most commonly used unelectrified type, ELRL instead of the most commonly used electrified type and so on. The label according to this scheme is then set as an alternate.

== Summary for track sets ==
This section summarizes the above for track sets.

; [X***] Track gauge and type class
* Define at least one track type for every track gauge/type class you want in your set.
* If you only provide tracks for one gauge/type, consider leaving some free railtypes so a player can load an additional set for some other type.
; [*X**] Speed limit class
* Make sure class A is always available, either directly or via an alternate label.
* Use only class A if you don't want speed limits;
* With speed limits, A is the lowest speed limit. Continue with B, C, etc. for increasing speed limits;
* The speed class can also be used to implement additional eye-candy track types, use letters higher in the alphabet for this.
; [**X*] Axle load class
* Always define all classes A through E for every track type class / electrification combination, either:
** Directly via a real railtype definition;
** Indirectly via the alternate rail type label list, property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].
* Extend the predefined classes only if you also provide a train set that makes use of these.
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via property 1D.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Always define the standard labels when possible, instead of what would be the equivalent of the standard label in this scheme.
* Map the equivalent labels from this scheme to the standard labels using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

Or, put differently, for each gauge/type, select one or more energy source types. For each type/energy combination provide all axle load classes for the speed class "A", either as a real type or as an alternate of another type. Provide more types with a different speed letter if you want to provide several different speeds or other eye-candy tracks.

== Summary for train sets ==
This section summarizes the above for train sets.

; [X***] Track gauge and type class
* Use the track type class that matches the vehicle;
* Define a fallback type via the railtype table in case you want the vehicle to be available on a different track if no matching track set is loaded.
** Specialized subtypes like "n" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "N").
; [*X**] Speed limit class
* Always use class A for every vehicle.
; [**X*] Axle load class
* Use all classes A through E according to the maximum axle weight of the vehicle.
* Extend the predefined classes only if you also provide a track set that makes use of these;
** When extending the predefined classes A through E, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Define a fallback type to the standard labels via the railtype table in case you want the vehicle to be available on the standard tracks if no matching track set is loaded.

Be as specific as you want when selecting the railtype, it is the job of the track set to select a playable, reduced subset out of all possible type combinations.

== In case you're not convinced by this scheme ==
Adopting this scheme gives the player freedom to use any track set in combination with any train set that follow the scheme.

This means that you can make your train set compatible with track sets that provide axle load classes, and track sets that provide speed limits, and at the same time with track sets that provide none of this. This way, the player can decide to play with or without axle load classes, or with or without speed limits, simply by loading a track set that does or does not provide these features.

And for your track set, it means that you can make it as simple or as complicated as you want (within the 64 track type limit), while not having to worry about compatibility with train sets.

Still not convinced? Feel free to use railtype labels of your own, but know that you will likely come to regret that at some point in the future.

==Forum topic==
If you want to discuss the standardized railtype scheme or have any questions about it, you can visit [http://www.tt-forums.net/viewtopic.php?t=59379 the forum topic].

=="Innsbruck 2022 Convention" for partial compliance==

This is really esoteric, but eh. It was the product of long discussion / debate / argument / reasoning between grf authors.

1. The Standardized Railtype Scheme '''is a useful tool''' for providing reliable compatibility between train grfs and railtype grfs.

2. The '''axle load class''' in the scheme presents a number of issues for compliance.

2.1. Over 10 years since the scheme was standardised, not many train grfs implement multiple axle load classes '''as required by the scheme'''. Known examples that '''do''' comply include Dutch Train Set, French Narrow Gauge Trains, and Finnish Trains.

2.2. Elements of the axle load rules have proven hard to interpret. For example:

* is it compliant to use ''fewer'' than 5 classes in a train grf? There is a lack of consensus on this.
* axle load is only one of many factors that govern whether a vehicle is compatible with a route, for example loading gauge, minimum curve, signalling types etc

2.3. Meanwhile ''multiple existing train grfs use class ''A'' for the axle load for all trains'' (except where relying on default railtypes such as RAIL and ELRL).

'''3. The Innsbruck 2022 Convention uses class ''A'' for axle load for '''all''' trains in a train grf (except where relying on default railtypes such as RAIL and ELRL).'''

This is '''not''' fully compliant with the Standardized Railtype Scheme and does not claim to be.

However train grfs using the Innsbruck 2022 Convention are ''broadly compatible'' with railtype grfs using the Standardized Railtype Scheme.

Obligatory XKCD link about 'standards': https://xkcd.com/927/

===Known issues===

Known problems are that trains using only class 'A' may limit the ability of railtype grf authors to achieve their design goals for separating railtypes by axle load.
But on reflection, it can be seen that a train grf might not be able to provide a broad enough range of vehicles to cover at least 5 axle load classes.

3.1. The Innsbruck 2022 Convention is '''not''' appropriate for train grf authors who wish to provide more than one axle load class.

3.2. The Innsbruck 2022 Convention treats the meaning of class ''A'' as ''undefined'', ''ignored'' or ''compatible with most restricted railtype'' for axle load.

Axle load class ''A'' '''cannot''' be safely interpreted as ''universal'' because from the perspective of a railtype grf ''A'' is ''most restricted railtype'', where ''universal'' is better represented as ''least restricted railtype''. Depending how many axle load classes are in use by the railtype grf, this could be class ''B'', ''C'', ''D'', ''E'' etc. To illustrate this issue, take the following scenario

* railtype grf defines axle loads ''A'' to ''E''. In this case the railtype grf author intends that ''A'' is compatible with the smallest range of vehicles, ''E'' is compatible with the largest range of vehicles, and ''B'', ''C'' and ''D'' are compatible with some intermediate ranges of vehicles
* but the vehicle grf author has defined all vehicles to be axle load ''A'' in an attempt to express this vehicle is ''universal''. The result in the game is that an identical range of vehicles will be compatible with railtypes ''A'' to ''E''.

This is clearly '''not''' the intended outcome of the railtype author. But nor is it clear within the spec that the vehicle author has particularly done anything wrong.

It ''would'' be possible to use railtype availability testing to adjust the vehicle property 05 (track_type) to fit the highest defined axle load (''E'' in this example case), but this is not insignificant work, and it's unlikely to be widely adopted by vehicle grf authors. Nor would this solution achieve ''universal'' as all vehicles in vehicle grf then would be incompatible with types ''A'' through ''D''.

3.3. When the Innsbruck 2022 Convention is used, this '''does not prevent''' a train grf being extended in some future release to achieve full compliance with Standardized Railtype Scheme. ''That choice remains with train grf authors''.

3.4. If 2012 could be revisited, providing an optional ''_'' axle load class in the Standardized Railtype Scheme for ''undefined'' would have been preferable, but as of 2022, ''A'' is already widely used for this purpose, and time travel is not known to be possible.

==Possible additions==

{|
! !!Track type/gauge
|-
|B ||Broad gauge rail (Also used by "ultra-broad" fictional tracktype; As broad gauge is a rare tracktype, it may still be feasible to cement B and b as broad gauges of two differing sizes)
|-
|b ||Broad gauge rail (Originally assigned to uppercase B; As broad gauge is a rare tracktype, it may still be feasible to cement B and b as broad gauges of two differing sizes)
|-
|s ||Multiple gauge rail, ultrabroad/broad/standard/narrow/secondary narrow gauge
|-
|m ||Minimum gauge rail; [https://en.wikipedia.org/wiki/Minimum-gauge_railway 15 in (381 mm), 400 mm (15+3⁄4 in), 16 in (406 mm), 18 in (457 mm), 19 in (483 mm), 500 mm (19+3⁄4 in) or 20 in (508 mm)]
|-
|0 ||(A number zero, not a letter "Oh") No track, eyecandy-use only
|}

It might be prefered to instead use keep "B" for current broad gauge and instead using lovercase "b" for the new ultra-broad gauge. This wouldn't be to different from narrow gauge since the lesser used ones are lowercase and fallback to the uppercase ones.

{|
! !!Electrification !!Fallback
|-
|t ||"Universal custom tunnel" (for electrified sub-surface rail tunnels) ||E (mandatory)
|}

Standardized Railtype Scheme

2023-11-12T17:03:16Z

Revenge of kiothedev: /* Possible additions */

This railtype label scheme aims to bring order to the uncontrolled growth of railtype labels. It groups the rail types into what matters from a technical perspective. The scheme provides a standardized way of defining railtype labels, based on track gauge and type, speed class, allowable axle weight and electrification type.

It is the explicit intent of this scheme to decouple track sets from vehicle sets to facilitate easy mixing. This way the player can select a track set of choice to go with a train set of choice. It allows the player to play with or without axle load classes, or with or without speed limit classes, simply by loading a track set that does or does not provide these features. In some cases it will also be possible to combine niche track sets, for instance a standard gauge track set with a narrow gauge and a metro track set.

== The Label Scheme ==
A railtype label consists of four characters. In this scheme, each position has a different purpose:
# Track gauge and type class (e.g. standard gauge rail, narrow gauge rail, monorail)
# Speed limit class
# Axle load class (maximum allowed axle weight for this track)
# Energy source type class

In the next sections, each of the four positions will be explained.

=== Track gauge and type class [X***] ===
The first position in the railtype label defines track gauge and/or track type class. The following classes are currently defined:

{|
! !!Track type/gauge
|-
|S ||Standard gauge rail
|-
|B ||Broad gauge rail
|-
|N ||Narrow gauge rail
|-
|n ||Secondary narrow gauge rail (e.g. when providing both metre and cape gauge, always use N in case of just one type of narrow gauge)
|-
|D ||Dual gauge rail, standard/broad gauge
|-
|d ||Dual gauge rail, standard/narrow gauge
|-
|M ||Monorail
|-
|L ||Magnetic Levitation
|}

=== Speed limit class [*X**] ===
The second position in the railtype label defines the speed limit class. These classes do not map to a fixed numeric value, but are used to define an internal speed limit order for the track set. This means that if your track set has two different speed limits for track types that are otherwise identical, you'll use letters A and B here. In case of three different speed limits, use A, B and C. In case your track set does not employ speed limits, always use A. Train sets do not care about the speed limit, and will always set the lowest speed class, i.e. A.

This gives for instance the following options:

<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||no speed limits
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||high speed
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||medium speed
|-
|C ||high speed
|}
</div>
<div style="float:left;">
 etc. 
</div>
</div>
<div style="clear:left;"></div>

The speed limit class may also be used for some advanced features of the label scheme, like specialized track types and eyecandy purposes. Be careful not to break the compatibility with other sets when using the speed limit class for these purposes.

An example of a special use is rack rail. In the French set it is used to give rack rail engines a higher speed and TE than normal rail engines when used on rack rail. When defining trains with a special speed limit class, always allow a fallback to speed limit class A via the railtype table.

An example of eyecandy use are urban tracks. These are a variation of regular tracks, but with concrete ground tiles to better match the urban environment. Train sets must not define vehicles for eyecandy classes. If you think you have special vehicles that should only run on the eyecandy class, it is ''not'' eyecandy but a separate track gauge/type.

The following special and eyecandy classes have been defined so far:

{|
! !!Description !!Type !!Used by
|-
|A-H ||speed limits ||colspan="2"|reserved
|-
|R ||rack rail ||special ||French Set Rails
|-
|S ||subterranean ||eyecandy ||Metro Track Set
|-
|U ||urban ||eyecandy ||Metro Track Set
|-
|g ||ground tile for 45° angles ||eyecandy ||(none yet)
|}

=== Axle load class [**X*] ===
The third position defines the axle weight limit. Heavy trains cannot run on tracks with a low axle weight limit; these trains need more expensive tracks with a heigher weight limit. There are five axle load classes '''A''' through '''E'''. '''A''' is for the lowest axle load limit, '''E''' for the highest. The exact axle load attached to each class is relative to the track gauge/type and trains in the set.

A train set should set the appropriate axle weight for each train via the railtype label, as to make the set work with track sets that do provide tracks with different weight limits, even if you don't care about it for your trainset. Split all vehicles of a certain track gauge/type into five groups of similar axle weight. The group with the lowest axle weights will get class '''A''', the second lowest class '''B''', etc. up to the group with the highest axle weights which will get class '''E'''. Do the same for the other track gauge/types if your train set has those.

A track set does not have to provide a dedicated track type for each axle weight limit. A track set that does not provide a dedicated track for each axle load class, must make sure to map all undefined axle load classes to a real railtype using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]]. This way a train set can rely on all labels for all axle load classes being available. Example: if you only want to provide 2 axle load classes for standard gauge unelectrified with no speed limits, you can map SA'''A'''N + SA'''B'''N to SA'''C'''N and SA'''D'''N to SA'''E'''N if the cost difference between the two railtypes is high, or SA'''A'''N to SA'''B'''N and SA'''C'''N + SA'''D'''N to SA'''E'''N if the cost difference is low.

If you don't want to provide any axle load classes in your track set, it doesn't really matter what axle load class you choose for the track, as you'll be mapping all other classes to this track anyways. But the lowest or highest class are the obvious choice. Example: if your track set only provides narrow gauge unelectrified track with no speed limits and no axle load limits, you may use NA'''A'''N for the track label, and provide NA'''B'''N, NA'''C'''N, NA'''D'''N, NA'''E'''N in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

If you need more than five axle load class, you may use lowercase letters for very low axle loads and continue the uppercase letters for very high axle loads. Be advised that your train set may not assume the existance of any other class than '''A''' through '''E''', so when the range make sure to program your railtype table such that trains with such a class will fall back to class '''A''' or '''E'''. If you make a track set with an extended range, be aware that not all train sets will define trains for these tracks. In general: only do this in case of a train set with a matching track set.

For the lowercase letters, '''b''' is lower than '''a''', so for increasing axle load limits: b < a < A < B < C etc.

Note that the axle load classes never map to a specific weight in tonnes. For that reason it does not make sense to add a numeric value for the axle load to the name of a track type or in the extended purchase info of a train. Instead use the relative expressions 'very low', 'low', 'medium', 'high' and 'very high' or use the class letters directly.

=== Energy source type class [***X] ===
The last position defines the energy source type class. This is split in generic energy source types like overhead wires and third rail and specialized types like alternating and direct current.

A track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

A vehicle set that uses specialized types should define a generic type as fallback, via the railtype table. If such a fallback is omitted, please note that certain vehicles may be unavailable depending on track set loaded.

{|
! !!Generic energy type classes
|-
|N ||no electrification
|-
|E ||overhead wires/catenary electrification
|-
|3 ||3rd rail electrification
|}

{|
! !!Specialized energy type classes !!Vehicle set fallback
|-
|Z ||3rd rail and catenary electrification || 3 or E
|-
|4 ||4th rail electrification || 3
|-
|Y ||4th rail and catenary electrification || 4 or E
|-
|T ||[http://en.wikipedia.org/wiki/Three-phase_AC_railway_electrification three phase AC electrification] || E
|-
| colspan="3" |  
|-
|D ||DC catenary electrification || E
|-
|d ||low voltage DC catenary electrification (only when D also used in set) || First A then E
|-
|A ||AC catenary electrification || E
|-
|a ||low voltage AC catenary electrification (only when A also used in set) || First A then E
|}

If you want multi-voltage/current vehicles in your set (i.e. a train that can run on both AC and DC current), you have to define a dedicated railtype for those vehicles. Without the railtype, it's not possible to define vehicles with this property. If you only have vehicles that can run on either one type of voltage/current or on all types of voltage/current (e.g. a 2-system if you only have '''A''' and '''D''' tracks, or a 4-system in case of all '''A''', '''a''', '''D''' and '''d'''), then use the generic class '''E''' for vehicles that should be able to run on all different voltage/currents. Also the track set needs to have one at least one railtype with class '''E''' defined.

Note that if you want more than one type of multi-voltage/current, you'll quickly get a combinatory explosion of railtype labels, so plan carefully or do not attempt it. For every different multi-voltage/current vehicle type a dedicated railtype is needed. If you want all possible combinations, then you need to define an additional 8 classes. It is not recommended to make your train/track set this complicated.

Example approach for a 4-system set, with trains that can run on either one or all systems:
* '''E''': generic catenary-powered electric engines. "universal" [4-system] if any of '''D'''/'''d'''/'''A'''/'''a''' are defined.
* '''A''': generic AC catenary electric engines. 25kV only if '''a''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''A''';
* '''a''': 15kV AC catenary electric engines. Only defined if '''A''' also defined. Vehicle sets should use '''A''' and '''E''' as fallback, if defining an engine for '''a''';
* '''D''': generic DC catenary electric engines. 3kV if '''d''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''D''';
* '''d''': 1.5kV DC catenary electric engines. Only defined if '''D''' also defined. Vehicle sets should use '''D''' and '''E''' as fallback, if defining an engine for '''d'''.
For a 2-system set, you can simply drop '''a''' and '''d'''.

=== Standard labels: RAIL, ELRL, MONO, MGLV ===
It's not possible to undefine the standard railtypes RAIL, ELRL, MONO and MGLV. The game will always add those if there are vehicles defined for these track types. As a result, for a track set it's best not to ignore those standard labels, but rather work with them and define them in the set. If your track set does not have monorail or maglev tracks, there of course is no need to define those. But if your track set defines anything that resembles unelectrified or electrified rail, you should use the RAIL and ELRL labels. Matching labels from the above scheme will then be defined in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

As vehicles from NewGRFs that do not use explicit railtypes will end up on these standard railtypes, you should use RAIL instead of whatever type could be regarded as the most commonly used unelectrified type, ELRL instead of the most commonly used electrified type and so on. The label according to this scheme is then set as an alternate.

== Summary for track sets ==
This section summarizes the above for track sets.

; [X***] Track gauge and type class
* Define at least one track type for every track gauge/type class you want in your set.
* If you only provide tracks for one gauge/type, consider leaving some free railtypes so a player can load an additional set for some other type.
; [*X**] Speed limit class
* Make sure class A is always available, either directly or via an alternate label.
* Use only class A if you don't want speed limits;
* With speed limits, A is the lowest speed limit. Continue with B, C, etc. for increasing speed limits;
* The speed class can also be used to implement additional eye-candy track types, use letters higher in the alphabet for this.
; [**X*] Axle load class
* Always define all classes A through E for every track type class / electrification combination, either:
** Directly via a real railtype definition;
** Indirectly via the alternate rail type label list, property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].
* Extend the predefined classes only if you also provide a train set that makes use of these.
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via property 1D.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Always define the standard labels when possible, instead of what would be the equivalent of the standard label in this scheme.
* Map the equivalent labels from this scheme to the standard labels using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

Or, put differently, for each gauge/type, select one or more energy source types. For each type/energy combination provide all axle load classes for the speed class "A", either as a real type or as an alternate of another type. Provide more types with a different speed letter if you want to provide several different speeds or other eye-candy tracks.

== Summary for train sets ==
This section summarizes the above for train sets.

; [X***] Track gauge and type class
* Use the track type class that matches the vehicle;
* Define a fallback type via the railtype table in case you want the vehicle to be available on a different track if no matching track set is loaded.
** Specialized subtypes like "n" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "N").
; [*X**] Speed limit class
* Always use class A for every vehicle.
; [**X*] Axle load class
* Use all classes A through E according to the maximum axle weight of the vehicle.
* Extend the predefined classes only if you also provide a track set that makes use of these;
** When extending the predefined classes A through E, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Define a fallback type to the standard labels via the railtype table in case you want the vehicle to be available on the standard tracks if no matching track set is loaded.

Be as specific as you want when selecting the railtype, it is the job of the track set to select a playable, reduced subset out of all possible type combinations.

== In case you're not convinced by this scheme ==
Adopting this scheme gives the player freedom to use any track set in combination with any train set that follow the scheme.

This means that you can make your train set compatible with track sets that provide axle load classes, and track sets that provide speed limits, and at the same time with track sets that provide none of this. This way, the player can decide to play with or without axle load classes, or with or without speed limits, simply by loading a track set that does or does not provide these features.

And for your track set, it means that you can make it as simple or as complicated as you want (within the 64 track type limit), while not having to worry about compatibility with train sets.

Still not convinced? Feel free to use railtype labels of your own, but know that you will likely come to regret that at some point in the future.

==Forum topic==
If you want to discuss the standardized railtype scheme or have any questions about it, you can visit [http://www.tt-forums.net/viewtopic.php?t=59379 the forum topic].

=="Innsbruck 2022 Convention" for partial compliance==

This is really esoteric, but eh. It was the product of long discussion / debate / argument / reasoning between grf authors.

1. The Standardized Railtype Scheme '''is a useful tool''' for providing reliable compatibility between train grfs and railtype grfs.

2. The '''axle load class''' in the scheme presents a number of issues for compliance.

2.1. Over 10 years since the scheme was standardised, not many train grfs implement multiple axle load classes '''as required by the scheme'''. Known examples that '''do''' comply include Dutch Train Set, French Narrow Gauge Trains, and Finnish Trains.

2.2. Elements of the axle load rules have proven hard to interpret. For example:

* is it compliant to use ''fewer'' than 5 classes in a train grf? There is a lack of consensus on this.
* axle load is only one of many factors that govern whether a vehicle is compatible with a route, for example loading gauge, minimum curve, signalling types etc

2.3. Meanwhile ''multiple existing train grfs use class ''A'' for the axle load for all trains'' (except where relying on default railtypes such as RAIL and ELRL).

'''3. The Innsbruck 2022 Convention uses class ''A'' for axle load for '''all''' trains in a train grf (except where relying on default railtypes such as RAIL and ELRL).'''

This is '''not''' fully compliant with the Standardized Railtype Scheme and does not claim to be.

However train grfs using the Innsbruck 2022 Convention are ''broadly compatible'' with railtype grfs using the Standardized Railtype Scheme.

Obligatory XKCD link about 'standards': https://xkcd.com/927/

===Known issues===

Known problems are that trains using only class 'A' may limit the ability of railtype grf authors to achieve their design goals for separating railtypes by axle load.
But on reflection, it can be seen that a train grf might not be able to provide a broad enough range of vehicles to cover at least 5 axle load classes.

3.1. The Innsbruck 2022 Convention is '''not''' appropriate for train grf authors who wish to provide more than one axle load class.

3.2. The Innsbruck 2022 Convention treats the meaning of class ''A'' as ''undefined'', ''ignored'' or ''compatible with most restricted railtype'' for axle load.

Axle load class ''A'' '''cannot''' be safely interpreted as ''universal'' because from the perspective of a railtype grf ''A'' is ''most restricted railtype'', where ''universal'' is better represented as ''least restricted railtype''. Depending how many axle load classes are in use by the railtype grf, this could be class ''B'', ''C'', ''D'', ''E'' etc. To illustrate this issue, take the following scenario

* railtype grf defines axle loads ''A'' to ''E''. In this case the railtype grf author intends that ''A'' is compatible with the smallest range of vehicles, ''E'' is compatible with the largest range of vehicles, and ''B'', ''C'' and ''D'' are compatible with some intermediate ranges of vehicles
* but the vehicle grf author has defined all vehicles to be axle load ''A'' in an attempt to express this vehicle is ''universal''. The result in the game is that an identical range of vehicles will be compatible with railtypes ''A'' to ''E''.

This is clearly '''not''' the intended outcome of the railtype author. But nor is it clear within the spec that the vehicle author has particularly done anything wrong.

It ''would'' be possible to use railtype availability testing to adjust the vehicle property 05 (track_type) to fit the highest defined axle load (''E'' in this example case), but this is not insignificant work, and it's unlikely to be widely adopted by vehicle grf authors. Nor would this solution achieve ''universal'' as all vehicles in vehicle grf then would be incompatible with types ''A'' through ''D''.

3.3. When the Innsbruck 2022 Convention is used, this '''does not prevent''' a train grf being extended in some future release to achieve full compliance with Standardized Railtype Scheme. ''That choice remains with train grf authors''.

3.4. If 2012 could be revisited, providing an optional ''_'' axle load class in the Standardized Railtype Scheme for ''undefined'' would have been preferable, but as of 2022, ''A'' is already widely used for this purpose, and time travel is not known to be possible.

==Possible additions==

{|
! !!Track type/gauge
|-
|B ||Broad gauge rail (Also used by "ultra-broad" fictional tracktype; As broad gauge is a rare tracktype, it may still be feasible to cement B and b as broad gauges of two differing sizes)
|-
|b ||Broad gauge rail (Originally assigned to uppercase B; As broad gauge is a rare tracktype, it may still be feasible to cement B and b as broad gauges of two differing sizes)
|-
|s ||Multiple gauge rail, ultrabroad/broad/standard/narrow/secondary narrow gauge
|-
|m ||Minimum gauge rail; [[Wikipedia:Minimum-gauge_railway|15 in (381 mm), 400 mm (15+3⁄4 in), 16 in (406 mm), 18 in (457 mm), 19 in (483 mm), 500 mm (19+3⁄4 in) or 20 in (508 mm)]]
|-
|0 ||(A number zero, not a letter "Oh") No track, eyecandy-use only
|}

It might be prefered to instead use keep "B" for current broad gauge and instead using lovercase "b" for the new ultra-broad gauge. This wouldn't be to different from narrow gauge since the lesser used ones are lowercase and fallback to the uppercase ones.

{|
! !!Electrification !!Fallback
|-
|t ||"Universal custom tunnel" (for electrified sub-surface rail tunnels) ||E (mandatory)
|}

Standardized Roadtype Scheme

2023-11-09T15:26:11Z

Revenge of kiothedev: /* Forum topic */

This scheme was originally conceived in order to decrease the amount of neccesary hidden road and tramtrack types. This is done by standardising which labels vehicles and infrastructure should use. The standard also allows for more gameplay depth by having the option to limit vehicles to certain types of roads. It does similarly to the railtype scheme allow mixing of any vehicle set with any infrastructure set. It does however not allow multible infrastructure sets to be used at the same time. It does not prevent it but all of the sets used have to be made to be used with each other, or use diffrent surfaces/types which don't conflict with each other. The standard sets no limit on how vehicle sets can be used.

It is ultimately up to the infrastructure set to chose what roadtypes are avaliable and thereby what vehicles are avaliable. Infrastructure and vehicles can both be in the same set, it is however recommended to be able to dissable the infrastructure with parameters in case the player wants to use a different set for their infrastucture.

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Regular Road
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
| E
|
|-
| p
| Pump/Pipeline
| p
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Regular Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
| E
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not. This means that road/tramtrack sets shouldn't add these to their [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] and [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]]

It is up to the track set to implement all powered roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A".

Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| N
| None
| None
|
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|
|-
| G
| Ground electrified
| Ground electrified
|
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
| E or G
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|}
A tramtrack set that only uses specialized types, should map the generic types to the most suitable specialized type in the set with the help of the [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

=== The default labels (ROAD, ELRL) and non-standard labels===
OpenTTD will allways define ROAD and ELRL incase there are vehicles for them. It is therefore recomended to have these present in the set so that you can map them to appropriete labels from the standard. There are a few ways of doing this:
*Replacing one of the standardised types with the default label and putting the standardised label in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].
*Defining ROAD and/or ELRL separately from the standardised labels and adding the standard ones to the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. The main advantage of this is that you can use a parameter to map ROAD and/or ELRL to the standardised labels. This allows the player to chose where there non standardised vehicles will be able to go.

Vehicle set authors might want to add the default labels and non-standard labels as a fallback. If not implemented for the defualt labels, their vehicles won't show up on the default roads and/or tracks, leading to countless bug reports from players. Non standard labels that might be worth adding fallbacks too are: ELRD, RAIL, HAUL and probably some more.

== Summary for Road/Tramtrack sets ==
This section summarizes the above for road/tramtrack sets.

; [X***] Surface / Type
* Chose which Surfaces and types you want in your set and give them the correct [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* If you only provide roads/tramtracks for one surface/type, consider leaving some free road/tramtypes so a player can load an additional set for some other type.
; [*X**] Speed / Feature
* Make sure class A is always available.
* Use B, C and so on if you have multible roads/tramtracks with the otherwise the same label.
; [**X*] Terrain / Stability
* Always define classes A through C for every road/tramtrack surface/type energy combination, either:
** Directly via a real road/tramtype definition;
** Indirectly via the alternate road/tramtype label list, [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; Default labels [ROAD, ELRL] and non-standard labels
* Always define the default labels when possible, instead of what would be the equivalent of the default label in this scheme.
* Map the equivalent labels from this scheme to the default labels using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* Map common non-standard labels to the most similar label in this scheme using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].

== Summary for vehicle sets ==
This section summarizes the above for vehicle sets.

; [X***] Surface / Type
* Use the surface / type class that matches the vehicle;
* Define a fallback type via the road/tramtype table in case you want the vehicle to be available on a different road or tramtrack if no matching road/tramtrack set is loaded.
** Specialized subtypes like "G" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "P" or "R").
; [*X**] Speed / Feature
* Always use class A for every vehicle.
; [**X*] Terrain / Stability
* Use A, B or C depending on where you want your vehicles to be able to drive.
** A is used for slow offroad capable vehicles which aren't allowed on Motorways and similar Roads
** B is used for vehicles which can drive offroad but are also allowed on Motorways.
** C is used for vehicles which can't go offroad or similar.
** Use B if you aren't sure what to chose.
* Never use a or c.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Default labels [ROAD, ELRL] and non-standard labels
* Define a fallback type to the default labels via the road/tramtype table in case you want the vehicle to be available on the default roads/track if no matching set is loaded.
* Do the same for any non-standard labels that may be relevant.

Be as specific as you want when selecting the road/tramtype, it is the job of the road/track set to select a playable, reduced subset out of all possible type combinations.
=== Example of fallback order for vehicle sets ===
{| class="wikitable"
|- style="font-style:italic;"
! Unchanged label
! Fallback order
|-
| GACE (road)
| GACE -> PACE -> RACE -> (ROAD)
|-
| PAB4 (tram)
| PAB4 -> PAB3 -> PABG -> RAB4 -> RAB3 -> RABG
|-
| IAAG (road)
| IAAG -> RAAG
|-
| AACE (road)
| AACE -> RAAE -> (ELRD)
|-
| RABE (tram)
| RABE -> (ELRL)
|-
| PAAN (tram)
| PAAN -> RAAN -> (RAIL)
|}
== Forum topic ==
Feel free to discuss and ask questions about the scheme at the forum topic [https://www.tt-forums.net/viewtopic.php?t=90715 Here].

=== Possible additions ===
To be discussed in the forum topic...

==== Surface / Type [X***] ====
Describes the road surface / rail type and thus the vehicle type.

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| X or x
| Multiple guidance systems or guages
| (Depends on intent; only two tramtype rail system combinations can exist for a given set of standardized labels - i.e. XABE and xABE - making it necessary to plan accordingly)

|}

==== Energy [***X] ====
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| I
| Induction-charge electrified
| Induction-charge electrified
| Z then E then G
|-
| i
| Eyecandy/Pipeline Infrastructure
| Eyecandy/Electric & Telecom Infrastructure
| I then Z then G then E
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| X
| N/A
| Multiple systems of electricity
| Use with surface X or x (e.g. XABX and xABX) or surface R (rail-based tramtype). For use only when at least one standardized label is an energy supply and multiple non-conflicting energy types are all at the same level, such as electrified, ground electrified and trackless tram overlap
|-
| x
| N/A
| Multiple systems of guidance, incompatible
| Use this with surface x (e.g. xABx) or the surface systems (e.g. SABx, RABx, MABx). For use when tramtypes are at different heights but all are fundamentally incompatible (i.e. suspended monorail, tram and pneumatic metro)
|-
| 0-2 & 5-9
| N/A
| Multiple systems of guidance, mix of compatible/incompatible
| For use when tramtypes are a mix of compatible and fundamentally incompatible (i.e. electrified, ground electrified, trackless tram, suspended monorail, tram and pneumatic metro); Do not set powered_railtype_list for these, instead use alternative_railtype_list, or define these in another label's powered_railtype_list (i.e. XAB0/XAB1/XAB2/XAB5/.../XAB9 for XABE/XABX and RAB0/RAB1/RAB2/RAB5/.../RAB9 for RABN/RABE/RABX).
|}

Standardized Roadtype Scheme

2023-11-09T15:25:26Z

Revenge of kiothedev: /* Energy [***X] */

This scheme was originally conceived in order to decrease the amount of neccesary hidden road and tramtrack types. This is done by standardising which labels vehicles and infrastructure should use. The standard also allows for more gameplay depth by having the option to limit vehicles to certain types of roads. It does similarly to the railtype scheme allow mixing of any vehicle set with any infrastructure set. It does however not allow multible infrastructure sets to be used at the same time. It does not prevent it but all of the sets used have to be made to be used with each other, or use diffrent surfaces/types which don't conflict with each other. The standard sets no limit on how vehicle sets can be used.

It is ultimately up to the infrastructure set to chose what roadtypes are avaliable and thereby what vehicles are avaliable. Infrastructure and vehicles can both be in the same set, it is however recommended to be able to dissable the infrastructure with parameters in case the player wants to use a different set for their infrastucture.

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Regular Road
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
| E
|
|-
| p
| Pump/Pipeline
| p
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Regular Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
| E
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not. This means that road/tramtrack sets shouldn't add these to their [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] and [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]]

It is up to the track set to implement all powered roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A".

Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| N
| None
| None
|
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|
|-
| G
| Ground electrified
| Ground electrified
|
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
| E or G
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|}
A tramtrack set that only uses specialized types, should map the generic types to the most suitable specialized type in the set with the help of the [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

=== The default labels (ROAD, ELRL) and non-standard labels===
OpenTTD will allways define ROAD and ELRL incase there are vehicles for them. It is therefore recomended to have these present in the set so that you can map them to appropriete labels from the standard. There are a few ways of doing this:
*Replacing one of the standardised types with the default label and putting the standardised label in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].
*Defining ROAD and/or ELRL separately from the standardised labels and adding the standard ones to the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. The main advantage of this is that you can use a parameter to map ROAD and/or ELRL to the standardised labels. This allows the player to chose where there non standardised vehicles will be able to go.

Vehicle set authors might want to add the default labels and non-standard labels as a fallback. If not implemented for the defualt labels, their vehicles won't show up on the default roads and/or tracks, leading to countless bug reports from players. Non standard labels that might be worth adding fallbacks too are: ELRD, RAIL, HAUL and probably some more.

== Summary for Road/Tramtrack sets ==
This section summarizes the above for road/tramtrack sets.

; [X***] Surface / Type
* Chose which Surfaces and types you want in your set and give them the correct [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* If you only provide roads/tramtracks for one surface/type, consider leaving some free road/tramtypes so a player can load an additional set for some other type.
; [*X**] Speed / Feature
* Make sure class A is always available.
* Use B, C and so on if you have multible roads/tramtracks with the otherwise the same label.
; [**X*] Terrain / Stability
* Always define classes A through C for every road/tramtrack surface/type energy combination, either:
** Directly via a real road/tramtype definition;
** Indirectly via the alternate road/tramtype label list, [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; Default labels [ROAD, ELRL] and non-standard labels
* Always define the default labels when possible, instead of what would be the equivalent of the default label in this scheme.
* Map the equivalent labels from this scheme to the default labels using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* Map common non-standard labels to the most similar label in this scheme using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].

== Summary for vehicle sets ==
This section summarizes the above for vehicle sets.

; [X***] Surface / Type
* Use the surface / type class that matches the vehicle;
* Define a fallback type via the road/tramtype table in case you want the vehicle to be available on a different road or tramtrack if no matching road/tramtrack set is loaded.
** Specialized subtypes like "G" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "P" or "R").
; [*X**] Speed / Feature
* Always use class A for every vehicle.
; [**X*] Terrain / Stability
* Use A, B or C depending on where you want your vehicles to be able to drive.
** A is used for slow offroad capable vehicles which aren't allowed on Motorways and similar Roads
** B is used for vehicles which can drive offroad but are also allowed on Motorways.
** C is used for vehicles which can't go offroad or similar.
** Use B if you aren't sure what to chose.
* Never use a or c.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Default labels [ROAD, ELRL] and non-standard labels
* Define a fallback type to the default labels via the road/tramtype table in case you want the vehicle to be available on the default roads/track if no matching set is loaded.
* Do the same for any non-standard labels that may be relevant.

Be as specific as you want when selecting the road/tramtype, it is the job of the road/track set to select a playable, reduced subset out of all possible type combinations.
=== Example of fallback order for vehicle sets ===
{| class="wikitable"
|- style="font-style:italic;"
! Unchanged label
! Fallback order
|-
| GACE (road)
| GACE -> PACE -> RACE -> (ROAD)
|-
| PAB4 (tram)
| PAB4 -> PAB3 -> PABG -> RAB4 -> RAB3 -> RABG
|-
| IAAG (road)
| IAAG -> RAAG
|-
| AACE (road)
| AACE -> RAAE -> (ELRD)
|-
| RABE (tram)
| RABE -> (ELRL)
|-
| PAAN (tram)
| PAAN -> RAAN -> (RAIL)
|}
== Forum topic ==
Feel free to discuss and ask questions about the scheme at the forum topic [https://www.tt-forums.net/viewtopic.php?t=90715 Here].

===Possible additions===
To be discussed in the forum topic...

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| X or x
| Multiple guidance systems or guages
| (Depends on intent; only two tramtype rail system combinations can exist for a given set of standardized labels - i.e. XABE and xABE - making it necessary to plan accordingly)

|}

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| I
| Induction-charge electrified
| Induction-charge electrified
| Z then E then G
|-
| i
| Eyecandy/Pipeline Infrastructure
| Eyecandy/Electric & Telecom Infrastructure
| I then Z then G then E
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| X
| N/A
| Multiple systems of electricity
| Use with surface X or x (e.g. XABX and xABX) or surface R (rail-based tramtype). For use only when at least one standardized label is an energy supply and multiple non-conflicting energy types are all at the same level, such as electrified, ground electrified and trackless tram overlap
|-
| x
| N/A
| Multiple systems of guidance, incompatible
| Use this with surface x (e.g. xABx) or the surface systems (e.g. SABx, RABx, MABx). For use when tramtypes are at different heights but all are fundamentally incompatible (i.e. suspended monorail, tram and pneumatic metro)
|-
| 0-2 & 5-9
| N/A
| Multiple systems of guidance, mix of compatible/incompatible
| For use when tramtypes are a mix of compatible and fundamentally incompatible (i.e. electrified, ground electrified, trackless tram, suspended monorail, tram and pneumatic metro); Do not set powered_railtype_list for these, instead use alternative_railtype_list, or define these in another label's powered_railtype_list (i.e. XAB0/XAB1/XAB2/XAB5/.../XAB9 for XABE/XABX and RAB0/RAB1/RAB2/RAB5/.../RAB9 for RABN/RABE/RABX).
|}

Standardized Roadtype Scheme

2023-11-09T15:24:51Z

Revenge of kiothedev: /* Energy [***X] */

This scheme was originally conceived in order to decrease the amount of neccesary hidden road and tramtrack types. This is done by standardising which labels vehicles and infrastructure should use. The standard also allows for more gameplay depth by having the option to limit vehicles to certain types of roads. It does similarly to the railtype scheme allow mixing of any vehicle set with any infrastructure set. It does however not allow multible infrastructure sets to be used at the same time. It does not prevent it but all of the sets used have to be made to be used with each other, or use diffrent surfaces/types which don't conflict with each other. The standard sets no limit on how vehicle sets can be used.

It is ultimately up to the infrastructure set to chose what roadtypes are avaliable and thereby what vehicles are avaliable. Infrastructure and vehicles can both be in the same set, it is however recommended to be able to dissable the infrastructure with parameters in case the player wants to use a different set for their infrastucture.

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Regular Road
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
| E
|
|-
| p
| Pump/Pipeline
| p
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Regular Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
| E
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not. This means that road/tramtrack sets shouldn't add these to their [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] and [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]]

It is up to the track set to implement all powered roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A".

Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| N
| None
| None
|
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|
|-
| G
| Ground electrified
| Ground electrified
|
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
| E or G
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|}
A tramtrack set that only uses specialized types, should map the generic types to the most suitable specialized type in the set with the help of the [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

=== The default labels (ROAD, ELRL) and non-standard labels===
OpenTTD will allways define ROAD and ELRL incase there are vehicles for them. It is therefore recomended to have these present in the set so that you can map them to appropriete labels from the standard. There are a few ways of doing this:
*Replacing one of the standardised types with the default label and putting the standardised label in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].
*Defining ROAD and/or ELRL separately from the standardised labels and adding the standard ones to the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. The main advantage of this is that you can use a parameter to map ROAD and/or ELRL to the standardised labels. This allows the player to chose where there non standardised vehicles will be able to go.

Vehicle set authors might want to add the default labels and non-standard labels as a fallback. If not implemented for the defualt labels, their vehicles won't show up on the default roads and/or tracks, leading to countless bug reports from players. Non standard labels that might be worth adding fallbacks too are: ELRD, RAIL, HAUL and probably some more.

== Summary for Road/Tramtrack sets ==
This section summarizes the above for road/tramtrack sets.

; [X***] Surface / Type
* Chose which Surfaces and types you want in your set and give them the correct [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* If you only provide roads/tramtracks for one surface/type, consider leaving some free road/tramtypes so a player can load an additional set for some other type.
; [*X**] Speed / Feature
* Make sure class A is always available.
* Use B, C and so on if you have multible roads/tramtracks with the otherwise the same label.
; [**X*] Terrain / Stability
* Always define classes A through C for every road/tramtrack surface/type energy combination, either:
** Directly via a real road/tramtype definition;
** Indirectly via the alternate road/tramtype label list, [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; Default labels [ROAD, ELRL] and non-standard labels
* Always define the default labels when possible, instead of what would be the equivalent of the default label in this scheme.
* Map the equivalent labels from this scheme to the default labels using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* Map common non-standard labels to the most similar label in this scheme using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].

== Summary for vehicle sets ==
This section summarizes the above for vehicle sets.

; [X***] Surface / Type
* Use the surface / type class that matches the vehicle;
* Define a fallback type via the road/tramtype table in case you want the vehicle to be available on a different road or tramtrack if no matching road/tramtrack set is loaded.
** Specialized subtypes like "G" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "P" or "R").
; [*X**] Speed / Feature
* Always use class A for every vehicle.
; [**X*] Terrain / Stability
* Use A, B or C depending on where you want your vehicles to be able to drive.
** A is used for slow offroad capable vehicles which aren't allowed on Motorways and similar Roads
** B is used for vehicles which can drive offroad but are also allowed on Motorways.
** C is used for vehicles which can't go offroad or similar.
** Use B if you aren't sure what to chose.
* Never use a or c.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Default labels [ROAD, ELRL] and non-standard labels
* Define a fallback type to the default labels via the road/tramtype table in case you want the vehicle to be available on the default roads/track if no matching set is loaded.
* Do the same for any non-standard labels that may be relevant.

Be as specific as you want when selecting the road/tramtype, it is the job of the road/track set to select a playable, reduced subset out of all possible type combinations.
=== Example of fallback order for vehicle sets ===
{| class="wikitable"
|- style="font-style:italic;"
! Unchanged label
! Fallback order
|-
| GACE (road)
| GACE -> PACE -> RACE -> (ROAD)
|-
| PAB4 (tram)
| PAB4 -> PAB3 -> PABG -> RAB4 -> RAB3 -> RABG
|-
| IAAG (road)
| IAAG -> RAAG
|-
| AACE (road)
| AACE -> RAAE -> (ELRD)
|-
| RABE (tram)
| RABE -> (ELRL)
|-
| PAAN (tram)
| PAAN -> RAAN -> (RAIL)
|}
== Forum topic ==
Feel free to discuss and ask questions about the scheme at the forum topic [https://www.tt-forums.net/viewtopic.php?t=90715 Here].

===Possible additions===
To be discussed in the forum topic...

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| X or x
| Multiple guidance systems or guages
| (Depends on intent; only two tramtype rail system combinations can exist for a given set of standardized labels - i.e. XABE and xABE - making it necessary to plan accordingly)

|}

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| I
| Induction electrified
| Induction electrified
| Z then E then G
|-
| i
| Eyecandy/Pipeline Infrastructure
| Eyecandy/Electric & Telecom Infrastructure
| I then Z then G then E
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| X
| N/A
| Multiple systems of electricity
| Use with surface X or x (e.g. XABX and xABX) or surface R (rail-based tramtype). For use only when at least one standardized label is an energy supply and multiple non-conflicting energy types are all at the same level, such as electrified, ground electrified and trackless tram overlap
|-
| x
| N/A
| Multiple systems of guidance, incompatible
| Use this with surface x (e.g. xABx) or the surface systems (e.g. SABx, RABx, MABx). For use when tramtypes are at different heights but all are fundamentally incompatible (i.e. suspended monorail, tram and pneumatic metro)
|-
| 0-2 & 5-9
| N/A
| Multiple systems of guidance, mix of compatible/incompatible
| For use when tramtypes are a mix of compatible and fundamentally incompatible (i.e. electrified, ground electrified, trackless tram, suspended monorail, tram and pneumatic metro); Do not set powered_railtype_list for these, instead use alternative_railtype_list, or define these in another label's powered_railtype_list (i.e. XAB0/XAB1/XAB2/XAB5/.../XAB9 for XABE/XABX and RAB0/RAB1/RAB2/RAB5/.../RAB9 for RABN/RABE/RABX).
|}

Standardized Roadtype Scheme

2023-11-09T14:54:19Z

Revenge of kiothedev: /* Energy [***X] */

This scheme was originally conceived in order to decrease the amount of neccesary hidden road and tramtrack types. This is done by standardising which labels vehicles and infrastructure should use. The standard also allows for more gameplay depth by having the option to limit vehicles to certain types of roads. It does similarly to the railtype scheme allow mixing of any vehicle set with any infrastructure set. It does however not allow multible infrastructure sets to be used at the same time. It does not prevent it but all of the sets used have to be made to be used with each other, or use diffrent surfaces/types which don't conflict with each other. The standard sets no limit on how vehicle sets can be used.

It is ultimately up to the infrastructure set to chose what roadtypes are avaliable and thereby what vehicles are avaliable. Infrastructure and vehicles can both be in the same set, it is however recommended to be able to dissable the infrastructure with parameters in case the player wants to use a different set for their infrastucture.

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Regular Road
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
| E
|
|-
| p
| Pump/Pipeline
| p
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Regular Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
| E
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not. This means that road/tramtrack sets shouldn't add these to their [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] and [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]]

It is up to the track set to implement all powered roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A".

Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| N
| None
| None
|
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|
|-
| G
| Ground electrified
| Ground electrified
|
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
| E or G
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|}
A tramtrack set that only uses specialized types, should map the generic types to the most suitable specialized type in the set with the help of the [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

=== The default labels (ROAD, ELRL) and non-standard labels===
OpenTTD will allways define ROAD and ELRL incase there are vehicles for them. It is therefore recomended to have these present in the set so that you can map them to appropriete labels from the standard. There are a few ways of doing this:
*Replacing one of the standardised types with the default label and putting the standardised label in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].
*Defining ROAD and/or ELRL separately from the standardised labels and adding the standard ones to the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. The main advantage of this is that you can use a parameter to map ROAD and/or ELRL to the standardised labels. This allows the player to chose where there non standardised vehicles will be able to go.

Vehicle set authors might want to add the default labels and non-standard labels as a fallback. If not implemented for the defualt labels, their vehicles won't show up on the default roads and/or tracks, leading to countless bug reports from players. Non standard labels that might be worth adding fallbacks too are: ELRD, RAIL, HAUL and probably some more.

== Summary for Road/Tramtrack sets ==
This section summarizes the above for road/tramtrack sets.

; [X***] Surface / Type
* Chose which Surfaces and types you want in your set and give them the correct [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* If you only provide roads/tramtracks for one surface/type, consider leaving some free road/tramtypes so a player can load an additional set for some other type.
; [*X**] Speed / Feature
* Make sure class A is always available.
* Use B, C and so on if you have multible roads/tramtracks with the otherwise the same label.
; [**X*] Terrain / Stability
* Always define classes A through C for every road/tramtrack surface/type energy combination, either:
** Directly via a real road/tramtype definition;
** Indirectly via the alternate road/tramtype label list, [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; Default labels [ROAD, ELRL] and non-standard labels
* Always define the default labels when possible, instead of what would be the equivalent of the default label in this scheme.
* Map the equivalent labels from this scheme to the default labels using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* Map common non-standard labels to the most similar label in this scheme using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].

== Summary for vehicle sets ==
This section summarizes the above for vehicle sets.

; [X***] Surface / Type
* Use the surface / type class that matches the vehicle;
* Define a fallback type via the road/tramtype table in case you want the vehicle to be available on a different road or tramtrack if no matching road/tramtrack set is loaded.
** Specialized subtypes like "G" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "P" or "R").
; [*X**] Speed / Feature
* Always use class A for every vehicle.
; [**X*] Terrain / Stability
* Use A, B or C depending on where you want your vehicles to be able to drive.
** A is used for slow offroad capable vehicles which aren't allowed on Motorways and similar Roads
** B is used for vehicles which can drive offroad but are also allowed on Motorways.
** C is used for vehicles which can't go offroad or similar.
** Use B if you aren't sure what to chose.
* Never use a or c.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Default labels [ROAD, ELRL] and non-standard labels
* Define a fallback type to the default labels via the road/tramtype table in case you want the vehicle to be available on the default roads/track if no matching set is loaded.
* Do the same for any non-standard labels that may be relevant.

Be as specific as you want when selecting the road/tramtype, it is the job of the road/track set to select a playable, reduced subset out of all possible type combinations.
=== Example of fallback order for vehicle sets ===
{| class="wikitable"
|- style="font-style:italic;"
! Unchanged label
! Fallback order
|-
| GACE (road)
| GACE -> PACE -> RACE -> (ROAD)
|-
| PAB4 (tram)
| PAB4 -> PAB3 -> PABG -> RAB4 -> RAB3 -> RABG
|-
| IAAG (road)
| IAAG -> RAAG
|-
| AACE (road)
| AACE -> RAAE -> (ELRD)
|-
| RABE (tram)
| RABE -> (ELRL)
|-
| PAAN (tram)
| PAAN -> RAAN -> (RAIL)
|}
== Forum topic ==
Feel free to discuss and ask questions about the scheme at the forum topic [https://www.tt-forums.net/viewtopic.php?t=90715 Here].

===Possible additions===
To be discussed in the forum topic...

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| X or x
| Multiple guidance systems or guages
| (Depends on intent; only two tramtype rail system combinations can exist for a given set of standardized labels - i.e. XABE and xABE - making it necessary to plan accordingly)

|}

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| i
| Eyecandy/Pipeline Infrastructure
| Eyecandy/Electric & Telecom Infrastructure
| N/A
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| X
| N/A
| Multiple systems of electricity
| Use with surface X or x (e.g. XABX and xABX) or surface R (rail-based tramtype). For use only when at least one standardized label is an energy supply and multiple non-conflicting energy types are all at the same level, such as electrified, ground electrified and trackless tram overlap
|-
| x
| N/A
| Multiple systems of guidance, incompatible
| Use this with surface x (e.g. xABx) or the surface systems (e.g. SABx, RABx, MABx). For use when tramtypes are at different heights but all are fundamentally incompatible (i.e. suspended monorail, tram and pneumatic metro)
|-
| 0-2 & 5-9
| N/A
| Multiple systems of guidance, mix of compatible/incompatible
| For use when tramtypes are a mix of compatible and fundamentally incompatible (i.e. electrified, ground electrified, trackless tram, suspended monorail, tram and pneumatic metro); Do not set powered_railtype_list for these, instead use alternative_railtype_list, or define these in another label's powered_railtype_list (i.e. XAB0/XAB1/XAB2/XAB5/.../XAB9 for XABE/XABX and RAB0/RAB1/RAB2/RAB5/.../RAB9 for RABN/RABE/RABX).
|}

Standardized Roadtype Scheme

2023-11-09T14:49:03Z

Revenge of kiothedev: /* Energy [***X] */

This scheme was originally conceived in order to decrease the amount of neccesary hidden road and tramtrack types. This is done by standardising which labels vehicles and infrastructure should use. The standard also allows for more gameplay depth by having the option to limit vehicles to certain types of roads. It does similarly to the railtype scheme allow mixing of any vehicle set with any infrastructure set. It does however not allow multible infrastructure sets to be used at the same time. It does not prevent it but all of the sets used have to be made to be used with each other, or use diffrent surfaces/types which don't conflict with each other. The standard sets no limit on how vehicle sets can be used.

It is ultimately up to the infrastructure set to chose what roadtypes are avaliable and thereby what vehicles are avaliable. Infrastructure and vehicles can both be in the same set, it is however recommended to be able to dissable the infrastructure with parameters in case the player wants to use a different set for their infrastucture.

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Regular Road
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
| E
|
|-
| p
| Pump/Pipeline
| p
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Regular Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
| E
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not. This means that road/tramtrack sets shouldn't add these to their [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] and [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]]

It is up to the track set to implement all powered roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A".

Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| N
| None
| None
|
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|
|-
| G
| Ground electrified
| Ground electrified
|
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
| E or G
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|}
A tramtrack set that only uses specialized types, should map the generic types to the most suitable specialized type in the set with the help of the [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

=== The default labels (ROAD, ELRL) and non-standard labels===
OpenTTD will allways define ROAD and ELRL incase there are vehicles for them. It is therefore recomended to have these present in the set so that you can map them to appropriete labels from the standard. There are a few ways of doing this:
*Replacing one of the standardised types with the default label and putting the standardised label in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].
*Defining ROAD and/or ELRL separately from the standardised labels and adding the standard ones to the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. The main advantage of this is that you can use a parameter to map ROAD and/or ELRL to the standardised labels. This allows the player to chose where there non standardised vehicles will be able to go.

Vehicle set authors might want to add the default labels and non-standard labels as a fallback. If not implemented for the defualt labels, their vehicles won't show up on the default roads and/or tracks, leading to countless bug reports from players. Non standard labels that might be worth adding fallbacks too are: ELRD, RAIL, HAUL and probably some more.

== Summary for Road/Tramtrack sets ==
This section summarizes the above for road/tramtrack sets.

; [X***] Surface / Type
* Chose which Surfaces and types you want in your set and give them the correct [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* If you only provide roads/tramtracks for one surface/type, consider leaving some free road/tramtypes so a player can load an additional set for some other type.
; [*X**] Speed / Feature
* Make sure class A is always available.
* Use B, C and so on if you have multible roads/tramtracks with the otherwise the same label.
; [**X*] Terrain / Stability
* Always define classes A through C for every road/tramtrack surface/type energy combination, either:
** Directly via a real road/tramtype definition;
** Indirectly via the alternate road/tramtype label list, [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; Default labels [ROAD, ELRL] and non-standard labels
* Always define the default labels when possible, instead of what would be the equivalent of the default label in this scheme.
* Map the equivalent labels from this scheme to the default labels using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* Map common non-standard labels to the most similar label in this scheme using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].

== Summary for vehicle sets ==
This section summarizes the above for vehicle sets.

; [X***] Surface / Type
* Use the surface / type class that matches the vehicle;
* Define a fallback type via the road/tramtype table in case you want the vehicle to be available on a different road or tramtrack if no matching road/tramtrack set is loaded.
** Specialized subtypes like "G" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "P" or "R").
; [*X**] Speed / Feature
* Always use class A for every vehicle.
; [**X*] Terrain / Stability
* Use A, B or C depending on where you want your vehicles to be able to drive.
** A is used for slow offroad capable vehicles which aren't allowed on Motorways and similar Roads
** B is used for vehicles which can drive offroad but are also allowed on Motorways.
** C is used for vehicles which can't go offroad or similar.
** Use B if you aren't sure what to chose.
* Never use a or c.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Default labels [ROAD, ELRL] and non-standard labels
* Define a fallback type to the default labels via the road/tramtype table in case you want the vehicle to be available on the default roads/track if no matching set is loaded.
* Do the same for any non-standard labels that may be relevant.

Be as specific as you want when selecting the road/tramtype, it is the job of the road/track set to select a playable, reduced subset out of all possible type combinations.
=== Example of fallback order for vehicle sets ===
{| class="wikitable"
|- style="font-style:italic;"
! Unchanged label
! Fallback order
|-
| GACE (road)
| GACE -> PACE -> RACE -> (ROAD)
|-
| PAB4 (tram)
| PAB4 -> PAB3 -> PABG -> RAB4 -> RAB3 -> RABG
|-
| IAAG (road)
| IAAG -> RAAG
|-
| AACE (road)
| AACE -> RAAE -> (ELRD)
|-
| RABE (tram)
| RABE -> (ELRL)
|-
| PAAN (tram)
| PAAN -> RAAN -> (RAIL)
|}
== Forum topic ==
Feel free to discuss and ask questions about the scheme at the forum topic [https://www.tt-forums.net/viewtopic.php?t=90715 Here].

===Possible additions===
To be discussed in the forum topic...

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| X or x
| Multiple guidance systems or guages
| (Depends on intent; only two tramtype rail system combinations can exist for a given set of standardized labels - i.e. XABE and xABE - making it necessary to plan accordingly)

|}

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| i
| Eyecandy/Pipeline Infrastructure
| Eyecandy/Electric & Telecom Infrastructure
| N/A
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| X
| N/A
| Multiple systems of electricity
| Use with surface X or x (e.g. XABX and xABX) or surface R (rail-based tramtype). For use only when at least one standardized label is an energy supply and multiple non-conflicting energy types are all at the same level, such as electrified, ground electrified and trackless tram overlap
|-
| x
| N/A
| Multiple systems of guidance, incompatible
| Use with surface X or x (e.g. XABx and xABx). For use when tramtypes are at different heights but all are fundamentally incompatible (i.e. suspended monorail, tram and pneumatic metro)
|-
| 0-2 & 5-9
| N/A
| Multiple systems of guidance, mix of compatible/incompatible
| For use when tramtypes are a mix of compatible and fundamentally incompatible (i.e. electrified, ground electrified, trackless tram, suspended monorail, tram and pneumatic metro); Do not set powered_railtype_list for these, instead use alternative_railtype_list, or define these in another label's powered_railtype_list (i.e. XAB0/XAB1/XAB2/XAB5/.../XAB9 for XABE/XABX and RAB0/RAB1/RAB2/RAB5/.../RAB9 for RABN/RABE/RABX).
|}

Standardized Roadtype Scheme

2023-11-09T14:18:24Z

Revenge of kiothedev: /* Energy [***X] */

This scheme was originally conceived in order to decrease the amount of neccesary hidden road and tramtrack types. This is done by standardising which labels vehicles and infrastructure should use. The standard also allows for more gameplay depth by having the option to limit vehicles to certain types of roads. It does similarly to the railtype scheme allow mixing of any vehicle set with any infrastructure set. It does however not allow multible infrastructure sets to be used at the same time. It does not prevent it but all of the sets used have to be made to be used with each other, or use diffrent surfaces/types which don't conflict with each other. The standard sets no limit on how vehicle sets can be used.

It is ultimately up to the infrastructure set to chose what roadtypes are avaliable and thereby what vehicles are avaliable. Infrastructure and vehicles can both be in the same set, it is however recommended to be able to dissable the infrastructure with parameters in case the player wants to use a different set for their infrastucture.

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Regular Road
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
| E
|
|-
| p
| Pump/Pipeline
| p
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Regular Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
| E
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not. This means that road/tramtrack sets shouldn't add these to their [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] and [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]]

It is up to the track set to implement all powered roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A".

Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| N
| None
| None
|
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|
|-
| G
| Ground electrified
| Ground electrified
|
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
| E or G
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|}
A tramtrack set that only uses specialized types, should map the generic types to the most suitable specialized type in the set with the help of the [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

=== The default labels (ROAD, ELRL) and non-standard labels===
OpenTTD will allways define ROAD and ELRL incase there are vehicles for them. It is therefore recomended to have these present in the set so that you can map them to appropriete labels from the standard. There are a few ways of doing this:
*Replacing one of the standardised types with the default label and putting the standardised label in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].
*Defining ROAD and/or ELRL separately from the standardised labels and adding the standard ones to the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. The main advantage of this is that you can use a parameter to map ROAD and/or ELRL to the standardised labels. This allows the player to chose where there non standardised vehicles will be able to go.

Vehicle set authors might want to add the default labels and non-standard labels as a fallback. If not implemented for the defualt labels, their vehicles won't show up on the default roads and/or tracks, leading to countless bug reports from players. Non standard labels that might be worth adding fallbacks too are: ELRD, RAIL, HAUL and probably some more.

== Summary for Road/Tramtrack sets ==
This section summarizes the above for road/tramtrack sets.

; [X***] Surface / Type
* Chose which Surfaces and types you want in your set and give them the correct [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* If you only provide roads/tramtracks for one surface/type, consider leaving some free road/tramtypes so a player can load an additional set for some other type.
; [*X**] Speed / Feature
* Make sure class A is always available.
* Use B, C and so on if you have multible roads/tramtracks with the otherwise the same label.
; [**X*] Terrain / Stability
* Always define classes A through C for every road/tramtrack surface/type energy combination, either:
** Directly via a real road/tramtype definition;
** Indirectly via the alternate road/tramtype label list, [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; Default labels [ROAD, ELRL] and non-standard labels
* Always define the default labels when possible, instead of what would be the equivalent of the default label in this scheme.
* Map the equivalent labels from this scheme to the default labels using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* Map common non-standard labels to the most similar label in this scheme using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].

== Summary for vehicle sets ==
This section summarizes the above for vehicle sets.

; [X***] Surface / Type
* Use the surface / type class that matches the vehicle;
* Define a fallback type via the road/tramtype table in case you want the vehicle to be available on a different road or tramtrack if no matching road/tramtrack set is loaded.
** Specialized subtypes like "G" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "P" or "R").
; [*X**] Speed / Feature
* Always use class A for every vehicle.
; [**X*] Terrain / Stability
* Use A, B or C depending on where you want your vehicles to be able to drive.
** A is used for slow offroad capable vehicles which aren't allowed on Motorways and similar Roads
** B is used for vehicles which can drive offroad but are also allowed on Motorways.
** C is used for vehicles which can't go offroad or similar.
** Use B if you aren't sure what to chose.
* Never use a or c.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Default labels [ROAD, ELRL] and non-standard labels
* Define a fallback type to the default labels via the road/tramtype table in case you want the vehicle to be available on the default roads/track if no matching set is loaded.
* Do the same for any non-standard labels that may be relevant.

Be as specific as you want when selecting the road/tramtype, it is the job of the road/track set to select a playable, reduced subset out of all possible type combinations.
=== Example of fallback order for vehicle sets ===
{| class="wikitable"
|- style="font-style:italic;"
! Unchanged label
! Fallback order
|-
| GACE (road)
| GACE -> PACE -> RACE -> (ROAD)
|-
| PAB4 (tram)
| PAB4 -> PAB3 -> PABG -> RAB4 -> RAB3 -> RABG
|-
| IAAG (road)
| IAAG -> RAAG
|-
| AACE (road)
| AACE -> RAAE -> (ELRD)
|-
| RABE (tram)
| RABE -> (ELRL)
|-
| PAAN (tram)
| PAAN -> RAAN -> (RAIL)
|}
== Forum topic ==
Feel free to discuss and ask questions about the scheme at the forum topic [https://www.tt-forums.net/viewtopic.php?t=90715 Here].

===Possible additions===
To be discussed in the forum topic...

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| X or x
| Multiple guidance systems or guages
| (Depends on intent; only two tramtype rail system combinations can exist for a given set of standardized labels - i.e. XABE and xABE - making it necessary to plan accordingly)

|}

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| i
| Eyecandy/Pipeline Infrastructure
| Eyecandy/Electric & Telecom Infrastructure
| N/A
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| X
| N/A
| Multiple systems of electricity
| For use only when energy supply is universal and multiple types are at the same level, such as electrified, ground, trackless tram overlap
|-
| x
| N/A
| Multiple systems of guidance, incompatible
| For use when tramtypes are at different heights but all are fundamentally incompatible (i.e. suspended monorail, tram and pneumatic metro)
|}

Standardized Roadtype Scheme

2023-11-09T14:11:55Z

Revenge of kiothedev: /* Surface / Type [X***] */

This scheme was originally conceived in order to decrease the amount of neccesary hidden road and tramtrack types. This is done by standardising which labels vehicles and infrastructure should use. The standard also allows for more gameplay depth by having the option to limit vehicles to certain types of roads. It does similarly to the railtype scheme allow mixing of any vehicle set with any infrastructure set. It does however not allow multible infrastructure sets to be used at the same time. It does not prevent it but all of the sets used have to be made to be used with each other, or use diffrent surfaces/types which don't conflict with each other. The standard sets no limit on how vehicle sets can be used.

It is ultimately up to the infrastructure set to chose what roadtypes are avaliable and thereby what vehicles are avaliable. Infrastructure and vehicles can both be in the same set, it is however recommended to be able to dissable the infrastructure with parameters in case the player wants to use a different set for their infrastucture.

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Regular Road
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
| E
|
|-
| p
| Pump/Pipeline
| p
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Regular Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
| E
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not. This means that road/tramtrack sets shouldn't add these to their [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] and [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]]

It is up to the track set to implement all powered roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A".

Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| N
| None
| None
|
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|
|-
| G
| Ground electrified
| Ground electrified
|
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
| E or G
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|}
A tramtrack set that only uses specialized types, should map the generic types to the most suitable specialized type in the set with the help of the [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

=== The default labels (ROAD, ELRL) and non-standard labels===
OpenTTD will allways define ROAD and ELRL incase there are vehicles for them. It is therefore recomended to have these present in the set so that you can map them to appropriete labels from the standard. There are a few ways of doing this:
*Replacing one of the standardised types with the default label and putting the standardised label in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].
*Defining ROAD and/or ELRL separately from the standardised labels and adding the standard ones to the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. The main advantage of this is that you can use a parameter to map ROAD and/or ELRL to the standardised labels. This allows the player to chose where there non standardised vehicles will be able to go.

Vehicle set authors might want to add the default labels and non-standard labels as a fallback. If not implemented for the defualt labels, their vehicles won't show up on the default roads and/or tracks, leading to countless bug reports from players. Non standard labels that might be worth adding fallbacks too are: ELRD, RAIL, HAUL and probably some more.

== Summary for Road/Tramtrack sets ==
This section summarizes the above for road/tramtrack sets.

; [X***] Surface / Type
* Chose which Surfaces and types you want in your set and give them the correct [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* If you only provide roads/tramtracks for one surface/type, consider leaving some free road/tramtypes so a player can load an additional set for some other type.
; [*X**] Speed / Feature
* Make sure class A is always available.
* Use B, C and so on if you have multible roads/tramtracks with the otherwise the same label.
; [**X*] Terrain / Stability
* Always define classes A through C for every road/tramtrack surface/type energy combination, either:
** Directly via a real road/tramtype definition;
** Indirectly via the alternate road/tramtype label list, [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; Default labels [ROAD, ELRL] and non-standard labels
* Always define the default labels when possible, instead of what would be the equivalent of the default label in this scheme.
* Map the equivalent labels from this scheme to the default labels using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* Map common non-standard labels to the most similar label in this scheme using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].

== Summary for vehicle sets ==
This section summarizes the above for vehicle sets.

; [X***] Surface / Type
* Use the surface / type class that matches the vehicle;
* Define a fallback type via the road/tramtype table in case you want the vehicle to be available on a different road or tramtrack if no matching road/tramtrack set is loaded.
** Specialized subtypes like "G" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "P" or "R").
; [*X**] Speed / Feature
* Always use class A for every vehicle.
; [**X*] Terrain / Stability
* Use A, B or C depending on where you want your vehicles to be able to drive.
** A is used for slow offroad capable vehicles which aren't allowed on Motorways and similar Roads
** B is used for vehicles which can drive offroad but are also allowed on Motorways.
** C is used for vehicles which can't go offroad or similar.
** Use B if you aren't sure what to chose.
* Never use a or c.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Default labels [ROAD, ELRL] and non-standard labels
* Define a fallback type to the default labels via the road/tramtype table in case you want the vehicle to be available on the default roads/track if no matching set is loaded.
* Do the same for any non-standard labels that may be relevant.

Be as specific as you want when selecting the road/tramtype, it is the job of the road/track set to select a playable, reduced subset out of all possible type combinations.
=== Example of fallback order for vehicle sets ===
{| class="wikitable"
|- style="font-style:italic;"
! Unchanged label
! Fallback order
|-
| GACE (road)
| GACE -> PACE -> RACE -> (ROAD)
|-
| PAB4 (tram)
| PAB4 -> PAB3 -> PABG -> RAB4 -> RAB3 -> RABG
|-
| IAAG (road)
| IAAG -> RAAG
|-
| AACE (road)
| AACE -> RAAE -> (ELRD)
|-
| RABE (tram)
| RABE -> (ELRL)
|-
| PAAN (tram)
| PAAN -> RAAN -> (RAIL)
|}
== Forum topic ==
Feel free to discuss and ask questions about the scheme at the forum topic [https://www.tt-forums.net/viewtopic.php?t=90715 Here].

===Possible additions===
To be discussed in the forum topic...

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| X or x
| Multiple guidance systems or guages
| (Depends on intent; only two tramtype rail system combinations can exist for a given set of standardized labels - i.e. XABE and xABE - making it necessary to plan accordingly)

|}

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| i
| Eyecandy/Pipeline Infrastructure
| Eyecandy/Electric & Telecom Infrastructure
| N/A
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| x
| N/A
| Unelectrified, Multiple Systems
| For use when a standardized tramtype (such as tram rails) label (RABN) with no catenary graphics and one or more specialized, non-compatible tramtype with catenary (such as suspended monorail and pneumatic subway) label (MONO, VACT) overlap
|-
| X
| N/A
| Electrified, Multiple Systems
| For use when the default label (ELRL) or a standardized tramtype label (RABE, etc.) with catenary graphics and one or more specialized, non-compatible tramtype with catenary (such as suspended monorail and pneumatic subway) label (MONO, VACT) overlap
|}

Standardized Roadtype Scheme

2023-11-09T13:23:21Z

Revenge of kiothedev:

This scheme was originally conceived in order to decrease the amount of neccesary hidden road and tramtrack types. This is done by standardising which labels vehicles and infrastructure should use. The standard also allows for more gameplay depth by having the option to limit vehicles to certain types of roads. It does similarly to the railtype scheme allow mixing of any vehicle set with any infrastructure set. It does however not allow multible infrastructure sets to be used at the same time. It does not prevent it but all of the sets used have to be made to be used with each other, or use diffrent surfaces/types which don't conflict with each other. The standard sets no limit on how vehicle sets can be used.

It is ultimately up to the infrastructure set to chose what roadtypes are avaliable and thereby what vehicles are avaliable. Infrastructure and vehicles can both be in the same set, it is however recommended to be able to dissable the infrastructure with parameters in case the player wants to use a different set for their infrastucture.

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Regular Road
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
| E
|
|-
| p
| Pump/Pipeline
| p
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Regular Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
| E
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not. This means that road/tramtrack sets shouldn't add these to their [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] and [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]]

It is up to the track set to implement all powered roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A".

Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| N
| None
| None
|
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|
|-
| G
| Ground electrified
| Ground electrified
|
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
| E or G
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|}
A tramtrack set that only uses specialized types, should map the generic types to the most suitable specialized type in the set with the help of the [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

=== The default labels (ROAD, ELRL) and non-standard labels===
OpenTTD will allways define ROAD and ELRL incase there are vehicles for them. It is therefore recomended to have these present in the set so that you can map them to appropriete labels from the standard. There are a few ways of doing this:
*Replacing one of the standardised types with the default label and putting the standardised label in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].
*Defining ROAD and/or ELRL separately from the standardised labels and adding the standard ones to the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. The main advantage of this is that you can use a parameter to map ROAD and/or ELRL to the standardised labels. This allows the player to chose where there non standardised vehicles will be able to go.

Vehicle set authors might want to add the default labels and non-standard labels as a fallback. If not implemented for the defualt labels, their vehicles won't show up on the default roads and/or tracks, leading to countless bug reports from players. Non standard labels that might be worth adding fallbacks too are: ELRD, RAIL, HAUL and probably some more.

== Summary for Road/Tramtrack sets ==
This section summarizes the above for road/tramtrack sets.

; [X***] Surface / Type
* Chose which Surfaces and types you want in your set and give them the correct [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* If you only provide roads/tramtracks for one surface/type, consider leaving some free road/tramtypes so a player can load an additional set for some other type.
; [*X**] Speed / Feature
* Make sure class A is always available.
* Use B, C and so on if you have multible roads/tramtracks with the otherwise the same label.
; [**X*] Terrain / Stability
* Always define classes A through C for every road/tramtrack surface/type energy combination, either:
** Directly via a real road/tramtype definition;
** Indirectly via the alternate road/tramtype label list, [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
; Default labels [ROAD, ELRL] and non-standard labels
* Always define the default labels when possible, instead of what would be the equivalent of the default label in this scheme.
* Map the equivalent labels from this scheme to the default labels using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].
* Map common non-standard labels to the most similar label in this scheme using [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]] or [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]].

== Summary for vehicle sets ==
This section summarizes the above for vehicle sets.

; [X***] Surface / Type
* Use the surface / type class that matches the vehicle;
* Define a fallback type via the road/tramtype table in case you want the vehicle to be available on a different road or tramtrack if no matching road/tramtrack set is loaded.
** Specialized subtypes like "G" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "P" or "R").
; [*X**] Speed / Feature
* Always use class A for every vehicle.
; [**X*] Terrain / Stability
* Use A, B or C depending on where you want your vehicles to be able to drive.
** A is used for slow offroad capable vehicles which aren't allowed on Motorways and similar Roads
** B is used for vehicles which can drive offroad but are also allowed on Motorways.
** C is used for vehicles which can't go offroad or similar.
** Use B if you aren't sure what to chose.
* Never use a or c.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Default labels [ROAD, ELRL] and non-standard labels
* Define a fallback type to the default labels via the road/tramtype table in case you want the vehicle to be available on the default roads/track if no matching set is loaded.
* Do the same for any non-standard labels that may be relevant.

Be as specific as you want when selecting the road/tramtype, it is the job of the road/track set to select a playable, reduced subset out of all possible type combinations.
=== Example of fallback order for vehicle sets ===
{| class="wikitable"
|- style="font-style:italic;"
! Unchanged label
! Fallback order
|-
| GACE (road)
| GACE -> PACE -> RACE -> (ROAD)
|-
| PAB4 (tram)
| PAB4 -> PAB3 -> PABG -> RAB4 -> RAB3 -> RABG
|-
| IAAG (road)
| IAAG -> RAAG
|-
| AACE (road)
| AACE -> RAAE -> (ELRD)
|-
| RABE (tram)
| RABE -> (ELRL)
|-
| PAAN (tram)
| PAAN -> RAAN -> (RAIL)
|}
== Forum topic ==
Feel free to discuss and ask questions about the scheme at the forum topic [https://www.tt-forums.net/viewtopic.php?t=90715 Here].

===Possible additions===
To be discussed in the forum topic...

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| X or x
| Multiple Systems
| (Depends on intent; only two tramtype rail system combinations can exist for a given set of standardized labels - i.e. XABE and xABE - making it necessary to plan accordingly)

|}

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| i
| Eyecandy/Pipeline Infrastructure
| Eyecandy/Electric & Telecom Infrastructure
| N/A
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| x
| N/A
| Unelectrified, Multiple Systems
| For use when a standardized tramtype (such as tram rails) label (RABN) with no catenary graphics and one or more specialized, non-compatible tramtype with catenary (such as suspended monorail and pneumatic subway) label (MONO, VACT) overlap
|-
| X
| N/A
| Electrified, Multiple Systems
| For use when the default label (ELRL) or a standardized tramtype label (RABE, etc.) with catenary graphics and one or more specialized, non-compatible tramtype with catenary (such as suspended monorail and pneumatic subway) label (MONO, VACT) overlap
|}

Standardized Railtype Scheme

2023-10-10T06:08:31Z

Revenge of kiothedev: /* Possible additions */

This railtype label scheme aims to bring order to the uncontrolled growth of railtype labels. It groups the rail types into what matters from a technical perspective. The scheme provides a standardized way of defining railtype labels, based on track gauge and type, speed class, allowable axle weight and electrification type.

It is the explicit intent of this scheme to decouple track sets from vehicle sets to facilitate easy mixing. This way the player can select a track set of choice to go with a train set of choice. It allows the player to play with or without axle load classes, or with or without speed limit classes, simply by loading a track set that does or does not provide these features. In some cases it will also be possible to combine niche track sets, for instance a standard gauge track set with a narrow gauge and a metro track set.

== The Label Scheme ==
A railtype label consists of four characters. In this scheme, each position has a different purpose:
# Track gauge and type class (e.g. standard gauge rail, narrow gauge rail, monorail)
# Speed limit class
# Axle load class (maximum allowed axle weight for this track)
# Energy source type class

In the next sections, each of the four positions will be explained.

=== Track gauge and type class [X***] ===
The first position in the railtype label defines track gauge and/or track type class. The following classes are currently defined:

{|
! !!Track type/gauge
|-
|S ||Standard gauge rail
|-
|B ||Broad gauge rail
|-
|N ||Narrow gauge rail
|-
|n ||Secondary narrow gauge rail (e.g. when providing both metre and cape gauge, always use N in case of just one type of narrow gauge)
|-
|D ||Dual gauge rail, standard/broad gauge
|-
|d ||Dual gauge rail, standard/narrow gauge
|-
|M ||Monorail
|-
|L ||Magnetic Levitation
|}

=== Speed limit class [*X**] ===
The second position in the railtype label defines the speed limit class. These classes do not map to a fixed numeric value, but are used to define an internal speed limit order for the track set. This means that if your track set has two different speed limits for track types that are otherwise identical, you'll use letters A and B here. In case of three different speed limits, use A, B and C. In case your track set does not employ speed limits, always use A. Train sets do not care about the speed limit, and will always set the lowest speed class, i.e. A.

This gives for instance the following options:

<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||no speed limits
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||high speed
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||medium speed
|-
|C ||high speed
|}
</div>
<div style="float:left;">
 etc. 
</div>
</div>
<div style="clear:left;"></div>

The speed limit class may also be used for some advanced features of the label scheme, like specialized track types and eyecandy purposes. Be careful not to break the compatibility with other sets when using the speed limit class for these purposes.

An example of a special use is rack rail. In the French set it is used to give rack rail engines a higher speed and TE than normal rail engines when used on rack rail. When defining trains with a special speed limit class, always allow a fallback to speed limit class A via the railtype table.

An example of eyecandy use are urban tracks. These are a variation of regular tracks, but with concrete ground tiles to better match the urban environment. Train sets must not define vehicles for eyecandy classes. If you think you have special vehicles that should only run on the eyecandy class, it is ''not'' eyecandy but a separate track gauge/type.

The following special and eyecandy classes have been defined so far:

{|
! !!Description !!Type !!Used by
|-
|A-H ||speed limits ||colspan="2"|reserved
|-
|R ||rack rail ||special ||French Set Rails
|-
|S ||subterranean ||eyecandy ||Metro Track Set
|-
|U ||urban ||eyecandy ||Metro Track Set
|-
|g ||ground tile for 45° angles ||eyecandy ||(none yet)
|}

=== Axle load class [**X*] ===
The third position defines the axle weight limit. Heavy trains cannot run on tracks with a low axle weight limit; these trains need more expensive tracks with a heigher weight limit. There are five axle load classes '''A''' through '''E'''. '''A''' is for the lowest axle load limit, '''E''' for the highest. The exact axle load attached to each class is relative to the track gauge/type and trains in the set.

A train set should set the appropriate axle weight for each train via the railtype label, as to make the set work with track sets that do provide tracks with different weight limits, even if you don't care about it for your trainset. Split all vehicles of a certain track gauge/type into five groups of similar axle weight. The group with the lowest axle weights will get class '''A''', the second lowest class '''B''', etc. up to the group with the highest axle weights which will get class '''E'''. Do the same for the other track gauge/types if your train set has those.

A track set does not have to provide a dedicated track type for each axle weight limit. A track set that does not provide a dedicated track for each axle load class, must make sure to map all undefined axle load classes to a real railtype using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]]. This way a train set can rely on all labels for all axle load classes being available. Example: if you only want to provide 2 axle load classes for standard gauge unelectrified with no speed limits, you can map SA'''A'''N + SA'''B'''N to SA'''C'''N and SA'''D'''N to SA'''E'''N if the cost difference between the two railtypes is high, or SA'''A'''N to SA'''B'''N and SA'''C'''N + SA'''D'''N to SA'''E'''N if the cost difference is low.

If you don't want to provide any axle load classes in your track set, it doesn't really matter what axle load class you choose for the track, as you'll be mapping all other classes to this track anyways. But the lowest or highest class are the obvious choice. Example: if your track set only provides narrow gauge unelectrified track with no speed limits and no axle load limits, you may use NA'''A'''N for the track label, and provide NA'''B'''N, NA'''C'''N, NA'''D'''N, NA'''E'''N in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

If you need more than five axle load class, you may use lowercase letters for very low axle loads and continue the uppercase letters for very high axle loads. Be advised that your train set may not assume the existance of any other class than '''A''' through '''E''', so when the range make sure to program your railtype table such that trains with such a class will fall back to class '''A''' or '''E'''. If you make a track set with an extended range, be aware that not all train sets will define trains for these tracks. In general: only do this in case of a train set with a matching track set.

For the lowercase letters, '''b''' is lower than '''a''', so for increasing axle load limits: b < a < A < B < C etc.

Note that the axle load classes never map to a specific weight in tonnes. For that reason it does not make sense to add a numeric value for the axle load to the name of a track type or in the extended purchase info of a train. Instead use the relative expressions 'very low', 'low', 'medium', 'high' and 'very high' or use the class letters directly.

=== Energy source type class [***X] ===
The last position defines the energy source type class. This is split in generic energy source types like overhead wires and third rail and specialized types like alternating and direct current.

A track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

A vehicle set that uses specialized types should define a generic type as fallback, via the railtype table. If such a fallback is omitted, please note that certain vehicles may be unavailable depending on track set loaded.

{|
! !!Generic energy type classes
|-
|N ||no electrification
|-
|E ||overhead wires/catenary electrification
|-
|3 ||3rd rail electrification
|}

{|
! !!Specialized energy type classes !!Vehicle set fallback
|-
|Z ||3rd rail and catenary electrification || 3 or E
|-
|4 ||4th rail electrification || 3
|-
|Y ||4th rail and catenary electrification || 4 or E
|-
|T ||[http://en.wikipedia.org/wiki/Three-phase_AC_railway_electrification three phase AC electrification] || E
|-
| colspan="3" |  
|-
|D ||DC catenary electrification || E
|-
|d ||low voltage DC catenary electrification (only when D also used in set) || First A then E
|-
|A ||AC catenary electrification || E
|-
|a ||low voltage AC catenary electrification (only when A also used in set) || First A then E
|}

If you want multi-voltage/current vehicles in your set (i.e. a train that can run on both AC and DC current), you have to define a dedicated railtype for those vehicles. Without the railtype, it's not possible to define vehicles with this property. If you only have vehicles that can run on either one type of voltage/current or on all types of voltage/current (e.g. a 2-system if you only have '''A''' and '''D''' tracks, or a 4-system in case of all '''A''', '''a''', '''D''' and '''d'''), then use the generic class '''E''' for vehicles that should be able to run on all different voltage/currents. Also the track set needs to have one at least one railtype with class '''E''' defined.

Note that if you want more than one type of multi-voltage/current, you'll quickly get a combinatory explosion of railtype labels, so plan carefully or do not attempt it. For every different multi-voltage/current vehicle type a dedicated railtype is needed. If you want all possible combinations, then you need to define an additional 8 classes. It is not recommended to make your train/track set this complicated.

Example approach for a 4-system set, with trains that can run on either one or all systems:
* '''E''': generic catenary-powered electric engines. "universal" [4-system] if any of '''D'''/'''d'''/'''A'''/'''a''' are defined.
* '''A''': generic AC catenary electric engines. 25kV only if '''a''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''A''';
* '''a''': 15kV AC catenary electric engines. Only defined if '''A''' also defined. Vehicle sets should use '''A''' and '''E''' as fallback, if defining an engine for '''a''';
* '''D''': generic DC catenary electric engines. 3kV if '''d''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''D''';
* '''d''': 1.5kV DC catenary electric engines. Only defined if '''D''' also defined. Vehicle sets should use '''D''' and '''E''' as fallback, if defining an engine for '''d'''.
For a 2-system set, you can simply drop '''a''' and '''d'''.

=== Standard labels: RAIL, ELRL, MONO, MGLV ===
It's not possible to undefine the standard railtypes RAIL, ELRL, MONO and MGLV. The game will always add those if there are vehicles defined for these track types. As a result, for a track set it's best not to ignore those standard labels, but rather work with them and define them in the set. If your track set does not have monorail or maglev tracks, there of course is no need to define those. But if your track set defines anything that resembles unelectrified or electrified rail, you should use the RAIL and ELRL labels. Matching labels from the above scheme will then be defined in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

As vehicles from NewGRFs that do not use explicit railtypes will end up on these standard railtypes, you should use RAIL instead of whatever type could be regarded as the most commonly used unelectrified type, ELRL instead of the most commonly used electrified type and so on. The label according to this scheme is then set as an alternate.

== Summary for track sets ==
This section summarizes the above for track sets.

; [X***] Track gauge and type class
* Define at least one track type for every track gauge/type class you want in your set.
* If you only provide tracks for one gauge/type, consider leaving some free railtypes so a player can load an additional set for some other type.
; [*X**] Speed limit class
* Make sure class A is always available, either directly or via an alternate label.
* Use only class A if you don't want speed limits;
* With speed limits, A is the lowest speed limit. Continue with B, C, etc. for increasing speed limits;
* The speed class can also be used to implement additional eye-candy track types, use letters higher in the alphabet for this.
; [**X*] Axle load class
* Always define all classes A through E for every track type class / electrification combination, either:
** Directly via a real railtype definition;
** Indirectly via the alternate rail type label list, property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].
* Extend the predefined classes only if you also provide a train set that makes use of these.
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via property 1D.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Always define the standard labels when possible, instead of what would be the equivalent of the standard label in this scheme.
* Map the equivalent labels from this scheme to the standard labels using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

Or, put differently, for each gauge/type, select one or more energy source types. For each type/energy combination provide all axle load classes for the speed class "A", either as a real type or as an alternate of another type. Provide more types with a different speed letter if you want to provide several different speeds or other eye-candy tracks.

== Summary for train sets ==
This section summarizes the above for train sets.

; [X***] Track gauge and type class
* Use the track type class that matches the vehicle;
* Define a fallback type via the railtype table in case you want the vehicle to be available on a different track if no matching track set is loaded.
** Specialized subtypes like "n" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "N").
; [*X**] Speed limit class
* Always use class A for every vehicle.
; [**X*] Axle load class
* Use all classes A through E according to the maximum axle weight of the vehicle.
* Extend the predefined classes only if you also provide a track set that makes use of these;
** When extending the predefined classes A through E, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Define a fallback type to the standard labels via the railtype table in case you want the vehicle to be available on the standard tracks if no matching track set is loaded.

Be as specific as you want when selecting the railtype, it is the job of the track set to select a playable, reduced subset out of all possible type combinations.

== In case you're not convinced by this scheme ==
Adopting this scheme gives the player freedom to use any track set in combination with any train set that follow the scheme.

This means that you can make your train set compatible with track sets that provide axle load classes, and track sets that provide speed limits, and at the same time with track sets that provide none of this. This way, the player can decide to play with or without axle load classes, or with or without speed limits, simply by loading a track set that does or does not provide these features.

And for your track set, it means that you can make it as simple or as complicated as you want (within the 64 track type limit), while not having to worry about compatibility with train sets.

Still not convinced? Feel free to use railtype labels of your own, but know that you will likely come to regret that at some point in the future.

==Forum topic==
If you want to discuss the standardized railtype scheme or have any questions about it, you can visit [http://www.tt-forums.net/viewtopic.php?t=59379 the forum topic].

=="Innsbruck 2022 Convention" for partial compliance==

This is really esoteric, but eh. It was the product of long discussion / debate / argument / reasoning between grf authors.

1. The Standardized Railtype Scheme '''is a useful tool''' for providing reliable compatibility between train grfs and railtype grfs.

2. The '''axle load class''' in the scheme presents a number of issues for compliance.

2.1. Over 10 years since the scheme was standardised, not many train grfs implement multiple axle load classes '''as required by the scheme'''. Known examples that '''do''' comply include Dutch Train Set, French Narrow Gauge Trains, and Finnish Trains.

2.2. Elements of the axle load rules have proven hard to interpret. For example:

* is it compliant to use ''fewer'' than 5 classes in a train grf? There is a lack of consensus on this.
* axle load is only one of many factors that govern whether a vehicle is compatible with a route, for example loading gauge, minimum curve, signalling types etc

2.3. Meanwhile ''multiple existing train grfs use class ''A'' for the axle load for all trains'' (except where relying on default railtypes such as RAIL and ELRL).

'''3. The Innsbruck 2022 Convention uses class ''A'' for axle load for '''all''' trains in a train grf (except where relying on default railtypes such as RAIL and ELRL).'''

This is '''not''' fully compliant with the Standardized Railtype Scheme and does not claim to be.

However train grfs using the Innsbruck 2022 Convention are ''broadly compatible'' with railtype grfs using the Standardized Railtype Scheme.

Obligatory XKCD link about 'standards': https://xkcd.com/927/

===Known issues===

Known problems are that trains using only class 'A' may limit the ability of railtype grf authors to achieve their design goals for separating railtypes by axle load.
But on reflection, it can be seen that a train grf might not be able to provide a broad enough range of vehicles to cover at least 5 axle load classes.

3.1. The Innsbruck 2022 Convention is '''not''' appropriate for train grf authors who wish to provide more than one axle load class.

3.2. The Innsbruck 2022 Convention treats the meaning of class ''A'' as ''undefined'', ''ignored'' or ''compatible with most restricted railtype'' for axle load.

Axle load class ''A'' '''cannot''' be safely interpreted as ''universal'' because from the perspective of a railtype grf ''A'' is ''most restricted railtype'', where ''universal'' is better represented as ''least restricted railtype''. Depending how many axle load classes are in use by the railtype grf, this could be class ''B'', ''C'', ''D'', ''E'' etc. To illustrate this issue, take the following scenario

* railtype grf defines axle loads ''A'' to ''E''. In this case the railtype grf author intends that ''A'' is compatible with the smallest range of vehicles, ''E'' is compatible with the largest range of vehicles, and ''B'', ''C'' and ''D'' are compatible with some intermediate ranges of vehicles
* but the vehicle grf author has defined all vehicles to be axle load ''A'' in an attempt to express this vehicle is ''universal''. The result in the game is that an identical range of vehicles will be compatible with railtypes ''A'' to ''E''.

This is clearly '''not''' the intended outcome of the railtype author. But nor is it clear within the spec that the vehicle author has particularly done anything wrong.

It ''would'' be possible to use railtype availability testing to adjust the vehicle property 05 (track_type) to fit the highest defined axle load (''E'' in this example case), but this is not insignificant work, and it's unlikely to be widely adopted by vehicle grf authors. Nor would this solution achieve ''universal'' as all vehicles in vehicle grf then would be incompatible with types ''A'' through ''D''.

3.3. When the Innsbruck 2022 Convention is used, this '''does not prevent''' a train grf being extended in some future release to achieve full compliance with Standardized Railtype Scheme. ''That choice remains with train grf authors''.

3.4. If 2012 could be revisited, providing an optional ''_'' axle load class in the Standardized Railtype Scheme for ''undefined'' would have been preferable, but as of 2022, ''A'' is already widely used for this purpose, and time travel is not known to be possible.

==Possible additions==

{|
! !!Track type/gauge
|-
|B ||Broad gauge rail (Also used by "ultra-broad" fictional tracktype; As broad gauge is a rare tracktype, it may still be feasible to cement B and b as broad gauges of two differing sizes)
|-
|b ||Broad gauge rail (Originally assigned to uppercase B; As broad gauge is a rare tracktype, it may still be feasible to cement B and b as broad gauges of two differing sizes)
|-
|s ||Multiple gauge rail, ultrabroad/broad/standard/narrow/secondary narrow gauge
|-
|0 ||(A number zero, not a letter "Oh") No track, eyecandy-use only
|}

It might be prefered to instead use keep "B" for current broad gauge and instead using lovercase "b" for the new ultra-broad gauge. This wouldn't be to different from narrow gauge since the lesser used ones are lowercase and fallback to the uppercase ones.

{|
! !!Electrification !!Fallback
|-
|t ||"Universal custom tunnel" (for electrified sub-surface rail tunnels) ||E (mandatory)
|}

Standardized Railtype Scheme

2023-10-10T05:37:38Z

Revenge of kiothedev: /* Possible additions */

This railtype label scheme aims to bring order to the uncontrolled growth of railtype labels. It groups the rail types into what matters from a technical perspective. The scheme provides a standardized way of defining railtype labels, based on track gauge and type, speed class, allowable axle weight and electrification type.

It is the explicit intent of this scheme to decouple track sets from vehicle sets to facilitate easy mixing. This way the player can select a track set of choice to go with a train set of choice. It allows the player to play with or without axle load classes, or with or without speed limit classes, simply by loading a track set that does or does not provide these features. In some cases it will also be possible to combine niche track sets, for instance a standard gauge track set with a narrow gauge and a metro track set.

== The Label Scheme ==
A railtype label consists of four characters. In this scheme, each position has a different purpose:
# Track gauge and type class (e.g. standard gauge rail, narrow gauge rail, monorail)
# Speed limit class
# Axle load class (maximum allowed axle weight for this track)
# Energy source type class

In the next sections, each of the four positions will be explained.

=== Track gauge and type class [X***] ===
The first position in the railtype label defines track gauge and/or track type class. The following classes are currently defined:

{|
! !!Track type/gauge
|-
|S ||Standard gauge rail
|-
|B ||Broad gauge rail
|-
|N ||Narrow gauge rail
|-
|n ||Secondary narrow gauge rail (e.g. when providing both metre and cape gauge, always use N in case of just one type of narrow gauge)
|-
|D ||Dual gauge rail, standard/broad gauge
|-
|d ||Dual gauge rail, standard/narrow gauge
|-
|M ||Monorail
|-
|L ||Magnetic Levitation
|}

=== Speed limit class [*X**] ===
The second position in the railtype label defines the speed limit class. These classes do not map to a fixed numeric value, but are used to define an internal speed limit order for the track set. This means that if your track set has two different speed limits for track types that are otherwise identical, you'll use letters A and B here. In case of three different speed limits, use A, B and C. In case your track set does not employ speed limits, always use A. Train sets do not care about the speed limit, and will always set the lowest speed class, i.e. A.

This gives for instance the following options:

<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||no speed limits
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||high speed
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||medium speed
|-
|C ||high speed
|}
</div>
<div style="float:left;">
 etc. 
</div>
</div>
<div style="clear:left;"></div>

The speed limit class may also be used for some advanced features of the label scheme, like specialized track types and eyecandy purposes. Be careful not to break the compatibility with other sets when using the speed limit class for these purposes.

An example of a special use is rack rail. In the French set it is used to give rack rail engines a higher speed and TE than normal rail engines when used on rack rail. When defining trains with a special speed limit class, always allow a fallback to speed limit class A via the railtype table.

An example of eyecandy use are urban tracks. These are a variation of regular tracks, but with concrete ground tiles to better match the urban environment. Train sets must not define vehicles for eyecandy classes. If you think you have special vehicles that should only run on the eyecandy class, it is ''not'' eyecandy but a separate track gauge/type.

The following special and eyecandy classes have been defined so far:

{|
! !!Description !!Type !!Used by
|-
|A-H ||speed limits ||colspan="2"|reserved
|-
|R ||rack rail ||special ||French Set Rails
|-
|S ||subterranean ||eyecandy ||Metro Track Set
|-
|U ||urban ||eyecandy ||Metro Track Set
|-
|g ||ground tile for 45° angles ||eyecandy ||(none yet)
|}

=== Axle load class [**X*] ===
The third position defines the axle weight limit. Heavy trains cannot run on tracks with a low axle weight limit; these trains need more expensive tracks with a heigher weight limit. There are five axle load classes '''A''' through '''E'''. '''A''' is for the lowest axle load limit, '''E''' for the highest. The exact axle load attached to each class is relative to the track gauge/type and trains in the set.

A train set should set the appropriate axle weight for each train via the railtype label, as to make the set work with track sets that do provide tracks with different weight limits, even if you don't care about it for your trainset. Split all vehicles of a certain track gauge/type into five groups of similar axle weight. The group with the lowest axle weights will get class '''A''', the second lowest class '''B''', etc. up to the group with the highest axle weights which will get class '''E'''. Do the same for the other track gauge/types if your train set has those.

A track set does not have to provide a dedicated track type for each axle weight limit. A track set that does not provide a dedicated track for each axle load class, must make sure to map all undefined axle load classes to a real railtype using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]]. This way a train set can rely on all labels for all axle load classes being available. Example: if you only want to provide 2 axle load classes for standard gauge unelectrified with no speed limits, you can map SA'''A'''N + SA'''B'''N to SA'''C'''N and SA'''D'''N to SA'''E'''N if the cost difference between the two railtypes is high, or SA'''A'''N to SA'''B'''N and SA'''C'''N + SA'''D'''N to SA'''E'''N if the cost difference is low.

If you don't want to provide any axle load classes in your track set, it doesn't really matter what axle load class you choose for the track, as you'll be mapping all other classes to this track anyways. But the lowest or highest class are the obvious choice. Example: if your track set only provides narrow gauge unelectrified track with no speed limits and no axle load limits, you may use NA'''A'''N for the track label, and provide NA'''B'''N, NA'''C'''N, NA'''D'''N, NA'''E'''N in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

If you need more than five axle load class, you may use lowercase letters for very low axle loads and continue the uppercase letters for very high axle loads. Be advised that your train set may not assume the existance of any other class than '''A''' through '''E''', so when the range make sure to program your railtype table such that trains with such a class will fall back to class '''A''' or '''E'''. If you make a track set with an extended range, be aware that not all train sets will define trains for these tracks. In general: only do this in case of a train set with a matching track set.

For the lowercase letters, '''b''' is lower than '''a''', so for increasing axle load limits: b < a < A < B < C etc.

Note that the axle load classes never map to a specific weight in tonnes. For that reason it does not make sense to add a numeric value for the axle load to the name of a track type or in the extended purchase info of a train. Instead use the relative expressions 'very low', 'low', 'medium', 'high' and 'very high' or use the class letters directly.

=== Energy source type class [***X] ===
The last position defines the energy source type class. This is split in generic energy source types like overhead wires and third rail and specialized types like alternating and direct current.

A track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

A vehicle set that uses specialized types should define a generic type as fallback, via the railtype table. If such a fallback is omitted, please note that certain vehicles may be unavailable depending on track set loaded.

{|
! !!Generic energy type classes
|-
|N ||no electrification
|-
|E ||overhead wires/catenary electrification
|-
|3 ||3rd rail electrification
|}

{|
! !!Specialized energy type classes !!Vehicle set fallback
|-
|Z ||3rd rail and catenary electrification || 3 or E
|-
|4 ||4th rail electrification || 3
|-
|Y ||4th rail and catenary electrification || 4 or E
|-
|T ||[http://en.wikipedia.org/wiki/Three-phase_AC_railway_electrification three phase AC electrification] || E
|-
| colspan="3" |  
|-
|D ||DC catenary electrification || E
|-
|d ||low voltage DC catenary electrification (only when D also used in set) || First A then E
|-
|A ||AC catenary electrification || E
|-
|a ||low voltage AC catenary electrification (only when A also used in set) || First A then E
|}

If you want multi-voltage/current vehicles in your set (i.e. a train that can run on both AC and DC current), you have to define a dedicated railtype for those vehicles. Without the railtype, it's not possible to define vehicles with this property. If you only have vehicles that can run on either one type of voltage/current or on all types of voltage/current (e.g. a 2-system if you only have '''A''' and '''D''' tracks, or a 4-system in case of all '''A''', '''a''', '''D''' and '''d'''), then use the generic class '''E''' for vehicles that should be able to run on all different voltage/currents. Also the track set needs to have one at least one railtype with class '''E''' defined.

Note that if you want more than one type of multi-voltage/current, you'll quickly get a combinatory explosion of railtype labels, so plan carefully or do not attempt it. For every different multi-voltage/current vehicle type a dedicated railtype is needed. If you want all possible combinations, then you need to define an additional 8 classes. It is not recommended to make your train/track set this complicated.

Example approach for a 4-system set, with trains that can run on either one or all systems:
* '''E''': generic catenary-powered electric engines. "universal" [4-system] if any of '''D'''/'''d'''/'''A'''/'''a''' are defined.
* '''A''': generic AC catenary electric engines. 25kV only if '''a''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''A''';
* '''a''': 15kV AC catenary electric engines. Only defined if '''A''' also defined. Vehicle sets should use '''A''' and '''E''' as fallback, if defining an engine for '''a''';
* '''D''': generic DC catenary electric engines. 3kV if '''d''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''D''';
* '''d''': 1.5kV DC catenary electric engines. Only defined if '''D''' also defined. Vehicle sets should use '''D''' and '''E''' as fallback, if defining an engine for '''d'''.
For a 2-system set, you can simply drop '''a''' and '''d'''.

=== Standard labels: RAIL, ELRL, MONO, MGLV ===
It's not possible to undefine the standard railtypes RAIL, ELRL, MONO and MGLV. The game will always add those if there are vehicles defined for these track types. As a result, for a track set it's best not to ignore those standard labels, but rather work with them and define them in the set. If your track set does not have monorail or maglev tracks, there of course is no need to define those. But if your track set defines anything that resembles unelectrified or electrified rail, you should use the RAIL and ELRL labels. Matching labels from the above scheme will then be defined in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

As vehicles from NewGRFs that do not use explicit railtypes will end up on these standard railtypes, you should use RAIL instead of whatever type could be regarded as the most commonly used unelectrified type, ELRL instead of the most commonly used electrified type and so on. The label according to this scheme is then set as an alternate.

== Summary for track sets ==
This section summarizes the above for track sets.

; [X***] Track gauge and type class
* Define at least one track type for every track gauge/type class you want in your set.
* If you only provide tracks for one gauge/type, consider leaving some free railtypes so a player can load an additional set for some other type.
; [*X**] Speed limit class
* Make sure class A is always available, either directly or via an alternate label.
* Use only class A if you don't want speed limits;
* With speed limits, A is the lowest speed limit. Continue with B, C, etc. for increasing speed limits;
* The speed class can also be used to implement additional eye-candy track types, use letters higher in the alphabet for this.
; [**X*] Axle load class
* Always define all classes A through E for every track type class / electrification combination, either:
** Directly via a real railtype definition;
** Indirectly via the alternate rail type label list, property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].
* Extend the predefined classes only if you also provide a train set that makes use of these.
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via property 1D.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Always define the standard labels when possible, instead of what would be the equivalent of the standard label in this scheme.
* Map the equivalent labels from this scheme to the standard labels using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

Or, put differently, for each gauge/type, select one or more energy source types. For each type/energy combination provide all axle load classes for the speed class "A", either as a real type or as an alternate of another type. Provide more types with a different speed letter if you want to provide several different speeds or other eye-candy tracks.

== Summary for train sets ==
This section summarizes the above for train sets.

; [X***] Track gauge and type class
* Use the track type class that matches the vehicle;
* Define a fallback type via the railtype table in case you want the vehicle to be available on a different track if no matching track set is loaded.
** Specialized subtypes like "n" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "N").
; [*X**] Speed limit class
* Always use class A for every vehicle.
; [**X*] Axle load class
* Use all classes A through E according to the maximum axle weight of the vehicle.
* Extend the predefined classes only if you also provide a track set that makes use of these;
** When extending the predefined classes A through E, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Define a fallback type to the standard labels via the railtype table in case you want the vehicle to be available on the standard tracks if no matching track set is loaded.

Be as specific as you want when selecting the railtype, it is the job of the track set to select a playable, reduced subset out of all possible type combinations.

== In case you're not convinced by this scheme ==
Adopting this scheme gives the player freedom to use any track set in combination with any train set that follow the scheme.

This means that you can make your train set compatible with track sets that provide axle load classes, and track sets that provide speed limits, and at the same time with track sets that provide none of this. This way, the player can decide to play with or without axle load classes, or with or without speed limits, simply by loading a track set that does or does not provide these features.

And for your track set, it means that you can make it as simple or as complicated as you want (within the 64 track type limit), while not having to worry about compatibility with train sets.

Still not convinced? Feel free to use railtype labels of your own, but know that you will likely come to regret that at some point in the future.

==Forum topic==
If you want to discuss the standardized railtype scheme or have any questions about it, you can visit [http://www.tt-forums.net/viewtopic.php?t=59379 the forum topic].

=="Innsbruck 2022 Convention" for partial compliance==

This is really esoteric, but eh. It was the product of long discussion / debate / argument / reasoning between grf authors.

1. The Standardized Railtype Scheme '''is a useful tool''' for providing reliable compatibility between train grfs and railtype grfs.

2. The '''axle load class''' in the scheme presents a number of issues for compliance.

2.1. Over 10 years since the scheme was standardised, not many train grfs implement multiple axle load classes '''as required by the scheme'''. Known examples that '''do''' comply include Dutch Train Set, French Narrow Gauge Trains, and Finnish Trains.

2.2. Elements of the axle load rules have proven hard to interpret. For example:

* is it compliant to use ''fewer'' than 5 classes in a train grf? There is a lack of consensus on this.
* axle load is only one of many factors that govern whether a vehicle is compatible with a route, for example loading gauge, minimum curve, signalling types etc

2.3. Meanwhile ''multiple existing train grfs use class ''A'' for the axle load for all trains'' (except where relying on default railtypes such as RAIL and ELRL).

'''3. The Innsbruck 2022 Convention uses class ''A'' for axle load for '''all''' trains in a train grf (except where relying on default railtypes such as RAIL and ELRL).'''

This is '''not''' fully compliant with the Standardized Railtype Scheme and does not claim to be.

However train grfs using the Innsbruck 2022 Convention are ''broadly compatible'' with railtype grfs using the Standardized Railtype Scheme.

Obligatory XKCD link about 'standards': https://xkcd.com/927/

===Known issues===

Known problems are that trains using only class 'A' may limit the ability of railtype grf authors to achieve their design goals for separating railtypes by axle load.
But on reflection, it can be seen that a train grf might not be able to provide a broad enough range of vehicles to cover at least 5 axle load classes.

3.1. The Innsbruck 2022 Convention is '''not''' appropriate for train grf authors who wish to provide more than one axle load class.

3.2. The Innsbruck 2022 Convention treats the meaning of class ''A'' as ''undefined'', ''ignored'' or ''compatible with most restricted railtype'' for axle load.

Axle load class ''A'' '''cannot''' be safely interpreted as ''universal'' because from the perspective of a railtype grf ''A'' is ''most restricted railtype'', where ''universal'' is better represented as ''least restricted railtype''. Depending how many axle load classes are in use by the railtype grf, this could be class ''B'', ''C'', ''D'', ''E'' etc. To illustrate this issue, take the following scenario

* railtype grf defines axle loads ''A'' to ''E''. In this case the railtype grf author intends that ''A'' is compatible with the smallest range of vehicles, ''E'' is compatible with the largest range of vehicles, and ''B'', ''C'' and ''D'' are compatible with some intermediate ranges of vehicles
* but the vehicle grf author has defined all vehicles to be axle load ''A'' in an attempt to express this vehicle is ''universal''. The result in the game is that an identical range of vehicles will be compatible with railtypes ''A'' to ''E''.

This is clearly '''not''' the intended outcome of the railtype author. But nor is it clear within the spec that the vehicle author has particularly done anything wrong.

It ''would'' be possible to use railtype availability testing to adjust the vehicle property 05 (track_type) to fit the highest defined axle load (''E'' in this example case), but this is not insignificant work, and it's unlikely to be widely adopted by vehicle grf authors. Nor would this solution achieve ''universal'' as all vehicles in vehicle grf then would be incompatible with types ''A'' through ''D''.

3.3. When the Innsbruck 2022 Convention is used, this '''does not prevent''' a train grf being extended in some future release to achieve full compliance with Standardized Railtype Scheme. ''That choice remains with train grf authors''.

3.4. If 2012 could be revisited, providing an optional ''_'' axle load class in the Standardized Railtype Scheme for ''undefined'' would have been preferable, but as of 2022, ''A'' is already widely used for this purpose, and time travel is not known to be possible.

==Possible additions==

{|
! !!Track type/gauge
|-
|B ||Broad gauge rail (Also used by "ultra-broad" fictional tracktype; As broad gauge is a rare tracktype, it may still be feasible to cement B and b as broad gauges of two differing sizes)
|-
|b ||Broad gauge rail (Originally assigned to uppercase B; As broad gauge is a rare tracktype, it may still be feasible to cement B and b as broad gauges of two differing sizes)
|-
|s ||Multiple gauge rail, ultrabroad/broad/standard/narrow/secondary narrow gauge
|-
|0 ||No track, eyecandy-use only
|}
It might be prefered to instead use keep "B" for current broad gauge and instead using lovercase "b" for the new ultra-broad gauge. This wouldn't be to different from narrow gauge since the lesser used ones are lowercase and fallback to the uppercase ones.

Standardized Railtype Scheme

2023-10-10T05:31:05Z

Revenge of kiothedev: /* Speed limit class [*X**] */

This railtype label scheme aims to bring order to the uncontrolled growth of railtype labels. It groups the rail types into what matters from a technical perspective. The scheme provides a standardized way of defining railtype labels, based on track gauge and type, speed class, allowable axle weight and electrification type.

It is the explicit intent of this scheme to decouple track sets from vehicle sets to facilitate easy mixing. This way the player can select a track set of choice to go with a train set of choice. It allows the player to play with or without axle load classes, or with or without speed limit classes, simply by loading a track set that does or does not provide these features. In some cases it will also be possible to combine niche track sets, for instance a standard gauge track set with a narrow gauge and a metro track set.

== The Label Scheme ==
A railtype label consists of four characters. In this scheme, each position has a different purpose:
# Track gauge and type class (e.g. standard gauge rail, narrow gauge rail, monorail)
# Speed limit class
# Axle load class (maximum allowed axle weight for this track)
# Energy source type class

In the next sections, each of the four positions will be explained.

=== Track gauge and type class [X***] ===
The first position in the railtype label defines track gauge and/or track type class. The following classes are currently defined:

{|
! !!Track type/gauge
|-
|S ||Standard gauge rail
|-
|B ||Broad gauge rail
|-
|N ||Narrow gauge rail
|-
|n ||Secondary narrow gauge rail (e.g. when providing both metre and cape gauge, always use N in case of just one type of narrow gauge)
|-
|D ||Dual gauge rail, standard/broad gauge
|-
|d ||Dual gauge rail, standard/narrow gauge
|-
|M ||Monorail
|-
|L ||Magnetic Levitation
|}

=== Speed limit class [*X**] ===
The second position in the railtype label defines the speed limit class. These classes do not map to a fixed numeric value, but are used to define an internal speed limit order for the track set. This means that if your track set has two different speed limits for track types that are otherwise identical, you'll use letters A and B here. In case of three different speed limits, use A, B and C. In case your track set does not employ speed limits, always use A. Train sets do not care about the speed limit, and will always set the lowest speed class, i.e. A.

This gives for instance the following options:

<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||no speed limits
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||high speed
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||medium speed
|-
|C ||high speed
|}
</div>
<div style="float:left;">
 etc. 
</div>
</div>
<div style="clear:left;"></div>

The speed limit class may also be used for some advanced features of the label scheme, like specialized track types and eyecandy purposes. Be careful not to break the compatibility with other sets when using the speed limit class for these purposes.

An example of a special use is rack rail. In the French set it is used to give rack rail engines a higher speed and TE than normal rail engines when used on rack rail. When defining trains with a special speed limit class, always allow a fallback to speed limit class A via the railtype table.

An example of eyecandy use are urban tracks. These are a variation of regular tracks, but with concrete ground tiles to better match the urban environment. Train sets must not define vehicles for eyecandy classes. If you think you have special vehicles that should only run on the eyecandy class, it is ''not'' eyecandy but a separate track gauge/type.

The following special and eyecandy classes have been defined so far:

{|
! !!Description !!Type !!Used by
|-
|A-H ||speed limits ||colspan="2"|reserved
|-
|R ||rack rail ||special ||French Set Rails
|-
|S ||subterranean ||eyecandy ||Metro Track Set
|-
|U ||urban ||eyecandy ||Metro Track Set
|-
|g ||ground tile for 45° angles ||eyecandy ||(none yet)
|}

=== Axle load class [**X*] ===
The third position defines the axle weight limit. Heavy trains cannot run on tracks with a low axle weight limit; these trains need more expensive tracks with a heigher weight limit. There are five axle load classes '''A''' through '''E'''. '''A''' is for the lowest axle load limit, '''E''' for the highest. The exact axle load attached to each class is relative to the track gauge/type and trains in the set.

A train set should set the appropriate axle weight for each train via the railtype label, as to make the set work with track sets that do provide tracks with different weight limits, even if you don't care about it for your trainset. Split all vehicles of a certain track gauge/type into five groups of similar axle weight. The group with the lowest axle weights will get class '''A''', the second lowest class '''B''', etc. up to the group with the highest axle weights which will get class '''E'''. Do the same for the other track gauge/types if your train set has those.

A track set does not have to provide a dedicated track type for each axle weight limit. A track set that does not provide a dedicated track for each axle load class, must make sure to map all undefined axle load classes to a real railtype using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]]. This way a train set can rely on all labels for all axle load classes being available. Example: if you only want to provide 2 axle load classes for standard gauge unelectrified with no speed limits, you can map SA'''A'''N + SA'''B'''N to SA'''C'''N and SA'''D'''N to SA'''E'''N if the cost difference between the two railtypes is high, or SA'''A'''N to SA'''B'''N and SA'''C'''N + SA'''D'''N to SA'''E'''N if the cost difference is low.

If you don't want to provide any axle load classes in your track set, it doesn't really matter what axle load class you choose for the track, as you'll be mapping all other classes to this track anyways. But the lowest or highest class are the obvious choice. Example: if your track set only provides narrow gauge unelectrified track with no speed limits and no axle load limits, you may use NA'''A'''N for the track label, and provide NA'''B'''N, NA'''C'''N, NA'''D'''N, NA'''E'''N in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

If you need more than five axle load class, you may use lowercase letters for very low axle loads and continue the uppercase letters for very high axle loads. Be advised that your train set may not assume the existance of any other class than '''A''' through '''E''', so when the range make sure to program your railtype table such that trains with such a class will fall back to class '''A''' or '''E'''. If you make a track set with an extended range, be aware that not all train sets will define trains for these tracks. In general: only do this in case of a train set with a matching track set.

For the lowercase letters, '''b''' is lower than '''a''', so for increasing axle load limits: b < a < A < B < C etc.

Note that the axle load classes never map to a specific weight in tonnes. For that reason it does not make sense to add a numeric value for the axle load to the name of a track type or in the extended purchase info of a train. Instead use the relative expressions 'very low', 'low', 'medium', 'high' and 'very high' or use the class letters directly.

=== Energy source type class [***X] ===
The last position defines the energy source type class. This is split in generic energy source types like overhead wires and third rail and specialized types like alternating and direct current.

A track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

A vehicle set that uses specialized types should define a generic type as fallback, via the railtype table. If such a fallback is omitted, please note that certain vehicles may be unavailable depending on track set loaded.

{|
! !!Generic energy type classes
|-
|N ||no electrification
|-
|E ||overhead wires/catenary electrification
|-
|3 ||3rd rail electrification
|}

{|
! !!Specialized energy type classes !!Vehicle set fallback
|-
|Z ||3rd rail and catenary electrification || 3 or E
|-
|4 ||4th rail electrification || 3
|-
|Y ||4th rail and catenary electrification || 4 or E
|-
|T ||[http://en.wikipedia.org/wiki/Three-phase_AC_railway_electrification three phase AC electrification] || E
|-
| colspan="3" |  
|-
|D ||DC catenary electrification || E
|-
|d ||low voltage DC catenary electrification (only when D also used in set) || First A then E
|-
|A ||AC catenary electrification || E
|-
|a ||low voltage AC catenary electrification (only when A also used in set) || First A then E
|}

If you want multi-voltage/current vehicles in your set (i.e. a train that can run on both AC and DC current), you have to define a dedicated railtype for those vehicles. Without the railtype, it's not possible to define vehicles with this property. If you only have vehicles that can run on either one type of voltage/current or on all types of voltage/current (e.g. a 2-system if you only have '''A''' and '''D''' tracks, or a 4-system in case of all '''A''', '''a''', '''D''' and '''d'''), then use the generic class '''E''' for vehicles that should be able to run on all different voltage/currents. Also the track set needs to have one at least one railtype with class '''E''' defined.

Note that if you want more than one type of multi-voltage/current, you'll quickly get a combinatory explosion of railtype labels, so plan carefully or do not attempt it. For every different multi-voltage/current vehicle type a dedicated railtype is needed. If you want all possible combinations, then you need to define an additional 8 classes. It is not recommended to make your train/track set this complicated.

Example approach for a 4-system set, with trains that can run on either one or all systems:
* '''E''': generic catenary-powered electric engines. "universal" [4-system] if any of '''D'''/'''d'''/'''A'''/'''a''' are defined.
* '''A''': generic AC catenary electric engines. 25kV only if '''a''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''A''';
* '''a''': 15kV AC catenary electric engines. Only defined if '''A''' also defined. Vehicle sets should use '''A''' and '''E''' as fallback, if defining an engine for '''a''';
* '''D''': generic DC catenary electric engines. 3kV if '''d''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''D''';
* '''d''': 1.5kV DC catenary electric engines. Only defined if '''D''' also defined. Vehicle sets should use '''D''' and '''E''' as fallback, if defining an engine for '''d'''.
For a 2-system set, you can simply drop '''a''' and '''d'''.

=== Standard labels: RAIL, ELRL, MONO, MGLV ===
It's not possible to undefine the standard railtypes RAIL, ELRL, MONO and MGLV. The game will always add those if there are vehicles defined for these track types. As a result, for a track set it's best not to ignore those standard labels, but rather work with them and define them in the set. If your track set does not have monorail or maglev tracks, there of course is no need to define those. But if your track set defines anything that resembles unelectrified or electrified rail, you should use the RAIL and ELRL labels. Matching labels from the above scheme will then be defined in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

As vehicles from NewGRFs that do not use explicit railtypes will end up on these standard railtypes, you should use RAIL instead of whatever type could be regarded as the most commonly used unelectrified type, ELRL instead of the most commonly used electrified type and so on. The label according to this scheme is then set as an alternate.

== Summary for track sets ==
This section summarizes the above for track sets.

; [X***] Track gauge and type class
* Define at least one track type for every track gauge/type class you want in your set.
* If you only provide tracks for one gauge/type, consider leaving some free railtypes so a player can load an additional set for some other type.
; [*X**] Speed limit class
* Make sure class A is always available, either directly or via an alternate label.
* Use only class A if you don't want speed limits;
* With speed limits, A is the lowest speed limit. Continue with B, C, etc. for increasing speed limits;
* The speed class can also be used to implement additional eye-candy track types, use letters higher in the alphabet for this.
; [**X*] Axle load class
* Always define all classes A through E for every track type class / electrification combination, either:
** Directly via a real railtype definition;
** Indirectly via the alternate rail type label list, property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].
* Extend the predefined classes only if you also provide a train set that makes use of these.
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via property 1D.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Always define the standard labels when possible, instead of what would be the equivalent of the standard label in this scheme.
* Map the equivalent labels from this scheme to the standard labels using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

Or, put differently, for each gauge/type, select one or more energy source types. For each type/energy combination provide all axle load classes for the speed class "A", either as a real type or as an alternate of another type. Provide more types with a different speed letter if you want to provide several different speeds or other eye-candy tracks.

== Summary for train sets ==
This section summarizes the above for train sets.

; [X***] Track gauge and type class
* Use the track type class that matches the vehicle;
* Define a fallback type via the railtype table in case you want the vehicle to be available on a different track if no matching track set is loaded.
** Specialized subtypes like "n" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "N").
; [*X**] Speed limit class
* Always use class A for every vehicle.
; [**X*] Axle load class
* Use all classes A through E according to the maximum axle weight of the vehicle.
* Extend the predefined classes only if you also provide a track set that makes use of these;
** When extending the predefined classes A through E, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Define a fallback type to the standard labels via the railtype table in case you want the vehicle to be available on the standard tracks if no matching track set is loaded.

Be as specific as you want when selecting the railtype, it is the job of the track set to select a playable, reduced subset out of all possible type combinations.

== In case you're not convinced by this scheme ==
Adopting this scheme gives the player freedom to use any track set in combination with any train set that follow the scheme.

This means that you can make your train set compatible with track sets that provide axle load classes, and track sets that provide speed limits, and at the same time with track sets that provide none of this. This way, the player can decide to play with or without axle load classes, or with or without speed limits, simply by loading a track set that does or does not provide these features.

And for your track set, it means that you can make it as simple or as complicated as you want (within the 64 track type limit), while not having to worry about compatibility with train sets.

Still not convinced? Feel free to use railtype labels of your own, but know that you will likely come to regret that at some point in the future.

==Forum topic==
If you want to discuss the standardized railtype scheme or have any questions about it, you can visit [http://www.tt-forums.net/viewtopic.php?t=59379 the forum topic].

=="Innsbruck 2022 Convention" for partial compliance==

This is really esoteric, but eh. It was the product of long discussion / debate / argument / reasoning between grf authors.

1. The Standardized Railtype Scheme '''is a useful tool''' for providing reliable compatibility between train grfs and railtype grfs.

2. The '''axle load class''' in the scheme presents a number of issues for compliance.

2.1. Over 10 years since the scheme was standardised, not many train grfs implement multiple axle load classes '''as required by the scheme'''. Known examples that '''do''' comply include Dutch Train Set, French Narrow Gauge Trains, and Finnish Trains.

2.2. Elements of the axle load rules have proven hard to interpret. For example:

* is it compliant to use ''fewer'' than 5 classes in a train grf? There is a lack of consensus on this.
* axle load is only one of many factors that govern whether a vehicle is compatible with a route, for example loading gauge, minimum curve, signalling types etc

2.3. Meanwhile ''multiple existing train grfs use class ''A'' for the axle load for all trains'' (except where relying on default railtypes such as RAIL and ELRL).

'''3. The Innsbruck 2022 Convention uses class ''A'' for axle load for '''all''' trains in a train grf (except where relying on default railtypes such as RAIL and ELRL).'''

This is '''not''' fully compliant with the Standardized Railtype Scheme and does not claim to be.

However train grfs using the Innsbruck 2022 Convention are ''broadly compatible'' with railtype grfs using the Standardized Railtype Scheme.

Obligatory XKCD link about 'standards': https://xkcd.com/927/

===Known issues===

Known problems are that trains using only class 'A' may limit the ability of railtype grf authors to achieve their design goals for separating railtypes by axle load.
But on reflection, it can be seen that a train grf might not be able to provide a broad enough range of vehicles to cover at least 5 axle load classes.

3.1. The Innsbruck 2022 Convention is '''not''' appropriate for train grf authors who wish to provide more than one axle load class.

3.2. The Innsbruck 2022 Convention treats the meaning of class ''A'' as ''undefined'', ''ignored'' or ''compatible with most restricted railtype'' for axle load.

Axle load class ''A'' '''cannot''' be safely interpreted as ''universal'' because from the perspective of a railtype grf ''A'' is ''most restricted railtype'', where ''universal'' is better represented as ''least restricted railtype''. Depending how many axle load classes are in use by the railtype grf, this could be class ''B'', ''C'', ''D'', ''E'' etc. To illustrate this issue, take the following scenario

* railtype grf defines axle loads ''A'' to ''E''. In this case the railtype grf author intends that ''A'' is compatible with the smallest range of vehicles, ''E'' is compatible with the largest range of vehicles, and ''B'', ''C'' and ''D'' are compatible with some intermediate ranges of vehicles
* but the vehicle grf author has defined all vehicles to be axle load ''A'' in an attempt to express this vehicle is ''universal''. The result in the game is that an identical range of vehicles will be compatible with railtypes ''A'' to ''E''.

This is clearly '''not''' the intended outcome of the railtype author. But nor is it clear within the spec that the vehicle author has particularly done anything wrong.

It ''would'' be possible to use railtype availability testing to adjust the vehicle property 05 (track_type) to fit the highest defined axle load (''E'' in this example case), but this is not insignificant work, and it's unlikely to be widely adopted by vehicle grf authors. Nor would this solution achieve ''universal'' as all vehicles in vehicle grf then would be incompatible with types ''A'' through ''D''.

3.3. When the Innsbruck 2022 Convention is used, this '''does not prevent''' a train grf being extended in some future release to achieve full compliance with Standardized Railtype Scheme. ''That choice remains with train grf authors''.

3.4. If 2012 could be revisited, providing an optional ''_'' axle load class in the Standardized Railtype Scheme for ''undefined'' would have been preferable, but as of 2022, ''A'' is already widely used for this purpose, and time travel is not known to be possible.

==Possible additions==

{|
! !!Track type/gauge
|-
|B ||Broad gauge rail (Also used by "ultra-broad" fictional tracktype; As broad gauge is a rare tracktype, it may still be feasible to cement B and b as broad gauges of two differing sizes)
|-
|b ||Broad gauge rail (Originally assigned to uppercase B; As broad gauge is a rare tracktype, it may still be feasible to cement B and b as broad gauges of two differing sizes)
|-
|s ||Multiple gauge rail, ultrabroad/broad/standard/narrow/secondary narrow guage
|}
It might be prefered to instead use keep "B" for current broad gauge and instead using lovercase "b" for the new ultra-broad gauge. This wouldn't be to different from narrow gauge since the lesser used ones are lowercase and fallback to the uppercase ones.

TracktypeLabels

2023-10-10T05:25:05Z

Revenge of kiothedev: Corrected labels for early rails

== Labels for rail types, road types and tram type ==
All track types are identified via 4-byte labels.
The labels are unique within their type, but it is common that rail types and tram types use the same label for similar types.

Vehicles can check for their track type on a tile, but they only have access to their own type: On a level-crossing with all three tracks (rail, road, tram) trains can only check rail types, buses/trucks can only check road types, and trams can only check tram types.

=== Rail vs. tram ===
Rail and tram are very different wrt. game-play, but both are kind of rails.
To unify labels, rail and tram should use the same labels, if the tracks are similar.
* RAIL for unelectrified rail and tram.
* ELRL for electrified rail and tram.
* FNCY for fancy-powered rail and tram.

== Default labels ==

=== Rail type ===
These labels are used for the trains and tracks in the base game, as well as for train sets that are not rail-type-aware. Consequently, track NewGRFs should always override their properties, or at least make their tracks compatible to them.

{| class="wikitable"
|-
!'''Label'''
!'''Rail Type'''
|-
|RAIL
|Normal rail
|-
|ELRL
|electrified rail
|-
|MONO
|Monorail tracks
|-
|MGLV
|Maglev tracks
|}

=== Road types ===
By default there is only a single road type defined:
{| class="wikitable"
|-
!'''Label'''
!'''Road Type'''
|-
|ROAD
|Normal road
|}
However, if a NewGRF requires electrified "ELRD", an Action0 is sufficient to add this type and make it use the default road-ground and catenary sprites.

=== Tram types ===
By default there is only a single tram type defined:
{| class="wikitable"
|-
!'''Label'''
!'''Tram Type'''
|-
|ELRL
|Electrified rail
|}
However, if a NewGRF requires unelectrified "RAIL", an Action0 is sufficient to add this type and make it use the default tram-ground sprites.

Note: Please use the same label for tram types which already exist as rail types.

== Standardized Railtype Scheme ==
Several members of the TT Forums have collaborated to define a rail type label scheme that allows for compatibility between train and track sets by different authors. At the same time it allows fancy stuff like axle weight limits, speed limits, different track and electrification types, etc. See [[Standardized Railtype Scheme]].

The Standardized Railtype Scheme is not mandatory, and authors providing both trains and railtypes may have valid reasons to use labels outside the scheme. The Standardized Scheme cannot cover all possible cases, by design, as it would be too complex.

However even when using custom labels, it may be worth using Standardized Railtype labels:
* as fallbacks for trains when the custom label is not available (via NML railtypetable fallback lists)
* as alternates handled by a railtype with a custom label (via NML alternative_railtype_list or NFO prop 1D)
This will provide wider compatibility with other train and railtype grfs.

== Standardized Roadtype Scheme ==
Same story as the railtype one, also covers trams. See [[Standardized Roadtype Scheme]]

== Non-standard railtype labels ==

The following labels were defined before the Standardized Railtype Scheme existed. Using these or not is at the discretion of individual grf authors, but generally, if an equivalent label exists in the Standardized Railtype Scheme, it's better to use that.

{| class="wikitable"
|-
!'''Label'''
!'''Rail Type'''
!'''Notes'''
|-
|_040
|speed limit 40 km/h
|Slowrails, SwedishRails
|-
|_080
|speed limit 80 km/h
|Slowrails, SwedishRails
|-
|E040
|speed limit 40 km/h, with catenary
|Slowrails, SwedishRails
|-
|E080
|speed limit 80 km/h, with catenary
|Slowrails, SwedishRails
|-
|3RDR
|Tracks with third rail
|MetroTracks, NuTracks, UK Railway Set tracks, Japanese Track Set
|-
|3RDC
|Tracks with third rail and catenary
|MetroTracks, NuTracks, UK Railway Set tracks, Japanese Track Set
|-
|RLOW
|Low speed tracks
|NuTracks, SwedishRails, Japanese Track Set
|-
|ELOW
|Low speed tracks with catenary
|NuTracks, SwedishRails, Japanese Track Set
|-
|3LOW
|Low speed tracks with 3rd rail
|NuTracks,
|-
|CLOW
|Low speed tracks, 3rd rail and catenary
|NuTracks
|-
|RMED
|Medium speed tracks
|NuTracks, SwedishRails
|-
|EMED
|Medium speed tracks with catenary
|NuTracks, SwedishRails
|-
|3MED
|Medium speed tracks with 3rd rail
|NuTracks
|-
|CMED
|Medium speed tracks, 3rd rail and catenary
|NuTracks
|-
|RHIG
|High speed tracks
|NuTracks, SwedishRails, Japanese Track Set
|-
|EHIG
|High speed tracks with catenary
|NuTracks, SwedishRails, Japanese Track Set
|-
|HSTR
|Very high speed tracks with catenary
|NuTracks, SwedishRails, Japanese Track Set
|-
|NGRL
|Narrow gauge tracks
|Narrow Gauge Track Types, Japanese Track Set
|-
|ELNG
|Narrow gauge tracks with catenary
|Narrow Gauge Track Types, Japanese Track Set
|-
|PLAN
|Planning tracks (blue dotted lines)
|NuTracks
|-
|MTRO
|Metro tracks
|NuTracks
|-
|MTRC
|Metro tracks with concrete edges
|NuTracks
|-
|MTRS
|Metro tracks with suburban buildings on top
|NuTracks
|-
|MTRU
|Metro tracks with 'downtown' buildings on top
|NuTracks
|-
|MTRT
|Metro tracks with plain landscape on top
|NuTracks
|-
|DBNN
|branch line
|DBRails
|-
|DBNE
|branch line, electrified
|DBRails
|-
|DBHN
|main line
|DBRails
|-
|DBHE
|main line, electrified
|DBRails
|-
|DBHS
|high speed line electrified (NBS)
|DBRails
|-
|TRPD
|transrapid track
|Transrapid track type
|-
|NLOW
|Low speed narrow gauge tracks
|Japanese Track Set
|-
|ENLW
|Low speed narrow gauge tracks with catenary
|Japanese Track Set
|-
|ENHI
|Modern narrow gauge tracks with catenary
|Japanese Track Set
|-
|RLA0
|Broad (1520 mm) gauge unelectrified tracks. Speed limit 60 km/h
|xUSSR train set
|-
|RLA1
|Broad (1520 mm) gauge unelectrified tracks. Speed limit 100 km/h
|xUSSR train set
|-
|RLA2
|Broad (1520 mm) gauge unelectrified tracks. Speed limit 140 km/h
|xUSSR train set
|-
|RLA3
|Broad (1520 mm) gauge unelectrified tracks. Speed limit 250 km/h
|xUSSR train set
|-
|ERd0
|Broad (1520 mm) gauge tracks with generic DC catenary 1,5kV. Speed limit 60 km/h
|xUSSR train set
|-
|ERd1
|Broad (1520 mm) gauge tracks with generic DC catenary 1,5kV. Speed limit 100 km/h
|xUSSR train set
|-
|ERd2
|Broad (1520 mm) gauge tracks with generic DC catenary 1,5kV. Speed limit 140 km/h
|xUSSR train set add-on
|-
|ERd3
|Broad (1520 mm) gauge tracks with generic DC catenary 1,5kV. Speed limit 250 km/h
|xUSSR train set add-on
|-
|ERD1
|Broad (1520 mm) gauge tracks with generic DC catenary 3kV. Speed limit 100 km/h
|xUSSR train set
|-
|ERD2
|Broad (1520 mm) gauge tracks with generic DC catenary 3kV. Speed limit 140 km/h
|xUSSR train set
|-
|ERD3
|Broad (1520 mm) gauge tracks with generic DC catenary 3kV. Speed limit 250 km/h
|xUSSR train set
|-
|ERA1
|Broad (1520 mm) gauge tracks with generic AC catenary 25kV. Speed limit 100 km/h
|xUSSR train set
|-
|ERA2
|Broad (1520 mm) gauge tracks with generic AC catenary 25kV. Speed limit 140 km/h
|xUSSR train set
|-
|ERA3
|Broad (1520 mm) gauge tracks with generic AC catenary 25kV. Speed limit 250 km/h
|xUSSR train set
|-
|ERA4
|Broad (1520 mm) gauge tracks with generic AC catenary 25kV. No speed limit
|xUSSR train set
|-
|ERa0
|Broad (1520 mm) gauge tracks with generic AC catenary 15kV. Speed limit 60 km/h
|xUSSR train set
|-
|ERa1
|Broad (1520 mm) gauge tracks with generic AC catenary 15kV. Speed limit 100 km/h
|xUSSR train set add-on
|-
|ERa2
|Broad (1520 mm) gauge tracks with generic AC catenary 15kV. Speed limit 140 km/h
|xUSSR train set add-on
|-
|ERa3
|Broad (1520 mm) gauge tracks with generic AC catenary 15kV. Speed limit 250 km/h
|xUSSR train set add-on
|-
|ERa4
|Broad (1520 mm) gauge tracks with generic AC catenary 15kV. No speed limit
|xUSSR train set add-on
|-
|ER2D
|Broad (1520 mm) gauge tracks with DC 1,5kV / 3kV catenary. Speed limit 100 km/h
|xUSSR train set
|-
|ER2S
|Broad (1520 mm) gauge tracks with AC 25kV / DC 3kV catenary. Speed limit 120 km/h
|xUSSR train set
|-
|ER2s
|Broad (1520 mm) gauge tracks with AC 25kV / DC 1,5kV catenary. Speed limit 120 km/h
|xUSSR train set add-on
|-
|ER3a
|Broad (1520 mm) gauge tracks with AC 25kV / 15kV / DC 1,5kV catenary. Speed limit 120 km/h
|xUSSR train set add-on
|-
|ER3D
|Broad (1520 mm) gauge tracks with AC 25kV / DC 3kV / 1,5kV catenary. Speed limit 120 km/h
|xUSSR train set add-on
|-
|ER4S
|Broad (1520 mm) gauge tracks with AC 25kV / 15kV / DC 3kV / 1,5kV catenary. Speed limit 120 km/h
|xUSSR train set add-on
|-
|WWAY
|Wagonway
|Early Rails set
|-
|WGWY
|Wagonway
|Recycled Tracktype Set
|-
|LTRL
|Light Rails
|Early Rails set
|-
|WGWY
|Light Rails
|Recycled Tracktype Set
|-
|TYTX
|ToyTrax
|ToyTrax
|-
|ELTX
|ElecTrax
|ToyTrax
|-
|DPRK
|North Korean Urban Ground
|Trackless Trackset
|-
|JPU1
|Japanese Urban Ground
|Trackless Trackset
|-
|ISR1
|Industrial Stations Renewal Ground
|Trackless Trackset
|-
|ISR2
|CHIPS Dirt Ground
|Trackless Trackset
|-
|ISR3
|CHIPS Asphalt Ground
|Trackless Trackset
|-
|ISR4
|CHIPS Cobblestone Ground
|Trackless Trackset
|}

Standardized Railtype Scheme

2023-09-18T10:08:58Z

Revenge of kiothedev: /* Track gauge and type class [X***] */

This railtype label scheme aims to bring order to the uncontrolled growth of railtype labels. It groups the rail types into what matters from a technical perspective. The scheme provides a standardized way of defining railtype labels, based on track gauge and type, speed class, allowable axle weight and electrification type.

It is the explicit intent of this scheme to decouple track sets from vehicle sets to facilitate easy mixing. This way the player can select a track set of choice to go with a train set of choice. It allows the player to play with or without axle load classes, or with or without speed limit classes, simply by loading a track set that does or does not provide these features. In some cases it will also be possible to combine niche track sets, for instance a standard gauge track set with a narrow gauge and a metro track set.

== The Label Scheme ==
A railtype label consists of four characters. In this scheme, each position has a different purpose:
# Track gauge and type class (e.g. standard gauge rail, narrow gauge rail, monorail)
# Speed limit class
# Axle load class (maximum allowed axle weight for this track)
# Energy source type class

In the next sections, each of the four positions will be explained.

=== Track gauge and type class [X***] ===
The first position in the railtype label defines track gauge and/or track type class. The following classes are currently defined:

{|
! !!Track type/gauge
|-
|S ||Standard gauge rail
|-
|B ||Broad gauge rail (Also used by "ultra-broad" fictional tracktype; As broad gauge is a rare tracktype, it may still be feasible to cement B and b as broad gauges of two differing sizes)
|-
|b ||Broad gauge rail (Originally assigned to uppercase B; As broad gauge is a rare tracktype, it may still be feasible to cement B and b as broad gauges of two differing sizes)
|-
|N ||Narrow gauge rail
|-
|n ||Secondary narrow gauge rail (e.g. when providing both metre and cape gauge, always use N in case of just one type of narrow gauge)
|-
|D ||Dual gauge rail, standard/broad gauge
|-
|d ||Dual gauge rail, standard/narrow gauge
|-
|s ||Multiple gauge rail, ultrabroad/broad/standard/narrow/secondary narrow guage
|-
|M ||Monorail
|-
|L ||Magnetic Levitation
|}

=== Speed limit class [*X**] ===
The second position in the railtype label defines the speed limit class. These classes do not map to a fixed numeric value, but are used to define an internal speed limit order for the track set. This means that if your track set has two different speed limits for track types that are otherwise identical, you'll use letters A and B here. In case of three different speed limits, use A, B and C. In case your track set does not employ speed limits, always use A. Train sets do not care about the speed limit, and will always set the lowest speed class, i.e. A.

This gives for instance the following options:

<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||no speed limits
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||high speed
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||medium speed
|-
|C ||high speed
|}
</div>
<div style="float:left;">
 etc. 
</div>
</div>
<div style="clear:left;"></div>

The speed limit class may also be used for some advanced features of the label scheme, like specialized track types and eyecandy purposes. Be careful not to break the compatibility with other sets when using the speed limit class for these purposes.

An example of a special use is rack rail. In the French set it is used to give rack rail engines a higher speed and TE than normal rail engines when used on rack rail. When defining trains with a special speed limit class, always allow a fallback to speed limit class A via the railtype table.

An example of eyecandy use are urban tracks. These are a variation of regular tracks, but with concrete ground tiles to better match the urban environment. Train sets must not define vehicles for eyecandy classes. If you think you have special vehicles that should only run on the eyecandy class, it is ''not'' eyecandy but a separate track gauge/type.

The following special and eyecandy classes have been defined so far:

{|
! !!Description !!Type !!Used by
|-
|A-H ||speed limits ||colspan="2"|reserved
|-
|R ||rack rail ||special ||French Set Rails
|-
|S ||subterranean ||eyecandy ||Metro Track Set
|-
|U ||urban ||eyecandy ||Metro Track Set
|}

=== Axle load class [**X*] ===
The third position defines the axle weight limit. Heavy trains cannot run on tracks with a low axle weight limit; these trains need more expensive tracks with a heigher weight limit. There are five axle load classes '''A''' through '''E'''. '''A''' is for the lowest axle load limit, '''E''' for the highest. The exact axle load attached to each class is relative to the track gauge/type and trains in the set.

A train set should set the appropriate axle weight for each train via the railtype label, as to make the set work with track sets that do provide tracks with different weight limits, even if you don't care about it for your trainset. Split all vehicles of a certain track gauge/type into five groups of similar axle weight. The group with the lowest axle weights will get class '''A''', the second lowest class '''B''', etc. up to the group with the highest axle weights which will get class '''E'''. Do the same for the other track gauge/types if your train set has those.

A track set does not have to provide a dedicated track type for each axle weight limit. A track set that does not provide a dedicated track for each axle load class, must make sure to map all undefined axle load classes to a real railtype using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]]. This way a train set can rely on all labels for all axle load classes being available. Example: if you only want to provide 2 axle load classes for standard gauge unelectrified with no speed limits, you can map SA'''A'''N + SA'''B'''N to SA'''C'''N and SA'''D'''N to SA'''E'''N if the cost difference between the two railtypes is high, or SA'''A'''N to SA'''B'''N and SA'''C'''N + SA'''D'''N to SA'''E'''N if the cost difference is low.

If you don't want to provide any axle load classes in your track set, it doesn't really matter what axle load class you choose for the track, as you'll be mapping all other classes to this track anyways. But the lowest or highest class are the obvious choice. Example: if your track set only provides narrow gauge unelectrified track with no speed limits and no axle load limits, you may use NA'''A'''N for the track label, and provide NA'''B'''N, NA'''C'''N, NA'''D'''N, NA'''E'''N in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

If you need more than five axle load class, you may use lowercase letters for very low axle loads and continue the uppercase letters for very high axle loads. Be advised that your train set may not assume the existance of any other class than '''A''' through '''E''', so when the range make sure to program your railtype table such that trains with such a class will fall back to class '''A''' or '''E'''. If you make a track set with an extended range, be aware that not all train sets will define trains for these tracks. In general: only do this in case of a train set with a matching track set.

For the lowercase letters, '''b''' is lower than '''a''', so for increasing axle load limits: b < a < A < B < C etc.

Note that the axle load classes never map to a specific weight in tonnes. For that reason it does not make sense to add a numeric value for the axle load to the name of a track type or in the extended purchase info of a train. Instead use the relative expressions 'very low', 'low', 'medium', 'high' and 'very high' or use the class letters directly.

=== Energy source type class [***X] ===
The last position defines the energy source type class. This is split in generic energy source types like overhead wires and third rail and specialized types like alternating and direct current.

A track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

A vehicle set that uses specialized types should define a generic type as fallback, via the railtype table. If such a fallback is omitted, please note that certain vehicles may be unavailable depending on track set loaded.

{|
! !!Generic energy type classes
|-
|N ||no electrification
|-
|E ||overhead wires/catenary electrification
|-
|3 ||3rd rail electrification
|}

{|
! !!Specialized energy type classes !!Vehicle set fallback
|-
|Z ||3rd rail and catenary electrification || 3 or E
|-
|4 ||4th rail electrification || 3
|-
|Y ||4th rail and catenary electrification || 4 or E
|-
|T ||[http://en.wikipedia.org/wiki/Three-phase_AC_railway_electrification three phase AC electrification] || E
|-
| colspan="3" |  
|-
|D ||DC catenary electrification || E
|-
|d ||low voltage DC catenary electrification (only when D also used in set) || First A then E
|-
|A ||AC catenary electrification || E
|-
|a ||low voltage AC catenary electrification (only when A also used in set) || First A then E
|}

If you want multi-voltage/current vehicles in your set (i.e. a train that can run on both AC and DC current), you have to define a dedicated railtype for those vehicles. Without the railtype, it's not possible to define vehicles with this property. If you only have vehicles that can run on either one type of voltage/current or on all types of voltage/current (e.g. a 2-system if you only have '''A''' and '''D''' tracks, or a 4-system in case of all '''A''', '''a''', '''D''' and '''d'''), then use the generic class '''E''' for vehicles that should be able to run on all different voltage/currents. Also the track set needs to have one at least one railtype with class '''E''' defined.

Note that if you want more than one type of multi-voltage/current, you'll quickly get a combinatory explosion of railtype labels, so plan carefully or do not attempt it. For every different multi-voltage/current vehicle type a dedicated railtype is needed. If you want all possible combinations, then you need to define an additional 8 classes. It is not recommended to make your train/track set this complicated.

Example approach for a 4-system set, with trains that can run on either one or all systems:
* '''E''': generic catenary-powered electric engines. "universal" [4-system] if any of '''D'''/'''d'''/'''A'''/'''a''' are defined.
* '''A''': generic AC catenary electric engines. 25kV only if '''a''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''A''';
* '''a''': 15kV AC catenary electric engines. Only defined if '''A''' also defined. Vehicle sets should use '''A''' and '''E''' as fallback, if defining an engine for '''a''';
* '''D''': generic DC catenary electric engines. 3kV if '''d''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''D''';
* '''d''': 1.5kV DC catenary electric engines. Only defined if '''D''' also defined. Vehicle sets should use '''D''' and '''E''' as fallback, if defining an engine for '''d'''.
For a 2-system set, you can simply drop '''a''' and '''d'''.

=== Standard labels: RAIL, ELRL, MONO, MGLV ===
It's not possible to undefine the standard railtypes RAIL, ELRL, MONO and MGLV. The game will always add those if there are vehicles defined for these track types. As a result, for a track set it's best not to ignore those standard labels, but rather work with them and define them in the set. If your track set does not have monorail or maglev tracks, there of course is no need to define those. But if your track set defines anything that resembles unelectrified or electrified rail, you should use the RAIL and ELRL labels. Matching labels from the above scheme will then be defined in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

As vehicles from NewGRFs that do not use explicit railtypes will end up on these standard railtypes, you should use RAIL instead of whatever type could be regarded as the most commonly used unelectrified type, ELRL instead of the most commonly used electrified type and so on. The label according to this scheme is then set as an alternate.

== Summary for track sets ==
This section summarizes the above for track sets.

; [X***] Track gauge and type class
* Define at least one track type for every track gauge/type class you want in your set.
* If you only provide tracks for one gauge/type, consider leaving some free railtypes so a player can load an additional set for some other type.
; [*X**] Speed limit class
* Make sure class A is always available, either directly or via an alternate label.
* Use only class A if you don't want speed limits;
* With speed limits, A is the lowest speed limit. Continue with B, C, etc. for increasing speed limits;
* The speed class can also be used to implement additional eye-candy track types, use letters higher in the alphabet for this.
; [**X*] Axle load class
* Always define all classes A through E for every track type class / electrification combination, either:
** Directly via a real railtype definition;
** Indirectly via the alternate rail type label list, property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].
* Extend the predefined classes only if you also provide a train set that makes use of these.
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via property 1D.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Always define the standard labels when possible, instead of what would be the equivalent of the standard label in this scheme.
* Map the equivalent labels from this scheme to the standard labels using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

Or, put differently, for each gauge/type, select one or more energy source types. For each type/energy combination provide all axle load classes for the speed class "A", either as a real type or as an alternate of another type. Provide more types with a different speed letter if you want to provide several different speeds or other eye-candy tracks.

== Summary for train sets ==
This section summarizes the above for train sets.

; [X***] Track gauge and type class
* Use the track type class that matches the vehicle;
* Define a fallback type via the railtype table in case you want the vehicle to be available on a different track if no matching track set is loaded.
** Specialized subtypes like "n" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "N").
; [*X**] Speed limit class
* Always use class A for every vehicle.
; [**X*] Axle load class
* Use all classes A through E according to the maximum axle weight of the vehicle.
* Extend the predefined classes only if you also provide a track set that makes use of these;
** When extending the predefined classes A through E, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Define a fallback type to the standard labels via the railtype table in case you want the vehicle to be available on the standard tracks if no matching track set is loaded.

Be as specific as you want when selecting the railtype, it is the job of the track set to select a playable, reduced subset out of all possible type combinations.

== In case you're not convinced by this scheme ==
Adopting this scheme gives the player freedom to use any track set in combination with any train set that follow the scheme.

This means that you can make your train set compatible with track sets that provide axle load classes, and track sets that provide speed limits, and at the same time with track sets that provide none of this. This way, the player can decide to play with or without axle load classes, or with or without speed limits, simply by loading a track set that does or does not provide these features.

And for your track set, it means that you can make it as simple or as complicated as you want (within the 64 track type limit), while not having to worry about compatibility with train sets.

Still not convinced? Feel free to use railtype labels of your own, but know that you will likely come to regret that at some point in the future.

==Forum topic==
If you want to discuss the standardized railtype scheme or have any questions about it, you can visit [http://www.tt-forums.net/viewtopic.php?t=59379 the forum topic].

="Innsbruck 2022 Convention" for partial compliance=

This is really esoteric, but eh. It was the product of long discussion / debate / argument / reasoning between grf authors.

1. The Standardized Railtype Scheme '''is a useful tool''' for providing reliable compatibility between train grfs and railtype grfs.

2. The '''axle load class''' in the scheme presents a number of issues for compliance.

2.1. Over 10 years since the scheme was standardised, not many train grfs implement multiple axle load classes '''as required by the scheme'''. Known examples that '''do''' comply include Dutch Train Set, French Narrow Gauge Trains, and Finnish Trains.

2.2. Elements of the axle load rules have proven hard to interpret. For example:

* is it compliant to use ''fewer'' than 5 classes in a train grf? There is a lack of consensus on this.
* axle load is only one of many factors that govern whether a vehicle is compatible with a route, for example loading gauge, minimum curve, signalling types etc

2.3. Meanwhile ''multiple existing train grfs use class ''A'' for the axle load for all trains'' (except where relying on default railtypes such as RAIL and ELRL).

'''3. The Innsbruck 2022 Convention uses class ''A'' for axle load for '''all''' trains in a train grf (except where relying on default railtypes such as RAIL and ELRL).'''

This is '''not''' fully compliant with the Standardized Railtype Scheme and does not claim to be.

However train grfs using the Innsbruck 2022 Convention are ''broadly compatible'' with railtype grfs using the Standardized Railtype Scheme.

Obligatory XKCD link about 'standards': https://xkcd.com/927/

===Known issues===

Known problems are that trains using only class 'A' may limit the ability of railtype grf authors to achieve their design goals for separating railtypes by axle load.
But on reflection, it can be seen that a train grf might not be able to provide a broad enough range of vehicles to cover at least 5 axle load classes.

3.1. The Innsbruck 2022 Convention is '''not''' appropriate for train grf authors who wish to provide more than one axle load class.

3.2. The Innsbruck 2022 Convention treats the meaning of class ''A'' as ''undefined'', ''ignored'' or ''compatible with most restricted railtype'' for axle load.

Axle load class ''A'' '''cannot''' be safely interpreted as ''universal'' because from the perspective of a railtype grf ''A'' is ''most restricted railtype'', where ''universal'' is better represented as ''least restricted railtype''. Depending how many axle load classes are in use by the railtype grf, this could be class ''B'', ''C'', ''D'', ''E'' etc. To illustrate this issue, take the following scenario

* railtype grf defines axle loads ''A'' to ''E''. In this case the railtype grf author intends that ''A'' is compatible with the smallest range of vehicles, ''E'' is compatible with the largest range of vehicles, and ''B'', ''C'' and ''D'' are compatible with some intermediate ranges of vehicles
* but the vehicle grf author has defined all vehicles to be axle load ''A'' in an attempt to express this vehicle is ''universal''. The result in the game is that an identical range of vehicles will be compatible with railtypes ''A'' to ''E''.

This is clearly '''not''' the intended outcome of the railtype author. But nor is it clear within the spec that the vehicle author has particularly done anything wrong.

It ''would'' be possible to use railtype availability testing to adjust the vehicle property 05 (track_type) to fit the highest defined axle load (''E'' in this example case), but this is not insignificant work, and it's unlikely to be widely adopted by vehicle grf authors. Nor would this solution achieve ''universal'' as all vehicles in vehicle grf then would be incompatible with types ''A'' through ''D''.

3.3. When the Innsbruck 2022 Convention is used, this '''does not prevent''' a train grf being extended in some future release to achieve full compliance with Standardized Railtype Scheme. ''That choice remains with train grf authors''.

3.4. If 2012 could be revisited, providing an optional ''_'' axle load class in the Standardized Railtype Scheme for ''undefined'' would have been preferable, but as of 2022, ''A'' is already widely used for this purpose, and time travel is not known to be possible.

Standardized Roadtype Scheme

2023-09-18T09:01:34Z

Revenge of kiothedev: /* Energy [***X] */

= '''Not in a useable state do not use''' =
There is currently not enough clarification on how the standard is meant to be used along with other major issues
=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossing (Multiple/universal roadtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter the primary roadtype's first letter in a crossing between roadtypes (e.g. "XRBN" for a road and pipeline crossing). Please understand that as of this writing, the standardized roadtype scheme cannot yet account for more than two crossing roadtypes with the same primary roadtype. Finally, as of this writing, only some combination of a road, a pipeline, eyecandy or (potentially) a system not yet given a label can justify use of the "X" label.
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Junction/Crossover (Multiple/universal railtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter the primary tramtype's first letter in a junction tramtype (e.g. "XRBN" for light rail with bike lanes). Please understand that as of this writing, the standardized roadtype scheme cannot yet account for more than two crossing tramtypes with the same primary tramtype. If there is no primary tramtype (such as a "universal" tramtype or a tramtype with more than two systems in the junction) then it is recommended to use a lowercase x as the second letter.
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". It is suggested that roadtype and tramtype speeds use capital letters (A-Z) and roadtypes and tramtypes with specific features use lowercase letters (a-z). Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains (high-voltage, off-road, no lighting)
| X, then S, then i, then G, then E
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), roadside Infrastructure (Utility poles, fences, etc.), or Irrelevant
| ''For eyecandy tramtypes with underground infrastructure, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the alternative_roadtype_list or alternative_tramtype_list for a road/tramtype using this energy source''
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then i, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-09-18T09:00:02Z

Revenge of kiothedev: /* Energy [***X] */

= '''Not in a useable state do not use''' =
There is currently not enough clarification on how the standard is meant to be used along with other major issues
=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossing (Multiple/universal roadtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter the primary roadtype's first letter in a crossing between roadtypes (e.g. "XRBN" for a road and pipeline crossing). Please understand that as of this writing, the standardized roadtype scheme cannot yet account for more than two crossing roadtypes with the same primary roadtype. Finally, as of this writing, only some combination of a road, a pipeline, eyecandy or (potentially) a system not yet given a label can justify use of the "X" label.
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Junction/Crossover (Multiple/universal railtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter the primary tramtype's first letter in a junction tramtype (e.g. "XRBN" for light rail with bike lanes). Please understand that as of this writing, the standardized roadtype scheme cannot yet account for more than two crossing tramtypes with the same primary tramtype. If there is no primary tramtype (such as a "universal" tramtype or a tramtype with more than two systems in the junction) then it is recommended to use a lowercase x as the second letter.
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". It is suggested that roadtype and tramtype speeds use capital letters (A-Z) and roadtypes and tramtypes with specific features use lowercase letters (a-z). Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains (high-voltage, off-road, no lighting)
| X, then S, then i, then G, then E
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), roadside Infrastructure (Utility poles, fences, etc.), or Irrelevant
| ''For eyecandy tramtypes with underground infrastructure, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for a road/tramtype using this energy source''
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then i, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-09-18T08:46:19Z

Revenge of kiothedev: /* Energy [***X] */

= '''Not in a useable state do not use''' =
There is currently not enough clarification on how the standard is meant to be used along with other major issues
=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossing (Multiple/universal roadtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter the primary roadtype's first letter in a crossing between roadtypes (e.g. "XRBN" for a road and pipeline crossing). Please understand that as of this writing, the standardized roadtype scheme cannot yet account for more than two crossing roadtypes with the same primary roadtype. Finally, as of this writing, only some combination of a road, a pipeline, eyecandy or (potentially) a system not yet given a label can justify use of the "X" label.
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Junction/Crossover (Multiple/universal railtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter the primary tramtype's first letter in a junction tramtype (e.g. "XRBN" for light rail with bike lanes). Please understand that as of this writing, the standardized roadtype scheme cannot yet account for more than two crossing tramtypes with the same primary tramtype. If there is no primary tramtype (such as a "universal" tramtype or a tramtype with more than two systems in the junction) then it is recommended to use a lowercase x as the second letter.
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". It is suggested that roadtype and tramtype speeds use capital letters (A-Z) and roadtypes and tramtypes with specific features use lowercase letters (a-z). Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), roadside Infrastructure (Utility poles, fences, etc.), or Irrelevant
''For eyecandy and for underground infrastructure with compatibility toward certain vehicle sets, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains (high-voltage, off-road, no lighting)
| X, then S, then i, then G, then E
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then i, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Talk:Standardized Roadtype Scheme

2023-09-18T03:24:14Z

Revenge of kiothedev: Created page with "To Brickblock1 and anyone else who is concerned: hi its "~~~~" sorry for making changes without asking, i did not know about discussion topic and i not have any intent to forc..."

To Brickblock1 and anyone else who is concerned: hi its "[[User:Revenge of kiothedev|Revenge of kiothedev]] ([[User talk:Revenge of kiothedev|talk]]) 03:24, 18 September 2023 (UTC)" sorry for making changes without asking, i did not know about discussion topic and i not have any intent to force change only suggest useful additions

Standardized Railtype Scheme

2023-09-16T08:27:10Z

Revenge of kiothedev: /* Track gauge and type class [X***] */

This railtype label scheme aims to bring order to the uncontrolled growth of railtype labels. It groups the rail types into what matters from a technical perspective. The scheme provides a standardized way of defining railtype labels, based on track gauge and type, speed class, allowable axle weight and electrification type.

It is the explicit intent of this scheme to decouple track sets from vehicle sets to facilitate easy mixing. This way the player can select a track set of choice to go with a train set of choice. It allows the player to play with or without axle load classes, or with or without speed limit classes, simply by loading a track set that does or does not provide these features. In some cases it will also be possible to combine niche track sets, for instance a standard gauge track set with a narrow gauge and a metro track set.

== The Label Scheme ==
A railtype label consists of four characters. In this scheme, each position has a different purpose:
# Track gauge and type class (e.g. standard gauge rail, narrow gauge rail, monorail)
# Speed limit class
# Axle load class (maximum allowed axle weight for this track)
# Energy source type class

In the next sections, each of the four positions will be explained.

=== Track gauge and type class [X***] ===
The first position in the railtype label defines track gauge and/or track type class. The following classes are currently defined:

{|
! !!Track type/gauge
|-
|S ||Standard gauge rail
|-
|B ||Broad gauge rail (Also used by "ultra-broad" fictional tracktype; As broad gauge is a rare tracktype, it may still be feasible to cement B for "ultra-broad" and assign realistic broad-gauge to lowercase b)
|-
|b ||Broad gauge rail (Originally assigned to uppercase B; As broad gauge is a rare tracktype, it may still be feasible to cement B for "ultra-broad" and assign realistic broad-gauge to lowercase b)
|-
|N ||Narrow gauge rail
|-
|n ||Secondary narrow gauge rail (e.g. when providing both metre and cape gauge, always use N in case of just one type of narrow gauge)
|-
|D ||Dual gauge rail, standard/broad gauge
|-
|d ||Dual gauge rail, standard/narrow gauge
|-
|s ||Multiple gauge rail, ultrabroad/broad/standard/narrow/secondary narrow guage
|-
|M ||Monorail
|-
|L ||Magnetic Levitation
|}

=== Speed limit class [*X**] ===
The second position in the railtype label defines the speed limit class. These classes do not map to a fixed numeric value, but are used to define an internal speed limit order for the track set. This means that if your track set has two different speed limits for track types that are otherwise identical, you'll use letters A and B here. In case of three different speed limits, use A, B and C. In case your track set does not employ speed limits, always use A. Train sets do not care about the speed limit, and will always set the lowest speed class, i.e. A.

This gives for instance the following options:

<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||no speed limits
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||high speed
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||medium speed
|-
|C ||high speed
|}
</div>
<div style="float:left;">
 etc. 
</div>
</div>
<div style="clear:left;"></div>

The speed limit class may also be used for some advanced features of the label scheme, like specialized track types and eyecandy purposes. Be careful not to break the compatibility with other sets when using the speed limit class for these purposes.

An example of a special use is rack rail. In the French set it is used to give rack rail engines a higher speed and TE than normal rail engines when used on rack rail. When defining trains with a special speed limit class, always allow a fallback to speed limit class A via the railtype table.

An example of eyecandy use are urban tracks. These are a variation of regular tracks, but with concrete ground tiles to better match the urban environment. Train sets must not define vehicles for eyecandy classes. If you think you have special vehicles that should only run on the eyecandy class, it is ''not'' eyecandy but a separate track gauge/type.

The following special and eyecandy classes have been defined so far:

{|
! !!Description !!Type !!Used by
|-
|A-H ||speed limits ||colspan="2"|reserved
|-
|R ||rack rail ||special ||French Set Rails
|-
|S ||subterranean ||eyecandy ||Metro Track Set
|-
|U ||urban ||eyecandy ||Metro Track Set
|}

=== Axle load class [**X*] ===
The third position defines the axle weight limit. Heavy trains cannot run on tracks with a low axle weight limit; these trains need more expensive tracks with a heigher weight limit. There are five axle load classes '''A''' through '''E'''. '''A''' is for the lowest axle load limit, '''E''' for the highest. The exact axle load attached to each class is relative to the track gauge/type and trains in the set.

A train set should set the appropriate axle weight for each train via the railtype label, as to make the set work with track sets that do provide tracks with different weight limits, even if you don't care about it for your trainset. Split all vehicles of a certain track gauge/type into five groups of similar axle weight. The group with the lowest axle weights will get class '''A''', the second lowest class '''B''', etc. up to the group with the highest axle weights which will get class '''E'''. Do the same for the other track gauge/types if your train set has those.

A track set does not have to provide a dedicated track type for each axle weight limit. A track set that does not provide a dedicated track for each axle load class, must make sure to map all undefined axle load classes to a real railtype using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]]. This way a train set can rely on all labels for all axle load classes being available. Example: if you only want to provide 2 axle load classes for standard gauge unelectrified with no speed limits, you can map SA'''A'''N + SA'''B'''N to SA'''C'''N and SA'''D'''N to SA'''E'''N if the cost difference between the two railtypes is high, or SA'''A'''N to SA'''B'''N and SA'''C'''N + SA'''D'''N to SA'''E'''N if the cost difference is low.

If you don't want to provide any axle load classes in your track set, it doesn't really matter what axle load class you choose for the track, as you'll be mapping all other classes to this track anyways. But the lowest or highest class are the obvious choice. Example: if your track set only provides narrow gauge unelectrified track with no speed limits and no axle load limits, you may use NA'''A'''N for the track label, and provide NA'''B'''N, NA'''C'''N, NA'''D'''N, NA'''E'''N in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

If you need more than five axle load class, you may use lowercase letters for very low axle loads and continue the uppercase letters for very high axle loads. Be advised that your train set may not assume the existance of any other class than '''A''' through '''E''', so when the range make sure to program your railtype table such that trains with such a class will fall back to class '''A''' or '''E'''. If you make a track set with an extended range, be aware that not all train sets will define trains for these tracks. In general: only do this in case of a train set with a matching track set.

For the lowercase letters, '''b''' is lower than '''a''', so for increasing axle load limits: b < a < A < B < C etc.

Note that the axle load classes never map to a specific weight in tonnes. For that reason it does not make sense to add a numeric value for the axle load to the name of a track type or in the extended purchase info of a train. Instead use the relative expressions 'very low', 'low', 'medium', 'high' and 'very high' or use the class letters directly.

=== Energy source type class [***X] ===
The last position defines the energy source type class. This is split in generic energy source types like overhead wires and third rail and specialized types like alternating and direct current.

A track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

A vehicle set that uses specialized types should define a generic type as fallback, via the railtype table. If such a fallback is omitted, please note that certain vehicles may be unavailable depending on track set loaded.

{|
! !!Generic energy type classes
|-
|N ||no electrification
|-
|E ||overhead wires/catenary electrification
|-
|3 ||3rd rail electrification
|}

{|
! !!Specialized energy type classes !!Vehicle set fallback
|-
|Z ||3rd rail and catenary electrification || 3 or E
|-
|4 ||4th rail electrification || 3
|-
|Y ||4th rail and catenary electrification || 4 or E
|-
|T ||[http://en.wikipedia.org/wiki/Three-phase_AC_railway_electrification three phase AC electrification] || E
|-
| colspan="3" |  
|-
|D ||DC catenary electrification || E
|-
|d ||low voltage DC catenary electrification (only when D also used in set) || First A then E
|-
|A ||AC catenary electrification || E
|-
|a ||low voltage AC catenary electrification (only when A also used in set) || First A then E
|}

If you want multi-voltage/current vehicles in your set (i.e. a train that can run on both AC and DC current), you have to define a dedicated railtype for those vehicles. Without the railtype, it's not possible to define vehicles with this property. If you only have vehicles that can run on either one type of voltage/current or on all types of voltage/current (e.g. a 2-system if you only have '''A''' and '''D''' tracks, or a 4-system in case of all '''A''', '''a''', '''D''' and '''d'''), then use the generic class '''E''' for vehicles that should be able to run on all different voltage/currents. Also the track set needs to have one at least one railtype with class '''E''' defined.

Note that if you want more than one type of multi-voltage/current, you'll quickly get a combinatory explosion of railtype labels, so plan carefully or do not attempt it. For every different multi-voltage/current vehicle type a dedicated railtype is needed. If you want all possible combinations, then you need to define an additional 8 classes. It is not recommended to make your train/track set this complicated.

Example approach for a 4-system set, with trains that can run on either one or all systems:
* '''E''': generic catenary-powered electric engines. "universal" [4-system] if any of '''D'''/'''d'''/'''A'''/'''a''' are defined.
* '''A''': generic AC catenary electric engines. 25kV only if '''a''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''A''';
* '''a''': 15kV AC catenary electric engines. Only defined if '''A''' also defined. Vehicle sets should use '''A''' and '''E''' as fallback, if defining an engine for '''a''';
* '''D''': generic DC catenary electric engines. 3kV if '''d''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''D''';
* '''d''': 1.5kV DC catenary electric engines. Only defined if '''D''' also defined. Vehicle sets should use '''D''' and '''E''' as fallback, if defining an engine for '''d'''.
For a 2-system set, you can simply drop '''a''' and '''d'''.

=== Standard labels: RAIL, ELRL, MONO, MGLV ===
It's not possible to undefine the standard railtypes RAIL, ELRL, MONO and MGLV. The game will always add those if there are vehicles defined for these track types. As a result, for a track set it's best not to ignore those standard labels, but rather work with them and define them in the set. If your track set does not have monorail or maglev tracks, there of course is no need to define those. But if your track set defines anything that resembles unelectrified or electrified rail, you should use the RAIL and ELRL labels. Matching labels from the above scheme will then be defined in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

As vehicles from NewGRFs that do not use explicit railtypes will end up on these standard railtypes, you should use RAIL instead of whatever type could be regarded as the most commonly used unelectrified type, ELRL instead of the most commonly used electrified type and so on. The label according to this scheme is then set as an alternate.

== Summary for track sets ==
This section summarizes the above for track sets.

; [X***] Track gauge and type class
* Define at least one track type for every track gauge/type class you want in your set.
* If you only provide tracks for one gauge/type, consider leaving some free railtypes so a player can load an additional set for some other type.
; [*X**] Speed limit class
* Make sure class A is always available, either directly or via an alternate label.
* Use only class A if you don't want speed limits;
* With speed limits, A is the lowest speed limit. Continue with B, C, etc. for increasing speed limits;
* The speed class can also be used to implement additional eye-candy track types, use letters higher in the alphabet for this.
; [**X*] Axle load class
* Always define all classes A through E for every track type class / electrification combination, either:
** Directly via a real railtype definition;
** Indirectly via the alternate rail type label list, property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].
* Extend the predefined classes only if you also provide a train set that makes use of these.
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via property 1D.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Always define the standard labels when possible, instead of what would be the equivalent of the standard label in this scheme.
* Map the equivalent labels from this scheme to the standard labels using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

Or, put differently, for each gauge/type, select one or more energy source types. For each type/energy combination provide all axle load classes for the speed class "A", either as a real type or as an alternate of another type. Provide more types with a different speed letter if you want to provide several different speeds or other eye-candy tracks.

== Summary for train sets ==
This section summarizes the above for train sets.

; [X***] Track gauge and type class
* Use the track type class that matches the vehicle;
* Define a fallback type via the railtype table in case you want the vehicle to be available on a different track if no matching track set is loaded.
** Specialized subtypes like "n" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "N").
; [*X**] Speed limit class
* Always use class A for every vehicle.
; [**X*] Axle load class
* Use all classes A through E according to the maximum axle weight of the vehicle.
* Extend the predefined classes only if you also provide a track set that makes use of these;
** When extending the predefined classes A through E, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Define a fallback type to the standard labels via the railtype table in case you want the vehicle to be available on the standard tracks if no matching track set is loaded.

Be as specific as you want when selecting the railtype, it is the job of the track set to select a playable, reduced subset out of all possible type combinations.

== In case you're not convinced by this scheme ==
Adopting this scheme gives the player freedom to use any track set in combination with any train set that follow the scheme.

This means that you can make your train set compatible with track sets that provide axle load classes, and track sets that provide speed limits, and at the same time with track sets that provide none of this. This way, the player can decide to play with or without axle load classes, or with or without speed limits, simply by loading a track set that does or does not provide these features.

And for your track set, it means that you can make it as simple or as complicated as you want (within the 64 track type limit), while not having to worry about compatibility with train sets.

Still not convinced? Feel free to use railtype labels of your own, but know that you will likely come to regret that at some point in the future.

==Forum topic==
If you want to discuss the standardized railtype scheme or have any questions about it, you can visit [http://www.tt-forums.net/viewtopic.php?t=59379 the forum topic].

="Innsbruck 2022 Convention" for partial compliance=

This is really esoteric, but eh. It was the product of long discussion / debate / argument / reasoning between grf authors.

1. The Standardized Railtype Scheme '''is a useful tool''' for providing reliable compatibility between train grfs and railtype grfs.

2. The '''axle load class''' in the scheme presents a number of issues for compliance.

2.1. Over 10 years since the scheme was standardised, not many train grfs implement multiple axle load classes '''as required by the scheme'''. Known examples that '''do''' comply include Dutch Train Set, French Narrow Gauge Trains, and Finnish Trains.

2.2. Elements of the axle load rules have proven hard to interpret. For example:

* is it compliant to use ''fewer'' than 5 classes in a train grf? There is a lack of consensus on this.
* axle load is only one of many factors that govern whether a vehicle is compatible with a route, for example loading gauge, minimum curve, signalling types etc

2.3. Meanwhile ''multiple existing train grfs use class ''A'' for the axle load for all trains'' (except where relying on default railtypes such as RAIL and ELRL).

'''3. The Innsbruck 2022 Convention uses class ''A'' for axle load for '''all''' trains in a train grf (except where relying on default railtypes such as RAIL and ELRL).'''

This is '''not''' fully compliant with the Standardized Railtype Scheme and does not claim to be.

However train grfs using the Innsbruck 2022 Convention are ''broadly compatible'' with railtype grfs using the Standardized Railtype Scheme.

Obligatory XKCD link about 'standards': https://xkcd.com/927/

===Known issues===

Known problems are that trains using only class 'A' may limit the ability of railtype grf authors to achieve their design goals for separating railtypes by axle load.
But on reflection, it can be seen that a train grf might not be able to provide a broad enough range of vehicles to cover at least 5 axle load classes.

3.1. The Innsbruck 2022 Convention is '''not''' appropriate for train grf authors who wish to provide more than one axle load class.

3.2. The Innsbruck 2022 Convention treats the meaning of class ''A'' as ''undefined'', ''ignored'' or ''compatible with most restricted railtype'' for axle load.

Axle load class ''A'' '''cannot''' be safely interpreted as ''universal'' because from the perspective of a railtype grf ''A'' is ''most restricted railtype'', where ''universal'' is better represented as ''least restricted railtype''. Depending how many axle load classes are in use by the railtype grf, this could be class ''B'', ''C'', ''D'', ''E'' etc. To illustrate this issue, take the following scenario

* railtype grf defines axle loads ''A'' to ''E''. In this case the railtype grf author intends that ''A'' is compatible with the smallest range of vehicles, ''E'' is compatible with the largest range of vehicles, and ''B'', ''C'' and ''D'' are compatible with some intermediate ranges of vehicles
* but the vehicle grf author has defined all vehicles to be axle load ''A'' in an attempt to express this vehicle is ''universal''. The result in the game is that an identical range of vehicles will be compatible with railtypes ''A'' to ''E''.

This is clearly '''not''' the intended outcome of the railtype author. But nor is it clear within the spec that the vehicle author has particularly done anything wrong.

It ''would'' be possible to use railtype availability testing to adjust the vehicle property 05 (track_type) to fit the highest defined axle load (''E'' in this example case), but this is not insignificant work, and it's unlikely to be widely adopted by vehicle grf authors. Nor would this solution achieve ''universal'' as all vehicles in vehicle grf then would be incompatible with types ''A'' through ''D''.

3.3. When the Innsbruck 2022 Convention is used, this '''does not prevent''' a train grf being extended in some future release to achieve full compliance with Standardized Railtype Scheme. ''That choice remains with train grf authors''.

3.4. If 2012 could be revisited, providing an optional ''_'' axle load class in the Standardized Railtype Scheme for ''undefined'' would have been preferable, but as of 2022, ''A'' is already widely used for this purpose, and time travel is not known to be possible.

Standardized Railtype Scheme

2023-09-16T08:23:02Z

Revenge of kiothedev: /* Track gauge and type class [X***] */

This railtype label scheme aims to bring order to the uncontrolled growth of railtype labels. It groups the rail types into what matters from a technical perspective. The scheme provides a standardized way of defining railtype labels, based on track gauge and type, speed class, allowable axle weight and electrification type.

It is the explicit intent of this scheme to decouple track sets from vehicle sets to facilitate easy mixing. This way the player can select a track set of choice to go with a train set of choice. It allows the player to play with or without axle load classes, or with or without speed limit classes, simply by loading a track set that does or does not provide these features. In some cases it will also be possible to combine niche track sets, for instance a standard gauge track set with a narrow gauge and a metro track set.

== The Label Scheme ==
A railtype label consists of four characters. In this scheme, each position has a different purpose:
# Track gauge and type class (e.g. standard gauge rail, narrow gauge rail, monorail)
# Speed limit class
# Axle load class (maximum allowed axle weight for this track)
# Energy source type class

In the next sections, each of the four positions will be explained.

=== Track gauge and type class [X***] ===
The first position in the railtype label defines track gauge and/or track type class. The following classes are currently defined:

{|
! !!Track type/gauge
|-
|S ||Standard gauge rail
|-
|B ||Broad gauge rail (Also used by "ultra-broad" fictional tracktype; As broad gauge is a rare tracktype, it may still be feasible to cement B for "ultra-broad" and assign realistic broad-gauge to lowercase b)
|-
|b ||Broad gauge rail (Originally assigned to uppercase B; As broad gauge is a rare tracktype, it may still be feasible to cement B for "ultra-broad" and assign realistic broad-gauge to lowercase b)
|-
|N ||Narrow gauge rail
|-
|n ||Secondary narrow gauge rail (e.g. when providing both metre and cape gauge, always use N in case of just one type of narrow gauge)
|-
|D ||Dual gauge rail, standard+broad gauge
|-
|d ||Dual gauge rail, standard+narrow gauge
|-
|s ||Multiple gauge rail, broad+standard+narrow
|-
|M ||Monorail
|-
|L ||Magnetic Levitation
|}

=== Speed limit class [*X**] ===
The second position in the railtype label defines the speed limit class. These classes do not map to a fixed numeric value, but are used to define an internal speed limit order for the track set. This means that if your track set has two different speed limits for track types that are otherwise identical, you'll use letters A and B here. In case of three different speed limits, use A, B and C. In case your track set does not employ speed limits, always use A. Train sets do not care about the speed limit, and will always set the lowest speed class, i.e. A.

This gives for instance the following options:

<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||no speed limits
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||high speed
|}
</div>
<div style="float:left;">
 OR 
</div>
</div>
<div style="float:left;">
<div style="float:left;">
{|
! !!Speed limit class
|-
|A ||low speed
|-
|B ||medium speed
|-
|C ||high speed
|}
</div>
<div style="float:left;">
 etc. 
</div>
</div>
<div style="clear:left;"></div>

The speed limit class may also be used for some advanced features of the label scheme, like specialized track types and eyecandy purposes. Be careful not to break the compatibility with other sets when using the speed limit class for these purposes.

An example of a special use is rack rail. In the French set it is used to give rack rail engines a higher speed and TE than normal rail engines when used on rack rail. When defining trains with a special speed limit class, always allow a fallback to speed limit class A via the railtype table.

An example of eyecandy use are urban tracks. These are a variation of regular tracks, but with concrete ground tiles to better match the urban environment. Train sets must not define vehicles for eyecandy classes. If you think you have special vehicles that should only run on the eyecandy class, it is ''not'' eyecandy but a separate track gauge/type.

The following special and eyecandy classes have been defined so far:

{|
! !!Description !!Type !!Used by
|-
|A-H ||speed limits ||colspan="2"|reserved
|-
|R ||rack rail ||special ||French Set Rails
|-
|S ||subterranean ||eyecandy ||Metro Track Set
|-
|U ||urban ||eyecandy ||Metro Track Set
|}

=== Axle load class [**X*] ===
The third position defines the axle weight limit. Heavy trains cannot run on tracks with a low axle weight limit; these trains need more expensive tracks with a heigher weight limit. There are five axle load classes '''A''' through '''E'''. '''A''' is for the lowest axle load limit, '''E''' for the highest. The exact axle load attached to each class is relative to the track gauge/type and trains in the set.

A train set should set the appropriate axle weight for each train via the railtype label, as to make the set work with track sets that do provide tracks with different weight limits, even if you don't care about it for your trainset. Split all vehicles of a certain track gauge/type into five groups of similar axle weight. The group with the lowest axle weights will get class '''A''', the second lowest class '''B''', etc. up to the group with the highest axle weights which will get class '''E'''. Do the same for the other track gauge/types if your train set has those.

A track set does not have to provide a dedicated track type for each axle weight limit. A track set that does not provide a dedicated track for each axle load class, must make sure to map all undefined axle load classes to a real railtype using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]]. This way a train set can rely on all labels for all axle load classes being available. Example: if you only want to provide 2 axle load classes for standard gauge unelectrified with no speed limits, you can map SA'''A'''N + SA'''B'''N to SA'''C'''N and SA'''D'''N to SA'''E'''N if the cost difference between the two railtypes is high, or SA'''A'''N to SA'''B'''N and SA'''C'''N + SA'''D'''N to SA'''E'''N if the cost difference is low.

If you don't want to provide any axle load classes in your track set, it doesn't really matter what axle load class you choose for the track, as you'll be mapping all other classes to this track anyways. But the lowest or highest class are the obvious choice. Example: if your track set only provides narrow gauge unelectrified track with no speed limits and no axle load limits, you may use NA'''A'''N for the track label, and provide NA'''B'''N, NA'''C'''N, NA'''D'''N, NA'''E'''N in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

If you need more than five axle load class, you may use lowercase letters for very low axle loads and continue the uppercase letters for very high axle loads. Be advised that your train set may not assume the existance of any other class than '''A''' through '''E''', so when the range make sure to program your railtype table such that trains with such a class will fall back to class '''A''' or '''E'''. If you make a track set with an extended range, be aware that not all train sets will define trains for these tracks. In general: only do this in case of a train set with a matching track set.

For the lowercase letters, '''b''' is lower than '''a''', so for increasing axle load limits: b < a < A < B < C etc.

Note that the axle load classes never map to a specific weight in tonnes. For that reason it does not make sense to add a numeric value for the axle load to the name of a track type or in the extended purchase info of a train. Instead use the relative expressions 'very low', 'low', 'medium', 'high' and 'very high' or use the class letters directly.

=== Energy source type class [***X] ===
The last position defines the energy source type class. This is split in generic energy source types like overhead wires and third rail and specialized types like alternating and direct current.

A track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

A vehicle set that uses specialized types should define a generic type as fallback, via the railtype table. If such a fallback is omitted, please note that certain vehicles may be unavailable depending on track set loaded.

{|
! !!Generic energy type classes
|-
|N ||no electrification
|-
|E ||overhead wires/catenary electrification
|-
|3 ||3rd rail electrification
|}

{|
! !!Specialized energy type classes !!Vehicle set fallback
|-
|Z ||3rd rail and catenary electrification || 3 or E
|-
|4 ||4th rail electrification || 3
|-
|Y ||4th rail and catenary electrification || 4 or E
|-
|T ||[http://en.wikipedia.org/wiki/Three-phase_AC_railway_electrification three phase AC electrification] || E
|-
| colspan="3" |  
|-
|D ||DC catenary electrification || E
|-
|d ||low voltage DC catenary electrification (only when D also used in set) || First A then E
|-
|A ||AC catenary electrification || E
|-
|a ||low voltage AC catenary electrification (only when A also used in set) || First A then E
|}

If you want multi-voltage/current vehicles in your set (i.e. a train that can run on both AC and DC current), you have to define a dedicated railtype for those vehicles. Without the railtype, it's not possible to define vehicles with this property. If you only have vehicles that can run on either one type of voltage/current or on all types of voltage/current (e.g. a 2-system if you only have '''A''' and '''D''' tracks, or a 4-system in case of all '''A''', '''a''', '''D''' and '''d'''), then use the generic class '''E''' for vehicles that should be able to run on all different voltage/currents. Also the track set needs to have one at least one railtype with class '''E''' defined.

Note that if you want more than one type of multi-voltage/current, you'll quickly get a combinatory explosion of railtype labels, so plan carefully or do not attempt it. For every different multi-voltage/current vehicle type a dedicated railtype is needed. If you want all possible combinations, then you need to define an additional 8 classes. It is not recommended to make your train/track set this complicated.

Example approach for a 4-system set, with trains that can run on either one or all systems:
* '''E''': generic catenary-powered electric engines. "universal" [4-system] if any of '''D'''/'''d'''/'''A'''/'''a''' are defined.
* '''A''': generic AC catenary electric engines. 25kV only if '''a''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''A''';
* '''a''': 15kV AC catenary electric engines. Only defined if '''A''' also defined. Vehicle sets should use '''A''' and '''E''' as fallback, if defining an engine for '''a''';
* '''D''': generic DC catenary electric engines. 3kV if '''d''' also defined. Vehicle sets should use '''E''' as fallback, if defining an engine for '''D''';
* '''d''': 1.5kV DC catenary electric engines. Only defined if '''D''' also defined. Vehicle sets should use '''D''' and '''E''' as fallback, if defining an engine for '''d'''.
For a 2-system set, you can simply drop '''a''' and '''d'''.

=== Standard labels: RAIL, ELRL, MONO, MGLV ===
It's not possible to undefine the standard railtypes RAIL, ELRL, MONO and MGLV. The game will always add those if there are vehicles defined for these track types. As a result, for a track set it's best not to ignore those standard labels, but rather work with them and define them in the set. If your track set does not have monorail or maglev tracks, there of course is no need to define those. But if your track set defines anything that resembles unelectrified or electrified rail, you should use the RAIL and ELRL labels. Matching labels from the above scheme will then be defined in property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

As vehicles from NewGRFs that do not use explicit railtypes will end up on these standard railtypes, you should use RAIL instead of whatever type could be regarded as the most commonly used unelectrified type, ELRL instead of the most commonly used electrified type and so on. The label according to this scheme is then set as an alternate.

== Summary for track sets ==
This section summarizes the above for track sets.

; [X***] Track gauge and type class
* Define at least one track type for every track gauge/type class you want in your set.
* If you only provide tracks for one gauge/type, consider leaving some free railtypes so a player can load an additional set for some other type.
; [*X**] Speed limit class
* Make sure class A is always available, either directly or via an alternate label.
* Use only class A if you don't want speed limits;
* With speed limits, A is the lowest speed limit. Continue with B, C, etc. for increasing speed limits;
* The speed class can also be used to implement additional eye-candy track types, use letters higher in the alphabet for this.
; [**X*] Axle load class
* Always define all classes A through E for every track type class / electrification combination, either:
** Directly via a real railtype definition;
** Indirectly via the alternate rail type label list, property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].
* Extend the predefined classes only if you also provide a train set that makes use of these.
; [***X] Energy source type class
* If your set only uses specialized classes, always map the generic classes to the closest matching specialized type via property 1D.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Always define the standard labels when possible, instead of what would be the equivalent of the standard label in this scheme.
* Map the equivalent labels from this scheme to the standard labels using property [[Action0/Railtypes#Alternate_rail_type_labels_.281D.29|1D (NFO)]] or [[NML:Railtypes#Railtype_properties|alternative_railtype_list (NML)]].

Or, put differently, for each gauge/type, select one or more energy source types. For each type/energy combination provide all axle load classes for the speed class "A", either as a real type or as an alternate of another type. Provide more types with a different speed letter if you want to provide several different speeds or other eye-candy tracks.

== Summary for train sets ==
This section summarizes the above for train sets.

; [X***] Track gauge and type class
* Use the track type class that matches the vehicle;
* Define a fallback type via the railtype table in case you want the vehicle to be available on a different track if no matching track set is loaded.
** Specialized subtypes like "n" might not always be available. If you want those vehicles to be still available then, fall back the the generic class (e.g. "N").
; [*X**] Speed limit class
* Always use class A for every vehicle.
; [**X*] Axle load class
* Use all classes A through E according to the maximum axle weight of the vehicle.
* Extend the predefined classes only if you also provide a track set that makes use of these;
** When extending the predefined classes A through E, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; [***X] Energy source type class
* Use the energy source type class that matches the vehicle;
* When using specialized classes, define a fallback type via the railtype table in case you want the vehicle to be available if no matching track set is loaded.
; Standard labels [RAIL, ELRL, MONO, MGLV]
* Define a fallback type to the standard labels via the railtype table in case you want the vehicle to be available on the standard tracks if no matching track set is loaded.

Be as specific as you want when selecting the railtype, it is the job of the track set to select a playable, reduced subset out of all possible type combinations.

== In case you're not convinced by this scheme ==
Adopting this scheme gives the player freedom to use any track set in combination with any train set that follow the scheme.

This means that you can make your train set compatible with track sets that provide axle load classes, and track sets that provide speed limits, and at the same time with track sets that provide none of this. This way, the player can decide to play with or without axle load classes, or with or without speed limits, simply by loading a track set that does or does not provide these features.

And for your track set, it means that you can make it as simple or as complicated as you want (within the 64 track type limit), while not having to worry about compatibility with train sets.

Still not convinced? Feel free to use railtype labels of your own, but know that you will likely come to regret that at some point in the future.

==Forum topic==
If you want to discuss the standardized railtype scheme or have any questions about it, you can visit [http://www.tt-forums.net/viewtopic.php?t=59379 the forum topic].

="Innsbruck 2022 Convention" for partial compliance=

This is really esoteric, but eh. It was the product of long discussion / debate / argument / reasoning between grf authors.

1. The Standardized Railtype Scheme '''is a useful tool''' for providing reliable compatibility between train grfs and railtype grfs.

2. The '''axle load class''' in the scheme presents a number of issues for compliance.

2.1. Over 10 years since the scheme was standardised, not many train grfs implement multiple axle load classes '''as required by the scheme'''. Known examples that '''do''' comply include Dutch Train Set, French Narrow Gauge Trains, and Finnish Trains.

2.2. Elements of the axle load rules have proven hard to interpret. For example:

* is it compliant to use ''fewer'' than 5 classes in a train grf? There is a lack of consensus on this.
* axle load is only one of many factors that govern whether a vehicle is compatible with a route, for example loading gauge, minimum curve, signalling types etc

2.3. Meanwhile ''multiple existing train grfs use class ''A'' for the axle load for all trains'' (except where relying on default railtypes such as RAIL and ELRL).

'''3. The Innsbruck 2022 Convention uses class ''A'' for axle load for '''all''' trains in a train grf (except where relying on default railtypes such as RAIL and ELRL).'''

This is '''not''' fully compliant with the Standardized Railtype Scheme and does not claim to be.

However train grfs using the Innsbruck 2022 Convention are ''broadly compatible'' with railtype grfs using the Standardized Railtype Scheme.

Obligatory XKCD link about 'standards': https://xkcd.com/927/

===Known issues===

Known problems are that trains using only class 'A' may limit the ability of railtype grf authors to achieve their design goals for separating railtypes by axle load.
But on reflection, it can be seen that a train grf might not be able to provide a broad enough range of vehicles to cover at least 5 axle load classes.

3.1. The Innsbruck 2022 Convention is '''not''' appropriate for train grf authors who wish to provide more than one axle load class.

3.2. The Innsbruck 2022 Convention treats the meaning of class ''A'' as ''undefined'', ''ignored'' or ''compatible with most restricted railtype'' for axle load.

Axle load class ''A'' '''cannot''' be safely interpreted as ''universal'' because from the perspective of a railtype grf ''A'' is ''most restricted railtype'', where ''universal'' is better represented as ''least restricted railtype''. Depending how many axle load classes are in use by the railtype grf, this could be class ''B'', ''C'', ''D'', ''E'' etc. To illustrate this issue, take the following scenario

* railtype grf defines axle loads ''A'' to ''E''. In this case the railtype grf author intends that ''A'' is compatible with the smallest range of vehicles, ''E'' is compatible with the largest range of vehicles, and ''B'', ''C'' and ''D'' are compatible with some intermediate ranges of vehicles
* but the vehicle grf author has defined all vehicles to be axle load ''A'' in an attempt to express this vehicle is ''universal''. The result in the game is that an identical range of vehicles will be compatible with railtypes ''A'' to ''E''.

This is clearly '''not''' the intended outcome of the railtype author. But nor is it clear within the spec that the vehicle author has particularly done anything wrong.

It ''would'' be possible to use railtype availability testing to adjust the vehicle property 05 (track_type) to fit the highest defined axle load (''E'' in this example case), but this is not insignificant work, and it's unlikely to be widely adopted by vehicle grf authors. Nor would this solution achieve ''universal'' as all vehicles in vehicle grf then would be incompatible with types ''A'' through ''D''.

3.3. When the Innsbruck 2022 Convention is used, this '''does not prevent''' a train grf being extended in some future release to achieve full compliance with Standardized Railtype Scheme. ''That choice remains with train grf authors''.

3.4. If 2012 could be revisited, providing an optional ''_'' axle load class in the Standardized Railtype Scheme for ''undefined'' would have been preferable, but as of 2022, ''A'' is already widely used for this purpose, and time travel is not known to be possible.

Standardized Roadtype Scheme

2023-09-14T09:27:59Z

Revenge of kiothedev:

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossing (Multiple/universal roadtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter the primary roadtype's first letter in a crossing between roadtypes (e.g. "XRBN" for a road and pipeline crossing). Please understand that as of this writing, the standardized roadtype scheme cannot yet account for more than two crossing roadtypes with the same primary roadtype. Finally, as of this writing, only some combination of a road, a pipeline, eyecandy or (potentially) a system not yet given a label can justify use of the "X" label.
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Junction/Crossover (Multiple/universal railtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter the primary tramtype's first letter in a junction tramtype (e.g. "XRBN" for light rail with bike lanes). Please understand that as of this writing, the standardized roadtype scheme cannot yet account for more than two crossing tramtypes with the same primary tramtype. If there is no primary tramtype (such as a "universal" tramtype or a tramtype with more than two systems in the junction) then it is recommended to use a lowercase x as the second letter.
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". It is suggested that roadtype and tramtype speeds use capital letters (A-Z) and roadtypes and tramtypes with specific features use lowercase letters (a-z). Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), Infrastructure, or Irrelevant
''For eyecandy and for underground infrastructure with compatibility toward certain vehicle sets, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains (with no lighting)
| X, then S, then i, then G, then E
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then i, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-08-02T02:02:12Z

Revenge of kiothedev: /* Speed / Feature [*X**] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossing (Multiple/universal roadtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter the primary roadtype's first letter in a crossing between roadtypes (e.g. "XRBN" for a road and pipeline crossing). Please understand that as of this writing, the standardized roadtype scheme cannot yet account for more than two crossing roadtypes with the same primary tramtype. Finally, as of this writing, only some combination of a road, a pipeline, eyecandy or (potentially) a system not yet given a label can justify use of the "X" label.
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Junction/Crossover (Multiple/universal railtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter the primary tramtype's first letter in a junction tramtype (e.g. "XRBN" for light rail with bike lanes). Please understand that as of this writing, the standardized roadtype scheme cannot yet account for more than two crossing roadtypes with the same primary tramtype. If there is no primary tramtype (such as a "universal" tramtype or a tramtype with more than two systems in the junction) then it is recommended to use a lowercase x as the second letter.
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". It is suggested that roadtype and tramtype speeds use capital letters (A-Z) and roadtypes and tramtypes with specific features use lowercase letters (a-z). Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), Infrastructure, or Irrelevant
''For eyecandy and for underground infrastructure with compatibility toward certain vehicle sets, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains (with no lighting)
| X, then S, then i, then G, then E
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then i, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-08-02T01:54:50Z

Revenge of kiothedev: /* Surface / Type [X***] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossing (Multiple/universal roadtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter the primary roadtype's first letter in a crossing between roadtypes (e.g. "XRBN" for a road and pipeline crossing). Please understand that as of this writing, the standardized roadtype scheme cannot yet account for more than two crossing roadtypes with the same primary tramtype. Finally, as of this writing, only some combination of a road, a pipeline, eyecandy or (potentially) a system not yet given a label can justify use of the "X" label.
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Junction/Crossover (Multiple/universal railtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter the primary tramtype's first letter in a junction tramtype (e.g. "XRBN" for light rail with bike lanes). Please understand that as of this writing, the standardized roadtype scheme cannot yet account for more than two crossing roadtypes with the same primary tramtype. If there is no primary tramtype (such as a "universal" tramtype or a tramtype with more than two systems in the junction) then it is recommended to use a lowercase x as the second letter.
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". it is suggested that roadtype and tramtype speeds use capital letters (A-Z) and roadtypes and tramtypes with specific features use lowercase letters (a-z). Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), Infrastructure, or Irrelevant
''For eyecandy and for underground infrastructure with compatibility toward certain vehicle sets, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains (with no lighting)
| X, then S, then i, then G, then E
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then i, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-08-02T01:49:29Z

Revenge of kiothedev: /* Surface / Type [X***] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossing (Multiple/universal roadtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter the primary roadtype in a crossing between roadtypes. Please understand that as of this writing, the standardized roadtype scheme cannot yet account for more than two crossing roadtypes with the same primary tramtype. Finally, as of this writing, only some combination of a road, a pipeline, eyecandy or (potentially) a system not yet given a label can justify use of the "X" label.
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Junction/Crossover (Multiple/universal railtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter a lowercase version of the primary tramtype ("r" for "R", "p" for "P", etc.) in a junction tramtype. If there is no primary tramtype (such as a "universal" tramtype or a tramtype with more than two systems in the junction) then it is recommended to use a lowercase x as the second letter.
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". it is suggested that roadtype and tramtype speeds use capital letters (A-Z) and roadtypes and tramtypes with specific features use lowercase letters (a-z). Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), Infrastructure, or Irrelevant
''For eyecandy and for underground infrastructure with compatibility toward certain vehicle sets, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains (with no lighting)
| X, then S, then i, then G, then E
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then i, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-08-02T01:37:18Z

Revenge of kiothedev: /* Surface / Type [X***] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossing (Multiple/universal roadtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter a lowercase version of the primary roadtype ("r" for "R", "p" for "P", etc.) in a crossover. As of this writing, only some combination of a road, a pipeline, eyecandy or (potentially) a system not yet given a label can justify use of the "X" label.
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Junction/Crossover (Multiple/universal railtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter a lowercase version of the primary tramtype ("r" for "R", "p" for "P", etc.) in a junction tramtype. If there is no primary tramtype (such as a "universal" tramtype or a tramtype with more than two systems in the junction) then it is recommended to use a lowercase x as the second letter.
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". it is suggested that roadtype and tramtype speeds use capital letters (A-Z) and roadtypes and tramtypes with specific features use lowercase letters (a-z). Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), Infrastructure, or Irrelevant
''For eyecandy and for underground infrastructure with compatibility toward certain vehicle sets, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains (with no lighting)
| X, then S, then i, then G, then E
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then i, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-08-02T01:36:51Z

Revenge of kiothedev: /* Surface / Type [X***] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossing (Multiple/universal roadtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter a lowercase version of the primary roadtype ("r" for "R", "p" for "P", etc.) in a crossover. Also note that only some combination of a road, a pipeline, eyecandy or (potentially) a system not yet given a label can justify use of the "X" label.
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Junction/Crossover (Multiple/universal railtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter a lowercase version of the primary tramtype ("r" for "R", "p" for "P", etc.) in a junction tramtype. If there is no primary tramtype (such as a "universal" tramtype or a tramtype with more than two systems in the junction) then it is recommended to use a lowercase x as the second letter.
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". it is suggested that roadtype and tramtype speeds use capital letters (A-Z) and roadtypes and tramtypes with specific features use lowercase letters (a-z). Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), Infrastructure, or Irrelevant
''For eyecandy and for underground infrastructure with compatibility toward certain vehicle sets, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains (with no lighting)
| X, then S, then i, then G, then E
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then i, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-08-02T01:34:34Z

Revenge of kiothedev: /* Surface / Type [X***] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossing (Multiple/universal roadtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter a lowercase version of the primary roadtype ("r" for "R", "p" for "P", etc.) in a crossover. Also note that only some combination of a road, a pipeline, eyecandy or (potentially) a system not yet given a label can justify use of the "X" label.
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Junction/Crossover (Multiple/universal railtypes)
| n/a
| '''''NOTE:''''' It is suggested to make the second letter a lowercase version of the primary tramtype ("r" for "R", "p" for "P", etc.) in a crossover. If there is no primary tramtype (such as a "universal" tramtype or a tramtype with more than two systems, )
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". it is suggested that roadtype and tramtype speeds use capital letters (A-Z) and roadtypes and tramtypes with specific features use lowercase letters (a-z). Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), Infrastructure, or Irrelevant
''For eyecandy and for underground infrastructure with compatibility toward certain vehicle sets, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains (with no lighting)
| X, then S, then i, then G, then E
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then i, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-08-01T23:53:04Z

Revenge of kiothedev: /* Speed / Feature [*X**] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". it is suggested that roadtype and tramtype speeds use capital letters (A-Z) and roadtypes and tramtypes with specific features use lowercase letters (a-z). Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), Infrastructure, or Irrelevant
''For eyecandy and for underground infrastructure with compatibility toward certain vehicle sets, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains (with no lighting)
| X, then S, then i, then G, then E
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then i, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T09:56:44Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), Infrastructure, or Irrelevant
''For eyecandy and for underground infrastructure with compatibility toward certain vehicle sets, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains (with no lighting)
| X, then S, then i, then G, then E
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then i, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T09:56:08Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), Infrastructure, or Irrelevant
''For eyecandy and for underground infrastructure with compatibility toward certain vehicle sets, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains (with no lighting)
| X, then S, then E, then G
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then i, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T08:43:26Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), Infrastructure, or Irrelevant
''For eyecandy and for underground infrastructure with compatibility toward certain vehicle sets, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains
| X, then S, then E, then G
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then i, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T08:42:44Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), Infrastructure, or Irrelevant
''For eyecandy and for underground infrastructure with compatibility with certain vehicle sets, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains
| X, then S, then E, then G
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then i, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T08:41:51Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), Infrastructure, or Irrelevant
''For eyecandy and for underground infrastructure with compatibility with certain vehicle sets, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains
| X, then S, then E, then G
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
''It is recommended to use '''EABi''' in alternate_roadtype_list for this roadtype''
| Crossover (Multiple/universal powered types)
''It is recommended to use '''EABi''' in alternate_tramtype_list for this tramtype''
| Z, then E, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T08:41:13Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), Infrastructure, or Irrelevant
''For eyecandy and for underground infrastructure with compatibility with certain vehicle sets, you should use '''EABX''', '''EABS''', '''EABG''' and '''EABE''' in the powered_roadtype_list or powered_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains
| X, then S, then E, then G
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
''You should use '''EABi''' in alternate_roadtype_list for this roadtype''
| Crossover (Multiple/universal powered types)
''You should use '''EABi''' in alternate_tramtype_list for this tramtype''
| Z, then E, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T08:28:06Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), or Irrelevant
''For eyecandy and underground infrastructure, you should use '''EABX''' in the alternate_roadtype_list or alternate_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains
| X, then S, then E, then G
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
''You should use '''EABi''' in alternate_roadtype_list for this roadtype''
| Crossover (Multiple/universal powered types)
''You should use '''EABi''' in alternate_tramtype_list for this tramtype''
| Z, then E, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T08:27:36Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, Illumination (Road Lighting), or Irrelevant
''For eyecandy and underground infrastructure''
''You should use '''EABX''' in the alternate_roadtype_list or alternate_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains
| X, then S, then E, then G
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
''You should use '''EABi''' in alternate_roadtype_list for this roadtype''
| Crossover (Multiple/universal powered types)
''You should use '''EABi''' in alternate_tramtype_list for this tramtype''
| Z, then E, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T08:08:21Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, or Irrelevant
''For eyecandy and underground infrastructure''
''You should use '''EABX''' in the alternate_roadtype_list or alternate_tramtype_list for this road/tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains
| X, then S, then E, then G
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
''You should use '''EABi''' in alternate_roadtype_list for this roadtype''
| Crossover (Multiple/universal powered types)
''You should use '''EABi''' in alternate_tramtype_list for this tramtype''
| Z, then E, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T08:06:30Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, or Irrelevant
''You should use '''EABX''' in the alternate_roadtype_list or alternate_tramtype_list for this tramtype''
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains
| X, then S, then E, then G
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
''You should use '''EABi''' in alternate_roadtype_list or alternate_tramtype_list for this tramtype''
| Crossover (Multiple/universal powered types)
''You should use '''EABi''' in alternate_roadtype_list or alternate_tramtype_list for this tramtype''
| Z, then E, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T08:05:12Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, or Irrelevant (You should use EABX in the alternate_roadtype_list or alternate_tramtype_list for this tramtype)
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains
| X, then S, then E, then G
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover
(Multiple/universal powered types, you should use EABi in alternate_roadtype_list or alternate_tramtype_list for this tramtype)
| Crossover
(Multiple/universal powered types, You should use EABi in alternate_roadtype_list or alternate_tramtype_list for this tramtype)
| Z, then E, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T08:04:46Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible, or Irrelevant (You should use EABX in the alternate_roadtype_list or alternate_tramtype_list for this tramtype)
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains
| X, then S, then E, then G
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types, you should use EABi in alternate_roadtype_list or alternate_tramtype_list for this tramtype)
| Crossover (Multiple/universal powered types, You should use EABi in alternate_roadtype_list or alternate_tramtype_list for this tramtype)
| Z, then E, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T07:58:35Z

Revenge of kiothedev: /* Terrain / Stability [**X*] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features (ONLY use if you wish for vehicles to not be able to travel on the roadtype/tramtype)
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains
| X, then S, then E, then G
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T07:55:58Z

Revenge of kiothedev: /* Terrain / Stability [**X*] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| b
| Eyecandy and other features
| n/a
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains
| X, then S, then E, then G
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T07:49:31Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains
| X, then S, then E, then G
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T07:47:12Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| i
| Invisible
| Invisible
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains
| S
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T07:27:32Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail
| n/a
|-
| P
| Pump/Pipeline
| Power Line/Mains
| S
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.

Standardized Roadtype Scheme

2023-07-30T06:43:50Z

Revenge of kiothedev: /* Energy [***X] */

=== Surface / Type [X***] ===
Describes the road surface / rail type and thus the vehicle type.

'''Roadtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Powered Roadtypes
! Recomended vehicle set fallbacks
|-
| R
| Public Road / Rail
| RI(S)
|
|-
| P
| Passenger-only
| RPI(S)
| R
|-
| G
| Guided busway
| RPG
| P then R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| RB(Z)
| R
|-
| W
| Waterway
| W
|-
| A
| Amphibious on road (hidden)
| RPI(S)W
| R
|-
| S
| Snowy or Iced Track
| S
|-
| a
| Amphibious on snow (hidden)
| SW
| S
|-
| Z
| Pedestrian Zone
| Z
|
|-
| E
| Eyecandy
|
|
|-
| p
| Pump/Pipeline
| RIZ
| I then R
|-
| X
| Crossover (Multiple/universal roadtypes)
| n/a
|
|}

'''Tramtype:'''

{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Tram)
! Powered Tramtypes
! Recomended vehicle set fallbacks

|-
| R
| Public Rail
| RI(M)
|-
| P
| Passenger-only
| RPI(M)
| R
|-
| I
| Industrial Site (ISR)
| I
| R
|-
| B
| Bicycle Lane
| (R)B
|
|-
| S
| Suspended Monorail
| S
|
|-
| M
| Metro
| M(RP)
|
|-
| O
| Trackless trams
| O
|
|-
| E
| Eyecandy/Electrical infrastructure
|
|
|-
| X
| Crossover (Multiple/universal railtypes)
| n/a
|
|}

It is the vehicle set's responsibility to implement fallbacks to other appropriate surfaces. It is also up to the author to decide if they want to do it or not.

It is up to the track set to implement all recommended roadtypes in the [[NML:Roadtypes#Roadtype_properties|powered_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|powered_tramtype_list (NML)]]. It is further advised to implement support for the roadtypes/tramtypes in brackets, if applicable.

Hidden roadtypes for compatibility should be implemented by road sets. It is up to the author to decide if they want to implement it as a hidden roadtype or not.

=== Speed / Feature [*X**] ===
Any character may be used for roads, but at least one road must have "A". Vehicles should use "A".

=== Terrain / Stability [**X*] ===
Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning
! Powered Roadtypes
|-
| a
| Very slow / rough / light
| aA
|-
| A
| Slow / rough / light
| aAB
|-
| B
| Regular
| ABC
|-
| C
| Fast / stable
| BCc
|-
| c
| Very fast / stable
| Cc
|}
If all classes aren't defined by the road set, the other ones should be in the [[NML:Roadtypes#Roadtype_properties|alternative_roadtype_list (NML)]]. The same goes for tramtypes: [[NML:Tramtypes#Tramtype_properties|alternative_tramtype_list (NML)]].

Road vehicle sets should not implement fallbacks for terrain / stability.

Classes "a" and "c" are entirely optional for road/tramtype sets and should under no circumstances be used by vehicles.

=== Energy [***X] ===
Describes the energy source of the track / vehicle.

'''Generic classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
|-
| N
| None
| None
|-
| E
| Overhead electrified (Catenary)
| Overhead electrified (Catenary)
|-
| G
| Ground electrified
| Ground electrified
|-
| Z
| Ground and overhead electrified
| Ground and overhead electrified
|}
'''Specialized classes:'''
{| class="wikitable"
|- style="font-style:italic;"
! Letter
! Meaning (Road)
! Meaning (Tram)
! Vehicle set fallback
|-
| 3
| n/a
| Third Rail
| G
|-
| 4
| n/a
| Fourth Rail
| 3 then G
|-
| C
| n/a
| Cable
| G
|-
| M
| n/a
| Suspended Monorail & Elevated Metro
| X, then S, then 4, then 3
|-
| P
| Pump/Pipeline
| Power Line/Mains
| S, then G, then E
|-
| S
| Smart infrastructure
| Smart infrastructure
| n/a
|-
| X
| Crossover (Multiple/universal powered types)
| Crossover (Multiple/universal powered types)
| Z, then E, then N
|}
A road or track set that only uses specialized types, should map the generic types to the most suitable specialized type in the set.

=== The default labels (ROAD, ELRL)===
It is up to the road set author to decide what labels should replace these, but it is recommended to choose RABN / RABE.

Vehicle set authors might need to add the default labels as a fallback. If not implemented, their vehicles won't show up on the default roads and/or tracks.