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

Drop the requirement of no locked platforms in pathways.txt #517

Open
miklcct opened this issue Nov 5, 2024 · 2 comments
Open

Drop the requirement of no locked platforms in pathways.txt #517

miklcct opened this issue Nov 5, 2024 · 2 comments
Labels
Change: Clarification Revisions of the current specification to improve understanding. Extension: GTFS-Pathways Issues and Pull Requests that focus on GTFS-Pathways Extension 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

Comments

@miklcct
Copy link

miklcct commented Nov 5, 2024

Describe the problem

The specifications of pathways.txt mentions that,

No locked platforms: Each platform (location_type=0 or empty) or boarding area (location_type=4) must be connected to at least one entrance/exit (location_type=2) via some chain of pathways. Stations not allowing a pathway to the outside of the station from a given platform are rare.

The fact is that, there exist some stations where access to the outside world is prohibited. These stations are for interchange only. The most famous example in Hong Kong is called Shing Mun Tunnels Bus Interchange, which is an interchange-only station with no public access to outside the station.

Use cases

We need to define stations which are interchange only, i.e. no access to the outside world.

Proposed solution

Delete the quoted paragraph. Change the validator to produce a warning instead.

Additional information

No response

@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. Extension: GTFS-Pathways Issues and Pull Requests that focus on GTFS-Pathways Extension Change: Clarification Revisions of the current specification to improve understanding. Support: Needs Feedback labels Nov 5, 2024
@gcamp
Copy link
Contributor

gcamp commented Nov 6, 2024

I'm afraid of doing this because it's the error that we see the most often in pathways. Relaxing the requirement will just make things worst.

Even if the example that you provided is valid, the benefit of pathways in Shing Mun Tunnels Bus Interchange is marginal. What is your expectations, just walkways between platforms?

@miklcct
Copy link
Author

miklcct commented Nov 6, 2024

I'm afraid of doing this because it's the error that we see the most often in pathways. Relaxing the requirement will just make things worst.

Even if the example that you provided is valid, the benefit of pathways in Shing Mun Tunnels Bus Interchange is marginal. What is your expectations, just walkways between platforms?

Yes, walkway between platforms. The same situation happened in Prince Edward MTR station between 10 May 1982 and 16 May 1982, when the station was still under construction, with the interchange opening a week ahead before the street opening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Change: Clarification Revisions of the current specification to improve understanding. Extension: GTFS-Pathways Issues and Pull Requests that focus on GTFS-Pathways Extension 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

No branches or pull requests

3 participants