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

Small update of the spec for joining or splitting trips #13

Open
pietercolpaert opened this issue Nov 16, 2018 · 4 comments
Open

Small update of the spec for joining or splitting trips #13

pietercolpaert opened this issue Nov 16, 2018 · 4 comments
Assignees
Labels
backlog This requires fixing at some point, but not right now.

Comments

@pietercolpaert
Copy link
Member

openplannerteam/planner.js#18

Not yet in a public knowledge graph, yet know that the spec slightly updated to be able to support this use case!

@xivk
Copy link
Contributor

xivk commented Feb 14, 2019

@pietervdvn Has this been taken into account? Can we close this or not?

@xivk xivk assigned xivk and pietervdvn and unassigned xivk Feb 14, 2019
@pietercolpaert
Copy link
Member Author

No test data available yet for this

@xivk xivk added the backlog This requires fixing at some point, but not right now. label Feb 14, 2019
@pietervdvn
Copy link
Contributor

No, I haven't taken this into account, because I'm not convinced of the spec.

If two Desiro-Trains are linked together, it is not possible to walk from the front to the end - see picture. So, consider the following situation:

  • Train A departs in ADep
  • Train B departs in BDep
  • They merge in some location
  • They split in some later location
  • Train A continues till AArr
  • Train B continues till BArr

A traveller which goes from ADep till BArr will have to leave the train at some location to mount the other train. In other words, I'd model these trains as two completely seperate trips, which coincidentally are on the same places at the same times for a part of the track.

@pietercolpaert
Copy link
Member Author

pietercolpaert commented Feb 15, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog This requires fixing at some point, but not right now.
Projects
None yet
Development

No branches or pull requests

3 participants