NIMBY Rails Wiki - User contributions [en]

Resources for realism

2024-12-28T16:39:18Z

Danny252: /* North America */ Move links and fix broken sentence

This is a page that lists many resources useful for achieving realism in your NIMBY Rail saves. It is split up by country and region for your convenience.

= Worldwide =
* [https://www.openrailwaymap.org/ OpenRailwayMap] is the definitive mapping resource. OpenRailwayMap displays up-to-date data on railway tracks, providing information on track gauge, speed, electrification, etc. This is an absolute must-have for any player aiming for realism.
* [https://www.openstreetmap.org OpenStreetMap] is one of the best open source mapping resources, it often has more up-to-date and accurate map data compared to other mapping tools, with the only downside being a lack of satellite view. Use this if you want the most up-to-date mapping information.
* [https://www.google.com/maps Google Maps] is a very useful tool, especially given the often highly detailed satellite view you can get with it. While Google Maps is not as up-to-date as OpenStreetMap, you can still usually rely on it for accurate mapping data except in some niche cases. Another benefit of Google Maps is the "Public Transport" or "Transit" layer along with public transport integration in general. The accuracy of this integration can vary between public transport operators but it is still very useful.
* [https://www.wikipedia.org/ Wikipedia]. While the accuracy of Wikipedia articles does vary quite a bit between lines and operators, it can be extremely helpful and useful with finding service patterns, station locations, rolling stock, etc. Wikipedia is a must-have for NIMBY Rails realism.
* [https://www.transit.land/map/ Transit.land] is a tool which catalogues GTFS (realtime or static) data from transit operators around the world. This can help with finding specific routings for all transit modes, this is especially useful for visualising routings that may have seemed confusing in a non-map format.
* [https://timetableworld.com/ Timetable World] is a comprehensive source of historic timetables. Originally mainly UK in focus, it now has significant coverage worldwide. Some timetables are available to view online or download for free, others are available for a small fee.

= Europe=
== United Kingdom ==
Note that the standard units of distance measurement on UK railways are miles and chains, expressed as 1m54c for 1 mile and 54 chains. There are exactly 80 chains in 1 mile, and 1 chain is approximately 20.1 meters.

Network Rail provides a number of live data feeds for timetables, train movements, etc. Websites showing live UK data will all be deriving it from the same source, so feel free to use whichever site works best.

=== Track and signalling ===

* [https://www.networkrail.co.uk/industry-and-commercial/information-for-operators/national-electronic-sectional-appendix/#SA Network Rail's Sectional Appendix] is the official description of every section of track managed by NR, showing track layouts, mileages, and all speed limits.
* [https://www.opentraintimes.com/maps OpenTrainTimes] provides live signalling maps for a range of areas, showing track and signal layouts.
* [https://traksy.uk/live/ Traksy] also provides live signalling maps.
* [https://www.railmaponline.com/UKIEMap.php UK & Irish Railways] is a website that essentially is a more accurate version of ORM for specifically the UK and Ireland. The website provides very accurate historical data, not just for station locations but also track layout. If you are looking to make a historically realistic UK save, this website is a must-have.

==== Historic ====
* [https://maps.nls.uk/ The National Library of Scotland's map archive] is widely considered to be the best source of historic maps of the UK.
* [https://britishrailways1960.co.uk/ British Railways in the 1960s] provides a subset of data showing track layouts for some lines, derived from British Railways sectional appendices ca. 1960.
* [https://www.s-r-s.org.uk/ The Signalling Record Society] has a significant collection of historic signalling information, with a fair amount available via its [https://www.s-r-s.org.uk/archivedigitalcatalogue.php digital archive], some to members only. It also offers CD/USB/downloads (few, but increasing in number!) of collections of [https://www.s-r-s.org.uk/Bookstall/ historic signalling diagrams].

=== Timetables ===

Note that platform allocations in published timetables may be wrong - it is not ''too'' unusual to see a train planned to arrive on one platform and then somehow teleport to form a different service from a different platform. It is also common to see ad-hoc "set swaps" on any given day in historic data, where two inbound trains swap platforms and take up each other's outbound services, so train diagrams or rolling stock allocations can vary day to day.

* [https://www.networkrail.co.uk/running-the-railway/the-timetable/working-timetable/ Network Rail's Working Timetable] is the official timetable for the national network, set over six month periods. However, you should consider using the online timetable feeds below - the format of the WTT makes it difficult to follow a single train across the network.
* [https://tfl.gov.uk/corporate/publications-and-reports/working-timetables TfL's Working Timetable] is the official timetable for the London Underground, also providing train allocations.
* [https://www.realtimetrains.co.uk/ Realtime Trains] provides full timetable data from NR data feeds - long-term planned timetables, short term alterations, and historic data up to 7 days in the past. RTT also provides live and historic train allocation data for most train operators (depending on the availability of data feeds).
* [https://www.opentraintimes.com/ OpenTrainTimes] also provides full timetable data from NR data feeds.
* [https://timetableworld.com/ Timetable World] is a comprehensive source of historic public timetables, as well as some employee timetables. Some can be viewed online on the site, some as free downloads, and some as paid downloads at a reasonable price.

= North America =
== United States ==
* [http://rail.guide/ Rail.guide] is a very useful tool for specifically American rails. While it isn't often the most accurate, it really depends on the region. Rail.guide often has data which ORM lacks, especially for historical data (either Current-Classic, Classic Owners or Early Owners map modes, abandoned is useful as well) which is by far the best feature of this website.
* [https://www.nashuacitystation.org/ Nashua City Station] is a railroad history website that provides very accurate and useful historical railroad data for mainly states in the New England region of the U.S. whether you want to know the exact location of a random station in Rhode Island or just want to see what trains used to run to Worcester, MA, this website has your back.
* The [https://www.loc.gov/ Library of Congress] has a large collection of historical railroad maps, the site can be hard to navigate but it's very useful.
* [https://www.american-rails.com/ American-Rails] is a very useful site for U.S. railroad information, specifically historical. There are articles for almost every "Fallen Flag" of U.S. railroads, each one written in great detail often including a detailed map of the railroad at its peak, with other useful data to work from as well.
* [https://www.vanshnookenraggen.com/_index/ Vanshnookenraggen] creates many highly realistic track maps for U.S. transit systems such as Chicago's "L" and the New York City Subway, as well as creating historical track maps and track maps with planned extensions built out.
* [https://timetableworld.com/nam-official-guide/ Timetable World's Official Guide of the Railways] collection provides historic passenger timetables for all of North America from 1868 to 1971. Follow guidance on the page for information on how to access the free online viewer.
* [https://wx4.org/to/foam/maps/and_timetables.html Wx4's Historical Maps & Timetables] archive contains a very large collection of employee timetables.
* [http://www.multimodalways.org/archives/rrs/rrs.html Multimodalways] provides an assorted archive of rail (and other) documentation.

=== New York ===
==== New York City ====
* [https://www.nycsubway.org/wiki/Main_Page nycsubway.org] is an excellent website with a large collection of New York City Subway track maps and track diagrams both historical and up-to-date. The website also has a very comprehensive history on the New York City Subway.
* [https://www.vanshnookenraggen.com/_index/docs/NYC_full_trackmap.pdf Vanshnookenraggen's New York City Subway Track Map] See, [[#vanshnookenraggen|first entry]] for why.
=== Illinois ===
==== Chicago ====
* [https://www.greatthirdrail.org/ GreatThirdRail.org] is the best site for anyone wanting to recreate the Chicago, Aurora & Elgin interurban railroad. This site specifically covers the CA&E and in great detail, providing very high quality historical maps and timetables, accurate station locations, anything you would really need to recreate the CA&E.
* [https://www.chicago-l.org/ Chicago-L.org] is the best site for information about the Chicago L, past, present or future. The amount of data on this site is extraordinary and I would highly recommend this website in addition to Wikipedia.
* [https://en.wikipedia.org/wiki/Template:Chicago_%22L%22_system_(all_time) Wikipedia's Chicago "L" system (all time) Track Diagram]. While Wikipedia is already on this page, this track diagram is especially useful for Chicago's "L", it should be noted that this track diagram contains all of the tracks past and present on the system, along with almost all stations having a dedicated article.
* [https://www.vanshnookenraggen.com/_index/docs/Chicago_TrackMap.pdf Vanshnookenraggen's Chicago "L" Track Map] See, [[#vanshnookenraggen|first entry]] for why.
* [https://wx4.org/to/foam/maps/and_timetables.html Wx4's Historical Maps & Timetables] archive contains a very large collection of
* [http://www.multimodalways.org/archives/rrs/rrs.html Multimodalways] provides an assorted archive of rail (and other) documentation.

= Oceania =
== Australia ==
=== Victoria ===
* [https://victorianrailways.net/index.html victorianrailways.net] has an amazing collection of historical railroad maps, timetables, line guides, etc for the state of Victoria, all in very high detail. This can help for historical recreations. This website is also in general a great collection of Victorian Railways history.
* [https://vicsig.net/ vicsig.net] is another great website for information on Victorian railway infrastructure, rolling stock and history either past, present or even future. The line guides on this website are paired well with the maps from [https://victorianrailways.net/index.html victorianrailways.net]
* [https://www.ptv.vic.gov.au/ Public Transport Victoria] is a useful website for timetables, maps and live updates related to all public transport in Victoria.
* [https://transportvic.me/ transportvic.me] is an unofficial website with trackers for all PTV vehicles (besides buses, due to a PTV data issue) and helpful information on frequencies, departure times, etc.

Resources for realism

2024-12-28T16:38:49Z

Danny252: Undo revision 477 by Danny252 (talk) - because I'm an idiot

This is a page that lists many resources useful for achieving realism in your NIMBY Rail saves. It is split up by country and region for your convenience.

= Worldwide =
* [https://www.openrailwaymap.org/ OpenRailwayMap] is the definitive mapping resource. OpenRailwayMap displays up-to-date data on railway tracks, providing information on track gauge, speed, electrification, etc. This is an absolute must-have for any player aiming for realism.
* [https://www.openstreetmap.org OpenStreetMap] is one of the best open source mapping resources, it often has more up-to-date and accurate map data compared to other mapping tools, with the only downside being a lack of satellite view. Use this if you want the most up-to-date mapping information.
* [https://www.google.com/maps Google Maps] is a very useful tool, especially given the often highly detailed satellite view you can get with it. While Google Maps is not as up-to-date as OpenStreetMap, you can still usually rely on it for accurate mapping data except in some niche cases. Another benefit of Google Maps is the "Public Transport" or "Transit" layer along with public transport integration in general. The accuracy of this integration can vary between public transport operators but it is still very useful.
* [https://www.wikipedia.org/ Wikipedia]. While the accuracy of Wikipedia articles does vary quite a bit between lines and operators, it can be extremely helpful and useful with finding service patterns, station locations, rolling stock, etc. Wikipedia is a must-have for NIMBY Rails realism.
* [https://www.transit.land/map/ Transit.land] is a tool which catalogues GTFS (realtime or static) data from transit operators around the world. This can help with finding specific routings for all transit modes, this is especially useful for visualising routings that may have seemed confusing in a non-map format.
* [https://timetableworld.com/ Timetable World] is a comprehensive source of historic timetables. Originally mainly UK in focus, it now has significant coverage worldwide. Some timetables are available to view online or download for free, others are available for a small fee.

= Europe=
== United Kingdom ==
Note that the standard units of distance measurement on UK railways are miles and chains, expressed as 1m54c for 1 mile and 54 chains. There are exactly 80 chains in 1 mile, and 1 chain is approximately 20.1 meters.

Network Rail provides a number of live data feeds for timetables, train movements, etc. Websites showing live UK data will all be deriving it from the same source, so feel free to use whichever site works best.

=== Track and signalling ===

* [https://www.networkrail.co.uk/industry-and-commercial/information-for-operators/national-electronic-sectional-appendix/#SA Network Rail's Sectional Appendix] is the official description of every section of track managed by NR, showing track layouts, mileages, and all speed limits.
* [https://www.opentraintimes.com/maps OpenTrainTimes] provides live signalling maps for a range of areas, showing track and signal layouts.
* [https://traksy.uk/live/ Traksy] also provides live signalling maps.
* [https://www.railmaponline.com/UKIEMap.php UK & Irish Railways] is a website that essentially is a more accurate version of ORM for specifically the UK and Ireland. The website provides very accurate historical data, not just for station locations but also track layout. If you are looking to make a historically realistic UK save, this website is a must-have.

==== Historic ====
* [https://maps.nls.uk/ The National Library of Scotland's map archive] is widely considered to be the best source of historic maps of the UK.
* [https://britishrailways1960.co.uk/ British Railways in the 1960s] provides a subset of data showing track layouts for some lines, derived from British Railways sectional appendices ca. 1960.
* [https://www.s-r-s.org.uk/ The Signalling Record Society] has a significant collection of historic signalling information, with a fair amount available via its [https://www.s-r-s.org.uk/archivedigitalcatalogue.php digital archive], some to members only. It also offers CD/USB/downloads (few, but increasing in number!) of collections of [https://www.s-r-s.org.uk/Bookstall/ historic signalling diagrams].

=== Timetables ===

Note that platform allocations in published timetables may be wrong - it is not ''too'' unusual to see a train planned to arrive on one platform and then somehow teleport to form a different service from a different platform. It is also common to see ad-hoc "set swaps" on any given day in historic data, where two inbound trains swap platforms and take up each other's outbound services, so train diagrams or rolling stock allocations can vary day to day.

* [https://www.networkrail.co.uk/running-the-railway/the-timetable/working-timetable/ Network Rail's Working Timetable] is the official timetable for the national network, set over six month periods. However, you should consider using the online timetable feeds below - the format of the WTT makes it difficult to follow a single train across the network.
* [https://tfl.gov.uk/corporate/publications-and-reports/working-timetables TfL's Working Timetable] is the official timetable for the London Underground, also providing train allocations.
* [https://www.realtimetrains.co.uk/ Realtime Trains] provides full timetable data from NR data feeds - long-term planned timetables, short term alterations, and historic data up to 7 days in the past. RTT also provides live and historic train allocation data for most train operators (depending on the availability of data feeds).
* [https://www.opentraintimes.com/ OpenTrainTimes] also provides full timetable data from NR data feeds.
* [https://timetableworld.com/ Timetable World] is a comprehensive source of historic public timetables, as well as some employee timetables. Some can be viewed online on the site, some as free downloads, and some as paid downloads at a reasonable price.

= North America =
== United States ==
* [http://rail.guide/ Rail.guide] is a very useful tool for specifically American rails. While it isn't often the most accurate, it really depends on the region. Rail.guide often has data which ORM lacks, especially for historical data (either Current-Classic, Classic Owners or Early Owners map modes, abandoned is useful as well) which is by far the best feature of this website.
* [https://www.nashuacitystation.org/ Nashua City Station] is a railroad history website that provides very accurate and useful historical railroad data for mainly states in the New England region of the U.S. whether you want to know the exact location of a random station in Rhode Island or just want to see what trains used to run to Worcester, MA, this website has your back.
* The [https://www.loc.gov/ Library of Congress] has a large collection of historical railroad maps, the site can be hard to navigate but it's very useful.
* [https://www.american-rails.com/ American-Rails] is a very useful site for U.S. railroad information, specifically historical. There are articles for almost every "Fallen Flag" of U.S. railroads, each one written in great detail often including a detailed map of the railroad at its peak, with other useful data to work from as well.
* [https://www.vanshnookenraggen.com/_index/ Vanshnookenraggen] creates many highly realistic track maps for U.S. transit systems such as Chicago's "L" and the New York City Subway, as well as creating historical track maps and track maps with planned extensions built out.
* [https://timetableworld.com/nam-official-guide/ Timetable World's Official Guide of the Railways] collection provides historic passenger timetables for all of North America from 1868 to 1971. Follow guidance on the page for information on how to access the free online viewer.
=== New York ===
==== New York City ====
* [https://www.nycsubway.org/wiki/Main_Page nycsubway.org] is an excellent website with a large collection of New York City Subway track maps and track diagrams both historical and up-to-date. The website also has a very comprehensive history on the New York City Subway.
* [https://www.vanshnookenraggen.com/_index/docs/NYC_full_trackmap.pdf Vanshnookenraggen's New York City Subway Track Map] See, [[#vanshnookenraggen|first entry]] for why.
=== Illinois ===
==== Chicago ====
* [https://www.greatthirdrail.org/ GreatThirdRail.org] is the best site for anyone wanting to recreate the Chicago, Aurora & Elgin interurban railroad. This site specifically covers the CA&E and in great detail, providing very high quality historical maps and timetables, accurate station locations, anything you would really need to recreate the CA&E.
* [https://www.chicago-l.org/ Chicago-L.org] is the best site for information about the Chicago L, past, present or future. The amount of data on this site is extraordinary and I would highly recommend this website in addition to Wikipedia.
* [https://en.wikipedia.org/wiki/Template:Chicago_%22L%22_system_(all_time) Wikipedia's Chicago "L" system (all time) Track Diagram]. While Wikipedia is already on this page, this track diagram is especially useful for Chicago's "L", it should be noted that this track diagram contains all of the tracks past and present on the system, along with almost all stations having a dedicated article.
* [https://www.vanshnookenraggen.com/_index/docs/Chicago_TrackMap.pdf Vanshnookenraggen's Chicago "L" Track Map] See, [[#vanshnookenraggen|first entry]] for why.
* [https://wx4.org/to/foam/maps/and_timetables.html Wx4's Historical Maps & Timetables] archive contains a very large collection of
* [http://www.multimodalways.org/archives/rrs/rrs.html Multimodalways] provides an assorted archive of rail (and other) documentation.

= Oceania =
== Australia ==
=== Victoria ===
* [https://victorianrailways.net/index.html victorianrailways.net] has an amazing collection of historical railroad maps, timetables, line guides, etc for the state of Victoria, all in very high detail. This can help for historical recreations. This website is also in general a great collection of Victorian Railways history.
* [https://vicsig.net/ vicsig.net] is another great website for information on Victorian railway infrastructure, rolling stock and history either past, present or even future. The line guides on this website are paired well with the maps from [https://victorianrailways.net/index.html victorianrailways.net]
* [https://www.ptv.vic.gov.au/ Public Transport Victoria] is a useful website for timetables, maps and live updates related to all public transport in Victoria.
* [https://transportvic.me/ transportvic.me] is an unofficial website with trackers for all PTV vehicles (besides buses, due to a PTV data issue) and helpful information on frequencies, departure times, etc.

Resources for realism

2024-12-28T16:38:08Z

Danny252: /* North America */ Timetable sources

= North America =
== United States ==
* [http://rail.guide/ Rail.guide] is a very useful tool for specifically American rails. While it isn't often the most accurate, it really depends on the region. Rail.guide often has data which ORM lacks, especially for historical data (either Current-Classic, Classic Owners or Early Owners map modes, abandoned is useful as well) which is by far the best feature of this website.
* [https://www.nashuacitystation.org/ Nashua City Station] is a railroad history website that provides very accurate and useful historical railroad data for mainly states in the New England region of the U.S. whether you want to know the exact location of a random station in Rhode Island or just want to see what trains used to run to Worcester, MA, this website has your back.
* The [https://www.loc.gov/ Library of Congress] has a large collection of historical railroad maps, the site can be hard to navigate but it's very useful.
* [https://www.american-rails.com/ American-Rails] is a very useful site for U.S. railroad information, specifically historical. There are articles for almost every "Fallen Flag" of U.S. railroads, each one written in great detail often including a detailed map of the railroad at its peak, with other useful data to work from as well.
* [https://www.vanshnookenraggen.com/_index/ Vanshnookenraggen] creates many highly realistic track maps for U.S. transit systems such as Chicago's "L" and the New York City Subway, as well as creating historical track maps and track maps with planned extensions built out.
* [https://timetableworld.com/nam-official-guide/ Timetable World's Official Guide of the Railways] collection provides historic passenger timetables for all of North America from 1868 to 1971. Follow guidance on the page for information on how to access the free online viewer.
* [https://wx4.org/to/foam/maps/and_timetables.html Wx4's Historical Maps & Timetables] archive contains a very large collection of
* [http://www.multimodalways.org/archives/rrs/rrs.html Multimodalways] provides an assorted archive of rail (and other) documentation.
=== New York ===
==== New York City ====
* [https://www.nycsubway.org/wiki/Main_Page nycsubway.org] is an excellent website with a large collection of New York City Subway track maps and track diagrams both historical and up-to-date. The website also has a very comprehensive history on the New York City Subway.
* [https://www.vanshnookenraggen.com/_index/docs/NYC_full_trackmap.pdf Vanshnookenraggen's New York City Subway Track Map] See, [[#vanshnookenraggen|first entry]] for why.
=== Illinois ===
==== Chicago ====
* [https://www.greatthirdrail.org/ GreatThirdRail.org] is the best site for anyone wanting to recreate the Chicago, Aurora & Elgin interurban railroad. This site specifically covers the CA&E and in great detail, providing very high quality historical maps and timetables, accurate station locations, anything you would really need to recreate the CA&E.
* [https://www.chicago-l.org/ Chicago-L.org] is the best site for information about the Chicago L, past, present or future. The amount of data on this site is extraordinary and I would highly recommend this website in addition to Wikipedia.
* [https://en.wikipedia.org/wiki/Template:Chicago_%22L%22_system_(all_time) Wikipedia's Chicago "L" system (all time) Track Diagram]. While Wikipedia is already on this page, this track diagram is especially useful for Chicago's "L", it should be noted that this track diagram contains all of the tracks past and present on the system, along with almost all stations having a dedicated article.
* [https://www.vanshnookenraggen.com/_index/docs/Chicago_TrackMap.pdf Vanshnookenraggen's Chicago "L" Track Map] See, [[#vanshnookenraggen|first entry]] for why.

Resources for realism

2024-12-28T16:16:10Z

Danny252: /* Track and signalling */ SRS

This is a page that lists many resources useful for achieving realism in your NIMBY Rail saves. It is split up by country and region for your convenience.

= Worldwide =
* [https://www.openrailwaymap.org/ OpenRailwayMap] is the definitive mapping resource. OpenRailwayMap displays up-to-date data on railway tracks, providing information on track gauge, speed, electrification, etc. This is an absolute must-have for any player aiming for realism.
* [https://www.openstreetmap.org OpenStreetMap] is one of the best open source mapping resources, it often has more up-to-date and accurate map data compared to other mapping tools, with the only downside being a lack of satellite view. Use this if you want the most up-to-date mapping information.
* [https://www.google.com/maps Google Maps] is a very useful tool, especially given the often highly detailed satellite view you can get with it. While Google Maps is not as up-to-date as OpenStreetMap, you can still usually rely on it for accurate mapping data except in some niche cases. Another benefit of Google Maps is the "Public Transport" or "Transit" layer along with public transport integration in general. The accuracy of this integration can vary between public transport operators but it is still very useful.
* [https://www.wikipedia.org/ Wikipedia]. While the accuracy of Wikipedia articles does vary quite a bit between lines and operators, it can be extremely helpful and useful with finding service patterns, station locations, rolling stock, etc. Wikipedia is a must-have for NIMBY Rails realism.
* [https://www.transit.land/map/ Transit.land] is a tool which catalogues GTFS (realtime or static) data from transit operators around the world. This can help with finding specific routings for all transit modes, this is especially useful for visualising routings that may have seemed confusing in a non-map format.
* [https://timetableworld.com/ Timetable World] is a comprehensive source of historic timetables. Originally mainly UK in focus, it now has significant coverage worldwide. Some timetables are available to view online or download for free, others are available for a small fee.

= Europe=
== United Kingdom ==
Note that the standard units of distance measurement on UK railways are miles and chains, expressed as 1m54c for 1 mile and 54 chains. There are exactly 80 chains in 1 mile, and 1 chain is approximately 20.1 meters.

Network Rail provides a number of live data feeds for timetables, train movements, etc. Websites showing live UK data will all be deriving it from the same source, so feel free to use whichever site works best.

=== Track and signalling ===

* [https://www.networkrail.co.uk/industry-and-commercial/information-for-operators/national-electronic-sectional-appendix/#SA Network Rail's Sectional Appendix] is the official description of every section of track managed by NR, showing track layouts, mileages, and all speed limits.
* [https://www.opentraintimes.com/maps OpenTrainTimes] provides live signalling maps for a range of areas, showing track and signal layouts.
* [https://traksy.uk/live/ Traksy] also provides live signalling maps.
* [https://www.railmaponline.com/UKIEMap.php UK & Irish Railways] is a website that essentially is a more accurate version of ORM for specifically the UK and Ireland. The website provides very accurate historical data, not just for station locations but also track layout. If you are looking to make a historically realistic UK save, this website is a must-have.

==== Historic ====
* [https://maps.nls.uk/ The National Library of Scotland's map archive] is widely considered to be the best source of historic maps of the UK.
* [https://britishrailways1960.co.uk/ British Railways in the 1960s] provides a subset of data showing track layouts for some lines, derived from British Railways sectional appendices ca. 1960.
* [https://www.s-r-s.org.uk/ The Signalling Record Society] has a significant collection of historic signalling information, with a fair amount available via its [https://www.s-r-s.org.uk/archivedigitalcatalogue.php digital archive], some to members only. It also offers CD/USB/downloads (few, but increasing in number!) of collections of [https://www.s-r-s.org.uk/Bookstall/ historic signalling diagrams].

=== Timetables ===

Note that platform allocations in published timetables may be wrong - it is not ''too'' unusual to see a train planned to arrive on one platform and then somehow teleport to form a different service from a different platform. It is also common to see ad-hoc "set swaps" on any given day in historic data, where two inbound trains swap platforms and take up each other's outbound services, so train diagrams or rolling stock allocations can vary day to day.

* [https://www.networkrail.co.uk/running-the-railway/the-timetable/working-timetable/ Network Rail's Working Timetable] is the official timetable for the national network, set over six month periods. However, you should consider using the online timetable feeds below - the format of the WTT makes it difficult to follow a single train across the network.
* [https://tfl.gov.uk/corporate/publications-and-reports/working-timetables TfL's Working Timetable] is the official timetable for the London Underground, also providing train allocations.
* [https://www.realtimetrains.co.uk/ Realtime Trains] provides full timetable data from NR data feeds - long-term planned timetables, short term alterations, and historic data up to 7 days in the past. RTT also provides live and historic train allocation data for most train operators (depending on the availability of data feeds).
* [https://www.opentraintimes.com/ OpenTrainTimes] also provides full timetable data from NR data feeds.
* [https://timetableworld.com/ Timetable World] is a comprehensive source of historic public timetables, as well as some employee timetables. Some can be viewed online on the site, some as free downloads, and some as paid downloads at a reasonable price.

= North America =
== United States ==
* [http://rail.guide/ Rail.guide] is a very useful tool for specifically American rails. While it isn't often the most accurate, it really depends on the region. Rail.guide often has data which ORM lacks, especially for historical data (either Current-Classic, Classic Owners or Early Owners map modes, abandoned is useful as well) which is by far the best feature of this website.
* [https://www.nashuacitystation.org/ Nashua City Station] is a railroad history website that provides very accurate and useful historical railroad data for mainly states in the New England region of the U.S. whether you want to know the exact location of a random station in Rhode Island or just want to see what trains used to run to Worcester, MA, this website has your back.
* The [https://www.loc.gov/ Library of Congress] has a large collection of historical railroad maps, the site can be hard to navigate but it's very useful.
* [https://www.american-rails.com/ American-Rails] is a very useful site for U.S. railroad information, specifically historical. There are articles for almost every "Fallen Flag" of U.S. railroads, each one written in great detail often including a detailed map of the railroad at its peak, with other useful data to work from as well.
* [https://www.vanshnookenraggen.com/_index/ Vanshnookenraggen] creates many highly realistic track maps for U.S. transit systems such as Chicago's "L" and the New York City Subway, as well as creating historical track maps and track maps with planned extensions built out.
* [https://timetableworld.com/nam-official-guide/ Timetable World's Official Guide of the Railways] collection provides historic passenger timetables for all of North America from 1868 to 1971. Follow guidance on the page for information on how to access the free online viewer.
=== New York ===
==== New York City ====
* [https://www.nycsubway.org/wiki/Main_Page nycsubway.org] is an excellent website with a large collection of New York City Subway track maps and track diagrams both historical and up-to-date. The website also has a very comprehensive history on the New York City Subway.
* [https://www.vanshnookenraggen.com/_index/docs/NYC_full_trackmap.pdf Vanshnookenraggen's New York City Subway Track Map] See, [[#vanshnookenraggen|first entry]] for why.
=== Illinois ===
==== Chicago ====
* [https://www.greatthirdrail.org/ GreatThirdRail.org] is the best site for anyone wanting to recreate the Chicago, Aurora & Elgin interurban railroad. This site specifically covers the CA&E and in great detail, providing very high quality historical maps and timetables, accurate station locations, anything you would really need to recreate the CA&E.
* [https://www.chicago-l.org/ Chicago-L.org] is the best site for information about the Chicago L, past, present or future. The amount of data on this site is extraordinary and I would highly recommend this website in addition to Wikipedia.
* [https://en.wikipedia.org/wiki/Template:Chicago_%22L%22_system_(all_time) Wikipedia's Chicago "L" system (all time) Track Diagram]. While Wikipedia is already on this page, this track diagram is especially useful for Chicago's "L", it should be noted that this track diagram contains all of the tracks past and present on the system, along with almost all stations having a dedicated article.
* [https://www.vanshnookenraggen.com/_index/docs/Chicago_TrackMap.pdf Vanshnookenraggen's Chicago "L" Track Map] See, [[#vanshnookenraggen|first entry]] for why.

= Oceania =
== Australia ==
=== Victoria ===
* [https://victorianrailways.net/index.html victorianrailways.net] has an amazing collection of historical railroad maps, timetables, line guides, etc for the state of Victoria, all in very high detail. This can help for historical recreations. This website is also in general a great collection of Victorian Railways history.
* [https://vicsig.net/ vicsig.net] is another great website for information on Victorian railway infrastructure, rolling stock and history either past, present or even future. The line guides on this website are paired well with the maps from [https://victorianrailways.net/index.html victorianrailways.net]
* [https://www.ptv.vic.gov.au/ Public Transport Victoria] is a useful website for timetables, maps and live updates related to all public transport in Victoria.
* [https://transportvic.me/ transportvic.me] is an unofficial website with trackers for all PTV vehicles (besides buses, due to a PTV data issue) and helpful information on frequencies, departure times, etc.

Resources for realism

2024-12-28T16:12:06Z

Danny252: /* United States */ Timetable World

This is a page that lists many resources useful for achieving realism in your NIMBY Rail saves. It is split up by country and region for your convenience.

= Worldwide =
* [https://www.openrailwaymap.org/ OpenRailwayMap] is the definitive mapping resource. OpenRailwayMap displays up-to-date data on railway tracks, providing information on track gauge, speed, electrification, etc. This is an absolute must-have for any player aiming for realism.
* [https://www.openstreetmap.org OpenStreetMap] is one of the best open source mapping resources, it often has more up-to-date and accurate map data compared to other mapping tools, with the only downside being a lack of satellite view. Use this if you want the most up-to-date mapping information.
* [https://www.google.com/maps Google Maps] is a very useful tool, especially given the often highly detailed satellite view you can get with it. While Google Maps is not as up-to-date as OpenStreetMap, you can still usually rely on it for accurate mapping data except in some niche cases. Another benefit of Google Maps is the "Public Transport" or "Transit" layer along with public transport integration in general. The accuracy of this integration can vary between public transport operators but it is still very useful.
* [https://www.wikipedia.org/ Wikipedia]. While the accuracy of Wikipedia articles does vary quite a bit between lines and operators, it can be extremely helpful and useful with finding service patterns, station locations, rolling stock, etc. Wikipedia is a must-have for NIMBY Rails realism.
* [https://www.transit.land/map/ Transit.land] is a tool which catalogues GTFS (realtime or static) data from transit operators around the world. This can help with finding specific routings for all transit modes, this is especially useful for visualising routings that may have seemed confusing in a non-map format.
* [https://timetableworld.com/ Timetable World] is a comprehensive source of historic timetables. Originally mainly UK in focus, it now has significant coverage worldwide. Some timetables are available to view online or download for free, others are available for a small fee.

= Europe=
== United Kingdom ==
Note that the standard units of distance measurement on UK railways are miles and chains, expressed as 1m54c for 1 mile and 54 chains. There are exactly 80 chains in 1 mile, and 1 chain is approximately 20.1 meters.

Network Rail provides a number of live data feeds for timetables, train movements, etc. Websites showing live UK data will all be deriving it from the same source, so feel free to use whichever site works best.

=== Track and signalling ===

* [https://www.networkrail.co.uk/industry-and-commercial/information-for-operators/national-electronic-sectional-appendix/#SA Network Rail's Sectional Appendix] is the official description of every section of track managed by NR, showing track layouts, mileages, and all speed limits.
* [https://www.opentraintimes.com/maps OpenTrainTimes] provides live signalling maps for a range of areas, showing track and signal layouts.
* [https://traksy.uk/live/ Traksy] also provides live signalling maps.
* [https://www.railmaponline.com/UKIEMap.php UK & Irish Railways] is a website that essentially is a more accurate version of ORM for specifically the UK and Ireland. The website provides very accurate historical data, not just for station locations but also track layout. If you are looking to make a historically realistic UK save, this website is a must-have.

==== Historic ====
* [https://maps.nls.uk/ The National Library of Scotland's map archive] is widely considered to be the best source of historic maps of the UK.
* [https://britishrailways1960.co.uk/ British Railways in the 1960s] provides a subset of data showing track layouts for some lines, derived from British Railways sectional appendices ca. 1960.

=== Timetables ===

Note that platform allocations in published timetables may be wrong - it is not ''too'' unusual to see a train planned to arrive on one platform and then somehow teleport to form a different service from a different platform. It is also common to see ad-hoc "set swaps" on any given day in historic data, where two inbound trains swap platforms and take up each other's outbound services, so train diagrams or rolling stock allocations can vary day to day.

* [https://www.networkrail.co.uk/running-the-railway/the-timetable/working-timetable/ Network Rail's Working Timetable] is the official timetable for the national network, set over six month periods. However, you should consider using the online timetable feeds below - the format of the WTT makes it difficult to follow a single train across the network.
* [https://tfl.gov.uk/corporate/publications-and-reports/working-timetables TfL's Working Timetable] is the official timetable for the London Underground, also providing train allocations.
* [https://www.realtimetrains.co.uk/ Realtime Trains] provides full timetable data from NR data feeds - long-term planned timetables, short term alterations, and historic data up to 7 days in the past. RTT also provides live and historic train allocation data for most train operators (depending on the availability of data feeds).
* [https://www.opentraintimes.com/ OpenTrainTimes] also provides full timetable data from NR data feeds.
* [https://timetableworld.com/ Timetable World] is a comprehensive source of historic public timetables, as well as some employee timetables. Some can be viewed online on the site, some as free downloads, and some as paid downloads at a reasonable price.

= North America =
== United States ==
* [http://rail.guide/ Rail.guide] is a very useful tool for specifically American rails. While it isn't often the most accurate, it really depends on the region. Rail.guide often has data which ORM lacks, especially for historical data (either Current-Classic, Classic Owners or Early Owners map modes, abandoned is useful as well) which is by far the best feature of this website.
* [https://www.nashuacitystation.org/ Nashua City Station] is a railroad history website that provides very accurate and useful historical railroad data for mainly states in the New England region of the U.S. whether you want to know the exact location of a random station in Rhode Island or just want to see what trains used to run to Worcester, MA, this website has your back.
* The [https://www.loc.gov/ Library of Congress] has a large collection of historical railroad maps, the site can be hard to navigate but it's very useful.
* [https://www.american-rails.com/ American-Rails] is a very useful site for U.S. railroad information, specifically historical. There are articles for almost every "Fallen Flag" of U.S. railroads, each one written in great detail often including a detailed map of the railroad at its peak, with other useful data to work from as well.
* [https://www.vanshnookenraggen.com/_index/ Vanshnookenraggen] creates many highly realistic track maps for U.S. transit systems such as Chicago's "L" and the New York City Subway, as well as creating historical track maps and track maps with planned extensions built out.
* [https://timetableworld.com/nam-official-guide/ Timetable World's Official Guide of the Railways] collection provides historic passenger timetables for all of North America from 1868 to 1971. Follow guidance on the page for information on how to access the free online viewer.
=== New York ===
==== New York City ====
* [https://www.nycsubway.org/wiki/Main_Page nycsubway.org] is an excellent website with a large collection of New York City Subway track maps and track diagrams both historical and up-to-date. The website also has a very comprehensive history on the New York City Subway.
* [https://www.vanshnookenraggen.com/_index/docs/NYC_full_trackmap.pdf Vanshnookenraggen's New York City Subway Track Map] See, [[#vanshnookenraggen|first entry]] for why.
=== Illinois ===
==== Chicago ====
* [https://www.greatthirdrail.org/ GreatThirdRail.org] is the best site for anyone wanting to recreate the Chicago, Aurora & Elgin interurban railroad. This site specifically covers the CA&E and in great detail, providing very high quality historical maps and timetables, accurate station locations, anything you would really need to recreate the CA&E.
* [https://www.chicago-l.org/ Chicago-L.org] is the best site for information about the Chicago L, past, present or future. The amount of data on this site is extraordinary and I would highly recommend this website in addition to Wikipedia.
* [https://en.wikipedia.org/wiki/Template:Chicago_%22L%22_system_(all_time) Wikipedia's Chicago "L" system (all time) Track Diagram]. While Wikipedia is already on this page, this track diagram is especially useful for Chicago's "L", it should be noted that this track diagram contains all of the tracks past and present on the system, along with almost all stations having a dedicated article.
* [https://www.vanshnookenraggen.com/_index/docs/Chicago_TrackMap.pdf Vanshnookenraggen's Chicago "L" Track Map] See, [[#vanshnookenraggen|first entry]] for why.

= Oceania =
== Australia ==
=== Victoria ===
* [https://victorianrailways.net/index.html victorianrailways.net] has an amazing collection of historical railroad maps, timetables, line guides, etc for the state of Victoria, all in very high detail. This can help for historical recreations. This website is also in general a great collection of Victorian Railways history.
* [https://vicsig.net/ vicsig.net] is another great website for information on Victorian railway infrastructure, rolling stock and history either past, present or even future. The line guides on this website are paired well with the maps from [https://victorianrailways.net/index.html victorianrailways.net]
* [https://www.ptv.vic.gov.au/ Public Transport Victoria] is a useful website for timetables, maps and live updates related to all public transport in Victoria.
* [https://transportvic.me/ transportvic.me] is an unofficial website with trackers for all PTV vehicles (besides buses, due to a PTV data issue) and helpful information on frequencies, departure times, etc.

Resources for realism

2024-12-28T16:09:38Z

Danny252: /* Worldwide */ Timetable world

This is a page that lists many resources useful for achieving realism in your NIMBY Rail saves. It is split up by country and region for your convenience.

= Worldwide =
* [https://www.openrailwaymap.org/ OpenRailwayMap] is the definitive mapping resource. OpenRailwayMap displays up-to-date data on railway tracks, providing information on track gauge, speed, electrification, etc. This is an absolute must-have for any player aiming for realism.
* [https://www.openstreetmap.org OpenStreetMap] is one of the best open source mapping resources, it often has more up-to-date and accurate map data compared to other mapping tools, with the only downside being a lack of satellite view. Use this if you want the most up-to-date mapping information.
* [https://www.google.com/maps Google Maps] is a very useful tool, especially given the often highly detailed satellite view you can get with it. While Google Maps is not as up-to-date as OpenStreetMap, you can still usually rely on it for accurate mapping data except in some niche cases. Another benefit of Google Maps is the "Public Transport" or "Transit" layer along with public transport integration in general. The accuracy of this integration can vary between public transport operators but it is still very useful.
* [https://www.wikipedia.org/ Wikipedia]. While the accuracy of Wikipedia articles does vary quite a bit between lines and operators, it can be extremely helpful and useful with finding service patterns, station locations, rolling stock, etc. Wikipedia is a must-have for NIMBY Rails realism.
* [https://www.transit.land/map/ Transit.land] is a tool which catalogues GTFS (realtime or static) data from transit operators around the world. This can help with finding specific routings for all transit modes, this is especially useful for visualising routings that may have seemed confusing in a non-map format.
* [https://timetableworld.com/ Timetable World] is a comprehensive source of historic timetables. Originally mainly UK in focus, it now has significant coverage worldwide. Some timetables are available to view online or download for free, others are available for a small fee.

= Europe=
== United Kingdom ==
Note that the standard units of distance measurement on UK railways are miles and chains, expressed as 1m54c for 1 mile and 54 chains. There are exactly 80 chains in 1 mile, and 1 chain is approximately 20.1 meters.

Network Rail provides a number of live data feeds for timetables, train movements, etc. Websites showing live UK data will all be deriving it from the same source, so feel free to use whichever site works best.

=== Track and signalling ===

* [https://www.networkrail.co.uk/industry-and-commercial/information-for-operators/national-electronic-sectional-appendix/#SA Network Rail's Sectional Appendix] is the official description of every section of track managed by NR, showing track layouts, mileages, and all speed limits.
* [https://www.opentraintimes.com/maps OpenTrainTimes] provides live signalling maps for a range of areas, showing track and signal layouts.
* [https://traksy.uk/live/ Traksy] also provides live signalling maps.
* [https://www.railmaponline.com/UKIEMap.php UK & Irish Railways] is a website that essentially is a more accurate version of ORM for specifically the UK and Ireland. The website provides very accurate historical data, not just for station locations but also track layout. If you are looking to make a historically realistic UK save, this website is a must-have.

==== Historic ====
* [https://maps.nls.uk/ The National Library of Scotland's map archive] is widely considered to be the best source of historic maps of the UK.
* [https://britishrailways1960.co.uk/ British Railways in the 1960s] provides a subset of data showing track layouts for some lines, derived from British Railways sectional appendices ca. 1960.

=== Timetables ===

Note that platform allocations in published timetables may be wrong - it is not ''too'' unusual to see a train planned to arrive on one platform and then somehow teleport to form a different service from a different platform. It is also common to see ad-hoc "set swaps" on any given day in historic data, where two inbound trains swap platforms and take up each other's outbound services, so train diagrams or rolling stock allocations can vary day to day.

* [https://www.networkrail.co.uk/running-the-railway/the-timetable/working-timetable/ Network Rail's Working Timetable] is the official timetable for the national network, set over six month periods. However, you should consider using the online timetable feeds below - the format of the WTT makes it difficult to follow a single train across the network.
* [https://tfl.gov.uk/corporate/publications-and-reports/working-timetables TfL's Working Timetable] is the official timetable for the London Underground, also providing train allocations.
* [https://www.realtimetrains.co.uk/ Realtime Trains] provides full timetable data from NR data feeds - long-term planned timetables, short term alterations, and historic data up to 7 days in the past. RTT also provides live and historic train allocation data for most train operators (depending on the availability of data feeds).
* [https://www.opentraintimes.com/ OpenTrainTimes] also provides full timetable data from NR data feeds.
* [https://timetableworld.com/ Timetable World] is a comprehensive source of historic public timetables, as well as some employee timetables. Some can be viewed online on the site, some as free downloads, and some as paid downloads at a reasonable price.

= North America =
== United States ==
* [http://rail.guide/ Rail.guide] is a very useful tool for specifically American rails. While it isn't often the most accurate, it really depends on the region. Rail.guide often has data which ORM lacks, especially for historical data (either Current-Classic, Classic Owners or Early Owners map modes, abandoned is useful as well) which is by far the best feature of this website.
* [https://www.nashuacitystation.org/ Nashua City Station] is a railroad history website that provides very accurate and useful historical railroad data for mainly states in the New England region of the U.S. whether you want to know the exact location of a random station in Rhode Island or just want to see what trains used to run to Worcester, MA, this website has your back.
* The [https://www.loc.gov/ Library of Congress] has a large collection of historical railroad maps, the site can be hard to navigate but it's very useful.
* [https://www.american-rails.com/ American-Rails] is a very useful site for U.S. railroad information, specifically historical. There are articles for almost every "Fallen Flag" of U.S. railroads, each one written in great detail often including a detailed map of the railroad at its peak, with other useful data to work from as well.
* [https://www.vanshnookenraggen.com/_index/ Vanshnookenraggen] creates many highly realistic track maps for U.S. transit systems such as Chicago's "L" and the New York City Subway, as well as creating historical track maps and track maps with planned extensions built out.
=== New York ===
==== New York City ====
* [https://www.nycsubway.org/wiki/Main_Page nycsubway.org] is an excellent website with a large collection of New York City Subway track maps and track diagrams both historical and up-to-date. The website also has a very comprehensive history on the New York City Subway.
* [https://www.vanshnookenraggen.com/_index/docs/NYC_full_trackmap.pdf Vanshnookenraggen's New York City Subway Track Map] See, [[#vanshnookenraggen|first entry]] for why.
=== Illinois ===
==== Chicago ====
* [https://www.greatthirdrail.org/ GreatThirdRail.org] is the best site for anyone wanting to recreate the Chicago, Aurora & Elgin interurban railroad. This site specifically covers the CA&E and in great detail, providing very high quality historical maps and timetables, accurate station locations, anything you would really need to recreate the CA&E.
* [https://www.chicago-l.org/ Chicago-L.org] is the best site for information about the Chicago L, past, present or future. The amount of data on this site is extraordinary and I would highly recommend this website in addition to Wikipedia.
* [https://en.wikipedia.org/wiki/Template:Chicago_%22L%22_system_(all_time) Wikipedia's Chicago "L" system (all time) Track Diagram]. While Wikipedia is already on this page, this track diagram is especially useful for Chicago's "L", it should be noted that this track diagram contains all of the tracks past and present on the system, along with almost all stations having a dedicated article.
* [https://www.vanshnookenraggen.com/_index/docs/Chicago_TrackMap.pdf Vanshnookenraggen's Chicago "L" Track Map] See, [[#vanshnookenraggen|first entry]] for why.

= Oceania =
== Australia ==
=== Victoria ===
* [https://victorianrailways.net/index.html victorianrailways.net] has an amazing collection of historical railroad maps, timetables, line guides, etc for the state of Victoria, all in very high detail. This can help for historical recreations. This website is also in general a great collection of Victorian Railways history.
* [https://vicsig.net/ vicsig.net] is another great website for information on Victorian railway infrastructure, rolling stock and history either past, present or even future. The line guides on this website are paired well with the maps from [https://victorianrailways.net/index.html victorianrailways.net]
* [https://www.ptv.vic.gov.au/ Public Transport Victoria] is a useful website for timetables, maps and live updates related to all public transport in Victoria.
* [https://transportvic.me/ transportvic.me] is an unofficial website with trackers for all PTV vehicles (besides buses, due to a PTV data issue) and helpful information on frequencies, departure times, etc.

Resources for realism

2024-12-28T16:08:05Z

Danny252: /* United Kingdom */

This is a page that lists many resources useful for achieving realism in your NIMBY Rail saves. It is split up by country and region for your convenience.

= Worldwide =
* [https://www.openrailwaymap.org/ OpenRailwayMap] is the definitive mapping resource. OpenRailwayMap displays up-to-date data on railway tracks, providing information on track gauge, speed, electrification, etc. This is an absolute must-have for any player aiming for realism.
* [https://www.openstreetmap.org OpenStreetMap] is one of the best open source mapping resources, it often has more up-to-date and accurate map data compared to other mapping tools, with the only downside being a lack of satellite view. Use this if you want the most up-to-date mapping information.
* [https://www.google.com/maps Google Maps] is a very useful tool, especially given the often highly detailed satellite view you can get with it. While Google Maps is not as up-to-date as OpenStreetMap, you can still usually rely on it for accurate mapping data except in some niche cases. Another benefit of Google Maps is the "Public Transport" or "Transit" layer along with public transport integration in general. The accuracy of this integration can vary between public transport operators but it is still very useful.
* [https://www.wikipedia.org/ Wikipedia]. While the accuracy of Wikipedia articles does vary quite a bit between lines and operators, it can be extremely helpful and useful with finding service patterns, station locations, rolling stock, etc. Wikipedia is a must-have for NIMBY Rails realism.
* [https://www.transit.land/map/ Transit.land] is a tool which catalogues GTFS (realtime or static) data from transit operators around the world. This can help with finding specific routings for all transit modes, this is especially useful for visualising routings that may have seemed confusing in a non-map format.
= Europe=
== United Kingdom ==
Note that the standard units of distance measurement on UK railways are miles and chains, expressed as 1m54c for 1 mile and 54 chains. There are exactly 80 chains in 1 mile, and 1 chain is approximately 20.1 meters.

Network Rail provides a number of live data feeds for timetables, train movements, etc. Websites showing live UK data will all be deriving it from the same source, so feel free to use whichever site works best.

=== Track and signalling ===

* [https://www.networkrail.co.uk/industry-and-commercial/information-for-operators/national-electronic-sectional-appendix/#SA Network Rail's Sectional Appendix] is the official description of every section of track managed by NR, showing track layouts, mileages, and all speed limits.
* [https://www.opentraintimes.com/maps OpenTrainTimes] provides live signalling maps for a range of areas, showing track and signal layouts.
* [https://traksy.uk/live/ Traksy] also provides live signalling maps.
* [https://www.railmaponline.com/UKIEMap.php UK & Irish Railways] is a website that essentially is a more accurate version of ORM for specifically the UK and Ireland. The website provides very accurate historical data, not just for station locations but also track layout. If you are looking to make a historically realistic UK save, this website is a must-have.

==== Historic ====
* [https://maps.nls.uk/ The National Library of Scotland's map archive] is widely considered to be the best source of historic maps of the UK.
* [https://britishrailways1960.co.uk/ British Railways in the 1960s] provides a subset of data showing track layouts for some lines, derived from British Railways sectional appendices ca. 1960.

=== Timetables ===

Note that platform allocations in published timetables may be wrong - it is not ''too'' unusual to see a train planned to arrive on one platform and then somehow teleport to form a different service from a different platform. It is also common to see ad-hoc "set swaps" on any given day in historic data, where two inbound trains swap platforms and take up each other's outbound services, so train diagrams or rolling stock allocations can vary day to day.

* [https://www.networkrail.co.uk/running-the-railway/the-timetable/working-timetable/ Network Rail's Working Timetable] is the official timetable for the national network, set over six month periods. However, you should consider using the online timetable feeds below - the format of the WTT makes it difficult to follow a single train across the network.
* [https://tfl.gov.uk/corporate/publications-and-reports/working-timetables TfL's Working Timetable] is the official timetable for the London Underground, also providing train allocations.
* [https://www.realtimetrains.co.uk/ Realtime Trains] provides full timetable data from NR data feeds - long-term planned timetables, short term alterations, and historic data up to 7 days in the past. RTT also provides live and historic train allocation data for most train operators (depending on the availability of data feeds).
* [https://www.opentraintimes.com/ OpenTrainTimes] also provides full timetable data from NR data feeds.
* [https://timetableworld.com/ Timetable World] is a comprehensive source of historic public timetables, as well as some employee timetables. Some can be viewed online on the site, some as free downloads, and some as paid downloads at a reasonable price.

= North America =
== United States ==
* [http://rail.guide/ Rail.guide] is a very useful tool for specifically American rails. While it isn't often the most accurate, it really depends on the region. Rail.guide often has data which ORM lacks, especially for historical data (either Current-Classic, Classic Owners or Early Owners map modes, abandoned is useful as well) which is by far the best feature of this website.
* [https://www.nashuacitystation.org/ Nashua City Station] is a railroad history website that provides very accurate and useful historical railroad data for mainly states in the New England region of the U.S. whether you want to know the exact location of a random station in Rhode Island or just want to see what trains used to run to Worcester, MA, this website has your back.
* The [https://www.loc.gov/ Library of Congress] has a large collection of historical railroad maps, the site can be hard to navigate but it's very useful.
* [https://www.american-rails.com/ American-Rails] is a very useful site for U.S. railroad information, specifically historical. There are articles for almost every "Fallen Flag" of U.S. railroads, each one written in great detail often including a detailed map of the railroad at its peak, with other useful data to work from as well.
* [https://www.vanshnookenraggen.com/_index/ Vanshnookenraggen] creates many highly realistic track maps for U.S. transit systems such as Chicago's "L" and the New York City Subway, as well as creating historical track maps and track maps with planned extensions built out.
=== New York ===
==== New York City ====
* [https://www.nycsubway.org/wiki/Main_Page nycsubway.org] is an excellent website with a large collection of New York City Subway track maps and track diagrams both historical and up-to-date. The website also has a very comprehensive history on the New York City Subway.
* [https://www.vanshnookenraggen.com/_index/docs/NYC_full_trackmap.pdf Vanshnookenraggen's New York City Subway Track Map] See, [[#vanshnookenraggen|first entry]] for why.
=== Illinois ===
==== Chicago ====
* [https://www.greatthirdrail.org/ GreatThirdRail.org] is the best site for anyone wanting to recreate the Chicago, Aurora & Elgin interurban railroad. This site specifically covers the CA&E and in great detail, providing very high quality historical maps and timetables, accurate station locations, anything you would really need to recreate the CA&E.
* [https://www.chicago-l.org/ Chicago-L.org] is the best site for information about the Chicago L, past, present or future. The amount of data on this site is extraordinary and I would highly recommend this website in addition to Wikipedia.
* [https://en.wikipedia.org/wiki/Template:Chicago_%22L%22_system_(all_time) Wikipedia's Chicago "L" system (all time) Track Diagram]. While Wikipedia is already on this page, this track diagram is especially useful for Chicago's "L", it should be noted that this track diagram contains all of the tracks past and present on the system, along with almost all stations having a dedicated article.
* [https://www.vanshnookenraggen.com/_index/docs/Chicago_TrackMap.pdf Vanshnookenraggen's Chicago "L" Track Map] See, [[#vanshnookenraggen|first entry]] for why.

= Oceania =
== Australia ==
=== Victoria ===
* [https://victorianrailways.net/index.html victorianrailways.net] has an amazing collection of historical railroad maps, timetables, line guides, etc for the state of Victoria, all in very high detail. This can help for historical recreations. This website is also in general a great collection of Victorian Railways history.
* [https://vicsig.net/ vicsig.net] is another great website for information on Victorian railway infrastructure, rolling stock and history either past, present or even future. The line guides on this website are paired well with the maps from [https://victorianrailways.net/index.html victorianrailways.net]
* [https://www.ptv.vic.gov.au/ Public Transport Victoria] is a useful website for timetables, maps and live updates related to all public transport in Victoria.
* [https://transportvic.me/ transportvic.me] is an unofficial website with trackers for all PTV vehicles (besides buses, due to a PTV data issue) and helpful information on frequencies, departure times, etc.

How to have multiple trains share a platform

2023-10-15T16:26:24Z

Danny252:

From [[Version 1.9]], the Advanced mode for stop creation allows trains to share platforms. In this mode, the player specifies the exact stopping point for trains, and provided that two trains will not overlap while stopped in the station, NIMBY will allow them to share the platform.

__TOC__

== Platform sharing for trains arriving and departing in different directions ==

In the example below, the line A-B (red) runs from Ayton to Beesville, and the line B-C (green) runs from Beesville to Ceeside:

[[File:PlatformSharingABCLayout.png|1200px]]

At Beesville, both trains use Platform 1 simultaneously:

[[File:PlatformSharingBeesvilleTrains.png|1200px]]

The platform at Beesville is 250m long. Both trains are 80m long, and so there is plenty of space for both to use the platform.

On Line A-B, the stop at Beesville was created using Advanced mode. A stopping position 5m from the near end of the platform was selected, choosing the west-facing arrow marked as "245m":

[[File:PlatformSharingBeesville LineABConfig.png]]

Line B-C is set up in the same way, choosing a stopping position facing east at its end of the platform:

[[File:PlatformSharingBeesville LineBCConfig.png]]

=== Trains too long ===

If the trains will not fit in the platform simultaneously, the signalling system will not permit them to enter.

In the example below, both trains are 140m long, and they are too long for the 250m platform at Beesville. Train A-B arrived first and entered the platform, but train B-C is being held at a red signal because there is not enough room for it to fully enter the platform:

[[File:PlatformSharingBeesville TooLong.png|1200px]]

== Complex platform sharing ==

The method above works for trains departing in different directions. For the Ayton-Beesville-Ceeside layout, the possibilities it can handle are:
* Train 1 arrives from the Ayton, reverses at Beesville, and departs back towards Ayton. Train 2 arrives from Ceeside, reverses at Beesville, and departs back towards Ceeside. In short, there is an A-B-A train and a C-B-C train.
* Train 1 arrives first from Ayton, stops at the far end of Beesville, and departs towards Ceeside. Train 2 follows Train 1 from Ayton, reverses at Beesville, and departs back towards Ayton. In short, there is an A-B-C train and an A-B-A train behind it.

The method above will not work for:
* Train 1 arrives first from Ayton, stops at the far end of Beesville, and departs towards Ceeside. Train 2 follows Train 1 from Ayton, stops at the near end of Beesville behind Train 1, and departs later towards Ceeside. In short, two A-B-C trains which have overlapping stops at B.
* Train 1 arrives first from Ayton, and stops at the far end of Beesville. Train 2 follows Train 1 from Ayton, stops at the near end of Beesville behind Train 1, and departs back towards Ayton. Later, Train 1 also reverses and departs back towards Ayton. In Short, two A-B-A trains which have overlapping stops at B.

These situations do not work because NIMBY trains always reserve the track to the next signal in their direction of departure after a stop. This is a safety measure to prevent trains becoming trapped by a following train, or colliding on single track lines.

In the case of two A-B-C trains, the Train 2 attempts to reserve the track through to the signal at the end of the platform, but cannot due to Train 1 already occupying that end of the platform. In the case of two A-B-A trains, Train 1 reserves the platform back towards A, preventing Train 2 from entering the platform.

It is possible to enable platform sharing in these cases by placing a balise at the entrance to the platform, overriding the platform reservation behaviour - any train will always be able to enter the platform. In the example below, a balise has been placed at the entrance to Platform 1:

[[File:PlatformSharing BaliseAtBeesville.png|1200px]]

For the example of two trains with A-B-C schedules, this allows Train 2 to enter the platform behind Train 1:

[[File:PlatformSharing ABCFollowing.png|1200px]]

This solution could theoretically be extended to any number of trains - three, four, or more trains could be timetabled into the platform, with careful selection of stopping points.

With this solution, '''the player must ensure precise timetabling'''. NIMBY will have no ability to prevent trains getting into ridiculous situations. In particular:
* Train 2 will still attempt to enter the platform, even if it is not long enough for both Train 1 and Train 2
* If Train 2 arrives first, Train 1 will attempt to drive through it to reach the far end of the platform
* If another unrelated train scheduled to use the platform arrives, it will attempt to enter the platform
* If another unrelated train is already in the platform, Train 1 and 2 will still attempt to enter the platform
* If another train on the same line as Train 1 or Train 2 arrives (due to delays or poor scheduling), it will attempt to enter the platform
Any of these circumstances will likely result in trains colliding and the player needing to intervene.

[[Category:Guide]]

How to manual timetable

2023-07-30T13:21:07Z

Danny252: /* Auto run line */ Notes on limitations of auto run

NIMBY provides a range of timetabling tools that can be combined in many ways.

== Concepts ==

=== Line Stops ===

The Stops interface of a Line provides a template to which trains can run. The times shown for each stop are '''relative times''' - they do not represent clock times on a 24 hour timetable. Instead, the times show when a train will arrive, depart, or pass a location '''relative to the arrival time at the first stop, which is always 0:00:00'''.

=== Train Orders ===

The Orders applied to a Train determine how Runs of a timetable are generated. Orders may be Automatic, in which case the Train will perform Runs of the same Line forever based on the "Auto run line" settings for that Line, or Manual, allowing the user to specify Orders for several different lines.

=== Runs ===

A Run specifies the actual timetable to which a Train will run. A Run consists of:
* A Train
* A Line
* An '''absolute time''' for some event on the line

The '''absolute time of the event is a clock time''' (often on a specific day) used to convert the relative times of the Line Stops into absolute times - the actual times when a train will arrive and depart from a station.

The event that is specified is usually the Departure from the first station. Possible ways of specifying this event are:
* Set a train to "Auto run a line", where the Departure Time from the first station is the event, and the times are computed automatically based on the line settings
* Select "Depart exactly at" in Manual Orders, where the Departure Time from the first station is set to the specified time
* Select "Arrive exactly at" in Manual Orders, where the Arrival Time at the first station is set to the specified time
* Select "Arrive no later than" in Manual Orders, where NIMBY automatically computes the earliest possible arrival time based on the previous order

=== Line duration ===

The Line duration is used for generating Runs when a Train is set to "Auto run a line", or a Manual Order is set with "Loop until next order". A sequence of Runs is generated at an interval matching the duration. For example, if a train has a first stop departure set to of 06:00:00 (6 am), and the line has a duration of 02:00:00 (2 hours), runs will be generated with first stop departure times of 06:00:00, 08:00:00, 10:00:00, and so on.

== Auto run line ==

Trains set to "Auto run a line" will have Orders and Runs generated according to the Line settings. These settings are found under the "Auto run line" section in the Stops tab of the Line. Additionally, the duration of the line effects how runs are scheduled. Auto run timetables are the same every day of the week.

"Auto run a line" only allows you to specify a repeating schedule that runs 24/7. To have trains use a depot at night, you need to use Manual Orders. The combination of "Loop until next order" (where a train auto-runs a line until told otherwise) and "Auto copy manual orders" (copying the schedule of another train at a fixed interval) can provide significant automation for Manual Orders.

=== First train departure ===

This specifies the absolute departure time of the First Run of the line, departing from the first stop. If it is set to 04:29:00, a train will depart the first stop at 04:29:00 every day. Every other Run is scheduled based on the time set here. The "Time zone" setting controls what time zone this departure time is specified in.

=== Launch trains ===

This controls how the game schedules Runs after the First Run. There are two options - "Evenly spaced to fit one line loop" and "On a fixed, manual interval".

==== Evenly spaced to fit one line loop ====

Runs of the line are scheduled at a fixed interval. This interval is determined automatically by dividing the Line Duration by the number of Trains assigned to auto-run the line (trains on Manual Orders are always ignored, even if set to "Loop until next order"). The calculated interval is shown in the "Auto interval" field below this setting.

For example, if a line has a duration of 1:00:00, and 3 trains are assigned to auto-run the line, the interval is 00:20:00. Then, if the "First train departure" is set to 04:09:00, trains will depart the first stop at 04:09:00, 04:29:00, 05:49:00, 05:09:00, and so on.

If the line duration does not divide exactly into 24 hours, the final run before the next day's First Run will have an extended wait time at the first stop. For example, if the duration if 05:00:00 with one assigned train and the First train departure is set to 08:00:00, the train will depart at 08:00:00, 13:00:00, 18:00:00, and 23:00:00. The next run would theoretically be at 04:00:00, but as the duration is 5 hours, it would not arrive back in time for the specified 08:00:00 arrival.

==== On a fixed, manual interval ====

The user specifies the interval for trains to depart at. The scheduling behaviour is otherwise the same as "Evenly spaced to fit one loop". However, if there are too few trains to match the specified interval, some runs will not be generated. For example, if a line has a duration 1:00:00, 3 auto-run trains assigned, a Fixed interval of 00:15:00 is specified, and a "First train departure" is set to 06:00:00, trains will depart at 06:00:00, 06:15:00, 06:30:00, (gap due to no available train) 07:00:00, 07:15:00, 07:30:00, (gap due to no available train) 08:00:00, and so on.

How to manual timetable

2023-07-30T13:15:42Z

Danny252: Emphasis

NIMBY provides a range of timetabling tools that can be combined in many ways.

== Concepts ==

=== Line Stops ===

The Stops interface of a Line provides a template to which trains can run. The times shown for each stop are '''relative times''' - they do not represent clock times on a 24 hour timetable. Instead, the times show when a train will arrive, depart, or pass a location '''relative to the arrival time at the first stop, which is always 0:00:00'''.

=== Train Orders ===

The Orders applied to a Train determine how Runs of a timetable are generated. Orders may be Automatic, in which case the Train will perform Runs of the same Line forever based on the "Auto run line" settings for that Line, or Manual, allowing the user to specify Orders for several different lines.

=== Runs ===

A Run specifies the actual timetable to which a Train will run. A Run consists of:
* A Train
* A Line
* An '''absolute time''' for some event on the line

The '''absolute time of the event is a clock time''' (often on a specific day) used to convert the relative times of the Line Stops into absolute times - the actual times when a train will arrive and depart from a station.

The event that is specified is usually the Departure from the first station. Possible ways of specifying this event are:
* Set a train to "Auto run a line", where the Departure Time from the first station is the event, and the times are computed automatically based on the line settings
* Select "Depart exactly at" in Manual Orders, where the Departure Time from the first station is set to the specified time
* Select "Arrive exactly at" in Manual Orders, where the Arrival Time at the first station is set to the specified time
* Select "Arrive no later than" in Manual Orders, where NIMBY automatically computes the earliest possible arrival time based on the previous order

=== Line duration ===

The Line duration is used for generating Runs when a Train is set to "Auto run a line", or a Manual Order is set with "Loop until next order". A sequence of Runs is generated at an interval matching the duration. For example, if a train has a first stop departure set to of 06:00:00 (6 am), and the line has a duration of 02:00:00 (2 hours), runs will be generated with first stop departure times of 06:00:00, 08:00:00, 10:00:00, and so on.

== Auto run line ==

Trains set to "Auto run a line" will have Orders and Runs generated according to the Line settings. These settings are found under the "Auto run line" section in the Stops tab of the Line. Additionally, the duration of the line effects how runs are scheduled. Auto run timetables are the same every day of the week.

=== First train departure ===

This specifies the absolute departure time of the First Run of the line, departing from the first stop. If it is set to 04:29:00, a train will depart the first stop at 04:29:00 every day. Every other Run is scheduled based on the time set here. The "Time zone" setting controls what time zone this departure time is specified in.

=== Launch trains ===

This controls how the game schedules Runs after the First Run. There are two options - "Evenly spaced to fit one line loop" and "On a fixed, manual interval".

==== Evenly spaced to fit one line loop ====

Runs of the line are scheduled at a fixed interval. This interval is determined automatically by dividing the Line Duration by the number of Trains assigned to auto-run the line (trains on Manual Orders are always ignored, even if set to "Loop until next order"). The calculated interval is shown in the "Auto interval" field below this setting.

For example, if a line has a duration of 1:00:00, and 3 trains are assigned to auto-run the line, the interval is 00:20:00. Then, if the "First train departure" is set to 04:09:00, trains will depart the first stop at 04:09:00, 04:29:00, 05:49:00, 05:09:00, and so on.

If the line duration does not divide exactly into 24 hours, the final run before the next day's First Run will have an extended wait time at the first stop. For example, if the duration if 05:00:00 with one assigned train and the First train departure is set to 08:00:00, the train will depart at 08:00:00, 13:00:00, 18:00:00, and 23:00:00. The next run would theoretically be at 04:00:00, but as the duration is 5 hours, it would not arrive back in time for the specified 08:00:00 arrival.

==== On a fixed, manual interval ====

The user specifies the interval for trains to depart at. The scheduling behaviour is otherwise the same as "Evenly spaced to fit one loop". However, if there are too few trains to match the specified interval, some runs will not be generated. For example, if a line has a duration 1:00:00, 3 auto-run trains assigned, a Fixed interval of 00:15:00 is specified, and a "First train departure" is set to 06:00:00, trains will depart at 06:00:00, 06:15:00, 06:30:00, (gap due to no available train) 07:00:00, 07:15:00, 07:30:00, (gap due to no available train) 08:00:00, and so on.

How to manual timetable

2023-07-30T13:13:47Z

Danny252: fix typo

NIMBY provides a range of timetabling tools that can be combined in many ways.

== Concepts ==

=== Line Stops ===

The Stops interface of a Line provides a template to which trains can run. The times shown for each stop are '''relative times''' - they do not represent clock times on a 24 hour timetable. Instead, the times show when a train will arrive, depart, or pass a location relative to the arrival time at the first stop, which is always 0:00:00.

=== Train Orders ===

The Orders applied to a Train determine how Runs of a timetable are generated. Orders may be Automatic, in which case the Train will perform Runs of the same Line forever based on the "Auto run line" settings for that Line, or Manual, allowing the user to specify Orders for several different lines.

=== Runs ===

A Run specifies the actual timetable to which a Train will run. A Run consists of:
* A Train
* A Line
* An '''absolute time''' for some event on the line

The absolute time of the event is a clock time (and often a specific day), which is used to convert the relative times of the Line Stops into absolute times - the actual times when a train will arrive and depart from a station.

The event that is specified is usually the Departure from the first station. Possible ways of specifying this event are:
* Set a train to "Auto run a line", where the Departure Time from the first station is the event, and the times are computed automatically based on the line settings
* Select "Depart exactly at" in Manual Orders, where the Departure Time from the first station is set to the specified time
* Select "Arrive exactly at" in Manual Orders, where the Arrival Time at the first station is set to the specified time
* Select "Arrive no later than" in Manual Orders, where NIMBY automatically computes the earliest possible arrival time based on the previous order

=== Line duration ===

The Line duration is used for generating Runs when a Train is set to "Auto run a line", or a Manual Order is set with "Loop until next order". A sequence of Runs is generated at an interval matching the duration. For example, if a train has a first stop departure set to of 06:00:00 (6 am), and the line has a duration of 02:00:00 (2 hours), runs will be generated with first stop departure times of 06:00:00, 08:00:00, 10:00:00, and so on.

== Auto run line ==

Trains set to "Auto run a line" will have Orders and Runs generated according to the Line settings. These settings are found under the "Auto run line" section in the Stops tab of the Line. Additionally, the duration of the line effects how runs are scheduled. Auto run timetables are the same every day of the week.

=== First train departure ===

This specifies the absolute departure time of the First Run of the line, departing from the first stop. If it is set to 04:29:00, a train will depart the first stop at 04:29:00 every day. Every other Run is scheduled based on the time set here. The "Time zone" setting controls what time zone this departure time is specified in.

=== Launch trains ===

This controls how the game schedules Runs after the First Run. There are two options - "Evenly spaced to fit one line loop" and "On a fixed, manual interval".

==== Evenly spaced to fit one line loop ====

Runs of the line are scheduled at a fixed interval. This interval is determined automatically by dividing the Line Duration by the number of Trains assigned to auto-run the line (trains on Manual Orders are always ignored, even if set to "Loop until next order"). The calculated interval is shown in the "Auto interval" field below this setting.

For example, if a line has a duration of 1:00:00, and 3 trains are assigned to auto-run the line, the interval is 00:20:00. Then, if the "First train departure" is set to 04:09:00, trains will depart the first stop at 04:09:00, 04:29:00, 05:49:00, 05:09:00, and so on.

If the line duration does not divide exactly into 24 hours, the final run before the next day's First Run will have an extended wait time at the first stop. For example, if the duration if 05:00:00 with one assigned train and the First train departure is set to 08:00:00, the train will depart at 08:00:00, 13:00:00, 18:00:00, and 23:00:00. The next run would theoretically be at 04:00:00, but as the duration is 5 hours, it would not arrive back in time for the specified 08:00:00 arrival.

==== On a fixed, manual interval ====

The user specifies the interval for trains to depart at. The scheduling behaviour is otherwise the same as "Evenly spaced to fit one loop". However, if there are too few trains to match the specified interval, some runs will not be generated. For example, if a line has a duration 1:00:00, 3 auto-run trains assigned, a Fixed interval of 00:15:00 is specified, and a "First train departure" is set to 06:00:00, trains will depart at 06:00:00, 06:15:00, 06:30:00, (gap due to no available train) 07:00:00, 07:15:00, 07:30:00, (gap due to no available train) 08:00:00, and so on.

How to manual timetable

2023-07-30T13:12:42Z

Danny252:

NIMBY provides a range of timetabling tools that can be combined in many ways.

== Concepts ==

=== Line Stops ===

The Stops interface of a Line provides a template to which trains can run. The times shown for each stop are '''relative times''' - they do not represent clock times on a 24 hour timetable. Instead, the times show when a train will arrive, depart, or pass a location relative to the arrival time at the first stop, which is always 0:00:00.

=== Train Orders ===

The Orders applied to a Train determine how Runs of a timetable are generated. Orders may be Automatic, in which case the Train will perform Runs of the same Line forever based on the "Auto run line" settings for that Line, or Manual, allowing the user to specify Orders for several different lines.

=== Runs ===

A Run specifies the actual timetable to which a Train will run. A Run consists of:
* A Train
* A Line
* A '''absolute time''' for some event on the line

The absolute time of the event is a clock time (and often a specific day), which is used to convert the relative times of the Line Stops into absolute times - the actual times when a train will arrive and depart from a station.

The event that is specified is usually the Departure from the first station. Possible ways of specifying this event are:
* Set a train to "Auto run a line", where the Departure Time from the first station is the event, and the times are computed automatically based on the line settings
* Select "Depart exactly at" in Manual Orders, where the Departure Time from the first station is set to the specified time
* Select "Arrive exactly at" in Manual Orders, where the Arrival Time at the first station is set to the specified time
* Select "Arrive no later than" in Manual Orders, where NIMBY automatically computes the earliest possible arrival time based on the previous order

=== Line duration ===

The Line duration is used for generating Runs when a Train is set to "Auto run a line", or a Manual Order is set with "Loop until next order". A sequence of Runs is generated at an interval matching the duration. For example, if a train has a first stop departure set to of 06:00:00 (6 am), and the line has a duration of 02:00:00 (2 hours), runs will be generated with first stop departure times of 06:00:00, 08:00:00, 10:00:00, and so on.

== Auto run line ==

Trains set to "Auto run a line" will have Orders and Runs generated according to the Line settings. These settings are found under the "Auto run line" section in the Stops tab of the Line. Additionally, the duration of the line effects how runs are scheduled. Auto run timetables are the same every day of the week.

=== First train departure ===

This specifies the absolute departure time of the First Run of the line, departing from the first stop. If it is set to 04:29:00, a train will depart the first stop at 04:29:00 every day. Every other Run is scheduled based on the time set here. The "Time zone" setting controls what time zone this departure time is specified in.

=== Launch trains ===

This controls how the game schedules Runs after the First Run. There are two options - "Evenly spaced to fit one line loop" and "On a fixed, manual interval".

==== Evenly spaced to fit one line loop ====

Runs of the line are scheduled at a fixed interval. This interval is determined automatically by dividing the Line Duration by the number of Trains assigned to auto-run the line (trains on Manual Orders are always ignored, even if set to "Loop until next order"). The calculated interval is shown in the "Auto interval" field below this setting.

For example, if a line has a duration of 1:00:00, and 3 trains are assigned to auto-run the line, the interval is 00:20:00. Then, if the "First train departure" is set to 04:09:00, trains will depart the first stop at 04:09:00, 04:29:00, 05:49:00, 05:09:00, and so on.

If the line duration does not divide exactly into 24 hours, the final run before the next day's First Run will have an extended wait time at the first stop. For example, if the duration if 05:00:00 with one assigned train and the First train departure is set to 08:00:00, the train will depart at 08:00:00, 13:00:00, 18:00:00, and 23:00:00. The next run would theoretically be at 04:00:00, but as the duration is 5 hours, it would not arrive back in time for the specified 08:00:00 arrival.

==== On a fixed, manual interval ====

The user specifies the interval for trains to depart at. The scheduling behaviour is otherwise the same as "Evenly spaced to fit one loop". However, if there are too few trains to match the specified interval, some runs will not be generated. For example, if a line has a duration 1:00:00, 3 auto-run trains assigned, a Fixed interval of 00:15:00 is specified, and a "First train departure" is set to 06:00:00, trains will depart at 06:00:00, 06:15:00, 06:30:00, (gap due to no available train) 07:00:00, 07:15:00, 07:30:00, (gap due to no available train) 08:00:00, and so on.

How to manual timetable

2023-07-30T12:30:53Z

Danny252: Created page with "NIMBY provides a range of timetabling tools that can be combined in many ways. == Concepts == === Line Stops === The Stops interface of a Line provides a template to which trains can run. The times shown for each stop are '''relative times''' - they do not represent clock times on a 24 hour timetable. Instead, the times show when a train will arrive, depart, or pass a location relative to the arrival time at the first stop, which is always 0:00:00. === Train Orders =..."

How to have multiple trains share a platform

2023-07-30T12:03:04Z

Danny252:

From [[Version 1.9]], the Advanced mode for stop creation allows trains to share platforms. In this mode, the player specifies the exact stopping point for trains, and provided that two trains will not overlap while stopped in the station, NIMBY will allow them to share the platform.

== Platform sharing for trains arriving and departing in different directions ==

In the example below, the line A-B (red) runs from Ayton to Beesville, and the line B-C (green) runs from Beesville to Ceeside:

[[File:PlatformSharingABCLayout.png|1200px]]

At Beesville, both trains use Platform 1 simultaneously:

[[File:PlatformSharingBeesvilleTrains.png|1200px]]

The platform at Beesville is 250m long. Both trains are 80m long, and so there is plenty of space for both to use the platform.

On Line A-B, the stop at Beesville was created using Advanced mode. A stopping position 5m from the near end of the platform was selected, choosing the west-facing arrow marked as "245m":

[[File:PlatformSharingBeesville LineABConfig.png]]

Line B-C is set up in the same way, choosing a stopping position facing east at its end of the platform:

[[File:PlatformSharingBeesville LineBCConfig.png]]

=== Trains too long ===

If the trains will not fit in the platform simultaneously, the signalling system will not permit them to enter.

In the example below, both trains are 140m long, and they are too long for the 250m platform at Beesville. Train A-B arrived first and entered the platform, but train B-C is being held at a red signal because there is not enough room for it to fully enter the platform:

[[File:PlatformSharingBeesville TooLong.png|1200px]]

== Complex platform sharing ==

The method above works for trains departing in different directions. For the Ayton-Beesville-Ceeside layout, the possibilities it can handle are:
* Train 1 arrives from the Ayton, reverses at Beesville, and departs back towards Ayton. Train 2 arrives from Ceeside, reverses at Beesville, and departs back towards Ceeside. In short, there is an A-B-A train and a C-B-C train.
* Train 1 arrives first from Ayton, stops at the far end of Beesville, and departs towards Ceeside. Train 2 follows Train 1 from Ayton, reverses at Beesville, and departs back towards Ayton. In short, there is an A-B-C train and an A-B-A train behind it.

The method above will not work for:
* Train 1 arrives first from Ayton, stops at the far end of Beesville, and departs towards Ceeside. Train 2 follows Train 1 from Ayton, stops at the near end of Beesville behind Train 1, and departs later towards Ceeside. In short, two A-B-C trains which have overlapping stops at B.
* Train 1 arrives first from Ayton, and stops at the far end of Beesville. Train 2 follows Train 1 from Ayton, stops at the near end of Beesville behind Train 1, and departs back towards Ayton. Later, Train 1 also reverses and departs back towards Ayton. In Short, two A-B-A trains which have overlapping stops at B.

These situations do not work because NIMBY trains always reserve the track to the next signal in their direction of departure after a stop. This is a safety measure to prevent trains becoming trapped by a following train, or colliding on single track lines.

In the case of two A-B-C trains, the Train 2 attempts to reserve the track through to the signal at the end of the platform, but cannot due to Train 1 already occupying that end of the platform. In the case of two A-B-A trains, Train 1 reserves the platform back towards A, preventing Train 2 from entering the platform.

It is possible to enable platform sharing in these cases by placing a balise at the entrance to the platform, overriding the platform reservation behaviour - any train will always be able to enter the platform. In the example below, a balise has been placed at the entrance to Platform 1:

[[File:PlatformSharing BaliseAtBeesville.png|1200px]]

For the example of two trains with A-B-C schedules, this allows Train 2 to enter the platform behind Train 1:

[[File:PlatformSharing ABCFollowing.png|1200px]]

This solution could theoretically be extended to any number of trains - three, four, or more trains could be timetabled into the platform, with careful selection of stopping points.

With this solution, '''the player must ensure precise timetabling'''. NIMBY will have no ability to prevent trains getting into ridiculous situations. In particular:
* Train 2 will still attempt to enter the platform, even if it is not long enough for both Train 1 and Train 2
* If Train 2 arrives first, Train 1 will attempt to drive through it to reach the far end of the platform
* If another unrelated train scheduled to use the platform arrives, it will attempt to enter the platform
* If another unrelated train is already in the platform, Train 1 and 2 will still attempt to enter the platform
* If another train on the same line as Train 1 or Train 2 arrives (due to delays or poor scheduling), it will attempt to enter the platform
Any of these circumstances will likely result in trains colliding and the player needing to intervene.

[[Category:Guide]]

How to have multiple trains share a platform

2023-07-16T11:58:29Z

Danny252: Created page with "From Version 1.9, the Advanced mode for stop creation allows trains to share platforms. In this mode, the player specifies the exact stopping point for trains, and provided that two trains will not overlap while stopped in the station, NIMBY will allow them to share the platform. == Platform sharing for trains arriving and departing in different directions == In the example below, the line A-B (red) runs from Ayton to Beesville, and the line B-C (green) runs from B..."

From [[Version 1.9]], the Advanced mode for stop creation allows trains to share platforms. In this mode, the player specifies the exact stopping point for trains, and provided that two trains will not overlap while stopped in the station, NIMBY will allow them to share the platform.

== Platform sharing for trains arriving and departing in different directions ==

In the example below, the line A-B (red) runs from Ayton to Beesville, and the line B-C (green) runs from Beesville to Ceeside:

[[File:PlatformSharingABCLayout.png|1200px]]

At Beesville, both trains use Platform 1 simultaneously:

[[File:PlatformSharingBeesvilleTrains.png|1200px]]

The platform at Beesville is 250m long. Both trains are 80m long, and so there is plenty of space for both to use the platform.

On Line A-B, the stop at Beesville was created using Advanced mode. A stopping position 5m from the near end of the platform was selected, choosing the west-facing arrow marked as "245m":

[[File:PlatformSharingBeesville LineABConfig.png]]

Line B-C is set up in the same way, choosing a stopping position facing east at its end of the platform:

[[File:PlatformSharingBeesville LineBCConfig.png]]

=== Trains too long ===

If the trains will not fit in the platform simultaneously, the signalling system will not permit them to enter.

In the example below, both trains are 140m long, and they are too long for the 250m platform at Beesville. Train A-B arrived first and entered the platform, but train B-C is being held at a red signal because there is not enough room for it to fully enter the platform:

[[File:PlatformSharingBeesville TooLong.png|1200px]]

== Complex platform sharing ==

The method above works for trains departing in different directions. For the Ayton-Beesville-Ceeside layout, the possibilities it can handle are:
* Train 1 arrives from the Ayton, reverses at Beesville, and departs back towards Ayton. Train 2 arrives from Ceeside, reverses at Beesville, and departs back towards Ceeside. In short, there is an A-B-A train and a C-B-C train.
* Train 1 arrives first from Ayton, stops at the far end of Beesville, and departs towards Ceeside. Train 2 follows Train 1 from Ayton, reverses at Beesville, and departs back towards Ayton. In short, there is an A-B-C train and an A-B-A train behind it.

The method above will not work for:
* Train 1 arrives first from Ayton, stops at the far end of Beesville, and departs towards Ceeside. Train 2 follows Train 1 from Ayton, stops at the near end of Beesville behind Train 1, and departs later towards Ceeside. In short, two A-B-C trains which have overlapping stops at B.
* Train 1 arrives first from Ayton, and stops at the far end of Beesville. Train 2 follows Train 1 from Ayton, stops at the near end of Beesville behind Train 1, and departs back towards Ayton. Later, Train 1 also reverses and departs back towards Ayton. In Short, two A-B-A trains which have overlapping stops at B.

These situations do not work because NIMBY trains always reserve the track to the next signal in their direction of departure after a stop. This is a safety measure to prevent trains becoming trapped by a following train, or colliding on single track lines.

In the case of two A-B-C trains, the Train 2 attempts to reserve the track through to the signal at the end of the platform, but cannot due to Train 1 already occupying that end of the platform. In the case of two A-B-A trains, Train 1 reserves the platform back towards A, preventing Train 2 from entering the platform.

It is possible to enable platform sharing in these cases by placing a balise at the entrance to the platform, overriding the platform reservation behaviour - any train will always be able to enter the platform. In the example below, a balise has been placed at the entrance to Platform 1:

[[File:PlatformSharing BaliseAtBeesville.png|1200px]]

For the example of two trains with A-B-C schedules, this allows Train 2 to enter the platform behind Train 1:

[[File:PlatformSharing ABCFollowing.png|1200px]]

This solution could theoretically be extended to any number of trains - three, four, or more trains could be timetabled into the platform, with careful selection of stopping points.

With this solution, '''the player must ensure precise timetabling'''. NIMBY will have no ability to prevent trains getting into ridiculous situations. In particular:
* Train 2 will still attempt to enter the platform, even if it is not long enough for both Train 1 and Train 2
* If Train 2 arrives first, Train 1 will attempt to drive through it to reach the far end of the platform
* If another unrelated train scheduled to use the platform arrives, it will attempt to enter the platform
* If another unrelated train is already in the platform, Train 1 and 2 will still attempt to enter the platform
* If another train on the same line as Train 1 or Train 2 arrives (due to delays or poor scheduling), it will attempt to enter the platform
Any of these circumstances will likely result in trains colliding and the player needing to intervene.

File:PlatformSharing BaliseAtBeesville.png

2023-07-16T11:51:22Z

Danny252: Danny252 uploaded a new version of File:PlatformSharing BaliseAtBeesville.png

== Summary ==
Advanced platform sharing with balises

File:PlatformSharing ABCFollowing.png

2023-07-16T11:50:09Z

Danny252: Example of two trains following each other and sharing a platform

== Summary ==
Example of two trains following each other and sharing a platform

File:PlatformSharing BaliseAtBeesville.png

2023-07-16T11:47:41Z

Danny252: Danny252 uploaded a new version of File:PlatformSharing BaliseAtBeesville.png

== Summary ==
Advanced platform sharing with balises

File:PlatformSharing BaliseAtBeesville.png

2023-07-16T11:46:49Z

Danny252: Advanced platform sharing with balises

== Summary ==
Advanced platform sharing with balises

File:PlatformSharingBeesville TooLong.png

2023-07-16T11:12:38Z

Danny252: Platform sharing - trains too long

== Summary ==
Platform sharing - trains too long

File:PlatformSharingBeesville LineBCConfig.png

2023-07-16T11:09:43Z

Danny252: Platform sharing set up at Beesville

== Summary ==
Platform sharing set up at Beesville

File:PlatformSharingBeesville LineABConfig.png

2023-07-16T11:05:48Z

Danny252: Platform sharing set up at Beesville

== Summary ==
Platform sharing set up at Beesville

File:PlatformSharingBeesvilleTrains.png

2023-07-16T11:02:50Z

Danny252: Platform sharing example - two trains from opposite ends

== Summary ==
Platform sharing example - two trains from opposite ends

File:PlatformSharingABCLayout.png

2023-07-16T10:58:48Z

Danny252: Sample layout for platform sharing examples

== Summary ==
Sample layout for platform sharing examples

NIMBY:Contents

2023-07-16T10:39:50Z

Danny252: /* Advanced */

= 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]]
*[[How to have multiple trains share a platform]]

== 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]]
*[[Version 1.7]]

NIMBY:Contents

2023-03-01T08:37:39Z

Danny252: /* Versions */ V1.7

= 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]]
*[[Version 1.7]]

Version 1.7

2023-03-01T08:37:23Z

Danny252: Created page with "Version 1.7 entered beta on 28 Feburary 2022. New features and fixes in V1.7 were covered in the [https://carloscarrasco.com/nimby-rails-january-2023/ January] and [https://carloscarrasco.com/nimby-rails-february-2023/ February] devblogs. Key features discussed in the devblogs are:: * A new option to share saved games, and to view them online at https://share.nimbyrails.com/ (in-game viewing to follow) * Custom train compositions, allowing players to combine cars from..."

Version 1.7 entered beta on 28 Feburary 2022.

New features and fixes in V1.7 were covered in the [https://carloscarrasco.com/nimby-rails-january-2023/ January] and [https://carloscarrasco.com/nimby-rails-february-2023/ February] devblogs.

Key features discussed in the devblogs are::
* A new option to share saved games, and to view them online at https://share.nimbyrails.com/ (in-game viewing to follow)
* Custom train compositions, allowing players to combine cars from different trains (mods need to enable this feature)
* Fixes to predicted line timings, usually causing travel times to be overestimated

[[Category:Version]]

Version 1.6

2023-03-01T08:32:48Z

Danny252: Devlog -> devblog

Version 1.6 was released on 16 January 2023, containing several new track tools, and improvements to multiplayer. It initially entered beta on 9 December 2022.

New features and fixes in V1.6 were covered in the [https://carloscarrasco.com/nimby-rails-october-2022/ October], [https://carloscarrasco.com/nimby-rails-november-2022/ November], and [https://carloscarrasco.com/nimby-rails-december-2022/ December] devblogs.

Key features listed in the [https://store.steampowered.com/news/app/1134710/view/3654141654863909262?l=english Update Notes] are:
* Multiplayer optimizations
* Private simulation mode for multiplayer, improving game speed and reducing bandwidth requirements
* Direct connection mode for multiplayer, working around bandwidth limits on the Steam Relay network
* Track curve weight, allowing the halfway point between two track nodes and move it
* Track split and tape tools, a new suite of tools for modifying existing track
* New "hold" mode option for the track editor, which only enabled tools while the player holds down the relevant hotkey
* Track editing optimizations
* Path tracing options for trains, showing the projected path of a train
* Bulk edit options for trains

[[Category:Version]]

Version 1.6

2023-03-01T08:31:03Z

Danny252: Fix links

Version 1.6 was released on 16 January 2023, containing several new track tools, and improvements to multiplayer. It initially entered beta on 9 December 2022.

New features and fixes in V1.6 were covered in the [https://carloscarrasco.com/nimby-rails-october-2022/ October], [https://carloscarrasco.com/nimby-rails-november-2022/ November], and [https://carloscarrasco.com/nimby-rails-december-2022/ December] devlogs.

Key features listed in the [https://store.steampowered.com/news/app/1134710/view/3654141654863909262?l=english Update Notes] are:
* Multiplayer optimizations
* Private simulation mode for multiplayer, improving game speed and reducing bandwidth requirements
* Direct connection mode for multiplayer, working around bandwidth limits on the Steam Relay network
* Track curve weight, allowing the halfway point between two track nodes and move it
* Track split and tape tools, a new suite of tools for modifying existing track
* New "hold" mode option for the track editor, which only enabled tools while the player holds down the relevant hotkey
* Track editing optimizations
* Path tracing options for trains, showing the projected path of a train
* Bulk edit options for trains

[[Category:Version]]

Version 1.6

2023-03-01T08:30:35Z

Danny252:

Version 1.6 was released on 16 January 2023, containing several new track tools, and improvements to multiplayer. It initially entered beta on 9 December 2022.

New features and fixes in V1.6 were covered in the [October https://carloscarrasco.com/nimby-rails-october-2022/], [November https://carloscarrasco.com/nimby-rails-november-2022/], and [December https://carloscarrasco.com/nimby-rails-december-2022/] devlogs.

Key features listed in the [Update Notes https://store.steampowered.com/news/app/1134710/view/3654141654863909262?l=english] are:
* Multiplayer optimizations
* Private simulation mode for multiplayer, improving game speed and reducing bandwidth requirements
* Direct connection mode for multiplayer, working around bandwidth limits on the Steam Relay network
* Track curve weight, allowing the halfway point between two track nodes and move it
* Track split and tape tools, a new suite of tools for modifying existing track
* New "hold" mode option for the track editor, which only enabled tools while the player holds down the relevant hotkey
* Track editing optimizations
* Path tracing options for trains, showing the projected path of a train
* Bulk edit options for trains

[[Category:Version]]

How to build track

2023-01-21T22:08:31Z

Danny252: Fix links

All [[Train|trains]] in NIMBY Rails must run on [[Track|track]], and [[Station|stations]] are constructed from track sections that are designated as [[Platform|platforms]].

== Tracks menu overview ==

[[File:TracksMenu.PNG|thumb|300px|right|Tracks menu.]]

All tools for creating and modifying track are found under the Tracks menu, accessed at the top left (default hotkey: F2). It contains several tools:
; [[File:Icon sel track.png|24px|Move, delete, and edit tracks icon]] Move, delete, and edit tracks (default hotkey M)
: Select and edit track with the mouse cursor
; [[File:Icon add track.png|24px|Append to tracks or create new ones icon]] Append to tracks or create new ones (default hotkey N)
: Create new track with the mouse
; [[File:Icon branch.png|24px|Create new track branches icon]] Create new track branches (default hotkey B)
: Create junctions / switches with the mouse
; [[File:Icon sat.png|24px|Split and tape tools icon]] Split and tape tools
: Opens a new submenu with advanced tools
; [[File:Icon station.png|24px|Create stations icon]] Create stations (default hotkey T)
: Create new stations, or add platforms to an existing station
; [[File:Icon building.png|24px|Create new buildings icon]] Create new buildings (default hotkey U)
: Create buildings, either freestanding or attached to a track
; [[File:Icon sel signal.png|24px|Move, delete, and edit signals icon]] Move, delete, and edit signals (default hotkey K)
: Select and edit signals with the mouse
; [[File:Icon add signal.png|24px|Create new signals icon]] Create new signals (default hotkey L)
: Create new signals with the mouse

Most of these tools include additional settings, controlled by buttons displayed at the bottom of the menu, and new menus to the side. The most common additional button is [[File:Icon 2x tracks.png|24px]] Double track mode (default hotkey J).

== Laying track ==

New track is created with the [[File:Icon add track.png|24px|Append to tracks or create new ones icon]] create track tool (default hotkey N).

=== Creating an unconnected track section ===

[[File:TrackSectionNew.PNG|thumb|300px|right|A newly created track section.]]

Click once on the map to place the first control point, defining the start of the track section. The other end will follow your mouse until you click a second time to create a second control point, ending the section. While laying, the length of the ''two halves'' of the new section will be shown, with the length of the half nearest the mouse highlighted in white.

After creating a section, and with the [[File:Icon add track.png|24px|Append to tracks or create new ones icon]] create track tool still selected, the newly created section will:
* Be shown in blue, indicating it is still in blueprint mode
* Be divided into two halves, with the midpoint shown by a small grey bar
* Have two [[File:Control interactive with icon add.png|24px|Connect track]] connection points at either end, corresponding to the unconnected control points.
* Show the track's speed limit in km/h, inside small white circles
* Have the length of the two halves shown in m
(Some of this information will not be visible when zoomed out)

=== Extending with a new track section ===

[[File:TrackSectionConnectedCurve.PNG|thumb|300px|right|Two track sections, forming a curve. The track type normally allows 160km/h, but the curve is limited to 70km/h.]]
[[File:TrackCurveInvalid.PNG|thumb|300px|right|An invalid track section, which has too tight a curve. This track cannot be built.]]

To extend the track with a new section, click on one of the two [[File:Icon add track.png|24px|Append to tracks or create new ones icon]] connection points. This will start laying a new section like before, but will now create a curve to connect the existing section to the new section being laid. While laying track, the curve radius will be shown as well as the track length, as well as an indicative circle - the curve will smoothly transition from straight track to a curve.

If the curve is too tight for the speed limit of the track, the speed limit will be reduced. Track types also have a minimum curve radius, and track that curves below this radius is invalid. Invalid track cannot be built.

To force the new section to be straight, hold down the '''Ctrl''' key.

To keep laying new track sections after finishing one section, hold down the '''Shift''' key.

=== Modifying track ===

Track that has been laid can be edited in the [[File:Icon sel track.png|24px|Move, delete, and edit tracks icon]] edit tracks tool. You can:
* Click and drag blueprinted track control points to move them
* Select control points by clicking on them
* Delete selected control points (default hotkey Delete)
* Modify the track type and various other properties
* Move the midpoint of a track section (indicated by a small grey bar), changing how curves behave, and where track types change

It is possible to select both blueprinted (unbuilt) and built track control points. However, only a few changes can be made to built track. It is possible to convert built track back to blueprints with the '''Insert''' hotkey - note that you will not be refunded the original build cost when doing this, and you will pay for the construction a second time when building!

Multiple control points can be selected at once. You can click and drag to draw a box around multiple control points at once, or shift-click to add control points to the current selection.

== Changing track levels and types ==

[[File:TrackLevelsAndTypes.PNG|thumb|300px|right|Menus for selecting track levels (top) and track types (bottom).]]
[[File:GroundLevelRoadsStreams.PNG|thumb|300px|right|Ground level track cannot be built across streams or roads at shallow angles.]]
[[File:DifferentLevels.PNG|thumb|300px|right|Tracks pass over/under tracks at different levels, but intersect tracks at the same level.]]
[[File:TrackTypes.PNG|thumb|300px|right|Tunnel, ground, and viaduct tracks. Note that track types change at mid points.]]

Most of the track editing tools enable the track level and track type menus, which are displayed to the right of the tool buttons. These menus work together, and apply to newly created track, or modify selected track.

=== Track level menu ===

Track can be laid at ground level, above ground on viaducts, or below ground in tunnels. Tracks on different levels will pass over/under each other.

The '''Ground''' option lays track at ground level. This is the cheapest option, but has some limitations:
* Track cannot be laid across rivers, lakes, or seas
* Roads cannot be crossed diagonally (stations and some track types - e.g. the default tram track type - ignore this restriction)
* Streams cannot be crossed diagonally (stations ignore this restriction)

Viaducts are built with the '''+1''', '''+2''', and '''+3''' options. The '''+2''' option builds taller viaducts that can pass over tracks on the '''+1''' level, and the '''+3''' level is even higher. Two tracks that are built at the same level will intersect.

Tunnels are built and behave similarly, with the '''-1''', '''-2''', and '''-3''' level.

The special Unlimited Height and Unlimited Depth ('''+∞''' and '''-∞''') levels create tracks that never intersect, not even with tracks on the same level.

Track levels are defined at each track control point, and always change at the midpoint between two control points.

When laying new track with the [[File:Icon add track.png|24px|Append to tracks or create new ones icon]] create track tool, you can place the first control point at one level, and then select a different level before placing the second control point. When connecting new track to existing control points, the track level of the existing point is never changed.

In the [[File:Icon sel track.png|24px|Move, delete, and edit tracks icon]] edit tracks tool, track levels can be changed for blueprinted track, and midpoints can be moved to change where track types change.

=== Track type menu ===

The track type menu consists of two sections:
* A favourites hotbar with 9 track types and level combinations, selected by the hotkeys 1-9
* The [[File:Icon all tracks.png|24px|All tracks icon]] all tracks menu, allowing you to specify any track type, and redefine favourites

Track types behave very similarly to track levels.

The [[File:Icon all tracks.png|24px|All tracks icon]] all tracks menu is hidden by default, and can be toggled by clicking the button. When open, you can select a track type from the list on the left, and a track level from the menu above. The track type will apply to new tracks being created, or to selected tracks being modified.

The combination of the track type and level selected can be saved to the favourites hotbar by selecting a slot in dropdown menu, replacing any existing favourite in the selected slot. If the combination is already favourited, the existing slot will become empty.

Additional track types can be added using [[Modding|mods]], available in the Steam Workshop.

How to build track

2023-01-21T22:01:07Z

Danny252: Start writing guide

All [[Trains|trains]] in NIMBY Rails must run on [[Track|track]], and [[Stations|stations]] are constructed from track sections that are designated as [[Platform|platforms]].

== Tracks menu overview ==

[[File:TracksMenu.PNG|thumb|300px|right|Tracks menu.]]

All tools for creating and modifying track are found under the Tracks menu, accessed at the top left (default hotkey: F2). It contains several tools:
; [[File:Icon sel track.png|24px|Move, delete, and edit tracks icon]] Move, delete, and edit tracks (default hotkey M)
: Select and edit track with the mouse cursor
; [[File:Icon add track.png|24px|Append to tracks or create new ones icon]] Append to tracks or create new ones (default hotkey N)
: Create new track with the mouse
; [[File:Icon branch.png|24px|Create new track branches icon]] Create new track branches (default hotkey B)
: Create junctions / switches with the mouse
; [[File:Icon sat.png|24px|Split and tape tools icon]] Split and tape tools
: Opens a new submenu with advanced tools
; [[File:Icon station.png|24px|Create stations icon]] Create stations (default hotkey T)
: Create new stations, or add platforms to an existing station
; [[File:Icon building.png|24px|Create new buildings icon]] Create new buildings (default hotkey U)
: Create buildings, either freestanding or attached to a track
; [[File:Icon sel signal.png|24px|Move, delete, and edit signals icon]] Move, delete, and edit signals (default hotkey K)
: Select and edit signals with the mouse
; [[File:Icon add signal.png|24px|Create new signals icon]] Create new signals (default hotkey L)
: Create new signals with the mouse

Most of these tools include additional settings, controlled by buttons displayed at the bottom of the menu, and new menus to the side. The most common additional button is [[File:Icon 2x tracks.png|24px]] Double track mode (default hotkey J).

== Laying track ==

New track is created with the [[File:Icon add track.png|24px|Append to tracks or create new ones icon]] create track tool (default hotkey N).

=== Creating an unconnected track section ===

[[File:TrackSectionNew.PNG|thumb|300px|right|A newly created track section.]]

Click once on the map to place the first control point, defining the start of the track section. The other end will follow your mouse until you click a second time to create a second control point, ending the section. While laying, the length of the ''two halves'' of the new section will be shown, with the length of the half nearest the mouse highlighted in white.

After creating a section, and with the [[File:Icon add track.png|24px|Append to tracks or create new ones icon]] create track tool still selected, the newly created section will:
* Be shown in blue, indicating it is still in blueprint mode
* Be divided into two halves, with the midpoint shown by a small grey bar
* Have two [[File:Control interactive with icon add.png|24px|Connect track]] connection points at either end, corresponding to the unconnected control points.
* Show the track's speed limit in km/h, inside small white circles
* Have the length of the two halves shown in m
(Some of this information will not be visible when zoomed out)

=== Extending with a new track section ===

[[File:TrackSectionConnectedCurve.PNG|thumb|300px|right|Two track sections, forming a curve. The track type normally allows 160km/h, but the curve is limited to 70km/h.]]
[[File:TrackCurveInvalid.PNG|thumb|300px|right|An invalid track section, which has too tight a curve. This track cannot be built.]]

To extend the track with a new section, click on one of the two [[File:Icon add track.png|24px|Append to tracks or create new ones icon]] connection points. This will start laying a new section like before, but will now create a curve to connect the existing section to the new section being laid. While laying track, the curve radius will be shown as well as the track length, as well as an indicative circle - the curve will smoothly transition from straight track to a curve.

If the curve is too tight for the speed limit of the track, the speed limit will be reduced. Track types also have a minimum curve radius, and track that curves below this radius is invalid. Invalid track cannot be built.

To force the new section to be straight, hold down the '''Ctrl''' key.

To keep laying new track sections after finishing one section, hold down the '''Shift''' key.

=== Modifying track ===

Track that has been laid can be edited in the [[File:Icon sel track.png|24px|Move, delete, and edit tracks icon]] edit tracks tool. You can:
* Click and drag blueprinted track control points to move them
* Select control points by clicking on them
* Delete selected control points (default hotkey Delete)
* Modify the track type and various other properties
* Move the midpoint of a track section (indicated by a small grey bar), changing how curves behave, and where track types change

It is possible to select both blueprinted (unbuilt) and built track control points. However, only a few changes can be made to built track. It is possible to convert built track back to blueprints with the '''Insert''' hotkey - note that you will not be refunded the original build cost when doing this, and you will pay for the construction a second time when building!

Multiple control points can be selected at once. You can click and drag to draw a box around multiple control points at once, or shift-click to add control points to the current selection.

== Changing track levels and types ==

[[File:TrackLevelsAndTypes.PNG|thumb|300px|right|Menus for selecting track levels (top) and track types (bottom).]]
[[File:GroundLevelRoadsStreams.PNG|thumb|300px|right|Ground level track cannot be built across streams or roads at shallow angles.]]
[[File:DifferentLevels.PNG|thumb|300px|right|Tracks pass over/under tracks at different levels, but intersect tracks at the same level.]]
[[File:TrackTypes.PNG|thumb|300px|right|Tunnel, ground, and viaduct tracks. Note that track types change at mid points.]]

Most of the track editing tools enable the track level and track type menus, which are displayed to the right of the tool buttons. These menus work together, and apply to newly created track, or modify selected track.

=== Track level menu ===

Track can be laid at ground level, above ground on viaducts, or below ground in tunnels. Tracks on different levels will pass over/under each other.

The '''Ground''' option lays track at ground level. This is the cheapest option, but has some limitations:
* Track cannot be laid across rivers, lakes, or seas
* Roads cannot be crossed diagonally (stations and some track types - e.g. the default tram track type - ignore this restriction)
* Streams cannot be crossed diagonally (stations ignore this restriction)

Viaducts are built with the '''+1''', '''+2''', and '''+3''' options. The '''+2''' option builds taller viaducts that can pass over tracks on the '''+1''' level, and the '''+3''' level is even higher. Two tracks that are built at the same level will intersect.

Tunnels are built and behave similarly, with the '''-1''', '''-2''', and '''-3''' level.

The special Unlimited Height and Unlimited Depth ('''+∞''' and '''-∞''') levels create tracks that never intersect, not even with tracks on the same level.

Track levels are defined at each track control point, and always change at the midpoint between two control points.

When laying new track with the [[File:Icon add track.png|24px|Append to tracks or create new ones icon]] create track tool, you can place the first control point at one level, and then select a different level before placing the second control point. When connecting new track to existing control points, the track level of the existing point is never changed.

In the [[File:Icon sel track.png|24px|Move, delete, and edit tracks icon]] edit tracks tool, track levels can be changed for blueprinted track, and midpoints can be moved to change where track types change.

=== Track type menu ===

The track type menu consists of two sections:
* A favourites hotbar with 9 track types and level combinations, selected by the hotkeys 1-9
* The [[File:Icon all tracks.png|24px|All tracks icon]] all tracks menu, allowing you to specify any track type, and redefine favourites

Track types behave very similarly to track levels.

The [[File:Icon all tracks.png|24px|All tracks icon]] all tracks menu is hidden by default, and can be toggled by clicking the button. When open, you can select a track type from the list on the left, and a track level from the menu above. The track type will apply to new tracks being created, or to selected tracks being modified.

The combination of the track type and level selected can be saved to the favourites hotbar by selecting a slot in dropdown menu, replacing any existing favourite in the selected slot. If the combination is already favourited, the existing slot will become empty.

Additional track types can be added using [[Modding|mods]], available in the Steam Workshop.

File:TrackLevelsAndTypes.PNG

2023-01-21T21:56:53Z

Danny252: Menus for setting track levels (top) and types (bpttom).

== Summary ==
Menus for setting track levels (top) and types (bpttom).

File:Icon all tracks.png

2023-01-21T21:48:21Z

Danny252:

File:TrackTypes.PNG

2023-01-21T21:25:35Z

Danny252: Track levels in NIMBY - tunnel (-3, -2, or -1), ground level, and viaduct (+1, +2, or +3). Track types are defined at each track node, and change at track mid points.

== Summary ==
Track levels in NIMBY - tunnel (-3, -2, or -1), ground level, and viaduct (+1, +2, or +3). Track types are defined at each track node, and change at track mid points.

File:DifferentLevels.PNG

2023-01-21T21:23:08Z

Danny252: Tracks pass over/under tracks at different levels, but intersect tracks at the same level.

== Summary ==
Tracks pass over/under tracks at different levels, but intersect tracks at the same level.

File:GroundLevelRoadsStreams.PNG

2023-01-21T21:13:38Z

Danny252: Ground level track cannot be laid across streams or roads at shallow angles

== Summary ==
Ground level track cannot be laid across streams or roads at shallow angles

File:TrackSectionConnectedCurve.PNG

2023-01-21T21:00:04Z

Danny252: Danny252 uploaded a new version of File:TrackSectionConnectedCurve.PNG

== Summary ==
Two track sections connected together, forming a curve.

File:TrackCurveInvalid.PNG

2023-01-21T20:59:37Z

Danny252: Danny252 uploaded a new version of File:TrackCurveInvalid.PNG

== Summary ==
A track section that cannot be created, because the curve is too tight.

File:TrackCurveInvalid.PNG

2023-01-21T20:57:41Z

Danny252: A track section that cannot be created, because the curve is too tight.

== Summary ==
A track section that cannot be created, because the curve is too tight.

File:TrackSectionConnectedCurve.PNG

2023-01-21T20:55:40Z

Danny252: Danny252 uploaded a new version of File:TrackSectionConnectedCurve.PNG

== Summary ==
Two track sections connected together, forming a curve.

File:TrackSectionConnectedCurve.PNG

2023-01-21T20:53:33Z

Danny252: Two track sections connected together, forming a curve.

== Summary ==
Two track sections connected together, forming a curve.

File:TrackSectionNew.PNG

2023-01-21T20:52:25Z

Danny252: Example of a newly created, unconnected track section.

== Summary ==
Example of a newly created, unconnected track section.

File:Control interactive with icon add.png

2023-01-21T20:30:47Z

Danny252:

File:Icon 2x tracks.png

2023-01-21T20:20:49Z

Danny252:

File:Icon add signal.png

2023-01-21T20:14:54Z

Danny252:

File:Icon sel signal.png

2023-01-21T20:14:24Z

Danny252:

File:Icon building.png

2023-01-21T20:12:45Z

Danny252:

File:Icon station.png

2023-01-21T20:12:03Z

Danny252:

File:Icon sat.png

2023-01-21T20:10:45Z

Danny252: