-
Notifications
You must be signed in to change notification settings - Fork 9
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
Critical problem with route_type. Bus and rail trips under one route #61
Comments
I thought the route took into account the mode, I'll check |
@tafflin please try again with release 6.4.1 |
@linusnorton hi, thanks for the quick update. |
@linusnorton |
Hi @linusnorton , |
I haven't had time to take a look. What TUID is causing the problem? |
train_uid=S12059 |
@tafflin this should be fixed in 6.4.2 |
@linusnorton thank you. I can see ~500 new routes and the situation with replacement buses looks solved. |
Hi,
I found a critical problem which has an impact on companies using atoc rail data to create shapes and in some other cases.
The problem is that the same route can have trips which belong to different route_types.
I looked throught the .MCA file provided by http:https://data.atoc.org and I can see that the trips of train category OO/XX (route_type=2) and BR (route_type=714) are linked to the same route which has a route_type=2. I checked the data by train_uid and retail_train_id.
The result of the issue is that in GTFS we get a mixed mode route.
Impact: Companies using such GTFS files to generate shapes will have problems trying to generate rail shapes for bus trips. The stop locations of such replacement bus stops are far off the rail tracks
The text was updated successfully, but these errors were encountered: