NIMBY Rails Wiki - User contributions [en]

Depot strategies

2022-12-12T11:16:33Z

Carlos:

== Depot strategies ==

=== Single depot ===
*All trains on the line return to a single depot at night
=== Dual depot ===
*The trains in the line are evenly divided in two groups, A and B
*Group A spends the night in a depot on one end of the line, Group B in the other.
=== Mixed dual depot ===
If you want to use nightly depots for very long lines, the total line duration per day usually dictates the service pattern in terms of runs. For example, if your target depot time is between 1am and 4am, that leaves 21 hours to run trains within the day. Trains running a line of 11h or more will only complete one run in the day. This reduces your effective capacity on the line, as a train starting at 4am will "finish the day" in the depot at 15h when there are many passengers around still.

You can fix this using the new "enter " and "exit" stop features in the timetable to break up the line in the middle. Trains will be able to run more hours in the day as a result. This requires a neatly fitting service pattern to ensure all parts of the line are equally covered, and that it fits in a seven day week. This is an example from my Eurostar London - Barcelona line. Half the trains are set up as follows.
[[File:Mixed_dual_depot.png|200px|thumb|left|In-game example of a mixed-days dual depot.]]
'''Group A (half the trains):'''
*Monday: Start in London Depot, start line in London. Complete run to Barcelona (5h45m). Then complete a full run back and forth (11:30). End in Barcelona Depot.
Tuesday: Start in Barcelona Depot, start line in Barcelona. Complete run to London (5h45m) Then complete a full run back and forth (11:30). End in London Depot.
*Wed: Start in London. [...]. End in Barcelona.
*Thu: Start in Barcelona. [...]. End in London.
*Fri: Start in London. [...]. End in Barcelona.
*Sat: special day, train runs a short day. Starts and ends in Barcelona and completes only a single run back and forth.
*Sun: Start in Barcelona. [...]. End in London.

'''Group B (other half)'''
*Same as above but shifted a full day such that the "rest day" is on Sunday.
*In addition, the rest day has to be in the other city (so complete a full run but from the perspective of London)

== How to design the appropriate depot strategy for your long distance line ==
Now that we know about the most complex depot design (the mixed days dual depot, see above), the question is when do we use it?

Here we compare a simple single depot design, as well as a simple dual depot design (at both 'ends' of the line, but no mixed days), and the mixed days dual depot.

In the end the most efficient design depends on three things:
*1) Line length in hours
*2) Your desired nightly depo time and its inverse, your "operating hours" during the day
*3) Interval / number of trains on the line
Given the three of these, the most efficient design is the one that maximises the number of train runs within your operating hours, with the fewest scheduling anomalies. See picture below for a comparison. Key things to note:

Single depot trains operate only in full multiples of the line time. For long lines, some trains will run two laps, some will do just one. Your effective service hours will be constrained late in the day close to the depot. This can be a problem if it's 4pm on a Friday.

Dual depot full multiples only, but doubles the number of trains leaving early enough to run two laps. Generates a scheduling anomalies if not all trains complete the same number of round trips.

Mixed days dual depot is special and forces your trains to operate in 0.5x or 1.5x multiples of the line duration, and similar to dual depot, has two sets of trains leaving early and has potential scheduling anomalies..

Which one do you pick? Well you need to excel through this for your own preferences. For me, it is the the following schedule (22 op hours 4am - 2am, 30m frequencies) depending on the line timing.
*<7h: single depot is fine, constrained operating hours only late in the evening/early morning.
*7.5h - 8.5h: dual depot; mixed allowed but inefficient.
*>=9h: mixed days dual needed; dual depot has scheduling anomaly

[[File:Depot_strategies.png|200px|thumb|left|Excel schematic comparing single, dual and mixed days dual depot strategies for a 10 hour (red) and 8-hour (blue) line]]

[[Category:Guide]]

How to use the in-game routeplanner

2022-12-12T11:14:38Z

Carlos:

You can see the optimal routes from any station in your network to another.

