Bertware

@koeleboe Thanks for the detailed report including dumps of both responses by the way, helped quickly verifying the issue and identifying the case

> Another difference between the current API and the new is the availability of data in the future. For example; in the current API you can look up months in...

The rate limiter is a global limit for the api instance, to ensure the services behind are not disturbed when someone starts scraping irail. It results in only irail going...

> Maybe another bug, but I'm currently on the train, so only a screenshot is possible. The IC738 is cancelled from Sint-Niklaas to Antwerpen. However, the train departs from Lokeren...

> > I just stumbled upon another discrepancy, don't know if it's temporary https://lumen.api.irail.be/v1/vehicle?id=2118&format=json fails while https://api.irail.be/vehicle?id=2118&format=json returns a response > > This happens in a certain way too with...

> The only issue I encountered is that the lang parameter seems to be ignored (on XML). All request return English results. This has now been fixed, the translations were...

The continuous deployment for staging got stuck, should be fixed now (unless this was caused by another bug).

Staging has been updated to be a completely different server with exactly the same setup, so it'll always be in sync with the development branch from now on. This should...

I think we really need URIs for entire Europe. Can we generate these automatically based on UIC station codes for railways? This way we have unique identifiers which can be...

> Technical Identifiers are also standardized. The format to make IDs unique in the own codespace. But the combination of a codespace URL with an ID forms a URI, even...