NIMBY Rails Wiki - User contributions [en]

Guide to station approaches

2023-03-07T15:20:41Z

Hannibal: Created page with "Large '''station approaches''' are likely some of the most complex track layouts in any network. This guide seeks to offer some general tips and advice on how to design station approaches, as well as some templates that can be useful. This guide does not deal with stations themselves, only with the track approaching stations. It also focuses on large station approaches that have at least some trains terminating. == Why station approaches are difficult == * * Stati..."

Large '''station approaches''' are likely some of the most complex track layouts in any network. This guide seeks to offer some general tips and advice on how to design station approaches, as well as some templates that can be useful. This guide does not deal with [[station]]s themselves, only with the track approaching stations. It also focuses on large station approaches that have at least some trains terminating.

== Why station approaches are difficult ==

*
* Station approa

For real life station approaches there are a couple of additional factors at play. Especially for players seeking to rebuild real railways in NIMBY Rails, or to build real-looking fictional railways, it is important to understand why real station approaches often look so chaotic or sub-optimal.
* Real station approaches were often built incrementally over time in constrained spaces in or close to city centres. This includes having to deal with actual NIMBYs, where space is required for noise barriers in residential areas.
* Legacy railways were often built when unit cargo goods traffic was much larger than it is today, and goods- and passenger trains were often mixed in a single train. This results in busy passenger station approaches sometimes devoting significant area to what is essentially a small goods yard, further constraining space.
* As rail passenger traffic expanded, the station platform- and waiting area has expanded, often at the expense of space available for approach tracks, or constraining the curves/junctions that are possible.
* Safety requirements for signalling constrain the actual junction design and speed limits. In general the main constraint is that the heaviest, largest trains allowed on the track need to be able to come to a complete stop after a signal before a junction. This safety requirement is why real life signals are placed so far in advance of the junction for high speed junctions in open areas. Where this is not feasible - such as station approaches - very low speed limits such as 60 or 40kmh are required to meet the safety standards.

== Approaches to through stations ==

Frequently asked questions

2023-01-04T13:48:06Z

Hannibal: Created page with "''This is a draft page'' == Simulation == === Station full === How to find out *Click on station window *Asset listing stations by contained pax Investigate root cause *Are trains departing empty / pax not boarding train? Watch the station for a while and see if pax are exiting but not boarding. *Are trains departing full? === Pax not boarding train === === Train delayed === How to find out *Click on train *Asset listing trains by time to arrival, negative is delaye..."

''This is a draft page''

== Simulation ==
=== Station full ===
How to find out
*Click on station window
*Asset listing stations by contained pax

Investigate root cause
*Are trains departing empty / pax not boarding train? Watch the station for a while and see if pax are exiting but not boarding.
*Are trains departing full?

=== Pax not boarding train ===

=== Train delayed ===
How to find out
*Click on train
*Asset listing trains by time to arrival, negative is delayed
*Line view
*Full stations, with a lot of expired pag in the waited line stop view, but no "boarding failed: full train" pax

Investigate root causes
*Check platform conflicts
*Signallying delays
*Boarding delays

Solutions
*More stop time
*Lower cruise speed
*Change timetable to avoid signalling and platform conflicts

[[Category:Guides]]

Admin layer

2022-12-27T12:21:59Z

Hannibal: Created page with "{{Concepts sidebar}} The Admin layer contains data about administrative divisions from OpenStreetMap. See [https://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative#10_admin_level_values_for_specific_countries OSM wiki] about how these values are defined for each country. In the game, these are currently only used for automatic station names."