== Steps to use ==
* Click on the origin station you to open the station window
* Click on the destination station to open the station window.
* When you having the two station windows open at the same time, go to the "show dominating trips" screen in the origin station.
* Select the other station in that screen, even if there is no pax currently in the station with that destination, marked as "(window)".

== Screenshot ==

[[File:Routeplanner.png]]

[[Category:Guide]]

How to use depots

2022-12-10T13:25:48Z

Carlos: empty trains is now named Technical maneuvers

How to build a depot in [[Version 1.5]]
== Background for [[Version 1.4]] players ==
*There's no longer a special depo building. To achieve the same function as a depot, you can now use stations as depos, which we call storage yards.
*There's no longer a special "go to depo" order. To achieve the same function as this order, you can now use a simple line order to the storage yard.

== Building a storage yard ==
* Build a station, called "Yard", with many parallel terminus tracks leading up to one entry point signal. The ideal location for this type of yard is behind a terminus station, but in front works as well.
* Set its coverage area to zero.
* Build blueprints

== Create a depot line==
* Create a line, called "Yard Express"
* Add one stop (and one only) to Yard Express, any one stop of the depot station. Use the secondary platform signal function (not covered in this tip) to enable all other stops of the yard "station" in that single stop of Yard Express
* Now the key bit: set the "service level" of the line to "Technical maneuvers". Note that the line icon now changes to the old depo icon.

[[File:Depot_image.png|200px|thumb|left|Creating a depot line]]

== Assign trains to the depot ==
* Trains can be assigned to the depot line just like any other line. Simply schedule the Yard Express at night, and trains will go hit the yard. The scheduled duration of Yard Express will be equal to the stop duration in step 6.

== Notes on how it works ==
* Pax won’t be capable of planning trips which involve “technical maneuvers” lines, so always exit before the yard.
* Pax won't spawn in or set destination to a zero coverage station, such as the yard station.
[[Category:Guide]]

Run

2022-12-09T16:15:25Z

Carlos:

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:Concepts]]
[[Category:Timetable]]

Order

2022-12-09T16:13:19Z

Carlos:

[[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:Concepts]]
[[Category:Timetable]]

Building

2022-12-09T16:08:35Z

Carlos:

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.
[[Category:Concepts]]

Layer

2022-12-09T16:07:36Z

Carlos: Removed redirect to Geographical layer

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.

Building

2022-12-09T16:06:16Z

Carlos: Created page with "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 Category:Concepts"

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
[[Category:Concepts]]

Layer

2022-12-09T16:05:26Z

Carlos: Carlos moved page Layer to Geographical layer: separate the concep of construction layer from the geo layer

#REDIRECT [[Geographical layer]]

Geographical layer

2022-12-09T16:05:26Z

Carlos: Carlos moved page Layer to Geographical layer: separate the concep of construction layer from the geo layer

