Bertware

icon indicating a website link https://www.linkedin.com/in/bertmarcelis/

icon company @trafiklab / trafiklab.se icon location Stockholm, Sweden icon location Public Transport, Open Data and Open source. Developer at @trafiklab Volunteering for a better commuter experience through @iRail and @hyperrail.

Results 142 comments of Bertware

internal NMBS API used by iRail is being shut down

> @Muspah Ugh Graphql... Fancy new technology that does the same but differently ;) Only for the stations endpoint which we don't use anyway. Ticketing as well, which is a...

internal NMBS API used by iRail is being shut down

> Ah okay, didn't recognize the exact scheme, HAFAS is not that common in NL. You were right about the proxy though, there is some data being added which is...

internal NMBS API used by iRail is being shut down

Liveboards are now almost completely re-implemented, only platform changes, train cancelled state and time selection has not been implemented yet. Train left/arrived (`left`) and extra train yes/no (`isExtra`) will likely...

internal NMBS API used by iRail is being shut down

> @Bertware Do you know how many differences there are compared to other HAFAS "open APIs"? > > There are some clients out there, and I wonder if they are...

internal NMBS API used by iRail is being shut down

The vehicle endpoint seems to be harder to re-implement. There are 2 endpoints the API uses: - The first one, `Hafas Journey Detail Service`, is available through `GET https://mobile-riv.api.belgianrail.be/riv/v1.0/journey/detail?id=1|750|0|80|8112022&lang=nl`. For...

internal NMBS API used by iRail is being shut down

In `88____:049::8895208:8895505:3:2415:20221202`, 8895208 and 8895505 are the origin id and the destination id. Somehow I overlooked that the train number can be fetched from trip_short_name, so trips.txt should be sufficient...

Backwards compatibility testing of new backend code

> I noticed that the variable NMBS_RIV_API_KEY is needed in this release. This release is based on the API from NMBS and not on GTFS-files? Internal NMBS APIs are used...

Backwards compatibility testing of new backend code

> https://[lumen.api.irail.be/v1/vehicle/?id=1835](https://lumen.api.irail.be/v1/vehicle/?id=1835) this returns an error: This request failed. Please check your query. Error code API_PARAM but in the original API, this works without a problem https://[api.irail.be/vehicle/?id=1835](https://api.irail.be/vehicle/?id=1835) Maybe this has...

Backwards compatibility testing of new backend code

> I noticed that the times are off by one hour. For example: https://[lumen.api.irail.be/v2/vehicle/660](https://lumen.api.irail.be/v2/vehicle/660) or https://[lumen.api.irail.be/v1/vehicle/?id=660](https://lumen.api.irail.be/v1/vehicle/?id=660) for the latest version gives the departure at Oudenaarde at "scheduledDateTime": "2024-03-14T11:07:00+01:00", but according...

Backwards compatibility testing of new backend code

I implemented a fix for this, by handling "cancelled: true", but when I wanted to verify the intermediate cancellation, I noted this train is also showing strange platforms at the...