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

"-U" stop activity flag seem to be incorrectly matched as "U " for non-public stop #25

Closed
mk-fg opened this issue Sep 10, 2017 · 1 comment

Comments

@mk-fg
Copy link
Contributor

mk-fg commented Sep 10, 2017

One of the schedules for G80225 has this sequence of stops in raw CIF file:

BSNG802251709031709100000001 PXX1A850252123540003 DMUE   100      B S T        O
...
LIERROLLC           1258 00000000                     1
LIDUNDCJ            1306H00000000
CRDUNDETB XX1A850252123540003 DMUE   090      B S T                SR025200
LIDUNDETB 1307H1311H     000000004        K -U
LICMPRDNJ           1314 00000000
...

Here "LIDUNDETB" is a location=DUNDETB crs=DEE stop, with 0000 for public stop times and "K -U" for activity flags, which gets translated to this GTFS trip:

  [81568] headsign=G80225 svc=275 svc_days=2:
    <TS ......7 [2017-09-03 2017-09-10] {}>
    stop sequence:
      GLQ 11:45 11:45 P-
      STG 12:11 12:11 PD
      DBL 12:17 12:18 PD
      GLE 12:29 12:29 PD
      PTH 12:45 12:46 PD
      DEE 13:07 13:11 P-
      ARB 13:28 13:28 PD
      ...

More info (this train has a lot of non-public stops):
https://gist.github.com/mk-fg/1659e402c7b98fead612a497c07a0e52

DEE 13:07 13:11 P- ("P-" = "pickup only") seem to be derived from scheduled times, with pickup-only matched from "-U" ("stops to attach vehicles") as "U " ("take up passengers"), which are different activity flags.

This GTFS trip for this train_uid should not have "DEE" stop at all, as it doesn't have neither passenger pickup nor dropoff.

@mk-fg
Copy link
Contributor Author

mk-fg commented Sep 10, 2017

sequence of stops in raw CIF file:

Additional note:
Everything seem to be parsed correctly from CIF to mysql, as also shown on the linked gist, only used raw CIF here because I was lazy to make mysql query for this case :)

linusnorton added a commit that referenced this issue Sep 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants