General Transit Feed Specification (GTFS) ist ein von Google entwickeltes digitales Austauschformat für Fahrpläne des öffentlichen Personenverkehrs und dazugehörigen geografischen Informationen, wie z.B. Standorte von Haltestellen. Die Daten werden durch Transportunternehmen zur Verfügung gestellt und als gesammelte Datenbank auf der Open-Data Plattform öV-Schweiz im GTFS Format publiziert. Genutzt werden die Daten zur Entwicklung von Applikationen im Zusammenhang mit dem öffentlichen Verkehr, wie z.B. Fahrplanabfragen.
Im Gegensatz zu GTFS Realtime (GTFS RT) liefert GTFS Static, wie der Name schon sagt, nur statische Daten und keine Echtzeitdaten.
Mit dieser Static-Datei wird erstmals der gesamte öffentliche Verkehr eines Landes in einem einzigen Feed dargestellt.
Fachliche Beschreibung
GTFS Static wird anhand einer Reihe Text Files im ZIP Format bereitgestellt. Jedes File gibt Informationen zu einem bestimmten Aspekt der Transit-Informationen wie beispielsweise Haltestellen (stops.txt), Routen (routes.txt), Fahrten (trips.txt), Transportunternehmen (agency.txt) und weiteren Fahrplanrelevanten Daten. Einige Angaben sind notwendig um valide GTFS Daten bereitzustellen, andere sind optional und liefern nützliche Zusatzinformationen (wie z.B. Änderungen des Fahrplans an spezifischen Feiertagen = calendar_dates.txt).
Die folgende Graphik zeigt das Zusammenspiel der verschiedenen Informationen, wobei zurzeit nicht alle für den öV-Schweiz erfasst und im GTFS Format verfügbar sind:
Gehe zu Datensatz: https://opentransportdata.swiss/de/dataset/timetable-2021-gtfs2020
Wichtige Konzepte
- GTFS Static: Publikation von statischen Transit-Informationen im GTFS Format.
- GTFS Realtime: Publikation von Echtzeit-Transit-Informationen als Anreicherung der statischen GTFS Daten, in der Form von Protocoll Buffers
Technische Aspekte
Struktur der Daten
Jedes File besteht aus kommagetrennten Text- und Zahlenreihen mit Feldern, welche zusammengesetzt die gesuchten Informationen liefern. Eine ausführliche Beschreibung der einzelnen Felder in den verschiedenen Files werden im Detail auf der folgenden Webseite erläutert: https://developers.google.com/transit/gtfs/reference/
Für den GTFS Export des öV-Schweiz werden zurzeit die folgenden Files bereitgestellt:
- agency.txt.
- calendar.txt.
- calendar_dates.txt
- feed_info.txt
- routes.txt
- stop_times.txt
- stops.txt
- transfers.txt (ist in Erarbeitung)
- trips.txt
Nicht zur Verfügung gestellt werden: fare_attributes.txt, fare_rules.txt, feed_info.txt und frequencies.txt
Agency.txt
|
1 2 3 4 5 6 7 8 |
agency_id,agency_name,agency_url,agency_timezone,agency_lang,agency_phone "11","Schweizerische Bundesbahnen SBB","http://www.sbb.ch/","Europe/Berlin","DE","0900 300 300 " "801","PostAuto Schweiz","http://www.sbb.ch/","Europe/Berlin","DE","0900 300 300 " "840","Busbetrieb Aarau","http://www.sbb.ch/","Europe/Berlin","DE","0900 300 300 " "31","BDWM Transport (bd)","http://www.sbb.ch/","Europe/Berlin","DE","0900 300 300 " "899","BDWM Transport (wm Auto)","http://www.sbb.ch/","Europe/Berlin","DE","0900 300 300 " "886","Regionale Verkehrsbetriebe Baden-Wettingen","http://www.sbb.ch/","Europe/Berlin","DE","0900 300 300 " "839","Zugerland Verkehrsbetriebe","http://www.sbb.ch/","Europe/Berlin","DE","0900 300 300 |
calendar.txt
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
service_id,monday,tuesday,wednesday,thursday,friday,saturday,sunday,start_date,end_date "TA+b000b","1","1","1","1","1","0","0","20161211","20171209" "TA+b0001","1","1","1","1","1","1","1","20161211","20171209" "TA+b0016","0","0","0","0","1","1","0","20161211","20171209" "TA+b0dmg","0","0","0","0","0","0","1","20161211","20171209" "TA+b12cr","1","1","1","1","0","0","0","20161211","20171209" "TA+b0008","1","1","1","1","1","0","0","20161211","20171209" "TA+b0027","1","1","1","1","1","1","0","20161211","20171209" "TA+b0dnc","0","0","0","0","0","1","1","20161211","20171209" "TA+b001r","1","1","1","1","1","0","1","20161211","20171209" "TA+b001j","0","0","0","0","0","1","0","20161211","20171209" "TA+b001t","0","0","0","0","0","0","1","20161211","20171209" "TA+b04oi","1","1","1","1","1","0","0","20161211","20171209" "TA+b0ch2","0","0","0","1","0","0","0","20161211","20171209 |
calendar_dates.txt
|
1 2 3 4 5 6 7 8 9 10 11 12 |
service_id,date,exception_type "TA+b0003","20161226","2" "TA+b0003","20170102","2" "TA+b0003","20170414","2" "TA+b0003","20170417","2" "TA+b0003","20170501","2" "TA+b0003","20170525","2" "TA+b0003","20170605","2" "TA+b0003","20170801","2" "TA+b0007","20161226","2" "TA+b0007","20170102","2" "TA+b0007","20170414","2 |
feed_info.txt
|
1 2 |
feed_publisher_name,feed_publisher_url,feed_lang,feed_start_date,feed_end_date,feed_version "SBB","http://www.sbb.ch/","DE","20161211","20171209","20170518 |
routes.txt
|
1 2 3 4 5 6 7 8 9 10 |
route_id,agency_id,route_short_name,route_long_name,route_type "23-56-j17-1","801","056","","3" "11-61-j17-1","7031","061","","3" "11-62-j17-1","7031","062","","3" "24-64-j17-1","801","064","","3" "24-65-j17-1","801","065","","3" "24-66-j17-1","801","066","","3" "24-67-j17-1","801","067","","3" "23-75-j17-1","801","075","","3" "11-83-j17-1","801","083","","3 |
Achtung:
- „route_short_name“ wird in Kürze noch angepasst und enthält dann eine interne Darstellung der Verkehrsmittelart.
- Einige Routen in GTFS haben eine Erweiterung „-Y“. Der Grund liegt darin, dass sie eine künstlich angelegte Liniennummer haben. Nur so kann „route_short_name“ gültig sein. Diese künstlichen Linien sollten nicht so den Benutzern angezeigt werden. Für Züge wird „trip_short_name“ die Zugnummer beinhalten.
Die Verkehrsmitteltexte, die zur Anwendung kommen werden (noch nicht umgesetzt):
stop_times.txt
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
trip_id,arrival_time,departure_time,stop_id,stop_sequence,pickup_type,drop_off_type "1.TA.1-9-j17-1.1.H","05:25:00","05:25:00","8502034:0:2","1","0","0" "1.TA.1-9-j17-1.1.H","05:28:00","05:29:00","8502033:0:2","2","0","0" "1.TA.1-9-j17-1.1.H","05:33:00","05:33:00","8502032:0:1","3","0","0" "1.TA.1-9-j17-1.1.H","05:36:00","05:36:00","8502031:0:1","4","0","0" "1.TA.1-9-j17-1.1.H","05:42:00","05:42:00","8502030:0:2","5","0","0" "1.TA.1-9-j17-1.1.H","05:50:00","05:50:00","8502119:0:7","6","0","0" "2.TA.1-9-j17-1.2.H","05:53:00","05:53:00","8502034:0:1","1","0","0" "2.TA.1-9-j17-1.2.H","05:57:00","05:58:00","8502033:0:2","2","0","0" "2.TA.1-9-j17-1.2.H","06:02:00","06:02:00","8502032:0:1","3","0","0" "2.TA.1-9-j17-1.2.H","06:04:00","06:04:00","8502031:0:1","4","0","0" "2.TA.1-9-j17-1.2.H","06:09:00","06:11:00","8502030:0:2","5","0","0" "2.TA.1-9-j17-1.2.H","06:20:00","06:20:00","8502119:0:7","6","0","0" "3.TA.1-9-j17-1.3.H","24:38:00","24:38:00","8502119:0:7","1","0","0" "3.TA.1-9-j17-1.3.H","24:46:00","24:46:00","8502030:0:1","2","0","0" "3.TA.1-9-j17-1.3.H","24:49:00","24:49:00","8502031:0:1","3","0","0" "3.TA.1-9-j17-1.3.H","24:52:00","24:52:00","8502032:0:1","4","0","0" "3.TA.1-9-j17-1.3.H","24:57:00","24:57:00","8502033:0:1","5","0","0" "3.TA.1-9-j17-1.3.H","25:01:00","25:01:00","8502034:0:1","6","0","0 |
stops.txt
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
stop_id,stop_name,stop_lat,stop_lon,location_type,parent_station "1101064","Malpensa Aeroporto, terminal 1","45.6272144319203","8.7111160249179","","" "8000339","Weissenhorn Eschach","48.3010036099201","10.135089480891","","" "8000709:0:2","Neckarsulm Mitte","49.1934688770383","9.22294014126908","","" "8000778","Asselheim (D)","49.5762169849528","8.16159859923981","","" "8000781","Grünstadt-Nord","49.5733510011593","8.17078836459763","","" "8000988","Witzighausen","48.3174402469306","10.097800413442","","" "8002015","Nördlingen","48.85084676195","10.4978651252803","","8002015P" "8002015:0:4","Nördlingen","48.85090587299","10.4978651252803","","8002015P" "8002015P","Nördlingen","48.85084676195","10.4978651252803","1","" "8002023","Ebermergen","48.7562093140126","10.7109634770088","","" "8002023:0:1","Ebermergen","48.7562685367003","10.7109634770088","","" "8002038","Möttingen","48.8068073922247","10.5978386332639","","8002038P" "8002038:0:1","Möttingen","48.8069257181851","10.5978386332639","","8002038P" "8002038:0:2","Möttingen","48.8068665552398","10.5978386332639","","8002038P" "8002038P","Möttingen","48.8068073922247","10.5978386332639","1","" "8002039","Hoppingen","48.8038195691943","10.6532018042319",""," |
Die Steige müssen in GTFS als einzelne Halte modelliert werden. Ein Wechsel des Steigs ist dann ein Wechsel des Stops aus Sicht GTFS.
Das Beispiel „8500010“ (Basel SBB):
Alle Halte von Basel haben einen gemeinsamen „Parent“ „8500010P“. Die einzelnen Gleise sind mit „:“ abgetrennt. Ein „Gleis“ kann auch ein Gleis+Sektoren sein (Bsp: „8500010:0:7CD“). Es gibt auch sehr komische Ergänzungen, wie „Bern Bfpl“ also „8507000:0:Bfpl“, wenn die RBS ihn für Bahnersatzbusse verwendet.
trips.txt
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
route_id,service_id,trip_id,trip_headsign,trip_short_name,direction_id "1-9-j17-1","TA+b0001","2.TA.1-9-j17-1.2.H","Lenzburg","21916","0" "1-90-j17-1","TA+b0001","4.TA.1-90-j17-1.2.R","Wallbach, Gemeindehaus","90074","1" "1-90-j17-1","TA+b0001","10.TA.1-90-j17-1.2.R","Wallbach, Gemeindehaus","90022","1" "1-90-j17-1","TA+b0001","43.TA.1-90-j17-1.13.R","Schupfart, Dorf","90071","1" "1-90-j17-1","TA+b0001","44.TA.1-90-j17-1.13.R","Schupfart, Dorf","90013","1" "1-90-j17-1","TA+b0001","50.TA.1-90-j17-1.13.R","Schupfart, Dorf","90067","1 "8002015P","Nördlingen","48.85084676195","10.4978651252803","1","" "8002023","Ebermergen","48.7562093140126","10.7109634770088","","" "8002023:0:1","Ebermergen","48.7562685367003","10.7109634770088","","" "8002038","Möttingen","48.8068073922247","10.5978386332639","","8002038P" "8002038:0:1","Möttingen","48.8069257181851","10.5978386332639","","8002038P" "8002038:0:2","Möttingen","48.8068665552398","10.5978386332639","","8002038P" "8002038P","Möttingen","48.8068073922247","10.5978386332639","1","" "8002039","Hoppingen","48.8038195691943","10.6532018042319",""," "1-350-j16-1","TA","49.TA.1-350-j16-1.2.R","1-350-j16-1.2.R","Zürich, Triemli","1" |
Achtung:
- Für Züge beinhaltet „trip_short_name“ die Zugnummer.
transfers.txt
Die Metabahnhöfe werden in Kürze im transfers.txt abgebildet sein.
Stabilität von Identifiern zwischen Versionen des Static Files
Jede Woche wird das GTFS Static neu erzeugt. Daher kann es sein, dass die „service_id“ und die „trip_id“ nicht identisch sind.
Wann gibt es neue GTFS Static Files?
Am Montag wird das neue HRDF publiziert.
Der GTFS Upload erfolgt Mittwochs 09:10 Uhr per Skript. Der GTFSR Feed ladet die Dateien um 14:00 Uhr per Skript ein. Dann dauert es ca. 5-10 Minuten bis die Dateien im System und somit der GTFS-RT Feed umgestellt ist.
Technische Details zum besseren Verständnis
Montags werden die HRDF-Daten in DIVA importiert. Anschliessend (ebenfalls montags) läuft eine Übernahme von Fahrplandaten für die EFA.
Dienstags machen wir den GTFS-Export.
Mittwochs wird der neue GTFS-ZIP-Datensatz gegen 9:10 Uhr auf FTP-Server der SBB hochgeladen, die neuen Kalenderfahrplandaten zusammen mit neuen GTFS-Daten werden Mittwochs gegen 14:00 Uhr auf entsprechenden Servern eingespielt.
Interne Konsistenz eines GTFS Static Files
Wir bemühen uns, immer korrekte GTFS Static Files zu produzieren. Google schlägt vor, die interne Konsistenz mit dem FeedValidator zu testen. Leider kann die aktuelle Version mit der Grösse unserer Datei nicht umgehen. Ein anderes mögliches Werkzeug ist gtfstidy, das unter anderem eine Validierung vornehmen kann mit dem Parameter „-v“
Weiterführende Angaben
Weiterführende Angaben zu GTFS Static finden Sie auf der GTFS Entwicklerseite von Google: https://developers.google.com/transit/gtfs/