"Request Stops" proposal (continuous_stops)

161 views
Skip to first unread message

Aaron Antrim

unread,
Mar 3, 2015, 11:54:32 PM3/3/15
to gtfs-fle...@googlegroups.com
I would like to offer a very late response to Brian's proposal for representing "Flexible Transportation Services in GTFS" (https://docs.google.com/document/d/1UTcpMJlANSoJ1ZEk5IrQh_plza1ZnvgwraMEBI_o2mw/edit?usp=sharing).

The proposal suggests indicating request stops (aka flag stops) by a new "continuous_stops" field in stop_times.txt. I'd like to request for the proposal to be amended to account for other attributes of request stop service, for example:
  • Request stops that can only be requested from on-board the vehicle
  • Request pickup that must be requested in advance (by phone)
To account for this, I suggest is to borrow from the existing pickup_type and dropoff_type fields. Here are two approach options:
  1. Split continuous_stops into two fields: continuous_stops_drop_off and continuous_stops_pickup. Values of digits 0-3 would indicate the same meaning as for the existing drop_off_type and pickup_type fields (https://developers.google.com/transit/gtfs/reference#stop_times_fields).
  2. Just add one field, continuous_stops, but define additional possible values. e.g. "32" indicates the passenger must request drop-off from the driver and that one must phone the agency for pickup. "31" indicates the passenger must coordinate with the driver for drop-off but that there is no pickup available.
Thoughts?

If we settle on a viable proposal, and if a GTFS-consuming application comes forward with interest, I will volunteer to publish and iterate on experimental GTFS data that describes request stop services. Is anyone interested?

Here are some examples of how flag stop policies are presented by agencies:
  • RCT/Rural Community Transportation (in Vermont) -- phrasing is "ON-BOARD REQUEST: Passengers may request stop along the service route in low speed zones at safelocations, such as the Health Center in Plainfield." (http://www.riderct.org/wp-content/uploads/2014/08/US2-route.pdf)
  • RCT/Redwood Coast Transit (Del Norte County, California) - "In addition to the stops shown on this schedule, RCTA will make flag stops on request at any safe location as determined by the driver. Passengers desiring flag stops are encouraged to call RCTA at (707) 464-6400 to determine the best place to wait." (http://www.redwoodcoasttransit.org/route20.html) 
-- 
Aaron Antrim
Trillium Solutions, Inc.
www.trilliumtransit.com
Portland, Oregon

Aaron Antrim

unread,
May 4, 2015, 1:55:02 AM5/4/15
to gtfs-fle...@googlegroups.com, Holly Krambeck
GTFS flexible working group:

I am posting a message to bring up flag (request) stops again. We (Trillium) are working with an increasing number of agencies that offer hail-and-ride style service.

In order to move this along, I would like to propose changes to the "Flexible Transportation Services in GTFS Proposal". Does anyone have preferences for, or alternatives to the earlier ideas for fields to add to stop_times (below)?
  • Split continuous_stops into two fields: continuous_stops_drop_off and continuous_stops_pickup. Values of digits 0-3 would indicate the same meaning as for the existing drop_off_type and pickup_type fields (https://developers.google.com/transit/gtfs/reference#stop_times_fields).
  • Just add one field, continuous_stops, but define additional possible values. e.g. "32" indicates the passenger must request drop-off from the driver and that one must phone the agency for pickup. "31" indicates the passenger must coordinate with the driver for drop-off but that there is no pickup available.

Ross Peterson

unread,
Jun 9, 2015, 5:21:24 PM6/9/15
to gtfs-fle...@googlegroups.com, hkra...@gmail.com
I am +1 for Aaron's proposal... with the caveat that the entire proposal still needs to be tested and until that happens all of this is academic... but yes, what you are proposing makes sense.

Aaron Antrim

unread,
Jun 11, 2015, 3:59:10 PM6/11/15
to Ross Peterson, gtfs-fle...@googlegroups.com, Holly Krambeck
Juste a heads up that this discussion continued over on the main gtfs-changes list:

Mike Gilligan had another idea, that I prefer over the options that I proposed.

--
You received this message because you are subscribed to the Google Groups "GTFS Flexible Transit Working Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gtfs-flexible-...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages