<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Transportation on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/transportation/</link>
    <description>Recent content in Transportation on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 08 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/transportation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Public Transit Data Servers: OneBusAway vs OpenTripPlanner vs TheTransitClock</title>
      <link>https://www.pistack.xyz/posts/2026-06-08-self-hosted-public-transit-data-servers-onebusaway-opentripplanner/</link>
      <pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-08-self-hosted-public-transit-data-servers-onebusaway-opentripplanner/</guid>
      <description>&lt;p&gt;Public transit agencies around the world publish their schedule and real-time data using the General Transit Feed Specification (GTFS). But serving that data to riders — powering trip planners, arrival predictions, and service alerts — requires dedicated transit data server software. Rather than relying on Google Maps or Apple Maps alone, many agencies and enthusiasts self-host their own transit information systems to maintain data sovereignty, reduce costs, and offer customized rider experiences.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
