Home
This repository aims to create enties for Home Assistant. It combines and impoves on work of others and verifies this with multiple data providers ... and adapts where possible. This is ongoing work but has proven working results
- configuration via the GUI, no configuration.yaml needed
- Uses a route to further select start/end stops
- Shows next 10 departures on the same stretch start/end , including alternative transport lines if applicable
- allows to load/update/delete datasources in gtfs2 folder from the GUI
- Option to add gtfs realtime source/url
- Option to add gtfs realtime vehicle location source/url, generates geojson file, e/g/ for tracking a vehicle on map card
- Option to add gtfs realtime alerts source/url
- Add sensors tracking departures of stops around 'you' (zone or person), also with realtime data
- A service to update the GTFS static datasource, e.g. for calling the service via automation
- A service to add/update GTFS realtime locally, e.g. to reduce multiple calls for the same data externally
- translations: English, French, German, Spanish, Portuguese
![image]
There are often multiple sources covering the same transport provider or geographical area. The background for that is unclear but there are known issues between them as inconsistent data, lack of updates, etc.
Interesting sites with multiple references are:
- Busmaps (aka GTFS.pro) who also have 'improved' datasets, probably cleaned and consistency-checked, often much smaller zip and thus quicker in unpacking.
- Mobility Database
Note: verify the individual datasources as quite a few of them have proven to be incomplete or incorrect. This is not the responsibility of the above sites, but I found busmaps/gtfs.pro providing better data till now
Sources working/tested with GTFS2 (links may change over time, please report if missing/erroneous)
| Provider | Geo-covering | Type* | Static | RT Trip | RT Veh. Pos. | RT Alert | Link | extract ** | Comment | Tested*** |
|---|---|---|---|---|---|---|---|---|---|---|
| Zou 06 | Region | B | x | x | link | 0.25 | 2024-04 | |||
| PalmBus Cannes | City | B | x | x | x | x | link | 0.5 | issue with feed_info.txt in zip, use the Service call | 2024-04 |
| Metz | City | B | x | link | 0.25 | 2023-12 | ||||
| Orleans | City | B | x | x | link | 0.25 | 2023-12 | |||
| Bibus Brest | City | B | x | x | x | x | link | 0.1 | 2023-12 | |
| Lille Ilevia | City | B, T, S | x | x | link | 0.5 | 2024-01 | |||
| Lyon | City | B, T | x | link | 0.4 | requires user/pwd so manual download of zip, use lower-case for zip-name | 2024-04 | |||
| Toulon | City | B | x | link | 0.05 | 2024-02 | ||||
| TER France | Country | R | x | x | link | 0.5 | 2024-03 | |||
| Brussels | City | B | x | link | 0.25 | 2023-12 | ||||
| TEC Wallonia | Region | B | x | link | 1 | 2024-02 | ||||
| Vilnius | City | B | x | link | 0.5 | 2023-12 | ||||
| Germany | Country, Region, Local | B, T, R, S | x | x | link | 0.5 - 2.5 | 2023-12 | |||
| Sweden | Country | B | x | x | link | 1 | use API key in url to get zip | 2023-12 | ||
| Skånetrafiken | Regional | B, T, R | x | ? | link | 0.2 | use API key in url to get zip | 2024-04 | ||
| Finland | Country | B | x | x | link | 2 | 2023-12 | |||
| Netherlands | Country | B, T, R, S | x | x | x | x | link | 2.5 | 2024-01 | |
| Switzerland | Country | B, T, R | x | x | link GTFS_RT | 3 | 2023-12 | |||
| NSW (greater Sydney area) | Region | B, T, R, S, F | x | link | 1 | 2023-12 | ||||
| Hungary (Volan) | Country | B | x | link | 0.3 | 2024-01 | ||||
| Budapest BKK | City | B, T | x | x | x | x | link | 0.75 | RT not confirmed (yet) | 2024-01 |
| London | City | B | x | link | 2.5 | 2024-01 | ||||
| UK | Country | B | - | - | - | - | link | - | zip too large to handle | 2024-01 |
| EastYorkshire | Region | B | x | link | 0.3 | 2024-03 | ||||
| Krakow | City | B, T | x | x | x | x | link | 0.2 | for T(rams) issue with feed_info.txt in zip, use the Service call | 2024-02 |
| Dublin | City | B | x | x | link | 0.3 | 2024-02 | |||
| Washington WMATA | City | B, T | x | x | ? | ? | link | 0.6 | for static: append api_key to static url works, although it throws an error (ignore) | 2024-02 |
| Spokane | City | B, T | x | x | x | x | link | 0.2 | 2024-04 | |
| New York MTA | City | B, T, R | x | x | - | ? | static and RT | ? | tested for Long Island RR only | 2024-02 |
| San Fransisco Bay | City | B, T | x | link | 0.5 | 2023-12 | ||||
| Bizkaia | Region | B | x | x | x | ? | link | 0.1 | 2024-02 | |
| Zagreb | City | B, T | x | link | 0.4 | 2024-02 | ||||
| Austria Vienna | City | B, T | x | link | 0.3 | 2024-03 | ||||
| Austria ÖBB | Country | R | x | link | 0.3 | 2024-03 |
*Types: B(us) T(ram), R(ail), S(ubway), F(erry) The datasource may cover other types as cable cars, gondola, stairs, taxi, etc. but not verified working (by me)
**Indicative extraction duration of the static/zip file in hours
*** Year month of initial testing with the release/version at that time. These are not part of any planned regression testing with new releases. The onces I use myself will show updates of course
Challenges (see also docu ):
- Some providers show to have realtime but are not in gtfs format 'protobuf' as expected by the library in use e.g. Brussels, SanFransisco Bay, Krakow. I will not be able to build individual solutions for 'deviating' providers.
- Multiple stop_id for the same stop, depending on vehicle(type) or even line (CH, NL), meaning that one has to configre multiple times.
- Realtime data may be provided along a route/trip but not all stops are always covered