<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Railway on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/railway/</link>
    <description>Recent content in Railway on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 23 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/railway/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OSRD vs OpenRailwayMap vs Open Rails in 2026: Self-Hosting a Railway Planning, Mapping and Simulation Stack</title>
      <link>https://www.pistack.xyz/posts/2026-09-23-railway-stack-osrd-openrailwaymap-open-rails/</link>
      <pubDate>Wed, 23 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-23-railway-stack-osrd-openrailwaymap-open-rails/</guid>
      <description>&lt;p&gt;Railway engineering has one of the worst open-source toolchains of any infrastructure discipline. Signalling layouts live in proprietary CAD formats, capacity studies are done in vendor software that costs more per seat than a car, and the schedule data your national operator publishes is a PDF. The result is that a small but genuinely useful stack of open tools goes almost completely unnoticed outside a handful of national railway labs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
