Skip to content
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

Problem with belgian train database #766

Closed
ZeCracotte opened this issue Jul 20, 2021 · 2 comments
Closed

Problem with belgian train database #766

ZeCracotte opened this issue Jul 20, 2021 · 2 comments
Labels
bug 🐞 A functional defect or unexpected behavior. coverage 🗺️ This is related to the geographic areas supported. upstream 🏞️ Related to an upstream issue.

Comments

@ZeCracotte
Copy link

Describe the bug
I think the SNCB/NMBS database (trains in Belgium) is not well interpreted : all train codes beginning with S (suburban trains) are not identified as train, so they don't appear in the route search. It's very problematic because a lot of trains in Belgium are S trains.

To Reproduce
Steps to reproduce the behavior:
Search the route Ottignies to Louvain-la-Neuve, you'll see the app will only propose buses.

Expected behavior
The app should propose trains, but it doesn't because all trains for this route are S trains, so they are not seen by the route search.
If you go and search departures in Ottignies station, the S trains appear.

Screenshots
Route search
Screenshot_20210720-030044_Transportr
Station search
Screenshot_20210720-030121_Transportr

Versions (please complete the following information):

  • Transportr Version: 2.1.2
  • Device: Asus Zenfone 3
  • Android Version: 9.0 (LineageOS 16.0)
@ZeCracotte ZeCracotte added the bug 🐞 A functional defect or unexpected behavior. label Jul 20, 2021
@ialokim ialokim added coverage 🗺️ This is related to the geographic areas supported. upstream 🏞️ Related to an upstream issue. labels Jul 24, 2021
@ialokim
Copy link
Collaborator

ialokim commented Jul 24, 2021

Thanks for your report, I was able to reproduce it here. This needs some further investigation but is most probably due to the internally used PTE library not interpreting the trains correctly.

@Altonss
Copy link
Collaborator

Altonss commented Dec 7, 2023

So quick update: we decided to disable SNCB/NMBS (#884) because this network isn't working anymore due to their API change, see #840 (comment).
I'll close the issue for now, and if SNCB/NMBS gets supported again in the future we could check if your issue is still there.

@Altonss Altonss closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐞 A functional defect or unexpected behavior. coverage 🗺️ This is related to the geographic areas supported. upstream 🏞️ Related to an upstream issue.
Projects
None yet
Development

No branches or pull requests

3 participants