Skip to content

Open Transport Community Conference 2026

Jump to bottom
Volker Krause edited this page Oct 11, 2026 · 3 revisions

Transitous at the Open Transport Community Conference 2026

When / Where

Oct 6-9 in Bern, Switzerland, see https://open-transport.org for details. Attendance is free but requires registration.

Who

  • Volker
  • Theo
  • Oliver (bovine3dom)
  • Jonah
  • Felix
  • Robin
  • networkException
  • Daniel (dabund24)
  • Jannis

Topics to discuss/work on during the hack days

Sessions during the unconference part:

  • RAPTOR/ULTRA/Algos
  • RT collection
  • GTFS Extensions
  • Italy
  • Border Controls
  • Ticketing
  • EU complaints

Notes

Usage Policy

  • Add examples in the hope that not everyone will need to ask in the chat
  • Add section on analytical queries that don't need to be real-time.
  • We also lack a higher-level documentation/manual on which API endpoints to use for which use-case, and the cost trade-offs and possible alternatives for this
  • Encourage adding a donation link (first we need this sorted out on our own website though)

Transitous Archive Publishing

List of possible solutions

Requirements:

  • growth of ~2TB/year forever; growth will increase as more realtime feeds are released/integrated. rough guess: 500GB/yr/rt country
  • egress: a few downloads a week
  • continuous release?

Rely more on the Mobility Database

Meta Stations

Prior work

Challenges

  • meta stations are mode-dependent: central station, bus station, airports
  • where is the threshold: French TGV stations outside of the city?
  • we need a way to properly define the expected results: collect those, try to derive rules from that

Examples

  • DUS airport station: a valid destination when flying into Düsseldorf, but not the desired result for ICE arrivals
  • Köln Messe Deutz: a valid destination for ICE trains bypassing Köln Hbf, but not for (regional) rail continuing to Köln Hbf
  • Lauf (rechts/links der Pegnitz): two equivalent stations in a small town
  • Berlin Ostkreuz: valid destination for trains bypassing Berlin Hbf, but not for anything continuing to Hbf
  • München Ost: similar, has both bypassing and continuing to Hbf lines
  • Limburg Süd: unclear whether that's a valid destination for Limburg

Possible ideas/data

  • define primary stations as preferred destination, allow secondary stations as viable end if they would need a transfer to the primary
  • OSM airport tag: city_served: as alias as meta station for flights (or not as good: closest town)

Possible approach

  • route to city center point (OSM city node), and in post-processing cut off at the first transfer inside the city boundary
    • we need to get sufficient level of detail admin boundary info for this from MOTIS
    • might fail for some external airports, but that's probably acceptable (protects against scam airports)
  • photon can return admin boundaries, which would help for this
  • counter-example: Dresden -> Berlin: ICE exit already at Südkreuz or Neustadt as that's closer to the center node
    • client-side post-processing wont be able to fix this, but server-side we could extend the last line after cutting off to a stop closer to the city center node
  • Felix also has an alternative penalty based approach in mind

Misc

Clone this wiki locally