User:Brickblock1

From GRFSpecs
Jump to navigationJump to search

Standardized Roadtype Scheme

The main reason for the creation of this standard is to allow for better compatibility between road and vehicle sets. It's also made with the intent of limiting the amount of necessary hidden roadtypes this is mostly accomplished by moving the roadtypes for compatibility away from the vehicle sets to the roadset.

What the standard does not do!

The standard is not made to make different roadsets work together

The Label Scheme

A roadtype label consists of four characters. In this scheme, each position has a different purpose:

  1. Surface and type class (e.g. Road, water, ice)
  2. Speed and id Class
  3. Tier class (e.g. Off-road, Road, Highway/Motorway)
  4. Energy source type class

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

Surface and type class [X***]

The first position in the roadtypelabel defines surface and/or road type class. The following classes are currently defined:

Road surface/type
R Road
B Bike
I Ice
S Snow
W Water
X Water and ice (probably hidden)
X Ice and road (probably hidden)
X Water and road (probably hidden)
U Universal (probably hidden)

X is undecided

Road sets don't have to define all of the types, this means that the vehicle set might want to use an undefined road type. If that is the case those vehicles wouldn't be available which can be mitigated by falling back to another appropriate surface type. For example a bike using BABN would reasonably be able to run on regular roads, therefore making it fallback is completely reasonable.

Speed and id class [*X**]

This character can be anything which the roadtype set author wants but there must always be one road type with A in it as it is what all road vehicles should use.

Tier class [**X*]

There are three possible characters here:

  1. A Off-road/rough terrain
  2. B Regular city/county road
  3. C Highway/Motorway

B should be made compatible with both A and C while A and C are only compatible with B. When not all of the tiers are provided the ones that aren't should be in the alternative_roadtype_labels list, that way vehicles defined for them will still be able to run on the most similar type of road. Similarly when the surfaces have different amount of tiers B should be considered the main one.

Energy source type class [***X]

Currently the only standard types are E and N, Where E is electrified and N is not.

The standard label (ROAD)

It is up to the roadset artuor to decide what label this should replace but it is recommended to chose either RABN or RACN.

Vehicle set authors will need to add this as a fallback or else their vehicles won't show up on the default roads.

Standardized Road/Tram Type Scheme (Proposal version 5)

Surface / Type [X***]

Describes the road surface and thus the vehicle type.

Letter Meaning (Road) Powered Roadtypes Available to Tram
R Public Road / Rail RI(S) yes
P Passenger-only RPI(S) yes
I Industrial Site (ISR) I yes
B Bicycle Lane RBZ yes
W Waterway W no
A Amphibious on road (hidden) RPI(S)W no
S Snowy or Iced Track S no
a Amphibious on snow (hidden) SW no
Z Pedestrian Zone Z no

Speed / Feature [*X**]

Any character may be used for roads. Vehicles ahould use "A"

Terrain / Stability [**X*]

Describes the roughness of the road surface / trackbed stability, and thus the vehicle tier.

Letter Meaning (Road) Meaning (Tram) Powered Roadtypes
A Rough (Dirt) Unsupported (very light rail) AB
B Regular Regular Support ABC
C High-speed High-Speed Rail (heavy rail) BC

Energy [***X]

Describes the energy source of the road / vehicle. Generic classes:

Letter Meaning (Road) Meaning (Tram)
N None None
E Electrified (catenary) Electrified (catenary)
G Ground Electrified Ground Electrified

Specaliced classes:

Letter Meaning (Road) Meaning (Tram) Vehicle set fallback
3 n/a Third Rail G
C n/a Cable G