https://github.com/derhuerst/berlin-gtfs-rt-server
Expose Berlin & Brandenburg transit data as a GTFS-RT feed.
https://github.com/derhuerst/berlin-gtfs-rt-server
berlin gtfs gtfs-realtime gtfs-rt public-transport transit
Last synced: 2 months ago
JSON representation
Expose Berlin & Brandenburg transit data as a GTFS-RT feed.
- Host: GitHub
- URL: https://github.com/derhuerst/berlin-gtfs-rt-server
- Owner: derhuerst
- License: other
- Created: 2020-10-20T16:58:53.000Z (almost 5 years ago)
- Default Branch: main
- Last Pushed: 2024-02-15T18:27:48.000Z (over 1 year ago)
- Last Synced: 2025-04-22T06:39:27.329Z (6 months ago)
- Topics: berlin, gtfs, gtfs-realtime, gtfs-rt, public-transport, transit
- Language: JavaScript
- Homepage: https://v0.berlin-gtfs-rt.transport.rest/
- Size: 120 KB
- Stars: 13
- Watchers: 3
- Forks: 1
- Open Issues: 5
-
Metadata Files:
- Readme: docs/readme.md
- License: LICENSE
Awesome Lists containing this project
README
# Unofficial [GTFS Realtime](https://gtfs.org/reference/realtime/v2/) feed for Berlin & Brandenburg
**This endpoint provides realtime transit data for Berlin & Brandenburg in the [GTFS Realtime (GTFS-RT)](https://gtfs.org/reference/realtime/v2/) format.**
[](https://stats.uptimerobot.com/57wNLs39M/786241281)
Underneath, it works by polling the [VBB](https://en.wikipedia.org/wiki/Verkehrsverbund_Berlin-Brandenburg) [HAFAS endpoint](https://github.com/public-transport/vbb-hafas). Those interested in delays of *all* vehicles, instead of a particular one, don't have to poll VBB's API brute-force: They're able to fetch the data efficiently from here.
*Note:* This feed is run by people *not related* to [VBB](https://en.wikipedia.org/wiki/Verkehrsverbund_Berlin-Brandenburg), [BVG](https://en.wikipedia.org/wiki/Berliner_Verkehrsbetriebe) and the government.
## Why use this API?
- **Realtime Data** – This API returns realtime data whenever the underlying [API for VBB's mobile app](https://github.com/public-transport/hafas-client/blob/33d7d30acf235c54887c6459a15fe581982c6a19/p/vbb/readme.md) provides it.
- **No API Key** – You can just use the API without authentication.
- **CORS** – This API has [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS) enabled, so you can query it from any webpage.
- **Caching-friendly** – This API sends [`ETag`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/ETag) & [`Date`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Date) headers, allowing clients to cache responses properly.
## Getting Started
*Note:* This project is work-in-progress, the feed might go offline at any time! I'm happy to receive any kind of feedback via the [`berlin-gtfs-rt-server` GitHub Issues](https://github.com/derhuerst/berlin-gtfs-rt-server/issues).
**The URL of the GTFS-RT feed is [`https://v0.berlin-gtfs-rt.transport.rest/feed`](https://v0.berlin-gtfs-rt.transport.rest/feed).**
As an example, let's use [`print-gtfs-rt-cli`](https://github.com/derhuerst/print-gtfs-rt-cli), [`head`](https://www.man7.org/linux/man-pages/man1/head.1.html) and [`jq`](https://stedolan.github.io/jq/) to inspect it:
```shell
curl 'https://v0.berlin-gtfs-rt.transport.rest/feed' -s | print-gtfs-rt --json | head -n 1 | jq
```
```json
{
"id": "10989100",
"is_deleted": false,
"trip_update": null,
"vehicle": {
"trip": {
"trip_id": "143651102",
"route_id": "17453_700",
"direction_id": 0,
"start_time": "",
"start_date": "",
"schedule_relationship": 0
},
"vehicle": {
"id": "m41",
"label": "U Hermannplatz",
"license_plate": ""
},
"position": {
"latitude": 52.48768997192383,
"longitude": 13.42607307434082,
"bearing": 0,
"odometer": 0,
"speed": 0
},
"current_stop_sequence": 0,
"stop_id": "900000078105",
"current_status": 1,
"timestamp": 0,
"congestion_level": 0,
"occupancy_status": 0
},
"alert": null
}
```