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

Add stops.stop_access field #515

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

tzujenchanmbd
Copy link
Collaborator

@tzujenchanmbd tzujenchanmbd commented Nov 4, 2024

This PR adds a stop_access field in stops.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:

  • Whether routing riders to stops requires passing through designated entrances.
  • That the station-stop hierarchy may include stops not within the same physical structure

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.

@tzujenchanmbd
Copy link
Collaborator Author

What about adding the following clarification for stop_access = empty, per this suggestion:

When its parent station does not contain any entrances/exits (location_type=2), data consumers should consider this stop as not part of the main station structure or enclosed area.

@jfabi
Copy link
Contributor

jfabi commented Nov 12, 2024

What about adding the following clarification for stop_access = empty, per this suggestion:

When its parent station does not contain any entrances/exits (location_type=2), data consumers should consider this stop as not part of the main station structure or enclosed area.

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 stop_access.

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.

@eliasmbd eliasmbd added GTFS Schedule Issues and Pull Requests that focus on GTFS Schedule Status: Discussion Issues and Pull Requests that are currently being discussed and reviewed by the community. Change: Addition New function proposed to the specification. Support: Needs Feedback labels Nov 19, 2024
@miklcct
Copy link

miklcct commented Dec 6, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Change: Addition New function proposed to the specification. GTFS Schedule Issues and Pull Requests that focus on GTFS Schedule Status: Discussion Issues and Pull Requests that are currently being discussed and reviewed by the community. Support: Needs Feedback
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants