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

[DRT] After the adoption of GTFS-Flex, stops.txt should no longer be a required file. #452

Closed
tzujenchanmbd opened this issue May 14, 2024 · 1 comment · Fixed by #472
Closed
Labels
Change: Clarification Revisions of the current specification to improve understanding. 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

@tzujenchanmbd
Copy link
Collaborator

tzujenchanmbd commented May 14, 2024

Context

Before the adoption of GTFS-Flex in PR#433, stops.txtwas the sole file in GTFS defining the geographic locations (geometry: points) where riders board and alight. However, after its adoption, producers can define riders boarding and alighting geographic areas through locations.geojson (geometry: polygons) as well. In theory, an agency may exclusively offer zone-based demand-responsive services, in which case the feed may only contain locations.geojson without stops.txt.

Proposed change

Therefore, we suggest changing the presence of stops.txt from Required to Conditionally required (required if locations.geojson doesn't exist).

GTFS validator behavior

Once the spec is modified, the GTFS validator can make corresponding adjustments, such as:

  • Both stops.txt and locations.geojson exist - no error
  • Either stops.txt or locations.geojson exists - no error
  • Neither stops.txt nor locations.geojson exists - error (missing required file stops.txt)

Please share any thoughts you have here. We plan to open a PR soon.

@tzujenchanmbd tzujenchanmbd changed the title [DRT] After the adoption of GTFS-Flex, stops.txt seems no longer be a required file. [DRT] After the adoption of GTFS-Flex, stops.txt should no longer be a required file. May 14, 2024
@tzujenchanmbd tzujenchanmbd 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: Clarification Revisions of the current specification to improve understanding. Support: Needs Feedback labels May 14, 2024
@LeoFrachet
Copy link
Contributor

I support taking a decision in short term on that, since a few of us are currently working on GTFS-Flex implementation.

I'm leaning toward making it optional, but if people have strong opinions against that, let us know.

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. 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 a pull request may close this issue.

2 participants