-
Notifications
You must be signed in to change notification settings - Fork 183
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
Add stops.stop_access field #515
base: master
Are you sure you want to change the base?
Conversation
What about adding the following clarification for When its parent station does not contain any entrances/exits ( |
Do we have a good sense about how frequently producers include entrances for their parent stations? Even for us at the MBTA, we include them (and pathways) in full for our metro stations, but for the most part have not added them for our many regional rail parent stations. I'm not sure that the exclusion of station entrances, at this time, can imply one behavior or the other—after all, this ambiguity about the definition of a parent station is part of the rational for Of course, consumers will (and already do) have to make assumptions in those cases—from a survey in our market, it looks like OTP and the major commercial apps are mixed in whether they route involving entrance-less stations to the parent or the child. |
How do you deal with the situation where a platform can either be accessed directly from the street, and also through the station building? Your proposed changes to pathways will prohibit such usages from happening. |
This PR adds a
stop_access
field instops.txt
to indicate how the stop is accessed for a particular station. Please refer to this proposal for details.We expect this field to clarify the following:
Adding this field is also the first phase of our three-phase plan to improve station modeling. For details on previous discussions, please refer to issue #438.