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.
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 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.geojsonwithoutstops.txt.Proposed change
Therefore, we suggest changing the presence of
stops.txtfromRequiredtoConditionally required(required iflocations.geojsondoesn't exist).GTFS validator behavior
Once the spec is modified, the GTFS validator can make corresponding adjustments, such as:
stops.txtandlocations.geojsonexist - no errorstops.txtorlocations.geojsonexists - no errorstops.txtnorlocations.geojsonexists - error (missing required file stops.txt)Please share any thoughts you have here. We plan to open a PR soon.