Before building a way, let us find the main requirements for it.
- Minimization of building cost
- Minimization of used space
|11.1||One-line way for one train
||One-line way for more than one train|
|11.3||Station for one-line way for more than one train
||11.4||Passing track for one-line way for loading and unloading stations|
|11.5||Passing track for one-line way for unloading stations
||11.6||Two one-line ways|
|11.7||Passing track for one-line way for unloading stations
||11.8||One-line ways T-junction. 2 to 1 variant|
|11.9||One-line ways T-junction. All to all variant
||11.10||One-line ways T-junction. All to all variant. Alternative|
|11.11||One-line ways intersection. Simple||11.12||One-line ways intersection. Advanced|
Beginning a new game, or building in-city station, it's often happens a lack of money or a lack of place. In this case building one-line way is a solution.
This solution can be used with single train per line or with a group of trains. In the second case passing track are used. The station's size and and the way of connecting a station to the way depend on available place and money. It consists of a station (A
), a depot before and after (usually the same depot) the station (E
) and a way to it (C
). Schemas 1.1
show some possible variants.
The number of passing tracks depends on the number of trains, but it's better to have more of them, than number of trains mines one. The distance between passing tracks has to be not too large to prevent long train's waiting. It's better not to build passing tracks fuhrer than 30 squares.
When the way is ended with unloading
stations on the one side and loading
station on the other, the priority for trains coming from loading stations can be simply achieved using schema 11.4
. In case of equal stations (for example passengers traffic between two cities), schema 11.5
is better. Represented solutions (11.4
) are incompatible and can't alternate.
In case of using schema 11.4
, exit signals on the loading station in-line block are required, as at unloading station represented on schema 1.7
When the number of trains increases, it's required to increase the way's capacity. In this case, two one-line ways are used. One for one direction and one for the other as it represented on schema 1.6
. Stations can be connected to two one-line ways with united station's enter and exit (schema 11.7
) or separated (Ro-Ro station
Known problem: when a trains comes in depot I and all the platforms become busy, a train can go to way from the station L and be lost.
Two one-line ways with fixed directions is also a way. Such ways can be connected to each other. First case - ways merging, represented at schema 11.8
. In this case B
direction is accessible from both A
directions. But direction A
is not accessible from direction A'
and vice versa.
To connect directions All
something like schema 11.9
is required (second case). But this solution has a little imperfection - trains from B
and from A'
impede each other (The exit from block N
is before the enter of block N'
). Solution at schema 11.10
doesn't have such a imperfection. This trains don't impede each other, because the exit from block N
is after the enter of block N'
Third case is intersection of the ways. Cloverleaf - the standard solution for intersections. Simplified version of the cloverleaf is represented at schema 11.11
. The imperfection of the schema is that train has to make three loops before turning right. For example, to go to A'
it has to pass N'
blocks. Standard version of cloverleaf (schema 11.12
) has additional blocks X
for turning right.
But both types of cloverleaf are liable to appearing of traffic jams. to prevent appearing of traffic jams, schema 11.13
should be used instead. This schema differs from cloverleaf schemas (11.11
) in one fundamental moment - it has no self-connected points. In case of cloverleaf any point in blocks group N
is connected to itself via this group of blocks. This is the origin of traffic jams. Schema 11.13
has no self-connected points and not affected by traffic jams.