In NIMBY rails, there are two map [[layer|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].

[[Category:Concepts]]

NIMBY:Contents

2022-12-09T16:04:42Z

Carlos: /* Geographical concepts */

= Guides =
== Tutorials ==
All tutorial pages start with "How to" and contain a step by step guide to a simple game concept.
Following the tutorial pages should enable you to build and run a simple network.

*[[Quickstart guide]]
*[[How to build track]]
*[[How to build stations]]
*[[How to create a line]]
*[[How to schedule a train]]

== Advanced ==
Advanced guides enable players to use optional functionality such as signals and depots which can be ignored and replaced with defaults if needed.
*[[How to signal a junction]]
*[[How to use depots]]
*[[How to manual timetable]]
*[[How to use the in-game routeplanner]]

== Strategy ==
Strategy pages assume you know ''how'' something is done and consider ''why'' you might want to do it.
*[[Depot strategies]]
*[[Mapping resources]]
*[[Transfer hub strategy]]

= Concepts =

== [[Geographical layer]]s ==
''Geographical background objects provided by the game data which cannot be modified by the player''
*[[Population layer]]
*[[Admin layer]]

== Map concepts ==
''Objects created by the player on top of the geographical data''
*[[Blueprint]]
*[[Track]]
*[[Station]]
*[[Signal]]
*[[Layer]]s
*[[Building]]

== Simulation concepts ==
''Things that the game generates as it runs the simulation''
*[[Pax]]
*[[Dominating trip]]
*[[Path]]
*[[Accounting]]
*[[Satisfaction]]

== Line concepts ==
*[[Line]]
*[[Stop]]
*[[Timetable]]
*[[Duration]]
*[[Custom Duration]]

== Train concepts ==
*[[Train]]
*[[Run]]
*[[Order]]
*[[Timetable]]

= Versions =
*[[Demo 1.0]]
*[[Version 1.1]]
*[[Version 1.2]]
*[[Version 1.3]]
*[[Version 1.4]]
*[[Version 1.5]]
*[[Version 1.6]]

NIMBY:Contents

2022-12-09T16:02:47Z

Carlos:

= Guides =
== Tutorials ==
All tutorial pages start with "How to" and contain a step by step guide to a simple game concept.
Following the tutorial pages should enable you to build and run a simple network.

*[[Quickstart guide]]
*[[How to build track]]
*[[How to build stations]]
*[[How to create a line]]
*[[How to schedule a train]]

== Advanced ==
Advanced guides enable players to use optional functionality such as signals and depots which can be ignored and replaced with defaults if needed.
*[[How to signal a junction]]
*[[How to use depots]]
*[[How to manual timetable]]
*[[How to use the in-game routeplanner]]

== Strategy ==
Strategy pages assume you know ''how'' something is done and consider ''why'' you might want to do it.
*[[Depot strategies]]
*[[Mapping resources]]
*[[Transfer hub strategy]]

= Concepts =

== Geographical concepts ==
''Geographical background objects provided by the game data which cannot be modified by the player''
*[[Population layer]]
*[[Admin layer]]

== Map concepts ==
''Objects created by the player on top of the geographical data''
*[[Blueprint]]
*[[Track]]
*[[Station]]
*[[Signal]]
*[[Layer]]s
*[[Building]]

== Simulation concepts ==
''Things that the game generates as it runs the simulation''
*[[Pax]]
*[[Dominating trip]]
*[[Path]]
*[[Accounting]]
*[[Satisfaction]]

== Line concepts ==
*[[Line]]
*[[Stop]]
*[[Timetable]]
*[[Duration]]
*[[Custom Duration]]

== Train concepts ==
*[[Train]]
*[[Run]]
*[[Order]]
*[[Timetable]]

= Versions =
*[[Demo 1.0]]
*[[Version 1.1]]
*[[Version 1.2]]
*[[Version 1.3]]
*[[Version 1.4]]
*[[Version 1.5]]
*[[Version 1.6]]

Signal

2022-12-09T15:57:25Z

Carlos:

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.

[[Category:Concepts]]

Talk:Duration

2022-12-08T22:36:58Z

Carlos: Created page with "I've removed the 24h duration table since the in-game line editor provides automatic duration fitting for 24h periods."

I've removed the 24h duration table since the in-game line editor provides automatic duration fitting for 24h periods.

Duration

2022-12-08T22:35:57Z

Carlos:

The [[Duration]] of a [[line]] is how long it takes a train.

== 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.

Line

2022-12-08T22:33:57Z

Carlos:

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.
[[Category:Concepts]]

Stop

2022-12-08T22:33:34Z

Carlos: Created page with "A line stop is a point in the map for trains to stop (or pass by) while running a line. Stops are always defined as two tracks, be it a station platform or a waypoint. Stops have other associated data like leg duration or stop wait time. Category:Concepts"

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.
[[Category:Concepts]]

Line

2022-12-08T22:30:56Z

Carlos:

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.
[[Category:Concepts]]

Blueprint

2022-12-08T22:28:41Z

Carlos: Created page with "Building new map objects like tracks and buildings 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 stations will be allowed in the line editor and by the train..."

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.
[[Category:Concepts]]

NIMBY:Contents

2022-12-08T22:24:32Z

Carlos:

= Guides =
== Tutorials ==
All tutorial pages start with "How to" and contain a step by step guide to a simple game concept.
Following the tutorial pages should enable you to build and run a simple network.

*[[Quickstart guide]]
*[[How to build track]]
*[[How to build stations]]
*[[How to create a line]]
*[[How to schedule a train]]

== Advanced ==
Advanced guides enable players to use optional functionality such as signals and depots which can be ignored and replaced with defaults if needed.
*[[How to signal a junction]]
*[[How to use depots]]
*[[How to manual timetable]]
*[[How to use the in-game routeplanner]]

== Strategy ==
Strategy pages assume you know ''how'' something is done and consider ''why'' you might want to do it.
*[[Depot strategies]]
*[[Mapping resources]]
*[[Transfer hub strategy]]

= Concepts =

== Geographical concepts ==
''Geographical background objects provided by the game data which cannot be modified by the player''
*[[Population layer]]
*[[Admin layer]]

== Map concepts ==
''Objects created by the player on top of the geographical data''
*[[Blueprint]]
*[[Track]]
*[[Station]]
*[[Signal]]
*[[Layers]]
*[[Building]]

== Simulation concepts ==
''Things that the game generates as it runs the simulation''
*[[Pax]]
*[[Dominating trip]]
*[[Path]]
*[[Accounting]]
*[[Satisfaction]]

== Line concepts ==
*[[Line]]
*[[Stop]]
*[[Timetable]]
*[[Duration]]
*[[Custom Duration]]

== Train concepts ==
*[[Train]]
*[[Run]]
*[[Order]]
*[[Timetable]]

= Versions =
*[[Demo 1.0]]
*[[Version 1.1]]
*[[Version 1.2]]
*[[Version 1.3]]
*[[Version 1.4]]
*[[Version 1.5]]
*[[Version 1.6]]

Waypoint

2022-12-08T22:20:20Z

Carlos:

A waypoint is a pair of contiguous, normal tracks used in the line editor to force trains to take a certain path.
[[Category:Concepts]]

Platform

2022-12-08T22:20:07Z

Carlos:

A [[station]] platform is a pair of contiguous [[track]]s flagged by the track editor as being a station platform. Any pair of contiguous tracks can be a platform, as long as they are free of [[branch]]es and certain [[signal]]s.
[[Category:Concepts]]

Track

2022-12-08T22:19:31Z

Carlos:

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.
[[Category:Concepts]]

Platform

2022-12-08T22:18:38Z

Carlos:

Platform

2022-12-08T22:18:23Z

Carlos:

A [[station]] platform is a pair of contiguous tracks flagged by the track editor as being a station platform. Any pair of contiguous tracks can be a platform, as long as they are free of [[branch]]es and certain [[signal]]s.

Platform

2022-12-08T22:17:04Z

Carlos:

Track

2022-12-08T22:16:39Z

Carlos:

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 other tracks in two ways: as a [[branch]] or as a [[parallel]] track.
[[Category:Concepts]]

NIMBY:Contents

2022-12-08T22:09:39Z

Carlos:

= Guides =
== Tutorials ==
All tutorial pages start with "How to" and contain a step by step guide to a simple game concept.
Following the tutorial pages should enable you to build and run a simple network.

*[[Quickstart guide]]
*[[How to build track]]
*[[How to build stations]]
*[[How to create a line]]
*[[How to schedule a train]]

== Advanced ==
Advanced guides enable players to use optional functionality such as signals and depots which can be ignored and replaced with defaults if needed.
*[[How to signal a junction]]
*[[How to use depots]]
*[[How to manual timetable]]
*[[How to use the in-game routeplanner]]

== Strategy ==
Strategy pages assume you know ''how'' something is done and consider ''why'' you might want to do it.
*[[Depot strategies]]
*[[Mapping resources]]
*[[Transfer hub strategy]]

= Concepts =

== Geographical concepts ==
''Geographical background objects provided by the game data which cannot be modified by the player''
*[[Population layer]]
*[[Admin layer]]

== Map concepts ==
''Objects created by the player on top of the geographical data''
*[[Station]]
*[[Track]]
*[[Signal]]
*[[Building]]
*[[Blueprint]]
*[[Layers]]

== Simulation concepts ==
''Things that the game generates as it runs the simulation''
*[[Pax]]
*[[Dominating trip]]
*[[Path]]
*[[Accounting]]
*[[Satisfaction]]

== Line concepts ==
*[[Line]]
*[[Stop]]
*[[Timetable]]
*[[Duration]]
*[[Custom Duration]]

== Train concepts ==
*[[Train]]
*[[Run]]
*[[Order]]
*[[Timetable]]

= Versions =
*[[Demo 1.0]]
*[[Version 1.1]]
*[[Version 1.2]]
*[[Version 1.3]]
*[[Version 1.4]]
*[[Version 1.5]]
*[[Version 1.6]]

Waypoint

2022-12-08T22:05:25Z

Carlos: Created page with "A waypoint is a pair of contiguous, normal tracks used in the line editor to force trains to take a certain path."

A waypoint is a pair of contiguous, normal tracks used in the line editor to force trains to take a certain path.

Station

2022-12-08T22:04:29Z

Carlos:

An 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]]

