-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIRI-ET feed quality overview #232
Comments
The good news is that I was able to match 363 of 1991 updates. |
@leonardehrenfried did you use https://otp.opendatahub.testingmachine.eu? Can you provide me some more detailed info about your attempts, so that I can also have a look? |
Yes, it's all deployed to now. For me I get the most real-time data when I use local busses in Merano, Bressanone or Bolzano. Here are some examples: MeranoBressanoneI never get real-time data for trains. |
After the NeTEx feed for 2025 is available again, I tried again with the following modifications to the data:
The result is this a success rate of 18%. That is not a good rate.
Here is the relevant log message:
We have the following obvious errors:
They affect over half of the updates.
Then we have errors of NEGATIVE_HOP_TIME and NEGATIVE_DWELL_TIME. This means that the SIRI data contains time traveling, which OTP of course rejects.
The rest is data where the fuzzy trip matcher could not identify the correct trip. We may be able to improve that but it will always remain a guessing game.
cc @rcavaliere
The text was updated successfully, but these errors were encountered: