koeleboe
koeleboe
Thank you! I've been testing it and it seems to work. Some issues that I encounter: - Status is often null on the liveboard, but always null on the vehicle...
I did some further testing. It seems to work pretty well. However, - Some vehicle calls return error: https://[lumen.api.irail.be/v2/vehicle/559](https://lumen.api.irail.be/v2/vehicle/559)
Hmm that's weird, but I was thinking it would be possible because the data was in real time available in the official NMBS app (and it was possible to open...
Another issue, L892 has some cancelled stops between Ghent and Kortrijk. The journey and liveboard do show this, but the vehicle call not. All stops are served according to it....
It doesnt seem to be fixed. S10 3887 has been canceled between Opwijk and Dendermonde, while the API shows the stops. Fore some reason, the request doesnt work (gives an...
Issue happened again today with S10 3868. It ran directly from Dendermonde to Jette, skipping stations between. The api doesn't show the stops as cancelled
@Bertware happens again with S53 662. Train is rerouted between Oudenaarde and Gent, but the stops between are not cancelled. With the journeyplanner, you dont have the option to go...
Yeah, that makes sense, but weird that the composition is updated after the train arrived at the last station.
@Bertware Another issue with partially cancelled trains. Sometimes the fall back does work, but sometimes not. For example: S53 667 S53 668 Ic2428 is fulle cancelled 18202 is fully cancelled,...
Sorry, it was 657 and 658! 18202 did work this morning, but now not anymore.