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
@transitous @jon Doesn’t need to be that crazy. Date and train number (or linked number) is what it’s designed to be matched on.
But I don’t believe a journey planner project should do this at import. It should be a separate project that sorts out the aggregation/integration and outputs clean files that can be used by journey planning projects. I would be happy to advise (not develop - time constrains) such a project. I know others I can ask too (they haven’t spoken publicly on this yet).
@jon @VolkerKrause Happy to do it!