{{Concepts sidebar}}
The [[Admin layer]] contains data about administrative divisions from OpenStreetMap. See [https://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative#10_admin_level_values_for_specific_countries OSM wiki] about how these values are defined for each country. In the game, these are currently only used for automatic station names.

World map

2022-12-27T12:20:18Z

Hannibal: Created page with "{{Concepts sidebar}} The NIMBY rails World map is a complete map of Earth based on a custom post-processed version of OpenStreetMap in 2019."

{{Concepts sidebar}}
The NIMBY rails [[World map]] is a complete map of Earth based on a custom post-processed version of OpenStreetMap in 2019.

Population layer

2022-12-27T12:19:39Z

Hannibal:

{{Concepts sidebar}}
The [[population layer]] is map [[layer]] in NIMBY rails that displays actual population density data for the entire world, combined with buildup data. The population layer has a resolution of 250m, and the buildup data is 30m. The game combines both of them to create a single layer for population density, which is used to calculate [[station]] [[coverage]].

== Data sources ==
The population density layer in game uses two data layers from the Global Human Settlement Layer, an academic project by the European Union.
*[https://ghsl.jrc.ec.europa.eu/ghs_pop2019.php GHS-POP], the Global Human Settlement Layer Population Grid, which uses various data sources to estimate population density at a resolution of 250m.
*[https://ghsl.jrc.ec.europa.eu/ghs_bu2019.php GHS-BUILT], the Global Human Settlement Layer Built-Up Area Grid, which uses satellite data on which areas contain buildings or not, at a resolution of 30m

== In-game layer details ==
The in-game population layer is constructed from the EU data sources by refining the coarse 250m 'GHS-POP' data using the granular 30m 'GHS-BUILT' data.

The game does this by assuming all the people in each 250x250 block only live in the buildings on that block, and not in parks or water.
[[File:Population_layer_tromso.png|200px|thumb|right|Tromsø, showing the checkerboard pattern where there is no building data.]]
There are a couple of anomalies that result fromt his process:
*The GHS-BUILT dataset sometimes identifies roads as buildings, which then results in the game allocating population to that road.
*Sometimes there are no buildings at all in the GHS-BUILT data even though there is population in the GHS-POP data. In this case, the game allocates all the population to a single dot in the middle of the 250x250 block from the GHS-POP data. This can be seen in game as a "checkerboard" pattern. This is particularly prevalent at extreme latitudes, because the satellite-based GHS-BUILT dataset has poor coverage there.

== Gameplay implications ==
[[File:Population_layer_moscow.png|200px|thumb|right|Moscow, showing how admin level data was used as the colours neatly match the boundaries, as well as checkerboard patterns.]]

Some things about this process are important to know for understanding station coverage.
*Some of the 'checkerboard pattern' dots have very high population per dot.
*The quality of the EU data depends on local government data. Some countries with large local government areas such as the Netherlands and Germany have less precise outcomes. Countries that are more detailed include the France, Spain and Italy, because more detailed data was used by the EU. Compare how all of Amsterdam or Berlin is one colour only vs Paris or Milan.
*The EU data model 'underweights' non-built up areas, but doesn't absolutely prohibit assigning population to them, so in dense areas quite a lot of people live in the middle of the river (in checkerboard dots).

The combination of the above means NIMBY networks are sometimes unbalanced compared to the real world. NIMBY can miss 10-20% of coverage in a city with a river and lots of parks, compared to an inland city that's all built up.

[[Category:Concepts]]

Building

2022-12-27T12:19:21Z

Hannibal:

{{Concepts sidebar}}
Buildings are (for the most part) cosmetic objects which represent an overhead view of some building, floor, or non-track construction. They can be located in any [[layer]] and within each layer, they support 3 additional layers: under tracks, over tracks and roof.

Layer

2022-12-27T12:17:44Z

Hannibal:

{{Concepts sidebar}}
''This article is about height layers when building. It is not to be confused with the [[Geographical layer]]s, background data that can be displayed on the map''

It is possible to create map objects like [[track]]s and [[building]]s in different height layers. The base ground layer is layer 0. Underground layers are -1 to -3, and elevated layers are 1 to 3. Constructions in a given layer do not collide with constructions in a different layer. Underground and elevated layer constructions also do not collide with water or roads. Two special infinite layers additionally do not collide with themselves.

[[File:Height layer.png|Height layer buttons in the game]]

File:Height layer.png

2022-12-27T12:17:22Z

Hannibal:

Template:Concepts sidebar

2022-12-27T12:15:24Z

Hannibal:

{| class="wikitable" style="font-size:12px; float:right;"
|- style="text-align:center;"
! colspan="2" style="background-color:#fcff2f;" | NIMBY rails game concepts<br />
|-
| style="background-color:#ffffc7;" | '''[[Geographical layer|Geography]]'''
|
*[[World map]]
*[[Population layer]]
*[[Admin layer]]
|-
| style="background-color:#ffffc7;" | '''Map objects'''
|
*[[Blueprint]]
*[[Track]]
*[[Station]]
*[[Signal]]
*[[Layer]]s
*[[Building]]
|-
| style="background-color:#ffffc7;" | '''[[Line]] concepts'''
|
*[[Stop]]
*[[Timetable]]
*[[Duration]]
|-
| style="background-color:#ffffc7;" | '''[[Train]] concepts'''<br />
|
*[[Run]]
*[[Order]]
|-
| style="background-color:#ffffc7;" | '''[[Simulation]]'''
|
*[[Pax]]
**[[Origin]]
**[[Destination]]
**[[Dominating trip]]
*[[Path]]
*[[Accounting]]
*[[Satisfaction]]
|}
</div>
<includeonly>[[Category:Concepts]]</includeonly>
<noinclude>[[Category:Templates]]</noinclude>

Geographical layer

2022-12-27T12:14:59Z

Hannibal:

{{Concepts sidebar}}
In NIMBY rails, there are two geograpghical layers that can be displayed on top of the base map:
*The [[population layer]], showing population density.
*The [[regions layer]], showing administrative regions.

Behind the scenes, there are also layers used by the game for visualisation.
*The [[elevation layer]], used for drawing hill shading visuals. This uses [http://www.earthenv.org//DEM DEM].

Layer

2022-12-27T12:14:22Z

Hannibal:

Layer

2022-12-27T12:14:14Z

Hannibal:

{{Concepts sidebar}}
''This article is about height layers when building. It is not to be confused with the [[Geographical layer]]s, background data that can be displayed on the map''
It is possible to create map objects like [[track]]s and [[building]]s in different height layers. The base ground layer is layer 0. Underground layers are -1 to -3, and elevated layers are 1 to 3. Constructions in a given layer do not collide with constructions in a different layer. Underground and elevated layer constructions also do not collide with water or roads. Two special infinite layers additionally do not collide with themselves.

Layer

2022-12-27T12:12:54Z

Hannibal:

{{Concepts sidebar}}
It is possible to create map objects like [[track]]s and [[building]]s in different height layers. The base ground layer is layer 0. Underground layers are -1 to -3, and elevated layers are 1 to 3. Constructions in a given layer do not collide with constructions in a different layer. Underground and elevated layer constructions also do not collide with water or roads. Two special infinite layers additionally do not collide with themselves.

Signal

2022-12-27T12:12:48Z

Hannibal:

{{Concepts sidebar}}
Signals make it possible to influence the behavior of [[train]]s running over [[track]]s.

= Platform train stop point =
This is a hint for the train AI to stop at the signal position when stopping in a [[station]] [[platform]].

= One way =
This is a hard rule for the train [[path]] finder to only run over the track in the signal direction. Trains will never consider tracing a path in the opposite direction.

= No way =
Trains will never trace a path crossing over this signal, from either direction.

= Path signal =
When a train arrives at this signal, it will consider the remaining path to its destination, up to the next same-facing path signal or block balise. If the path is clear of other trains or track reservations, it will proceed. If it's not, it will stop at the signal and check again in the future until it becomes clear. After the train proceeds past the signal it reserves the whole path of track segments for itself, until the next same-facing path signal or block balise.

= Block balise =
Block balises stop a train path check or path reservation from going beyond their point in the track, from both directions.

Station

2022-12-27T12:12:36Z

Hannibal:

{{Concepts sidebar}}
A station is a set of one or more [[platform]]s whose footprints overlap on each other (in particular, a single platform is a valid station too). Stations are the main destination kind available for picking as a [[line]] [[stop]] (the other being [[waypoint]]s).

There are no limits on how many platforms can be combined into an station, including overlapping them at any [[layer]] or aligned in any orientation.

== Station properties ==
[[File:Station_properties.png|200px|thumb|left|Station properties]]
The station properties window is used in the [[Tracks menu]] to edit the station's propertis, including:
*The station name
*The station label display settings
*The station coverage area

The station properties window also has a locator button (next to the "Done" button) to jump to the location of the station.

=== Station names ===
Using the "use automatic name" box,

==== Using station names as tags ====
As of [[Version 1.5]], NIMBY rails does not support station tags. An advanced strategy is to use the station name as a kind of station tag system, which can help in understanding certain menus that do not support tagged listings, as well as the [[Accounting export]]. For example, starting the station name with the stations [https://en.wikipedia.org/wiki/Nomenclature_of_Territorial_Units_for_Statistics|NUTS] regional code can make it easier to do regional aggregations on the accounting export.

== Station window ==
[[File:Station_window.png|200px|thumb|left|Station window]]
=== Passengers ===
Passengers can be show in
*Show all
*Show best current trip. This functions as an "in game routeplanner" for the current time.
*Show dominating trips. This functions as an "in game routeplanner" across time.
*Group by destination
*Group by origin
*Group by waited line stop
*Group by next stop

=== Platforms ===

=== Accounting ===
Stations have their own [[Accounting]] window, showing the accounting events that occured at this station.

== Stations as depots ==
[[Depot|Depots]] are technically just stations that are used for a particular purpose, storing trains for longer periods of time. Depots do not require any kind of special building to function.
*The station coverage area can be set to zero. This prevents pax from spawning or choosing the depot as a destination.
*The station label display settings can be made less prominent.

[[Category:Concepts]]

Track

2022-12-27T12:12:27Z

Hannibal:

{{Concepts sidebar}}
Track objects (also called track segments) model the railways over which trains can move. The consist of a single control point, and are always linked to one or two other tracks (the previous and next sibling). Tracks can also be attached to tracks in two other ways: as a [[branch]] or as a [[parallel]] track. Tracks can contain [[signal]]s.

Blueprint

2022-12-27T12:12:19Z

Hannibal:

{{Concepts sidebar}}
Building new map objects like [[track]]s and [[building]]s sets them into blueprint mode. In blueprint mode objects can be freely moved, edited and deleted without limitations, even allowing them to have temporary invalid states like building over water. Once a player is satisfied with a set of blueprinted objects, the track editor bill can be paid to switch them into built mode. Only built tracks and [[station]]s will be allowed in the [[line]] editor and by the [[train]] AI.

Destination

2022-12-27T12:12:02Z

Hannibal:

{{Concepts sidebar}}
The [[destination]] is where [[pax]] in the game want to go to. After spawning at their [[origin]], [[pax]] pick a destination, and upon reaching their destination, pax will despawn. Pax will use [[pax pathfinding]] logic to try and find the best route ("[[dominating trip]]") to their destination.

== Destination picking ==

The destination picking process can be seen in three steps

# Consider the list of all possible stations within the pax' [[distance category]]. This uses the "as the crow flies" distance, without accounting for actual railway routes or the presence of mountains, oceans, etc.
#*Local: 0 to 15km
#*Regional 15km to 100km
#*Long distance More than 100km.
# Probability weight each possible destination station by the destination coverage and the number of unique lines stopping there. The precise maths for this are not disclosed.
#*The number of unique lines effect appears to be roughly linear: stations with the same coverage but twice the number of lines will see twice the number of passengers picking it as destination.
#*Coverage appears to have a nonlinear impact, with stations that have very low coverage still attracting a "default" level of destinations.
# Pick a random station from the weighted list of possible stations.

== Viewing destinations ==

Destinations can be viewed in the following ways:
*The [[accounting]] event "reached destination" counts the number of pax reaching a destination for each line and station. It is available in the accounting screen of each station as well as the [[asset listing]].
*The [[station]] and [[train]] "passengers listing" window can be sorted to group "by destination". This displays all pax in the station or train, grouped by their destination.

Origin

2022-12-27T12:11:52Z

Hannibal:

{{Concepts sidebar}}
The [[station]] [[pax]] spawn at is labelled as their [[origin]].
After spawning and departing on their first train, the origin is not used anywhere in the game. However, it can be useful to view or group by origin station to get a sense of where pax are coming from and what route they have taken.

== Viewing origins ==
Pax origins can be viewed in the following ways:
*The [[accounting]] event "new pax" counts the number of pax spawning at a station. It is available in the accounting screen of each station as well as the [[asset listing]].
*The [[station]] and [[train]] "passengers listing" window can be sorted to group "by origin". This displays all pax in the station or train, grouped by their origin.

Pax

2022-12-27T12:11:35Z

Hannibal:

{{Concepts sidebar}}
In NIMBY Rails a passenger (also abbreviated as [[pax]]) is a person who travels on a [[train]] from an origin to a destination [[station]].
This page considers both the rules governing pax behaviour as well as static and dynamic properties of pax.
As a lot of the NIMBY Rails [[simulation]] concerns pax in some way, not all topics are covered in detail here. Please refer to the linked pages as appropriate.
As part of the development [[roadmap]], it may be possible to use [[rules mods]] in the future to change the rules governing pax behaviour, such as base demand and the expectations that drive satisfaction.

== New pax spawning ==
New pax spawn in [[station|stations]] according to the [[spawn rate]] of a station.
The place the pax spawned in is referred to as their [[origin]] station.
Pax are allocated immediately to one of the three [[distance category|distance categories]]: local, regional and long distance.
Upon spawning pax will pick a [[destination]].

== Pax pathfinding logic ==

== Pax boarding behaviour ==
See:
*[{Boarding]]

== Index of pax static properties ==
Pax pathfinding results in the following properties being applicable to pax at any point in time.
* [[Dominating trip]], the current "best trip" for the pax from their current location to their destination.
* [[Waited line stop]], for pax waiting in a [[station]]

== Pax groups ==
For [[pax pathfinding]] and [[boarding]], the game represents pax using groups of pax with the same destination.

Duration

2022-12-27T12:09:17Z

Hannibal:

{{Concepts sidebar}}
The [[duration]] of a [[line]] is how long it takes a train to run the line from its start to end. The game has two related duration concepts:
*The "loop" duration includes the time it takes the train to travel from the last stop back to the first stop. It is useful if trains run (continuous) line loops. This is the default displayed line duration.
*The "non-loop" duration excludes the time it takes the train to travel from the last stop back to the first stop. It is useful if you use complex [[manual orders]] that have the same trains run different lines in succession. You can view the non-loop duration by hovering over the duration in the [[Lines editor]].

== Calculation ==
*Line duration in the [[line editor]] is estimated by the game by running a phantom train on the whole line. Sometimes this estimation is off compared to the real outcome.

== Custom durations ==
If you want to avoid trains making very long stops around 6am (or your custom time) for 24hr services, your line duration must be a factor of 24 hours (1440 minutes) so there is no remainder time to make up before the line starts again. The custom duration feature of the line editor automatically finds an optimal line duration for 24h, 7d or any desired custom period of time.

Duration

2022-12-27T12:09:00Z

Hannibal:

{{Concepts sidebar}}
The [[duration]] of a [[line]] is how long it takes a train to run the line from its start to end. The game has two related duration concepts:
*The "loop" duration includes the time it takes the train to travel from the last stop back to the first stop. It is useful if trains run (continuous) line loops. This is the default displayed line duration.
*The "non-loop" duration excludes the time it takes the train to travel from the last stop back to the first stop. It is useful if you use complex [[manual orders]] that have the same trains run different lines in succession. You can view the non-loop duration by hovering over the duration in the [[Lines editor]].

== Calculation ==
*Line duration in the [[line editor]] is estimated by the game by running a phantom train on the whole line. Sometimes this estimation is off compared to the real outcome.
*If the first [[stop]] is not the last stop, the duration in the line editor does not include the travel time from the last stop to the first stop. The [[timetable]] of trains using the line will account for this time, however.

== Custom durations ==
If you want to avoid trains making very long stops around 6am (or your custom time) for 24hr services, your line duration must be a factor of 24 hours (1440 minutes) so there is no remainder time to make up before the line starts again. The custom duration feature of the line editor automatically finds an optimal line duration for 24h, 7d or any desired custom period of time.

Duration

2022-12-27T12:08:03Z

Hannibal:

{{Concepts sidebar}}
The [[duration]] of a [[line]] is how long it takes a train to run the line from its start to end. The game has two related duration concepts:
*The "loop" duration includes the time it takes the train to travel from the last stop back to the first stop. It is useful if trains run (continuous) line loops.
*The "non-loop" duration excludes the time it takes the train to travel from the last stop back to the first stop. It is useful if you use complex [[manual orders]] that have the same trains run different lines in succession.

== Calculation ==
*Line duration in the [[line editor]] is estimated by the game by running a phantom train on the whole line. Sometimes this estimation is off compared to the real outcome.
*If the first [[stop]] is not the last stop, the duration in the line editor does not include the travel time from the last stop to the first stop. The [[timetable]] of trains using the line will account for this time, however.

== Custom durations ==
If you want to avoid trains making very long stops around 6am (or your custom time) for 24hr services, your line duration must be a factor of 24 hours (1440 minutes) so there is no remainder time to make up before the line starts again. The custom duration feature of the line editor automatically finds an optimal line duration for 24h, 7d or any desired custom period of time.

Timetable

2022-12-27T12:05:00Z

Hannibal:

{{Concepts sidebar}}
The complete in-game [[timetable]] is the collection of all future scheduled train [[run]]s and their scheduled time at each stop. The in-game timetable can be visualised conceptually as a real-life printed timetable booklet, containing a listing of all stops and the arrival and departure times at those stops. The timetable can be thought of from different perspectives.
*The '''line timetable''' is the collection of arrival/departure times for each train belonging to a line. It often follows some kind of simple pattern, e.g. half-hourly or hourly, but it can be more complex with peak and off-peak schedules. The timetable of an individual line can be viewed using the timetable tab in the [[lines editor]].
*An individual '''train timetable''' is the collection of [[run]]s for a single [[train]] with the scheduled arrival and departure time at each stop that the train visits during the week. If a train has only one line, the train timetable is a subset of the line timetable. A train's timetable can be viewed in the "Orders" tab of the [[Trains editor]].
*The '''station timetable''' is the collection of trains arriving and departing at a station. A station "departures/arrivals board" view of the timetable can be accessed using the "Platforms" view of the [[Station window]]
*The [[dominating trip]] concept can be thought of as the '''"pax timetable"''': the timetable information relevant for a pax who wants to get from their [[origin]] to their [[destination]] and all possible efficient routes to that end. A "route-planner" view of pax timetable can be accessed using the "show [[dominating trip]]s" view in the Passengers tab of the Station window.

== Gameplay ==
The complete timetable is recalculated frequently in-game, each time a potentially timetable changing edit is made to a [[line]], [[station]] or [[train]]. Note that the timetable is not recalculated when changing [[track]]s or track speeds.
The timetable is also recalculuated upon loading the game, during the "initializing timetables" step.

The timetable repeats itself every week.

The timetable is used for [[pax pathfinding]], such as calculating the [[dominating trip]].

[[Category:Timetable]]

Timetable

2022-12-27T12:04:29Z

Hannibal:

{{Concepts sidebar}}
The complete in-game [[timetable]] is the collection of all future scheduled train [[run]]s and their scheduled time at each stop. The in-game timetable can be visualised conceptually as a real-life printed timetable booklet, containing a listing of all stops and the arrival and departure times at those stops. The timetable can be thought of from different perspectives.
*The '''line timetable''' is the collection of arrival/departure times for each train belonging to a line. It often follows some kind of simple pattern, e.g. half-hourly or hourly, but it can be more complex with peak and off-peak schedules. The timetable of an individual line can be viewed using the timetable tab in the [[lines editor]].
*An individual '''train timetable''' is the collection of [[run]]s for a single [[train]] with the scheduled arrival and departure time at each stop that the train visits during the week. A train's timetable can be viewed in the "Orders" tab of the [[Trains editor]].
*The '''station timetable''' is the collection of trains arriving and departing at a station. A station "departures/arrivals board" view of the timetable can be accessed using the "Platforms" view of the [[Station window]]
*The [[dominating trip]] concept can be thought of as the '''"pax timetable"''': the timetable information relevant for a pax who wants to get from their [[origin]] to their [[destination]] and all possible efficient routes to that end. A "route-planner" view of pax timetable can be accessed using the "show [[dominating trip]]s" view in the Passengers tab of the Station window.

== Gameplay ==
The complete timetable is recalculated frequently in-game, each time a potentially timetable changing edit is made to a [[line]], [[station]] or [[train]]. Note that the timetable is not recalculated when changing [[track]]s or track speeds.
The timetable is also recalculuated upon loading the game, during the "initializing timetables" step.

The timetable repeats itself every week.

The timetable is used for [[pax pathfinding]], such as calculating the [[dominating trip]].

[[Category:Timetable]]

Timetable

2022-12-27T12:03:36Z

Hannibal:

{{Concepts sidebar}}
The complete in-game [[timetable]] is the collection of all future scheduled train [[run]]s and their scheduled time at each stop. The in-game timetable can be visualised conceptually as a real-life printed timetable booklet, containing a listing of all stops and the arrival and departure times at those stops. The timetable can be thought of from different perspectives.
*The '''line timetable''' is the collection of arrival/departure times for each train belonging to a line. It often follows some kind of simple pattern, e.g. half-hourly or hourly, but it can be more complex with peak and off-peak schedules. The timetable of an individual line can be viewed using the timetable tab in the [[lines editor]].
*An individual '''train timetable''' is the collection of [[run]]s for a single [[train]], which together describe where a train is at each time of the week. A train's timetable can be viewed in the "Orders" tab of the [[Trains editor]].
*The '''station timetable''' is the collection of trains arriving and departing at a station. A station "departures/arrivals board" view of the timetable can be accessed using the "Platforms" view of the [[Station window]]
*The [[dominating trip]] concept can be thought of as the '''"pax timetable"''': the timetable information relevant for a pax who wants to get from their [[origin]] to their [[destination]] and all possible efficient routes to that end. A "route-planner" view of pax timetable can be accessed using the "show [[dominating trip]]s" view in the Passengers tab of the Station window.

== Gameplay ==
The complete timetable is recalculated frequently in-game, each time a potentially timetable changing edit is made to a [[line]], [[station]] or [[train]]. Note that the timetable is not recalculated when changing [[track]]s or track speeds.
The timetable is also recalculuated upon loading the game, during the "initializing timetables" step.

The timetable repeats itself every week.

The timetable is used for [[pax pathfinding]], such as calculating the [[dominating trip]].

[[Category:Timetable]]

Timetable

2022-12-27T12:02:53Z

Hannibal:

{{Concepts sidebar}}
The complete in-game [[timetable]] is the collection of all future scheduled train [[run]]s and their scheduled time at each stop. The in-game timetable can be visualised conceptually as a real-life printed timetable booklet, containing a listing of all stops and the arrival and departure times at those stops. The timetable can be thought of from different perspectives.
*The '''line timetable''' is the collection of arrival/departure times for each train belonging to a line. It often follows some kind of simple pattern, e.g. half-hourly or hourly, but it can be more complex with peak and off-peak schedules. The timetable of an individual line can be viewed using the timetable tab in the [[lines editor]].
*The [[dominating trip]] concept can be thought of as the '''"pax timetable"''': the timetable information relevant for a pax who wants to get from their [[origin]] to their [[destination]] and all possible efficient routes to that end. A "route-planner" view of pax timetable can be accessed using the "show [[dominating trip]]s" view in the Passengers tab of the Station window.
*An individual '''train timetable''' is the collection of [[run]]s for a single [[train]], which together describe where a train is at each time of the week. A train's timetable can be viewed in the "Orders" tab of the [[Trains editor]].
*The '''station timetable''' is the collection of trains arriving and departing at a station. A station "departures/arrivals board" view of the timetable can be accessed using the "Platforms" view of the [[Station window]]

== Gameplay ==
The complete timetable is recalculated frequently in-game, each time a potentially timetable changing edit is made to a [[line]], [[station]] or [[train]]. Note that the timetable is not recalculated when changing [[track]]s or track speeds.
The timetable is also recalculuated upon loading the game, during the "initializing timetables" step.

The timetable repeats itself every week.

The timetable is used for [[pax pathfinding]], such as calculating the [[dominating trip]].

[[Category:Timetable]]

Order

2022-12-27T11:55:05Z

Hannibal:

{{Concepts sidebar}}
[[Train]]s build their [[timetable]]s from one or more orders. Orders tell the train to arrive or depart a certain [[stop]] in a certain [[line]] at a certain day and time of the week, and from this single point of data, extrapolate the entire timetable starting at that moment, until the whole week is accounted for or the start of another order is found. This is done by creating one or more [[run]]s.
[[Category:Timetable]]

Order

2022-12-27T11:54:51Z

Hannibal:

{{Concepts sidebar}}
[[Train]]s build their [[run]]s from one or more orders. Orders tell the train to arrive or depart a certain [[stop]] in a certain [[line]] at a certain day and time of the week, and from this single point of data, extrapolate the entire timetable starting at that moment, until the whole week is accounted for or the start of another order is found. This is done by creating one or more [[run]]s.
[[Category:Timetable]]

Order

2022-12-27T11:54:38Z

Hannibal:

Run

2022-12-27T11:54:24Z

Hannibal:

{{Concepts sidebar}}
Runs represent the act of a train running a single loop of a line (or part of a line) starting at a certain time and day of the week. Runs can never be edited by the player; they are automatically generated from [[order]]s.

[[Category:Timetable]]

Train

2022-12-27T11:53:49Z

Hannibal:

{{Concepts sidebar}}
Trains carry [[pax]] from their origin [[station]] to their [[destination]] or intermediate transfer stops. Trains are composed of one or more train units in sequence. Train units are the indivisible parts of a train, like a locomotive, a passenger car, or some technical car. The game bundles [[List_of_trains|20 default trains]] and more can be added by subscribing to [[Modding|mods]].

Template:Concepts sidebar

2022-12-27T11:53:25Z

Hannibal:

{| class="wikitable" style="font-size:12px; float:right;"
|- style="text-align:center;"
! colspan="2" style="background-color:#fcff2f;" | NIMBY rails game concepts<br />
|-
| style="background-color:#ffffc7;" | '''Geography'''
|
*[[World map]]
*[[Population layer]]
*[[Admin layer]]
|-
| style="background-color:#ffffc7;" | '''Map objects'''
|
*[[Blueprint]]
*[[Track]]
*[[Station]]
*[[Signal]]
*[[Layer]]s
*[[Building]]
|-
| style="background-color:#ffffc7;" | '''[[Line]] concepts'''
|
*[[Stop]]
*[[Timetable]]
*[[Duration]]
|-
| style="background-color:#ffffc7;" | '''[[Train]] concepts'''<br />
|
*[[Run]]
*[[Order]]
|-
| style="background-color:#ffffc7;" | '''[[Simulation]]'''
|
*[[Pax]]
**[[Origin]]
**[[Destination]]
**[[Dominating trip]]
*[[Path]]
*[[Accounting]]
*[[Satisfaction]]
|}
</div>
<includeonly>[[Category:Concepts]]</includeonly>
<noinclude>[[Category:Templates]]</noinclude>

Simulation

2022-12-27T11:52:55Z

Hannibal: Created page with "{{Concepts sidebar}} The game simulation takes the player's inputs such as stations, lines, trains and their timetable and uses them to simulate the day to day operation of a railway transport network. The main elements of the simulation are: *Trains run to their next scheduled stop, reserving paths along the way and obeying any signals *Pax are spawned at each origin station, pathfind their way to their d..."

{{Concepts sidebar}}
The game [[simulation]] takes the player's inputs such as [[stations]], [[line]]s, [[train]]s and their [[timetable]] and uses them to simulate the day to day operation of a railway transport network.
The main elements of the simulation are:
*[[Train]]s run to their next scheduled [[stop]], reserving [[path]]s along the way and obeying any [[signal]]s
*[[Pax]] are spawned at each [[origin]] station, [[pax pathfinding|pathfind]] their way to their [[destination]], and [[pax boarding|board]] trains that get them there

== Simulation data and saving ==
Depending on the size of the network, running the game simulation generates a large amount of data.
The following data from the simulation state is stored in the save game file:
*All [[pax]], their exact location and final destination
*The exact location and [[run]] of each train
*[[Accounting]] events including [[money]]

The following game simulation data is not saved and is recalculated each time on reload:
*[[Pax pathfinding]] cache
*[[Line]] timings. Lines are stored by the game as a collection of stops and other input data (such as custom timings). Automatically calculated times between two stops are recalculated on reload.

== Simulation speed==
The game has four simulation speed settings
*1x
*10x
*100x
*"As fast as possible", which disables the [[UI]]

Timetable

2022-12-27T11:39:54Z

Hannibal:

Stop

2022-12-27T11:27:32Z

Hannibal:

{{Concepts sidebar}}
A [[line]] stop is a point in the map for [[train]]s to stop (or pass by) while running a line. Stops are always defined as two [[track]]s, be it a [[station]] [[platform]] or a [[waypoint]]. Stops have other associated data like leg duration or stop wait time.

Line

2022-12-27T10:31:31Z

Hannibal:

{{Concepts sidebar}}
A line is a sequence of one or more [[stop]]s, and some associated data like fares and line [[duration]]. [[Train]]s can follow lines by setting them in auto mode or by creating [[order]]s.

Template:Concepts sidebar

2022-12-27T10:31:21Z

Hannibal:

{| class="wikitable" style="font-size:12px; float:right;"
|- style="text-align:center;"
! colspan="2" style="background-color:#fcff2f;" | NIMBY rails game concepts<br />
|-
| style="background-color:#ffffc7;" | '''Geography'''
|
*[[World map]]
*[[Population layer]]
*[[Admin layer]]
|-
| style="background-color:#ffffc7;" | '''Map objects'''
|
*[[Blueprint]]
*[[Track]]
*[[Station]]
*[[Signal]]
*[[Layer]]s
*[[Building]]
|-
| style="background-color:#ffffc7;" | '''[[Line]] concepts'''
|
*[[Line]]
*[[Stop]]
*[[Timetable]]
*[[Duration]]
|-
| style="background-color:#ffffc7;" | '''[[Train]] concepts'''<br />
|
*[[Train]]
*[[Run]]
*[[Order]]
|-
| style="background-color:#ffffc7;" | '''[[Simulation]]'''
|
*[[Pax]]
**[[Origin]]
**[[Destination]]
**[[Dominating trip]]
*[[Path]]
*[[Accounting]]
*[[Satisfaction]]
|}
</div>
<includeonly>[[Category:Concepts]]</includeonly>
<noinclude>[[Category:Templates]]</noinclude>

Line

2022-12-27T10:29:21Z

Hannibal:

A line is a sequence of one or more [[stop]]s, and some associated data like fares and line [[duration]]. [[Train]]s can follow lines by setting them in auto mode or by creating [[order]]s.
{{Concepts sidebar}}

Template:Concepts sidebar

2022-12-27T10:29:11Z

Hannibal:

<div style="float:right;">
{| class="wikitable" style="font-size:12px"
|- style="text-align:center;"
! colspan="2" style="background-color:#fcff2f;" | NIMBY rails game concepts<br />
|-
| style="background-color:#ffffc7;" | '''Geography'''
|
*[[World map]]
*[[Population layer]]
*[[Admin layer]]
|-
| style="background-color:#ffffc7;" | '''Map objects'''
|
*[[Blueprint]]
*[[Track]]
*[[Station]]
*[[Signal]]
*[[Layer]]s
*[[Building]]
|-
| style="background-color:#ffffc7;" | '''[[Line]] concepts'''
|
*[[Line]]
*[[Stop]]
*[[Timetable]]
*[[Duration]]
|-
| style="background-color:#ffffc7;" | '''[[Train]] concepts'''<br />
|
*[[Train]]
*[[Run]]
*[[Order]]
|-
| style="background-color:#ffffc7;" | '''[[Simulation]]'''
|
*[[Pax]]
**[[Origin]]
**[[Destination]]
**[[Dominating trip]]
*[[Path]]
*[[Accounting]]
*[[Satisfaction]]
|}
</div>
<includeonly>[[Category:Concepts]]</includeonly>
<noinclude>[[Category:Templates]]</noinclude>

Template:Concepts sidebar

2022-12-27T10:28:57Z

Hannibal:

<div style="float:right;">
{| class="wikitable" style="margin-right:0px; margin-left:auto; font-size:12px"
|- style="text-align:center;"
! colspan="2" style="background-color:#fcff2f;" | NIMBY rails game concepts<br />
|-
| style="background-color:#ffffc7;" | '''Geography'''
|
*[[World map]]
*[[Population layer]]
*[[Admin layer]]
|-
| style="background-color:#ffffc7;" | '''Map objects'''
|
*[[Blueprint]]
*[[Track]]
*[[Station]]
*[[Signal]]
*[[Layer]]s
*[[Building]]
|-
| style="background-color:#ffffc7;" | '''[[Line]] concepts'''
|
*[[Line]]
*[[Stop]]
*[[Timetable]]
*[[Duration]]
|-
| style="background-color:#ffffc7;" | '''[[Train]] concepts'''<br />
|
*[[Train]]
*[[Run]]
*[[Order]]
|-
| style="background-color:#ffffc7;" | '''[[Simulation]]'''
|
*[[Pax]]
**[[Origin]]
**[[Destination]]
**[[Dominating trip]]
*[[Path]]
*[[Accounting]]
*[[Satisfaction]]
|}
</div>
<includeonly>[[Category:Concepts]]</includeonly>
<noinclude>[[Category:Templates]]</noinclude>

Template:Concepts sidebar

2022-12-27T10:28:50Z

Hannibal:

<div style="float:right;">{| class="wikitable" style="margin-right:0px; margin-left:auto; font-size:12px"
|- style="text-align:center;"
! colspan="2" style="background-color:#fcff2f;" | NIMBY rails game concepts<br />
|-
| style="background-color:#ffffc7;" | '''Geography'''
|
*[[World map]]
*[[Population layer]]
*[[Admin layer]]
|-
| style="background-color:#ffffc7;" | '''Map objects'''
|
*[[Blueprint]]
*[[Track]]
*[[Station]]
*[[Signal]]
*[[Layer]]s
*[[Building]]
|-
| style="background-color:#ffffc7;" | '''[[Line]] concepts'''
|
*[[Line]]
*[[Stop]]
*[[Timetable]]
*[[Duration]]
|-
| style="background-color:#ffffc7;" | '''[[Train]] concepts'''<br />
|
*[[Train]]
*[[Run]]
*[[Order]]
|-
| style="background-color:#ffffc7;" | '''[[Simulation]]'''
|
*[[Pax]]
**[[Origin]]
**[[Destination]]
**[[Dominating trip]]
*[[Path]]
*[[Accounting]]
*[[Satisfaction]]
|}
</div>
<includeonly>[[Category:Concepts]]</includeonly>
<noinclude>[[Category:Templates]]</noinclude>

Line

2022-12-27T10:27:56Z

Hannibal:

Line

2022-12-27T10:27:48Z

Hannibal:

Template:Concepts sidebar

2022-12-27T10:27:22Z

Hannibal:

{| class="wikitable" style="margin-right:0px; margin-left:auto; font-size:12px"
|- style="text-align:center;"
! colspan="2" style="background-color:#fcff2f;" | NIMBY rails game concepts<br />
|-
| style="background-color:#ffffc7;" | '''Geography'''
|
*[[World map]]
*[[Population layer]]
*[[Admin layer]]
|-
| style="background-color:#ffffc7;" | '''Map objects'''
|
*[[Blueprint]]
*[[Track]]
*[[Station]]
*[[Signal]]
*[[Layer]]s
*[[Building]]
|-
| style="background-color:#ffffc7;" | '''[[Line]] concepts'''
|
*[[Line]]
*[[Stop]]
*[[Timetable]]
*[[Duration]]
|-
| style="background-color:#ffffc7;" | '''[[Train]] concepts'''<br />
|
*[[Train]]
*[[Run]]
*[[Order]]
|-
| style="background-color:#ffffc7;" | '''[[Simulation]]'''
|
*[[Pax]]
**[[Origin]]
**[[Destination]]
**[[Dominating trip]]
*[[Path]]
*[[Accounting]]
*[[Satisfaction]]
|}
<includeonly>[[Category:Concepts]]</includeonly>
<noinclude>[[Category:Templates]]</noinclude>

Template:Concepts sidebar

2022-12-27T10:26:44Z

Hannibal:

Template:Concepts sidebar

2022-12-27T10:19:14Z

Hannibal: Created page with "{| class="wikitable" |- style="text-align:center;" ! colspan="2" style="background-color:#fcff2f;" | NIMBY rails game concepts<br /> |- | style="background-color:#ffffc7;" | Background layers | *Population layer *Admin layer |- | style="background-color:#ffffc7;" | Map objects | *Blueprint *Track *Station *Signal *Layers *Building |- | style="background-color:#ffffc7;" | Line concepts | *Line *Stop *Timetable *Duration *..."

{| class="wikitable"
|- style="text-align:center;"
! colspan="2" style="background-color:#fcff2f;" | NIMBY rails game concepts<br />
|-
| style="background-color:#ffffc7;" | Background layers
|
*[[Population layer]]
*[[Admin layer]]
|-
| style="background-color:#ffffc7;" | Map objects
|
*[[Blueprint]]
*[[Track]]
*[[Station]]
*[[Signal]]
*[[Layer]]s
*[[Building]]
|-
| style="background-color:#ffffc7;" | Line concepts
|
*[[Line]]
*[[Stop]]
*[[Timetable]]
*[[Duration]]
*[[Custom Duration]]
|-
| style="background-color:#ffffc7;" | Train concepts<br />
|
*[[Train]]
*[[Run]]
*[[Order]]
*[[Timetable]]
|-
| style="background-color:#ffffc7;" | Simulation
|
*[[Pax]]
*[[Dominating trip]]
*[[Path]]
*[[Accounting]]
*[[Satisfaction]]
|}

Origin

2022-12-27T09:53:04Z

Hannibal:

The [[station]] [[pax]] spawn at is labelled as their [[origin]].
After spawning and departing on their first train, the origin is not used anywhere in the game. However, it can be useful to view or group by origin station to get a sense of where pax are coming from and what route they have taken.

== Viewing origins ==
Pax origins can be viewed in the following ways:
*The [[accounting]] event "new pax" counts the number of pax spawning at a station. It is available in the accounting screen of each station as well as the [[asset listing]].
*The [[station]] and [[train]] "passengers listing" window can be sorted to group "by origin". This displays all pax in the station or train, grouped by their origin.

[[Category:Concepts]]

Origin

2022-12-27T09:52:56Z

Hannibal:

Origin

2022-12-27T09:52:43Z

Hannibal: Created page with "The station pax spawn at is labelled as their origin. After spawning and departing on their first train, the origin is not used anywhere in the game. However, it can be useful to view or group by origin station to get a sense of where pax are coming from and what route they have taken. == Viewing origins == Pax origins can be viewed in the following ways: *The accounting event "new pax" counts the number of pax spawning at a station. It is available in..."