Support chained check-ins for trains split across multiple data sources #5005
Replies: 3 comments 4 replies
|
+1 I am working on an improved dataset for Czech trains, and I often need to split trains into 2 at operational points (boarding/deboarding disallowed, train does not actually stop, but agency / line changes) The canonical way to represent this in GTFS is to connect them into one block_id, and specify it as an in-seat transfer in transfers.txt Träwelling however currently does not support this, which would make checking into such trips essentially impossible. |
|
Actually it's a problem with handling the trip blocks by Träwelling, in Transitous the trips are displayed as one train, but at some point just the line and/or headsign changes and Träwelling treats each part as separate train. Pretty annoying if the change happens at the border point, where there is no possibility to check in again |
|
Yep, in the CZ data I'm working on, this is an extremely "good" example - this would be 3 checkins that don't even start/end in the correct places: |
|
Indeed, it's exactly that! And I can add some connected trips of regional buses (like when they change the line after arriving at the terminus, for example PID 345 and IDOL 630) |
|
Update: It looks like a single check-in is now possible for many of these journeys. I’m not sure whether this is due to a recent Träwelling update or a change in the underlying data. I couldn’t find anything about it in the Träwelling changelog. There are still some trains where this doesn’t work, though. For example, NJ 13486 from Vienna to Zürich still requires separate check-ins. |
|
The joined trips are fixed in #5014 |
|
Ah good to know, I must have missed that. |
Uh oh!
There was an error while loading. Please reload this page.
Currently, many cross-border trains are split into multiple trains on Träwelling because the underlying data sources only cover individual countries.
For example, if you want to check in to ICE 108 from Zürich to Hamburg, the initial check-in is only possible as far as Basel SBB. From there, a second check-in is required for the remaining journey to Hamburg. The check-in page already shows that the train continues as ICE 108 to Hamburg, so it might be useful to introduce a function that allows these separate check-ins to be combined or chained into a single journey.
If this functionality were also available for manual check-ins, it could be useful in several situations. For example, there are cases where the data for one country ends at the last station in that country, while the data source for the neighboring country only starts at the first station in that country. This can leave a gap between the two parts of an otherwise continuous train journey. It would also be particularly useful for railway workers, as trains often continue beyond their final public stop as an empty or non-public service, which currently cannot easily be represented in a check-in.
All reactions