Knowledge base
Railway data sources by country
The same DAS logic can behave very differently depending on which data sources are available. That is why country and operator context matter so much.
Published: March 6, 2026
TopicsData integrationGermanyBelgiumOperational dataInfrastructure managers
Why local data matters
- DAS needs more than a file format. It needs data that means something in the real operation.
- The same interface name can be useful in one railway and weak in another.
- That is why data quality, timing, and operational meaning matter more than buzzwords.
Examples people talk about
- In Germany, people often mention sources such as Gruene Funktionen ZLR, LA data, EBuLa, and FPLO.
- In Belgium, people often mention Titanis, RCS ADL, and SFERA-related flows.
- In Switzerland and Austria, other local systems and extensions can matter just as much.
- Availability and depth still depend on the railway, not only on the country name.
What to check
- Ask what the source contains, how fresh it is, and who owns it.
- Check whether it supports conflict prevention, timing-point control, temporary restrictions, or only static planning data.
- Check what can be trusted enough to use in live advisory and what is only useful for analysis.
Limits
- Country examples are not a promise of the same integration depth everywhere.
- Access, governance, and operational cooperation still decide what can be used in practice.
- That is why real DAS work starts with the best local sources, not with a generic architecture slide.
Related articles