-
Notifications
You must be signed in to change notification settings - Fork 24
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
What does continuous_pick_up or dropoff mean for flex zones? #70
Comments
cc @hannesj |
Hey Leonard. This data looks incorrect (it's one of our feeds, so thanks for flagging!)–it looks to be the result of maintaining this data on our backend to be compatible with both v1 and v2 exports, and something went awry along the way. This is supposed to be a deviating service that also has continuous stopping, but as you can see, it's only including the deviation zones (no fixed stops) and incorrectly using the continuous_pickup/drop_off fields, making continuous stopping moot. Instead, the data should read:
The reason we may include deviation zones and continuous stopping rules in the same trip is to be able to define different pickup and drop-off rules for each if the route offers both. For example, one may be able to wave the driver down to be picked up along the route (continuous_pickup=3) but must call the agency for a deviation away from the path-of-travel (pickup_type=2). |
Ok, should these fields then be conditionally forbidden or are these combinations valid? |
Hmm, I think we would want to conditionally forbid continuous pickup/drop-off for stop_times that refer to a locations.geojson or location_group. I can't think of any issues with that, since even including continuous pickup/drop-off for a line string would be redundant. |
Here is the old documentation: But I am wondering if continuous_pickup & continuous_drop_off is still part of the spec? |
It is part of the core GTFS standard now, so in that sense it is part of Flex. There is nothing that conflicts with Flex apart from needing to conditionally forbid continuous pickup/drop-off for locations.geojson/location_group(soon-to-be stop_areas.txt). |
When implementing Flex v2 support we noticed the following combination that we don't know how to interpret:
The feed available at http://oregon-gtfs.com/gtfs_data/lincolncounty-or-us/lincolncounty-or-us--flex-v2.zip contains the following stop_times for trip
t_299275_b_26748_tn_0
:Here we see that the stop_times has continuous_pickup and dropoff set to 2 and 3 respectively.
The GTFS-Static spec says about these fields:
Can someone explain how this is meant to be interpreted in the context of flex stops? Does it mean that the vehicle follows the shape or that it doesn't?
Or is this perhaps a remnant in the feed to stay compatible with consumers that implement it and show it as some sort of "quasi-flex"?
The text was updated successfully, but these errors were encountered: