`start/end_pickup_dropoff_window` should be be allowed for regular stop

MobilityData / gtfs-flex

NOTICE: GTFS-Flex has been merged to GTFS. This repo is no longer up-to-date and will deprecated. Consult the google/transit repo for the up-to-date info.

https://github.com/google/transit

Apache License 2.0

119 stars 24 forks source link

`start/end_pickup_dropoff_window` should be be allowed for regular stop #52

Closed gcamp closed 3 years ago

gcamp commented 3 years ago

Is there a reason that start_pickup_dropoff_window is only allowed for locations of locations.geojson? To me it seems useful to have flexible service that have fixed stop.

westontrillium commented 3 years ago

+1 Would be interested in hearing the justification for this.

A current workaround, however is to use a location_group for the stop_times.stop_id entry with a single stop_id. This bypasses the limitation.

tsherlockcraig commented 3 years ago

I agree. So, suggested changes:

change "Time that on-demand service becomes available in a GeoJSON location, location group, or at a stop."
instead of forbidden when there's a stop_id, maybe it should be forbidden if there is a arrival_time and departure_time.

Does that sound right?

gcamp commented 3 years ago

PR open! https://github.com/MobilityData/gtfs-flex/pull/55