Based on the discussion around Metro North's real-time feed, I would
like to formally propose the addition of the "direction_id" field to
the TripDescriptor definition:
Field Name: direction_id
Type: uint32? bool? (open to suggestions here)
Cardinality: optional
Description: The direction_id from the GTFS that this selector
refers to.
The
direction_id field contains a binary value
that indicates the direction of travel for a trip. Use this field to
distinguish between bi-directional trips with the same route_id.
This field is not used in routing; it provides a way to separate
trips by direction when publishing time tables.
- 0 - travel in one direction (e.g. outbound
travel)
- 1 - travel in the opposite direction (e.g.
inbound travel)
The proposed initial GTFS-realtime producer is Metro North Railroad
(to be added to their real-time feed).
The proposed initial consumer is Roadify (to test the change).
This is an official request for comments on the proposed change.
Thanks for your consideration!
-ethan