Ahhhh 😊

[zugschlus@zug.network]

@jon It is an ICE 1. One of the last train of Deutsche Bahn that provides comfortable accomodation for tall people even in 2nd class?

In the new ICEs of Deutsche Bahn (ICE-L and the BR 408 with the new interior) I (193 cm, "Sitzriese") don't even fit comfortably in 1st class accomodation..

May I ask how tall you are?

[moof@cupoftea.social]

@semireg @jon And yet, they still complain more about DB than SNCF.

And the subreddit does too as a result.

So people watching the show get entirely the wrong vibes here

[sobex@social.sciences.re]

@tal @tml The specific text is not super important for actual travellers, it is more of a cute "This train runs DE, NL, BE (and perhaps FR)", special livery.

[semireg@nrw.social]

@moof @jon As a result, they appear more "typically German" than they might be aware of.

[sobex@social.sciences.re]

@stefanlindbohm @partim @jon Are you able to work using a cached copy of the time table, or can this result in large number of requests to the SNCF API to get the info needed ?

[sobex@social.sciences.re]

@semireg @jon Or the TGV is not full if you go to Paris, but it is "full" according to SNCF if you only want to go to the next stop.

(This one has annoyed a friend of mine very recently)

[jon@gruene.social]

@Zugschlus I know it’s a ICE 1, thanks. See the alt text 🙂

And I don’t dispute those are good. I’ve just taken them too often!

[jon@gruene.social]

@lollar yes. But I’ve taken them too often.

[jon@gruene.social]

@Sobex @semireg why would anyone go anywhere except Paris?

[sobex@social.sciences.re]

@jon @semireg Because they want to go to Switzerland from the Alps, obviously.

[jon@gruene.social]

Trainsplainers: yes I know that’s a ICE 1. I know those are good and comfortable trains.

But *today* I have my reasons for not taking it. That will become clear shortly 🙂

1549 reasons actually.

[stefanlindbohm@mastodon.social]

@Sobex Our journey planner runs 100% in our own systems. We have a license for the raw international timetables (MERITS) and complement that with some other data sources for operators who do not participate in the international dataset.

This is how we can plan any journey across Europe, even when we don’t have an integration to sell tickets.

@partim @jon

[jon@gruene.social]

@Sobex @semireg Drive. Obvs. Or covoiturage.

[sobex@social.sciences.re]

@stefanlindbohm @partim @jon And then, once you have the plan, you only go to the railways API to get the prices and do the actual booking.

This should result in better look / book ratios with the operators API themselves, right ?

Also, how long in advance are those timetable valid ? Does that allow you to identify connections that aren't open for booking yet, but will be eventually ?

(e.g. looking 4 month in advance when one of the train will only be opened for booking 3 month in advance)

[alex_p_roe@mastodon.world]

@jon Provided it’s got nothing to do with US ICE, you should be fine 🙂😁 Otherwise, the experience could be arresting! 😉

[deadliftbear@mas.to]

@jon the number of changes you’ll make? 😂😂

[waldi@chaos.social]

@jon ICE L. Are you seated in wagons 15-17?

And please note:
11:10: Kein gastronomisches Angebot

[stefanlindbohm@mastodon.social]

@Sobex First question depends on implementation. Many other booking sites run ”looks” straight and then yes, we (often, nuance possible) save ”looks” for results the user didn’t click on. There are also pure planning possibilities in some API’s that don’t count as ”looks”.

Timetable horizon is hit and miss. Most common is that operators publish the same data that is available in their own sales channel (regardless if bookable or not). But it varies both directions (yes really).

@partim @jon

[jon@gruene.social]

Step free 😂

[stefanlindbohm@mastodon.social]

@jon ”Free of vertical steps” wasn’t as catchy a name 😅