@quin_antarctic I also often notice the same thing where delays are not properly tracked across borders. Train operators generally only see delay within their "home" country but default to "on time" once abroad.

In my opinion, this is why the upcoming EU regulation on passenger rights should include mandatory tracking of delays across Europe in an open data manner. There cannot be effective compensation if operators pretend delays don't happen. cc @erpu @jon @stefanlindbohm @bovine3dom

@wnd @cycling_on_rails @erpu @jon @stefanlindbohm @bovine3dom I can imagine that you don't want to track delay information as a separate field per se, but I'd assume you do want to be able to track the actual train arrival/departure times. Or is that what's included with "all train service tracking and timetable data"?

I'd assume the planned arrival/departures are known, so any differences are pretty easily calculated.

Also seems very relevant information anyhow and I assume (again), that this information is available to the operators/planners anyway..

@quin_antarctic @cycling_on_rails @erpu @jon @stefanlindbohm @bovine3dom yes, this is what I meant by "all train service tracking and timetable data".

Determining whether or the cause of a delay or otherwise is more a performance analysis activity. About which the TEL TSI has very little to say.

@wnd My interpretation in practical terms is that all the (raw) data should by law be available by 2029, but law says nothing about who needs to build a UI to show it.

Realtime data is by definition split at borders (infrastructure managers change + different NAP’s for the data), so there’s nothing saying any particular app would add these data sources just because they exist.

@quin_antarctic @cycling_on_rails @erpu @jon @bovine3dom

@stefanlindbohm @quin_antarctic @cycling_on_rails @erpu @jon @bovine3dom I agree with the UI* stuff. But, and this is important, the linkage between paths and services is maintained across borders, and that this linkage is data is held in each message sent.

1/n
* but who needs a UI, they are difficult to build** and you can never get any one to agree on the of colour of the bicycle shed
** but feel free to roll your own especially if you feel someone else's APP doesn't cut it

@wnd @stefanlindbohm @quin_antarctic @erpu @jon @bovine3dom IMO open-data sharing is enough, as it enables 3rd parties to innovate and present it in a nice UI, ultimately overtaking the incumbent apps or pushing the incumbents to make improvements themselves.

But it works best when all the data is open (timetable, delays, train composition, ticket prices, etc.), otherwise the incumbent has a competitive advantage that shadows 3rd parties.

@cycling_on_rails i think we need more requirements for dog fooding open data because it is often crap compared to what they use internally

@wnd @stefanlindbohm @quin_antarctic @erpu @jon