Station

2022-12-08T22:03:36Z

Carlos:

An 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]]

Platform

2022-12-08T22:02:25Z

Carlos: Created page with "A station platform is a pair of contiguous tracks flagged by the track editor as being a station platform. Any pair of contiguous tracks can be a platform, as long as they are free of branches and certain signals."

Station

2022-12-08T21:59:57Z

Carlos:

An 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).

== 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]]

Station

2022-12-07T19:33:51Z

Carlos:

Stations are viewed in the simulation using the station window

== 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]]

Depot strategies

2022-12-05T20:59:41Z

Carlos:

How to use the in-game routeplanner

2022-12-05T20:59:29Z

Carlos:

How to use the in-game routeplanner

2022-12-05T20:42:10Z

Carlos:

Demo 1.0

2022-12-05T11:27:05Z

Carlos:

The first public build of the game was made available as a demo for the [https://store.steampowered.com/news/app/1134710/view/2219658305431027959 Steam Game Festival, 2020 Summer Edition].
[[Category:Version]]

Demo 1.0

2022-12-05T11:26:25Z

Carlos: Created page with "The first public build of the game was made available as a demo for the [https://store.steampowered.com/news/group/4/view/4534507336203365605 Steam Game Festival, 2020 Summer Edition]. Category:Version"

The first public build of the game was made available as a demo for the [https://store.steampowered.com/news/group/4/view/4534507336203365605 Steam Game Festival, 2020 Summer Edition].
[[Category:Version]]

Version 1.6

2022-12-05T11:01:13Z

Carlos: Created page with "Category:Version"

[[Category:Version]]

Version 1.5

2022-12-05T11:01:06Z

Carlos: Created page with "Category:Version"

[[Category:Version]]

Version 1.4

2022-12-05T11:00:59Z

Carlos: Created page with "Category:Version"

[[Category:Version]]

Version 1.3

2022-12-05T11:00:50Z

Carlos: Created page with "Category:Version"

[[Category:Version]]

Version 1.2

2022-12-05T11:00:43Z

Carlos: Created page with "Category:Version"

[[Category:Version]]

Category:Version

2022-12-05T11:00:30Z

Carlos: Created page with "Category:NIMBY Rails"

[[Category:NIMBY Rails]]

Version 1.1

2022-12-05T11:00:14Z

Carlos: Created page with "Category:Version"

[[Category:Version]]

Timetable

2022-12-05T09:51:00Z

Carlos: Created page with "Category:Concepts Category:Timetable"

[[Category:Concepts]]
[[Category:Timetable]]

Category:Timetable

2022-12-05T09:50:22Z

Carlos: Created page with "Category:Concepts"

[[Category:Concepts]]

Run

2022-12-05T09:50:00Z

Carlos: Created page with "Category:Concepts Category:Timetable"

[[Category:Concepts]]
[[Category:Timetable]]

Order

2022-12-05T09:49:37Z

Carlos:

[[Category:Concepts]]
[[Category:Timetable]]