Talking to the @transitous people at #OpenTransport2025
One headache: data on international trains that is missing the other side of the border
My EN Dacia Hegyeshalom 🇭🇺 - Sighisoara 🇷🇴 is 1 train but shows as 2 on Transitous
@jon @transitous This can also be due to the EN actually technically being a coach group (kurswagen), or train that turns into a coach group. Often the carriers on either side don’t even have data on what happens outside their own country.
This is solved in MERITS with a lot of manual links in the form of ”at border station X, train number Y is to be linked with train number Z”
Even with perfect open data in each country (lol), any aggregation of international data needs this integration layer
@stefanlindbohm @jon @transitous but (presumably?) one can buy a single ticket for the whole night train journey, and if so that ticket would (very likely) be purchaseable directly at one (or both) of the operators. Meaning the operators must know about each other's data to some extent, no?
(Maybe only the ticketing department has access not the timetable department, maybe only ticket counters have access not the website, but that's all a question of data management *within* an operator, no?)
@partim Yep. NeTEx is hell to work with, but it does support A LOT richer data. Like for example marking a scheduled point as a non-passenger border crossing.