[DRT] After the adoption of GTFS-Flex, stops.txt should no longer be a required file. #452
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
Context
Before the adoption of GTFS-Flex in PR#433,
stops.txt
was 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 throughlocations.geojson
(geometry: polygons) as well. In theory, an agency may exclusively offer zone-based demand-responsive services, in which case the feed may only containlocations.geojson
withoutstops.txt
.Proposed change
Therefore, we suggest changing the presence of
stops.txt
fromRequired
toConditionally required
(required iflocations.geojson
doesn't exist).GTFS validator behavior
Once the spec is modified, the GTFS validator can make corresponding adjustments, such as:
stops.txt
andlocations.geojson
exist - no errorstops.txt
orlocations.geojson
exists - no errorstops.txt
norlocations.geojson
exists - error (missing required file stops.txt)Please share any thoughts you have here. We plan to open a PR soon.
The text was updated successfully, but these errors were encountered: