Simon
Simon
This project never used the NS API, which indeed changed when it got transferred to the NS Mlab department, but called the HAFAS instance of NS International.
Duplicate of #438, RIG changed their (internal) API.
We've started mapping the station id's to the correct UIC codes ourself. NMBS returns the UIC code for the "carTo" field in both "carFrom" and "carTo", where their own ID...
NMBS ID's seems to match with Infrabel's open data > https://opendata.infrabel.be/explore/dataset/operationele-punten-van-het-newterk/information/?disjunctive.classification
NMBS occasionally returns an internal point, rather then an actual station (I'm not sure how to translate, we would call it a 'dienstregelpunt' in Holland). This breaks the iRail API...
Few words about myself, I used to have a professional background in the Dutch railway system, and started working on integrating Belgian data into some applications that I'm running as...
Sounds like a legitimate reason to break the API, especially if done when bumping major version. This should be a one-time change that needs to be done at some point...
Rijdendetreinen listens to pushdata from NDOVloket.nl, their API can be self-hosted: https://github.com/rijdendetreinen/gotrain
It's HAFAS proxied through some layer of NMBS oddities as far as I'm aware.
It's what I can remember at least, we're doing GTFS (-RT) and mix in platform information from querying SNCB. Not sure if the output matches HAFAS, but the underlying engine...