Jan Cornelissen
Jan Cornelissen
> So, if you want to get the right composition for let's say a station between Poperinge and Kortrijk, you have to make another request (as the composition call doesn't...
For the train number it's a different story, indeed. For some vehicle requests, where I know the departure station, I choose the relevant composition. For the others, I assume that...
The JSON errors are gone now indeed, but now XML has an error: ``` This page contains the following errors: error on line 2 at column 1: Extra content at...
Honestly, I'd love to see it replaced by the NMBS occupancy 😇 ``` "CommercialInfo": { "Occupancy": { "Level": 1 } } ```
I'm all for more data, the more information the better 😊 Maybe you've noticed in the logs, but I'm slowly moving away from XML. I have rewritten the API wrapper...
I got some people complaining about missing trains, but could never reproduce (a few days after complaint). This makes a lot of sense!
Same error btw for international trains: Eurostar, Thalys, TGV,... Here's me hoping that fixing this issue would fix that one too 😇
> A solution would be to see if this train shows up in the realtime data I guess that makes a lot of sense. The situation is leading to confusion...
> These trains show up in the timetable view and route-planner, but not in the vehicle endpoint, right? True, for the trains operated by other operators. Not sure about the...