Added a description of run_id field#1
Conversation
Added run_id field to both trips.txt and stop_times.txt
gtfs/spec/en/reference.md
Outdated
| | `shape_id` | ID referencing `shapes.shape_id` | Optional | Identifies a geospatial shape describing the vehicle travel path for a trip. | | ||
| | `wheelchair_accessible` | Enum | Optional | Indicates wheelchair accessibility. Valid options are:<br><br>`0` or empty - No accessibility information for the trip.<br>`1` - Vehicle being used on this particular trip can accommodate at least one rider in a wheelchair.<br>`2` - No riders in wheelchairs can be accommodated on this trip. | | ||
| | `bikes_allowed` | Enum | Optional | Indicates whether bikes are allowed. Valid options are:<br><br>`0` or empty - No bike information for the trip.<br>`1` - Vehicle being used on this particular trip can accommodate at least one bicycle.<br>`2` - No bicycles are allowed on this trip. | | ||
| | run_id | ID | Optional | Identifies the run to which the trip belongs. A run consists of a single trip or many sequential trips driven by the same driver, defined by shared service days and run_id. A run_id can have trips with different service days, making distinct runs. | |
There was a problem hiding this comment.
For consistency with the rest of the document, make sure that run_id is surrounded by `s, as in `run_id`. This formats the text using a mono-spaced font.
There was a problem hiding this comment.
Also add:
"Mid-trip driver changes are indicated in the stop_times.txt file."
Sassy-Tester
left a comment
There was a problem hiding this comment.
Added changes requested by Daniel James.
Add "Mid-trip driver changes are indicated in the stop_times.txt file.".
gtfs/spec/en/reference.md
Outdated
| | `shape_dist_traveled` | Non-negative float | Optional | Actual distance traveled along the associated shape, from the first stop to the stop specified in this record. This field specifies how much of the shape to draw between any two stops during a trip. Must be in the same units used in [shapes.txt](#shapestxt). Values used for `shape_dist_traveled` must increase along with `stop_sequence`; they cannot be used to show reverse travel along a route.<hr>*Example: If a bus travels a distance of 5.25 kilometers from the start of the shape to the stop,`shape_dist_traveled`=`5.25`.*| | ||
| | `timepoint` | Enum | Optional | Indicates if arrival and departure times for a stop are strictly adhered to by the vehicle or if they are instead approximate and/or interpolated times. This field allows a GTFS producer to provide interpolated stop-times, while indicating that the times are approximate. Valid options are:<br><br>`0` - Times are considered approximate.<br>`1` or empty - Times are considered exact. | | ||
|
|
||
| | `run_id` | ID | Optional | This value will take precedence over run_id that may be defined in trips.txt to indicate a change in drivers, such as is the case for a mid-trip relief. Mid-trip driver changes are indicated in the stop_times.txt file. | |
There was a problem hiding this comment.
"Mid-trip driver changes are indicated in the stop_times.txt file." should be moved to the description in trips.txt.
I put it in stop_times.txt instead of trips.txt.
Add "A run_id value specified for one stop_time does not apply to subsequent stop_times in the same trip. The run_id value must be repeated in each subsequent row for the remainder of the trip following a driver switch. If the entire trip is performed by a single driver, use the run_id in trips.txt instead."
gtfs/spec/en/reference.md
Outdated
| | `timepoint` | Enum | Optional | Indicates if arrival and departure times for a stop are strictly adhered to by the vehicle or if they are instead approximate and/or interpolated times. This field allows a GTFS producer to provide interpolated stop-times, while indicating that the times are approximate. Valid options are:<br><br>`0` - Times are considered approximate.<br>`1` or empty - Times are considered exact. | | ||
| | `run_id` | ID | Optional | This value will take precedence over run_id that may be defined in trips.txt to indicate a change in drivers, such as is the case for a mid-trip relief. Mid-trip driver changes are indicated in the stop_times.txt file. | | ||
| | `run_id` | ID | Optional | This value will take precedence over run_id that may be defined in trips.txt to indicate a change in drivers, such as is the case for a mid-trip relief. A run_id value specified for one stop_time does not apply to subsequent stop_times in the same trip. The run_id value must be repeated in each subsequent row for the remainder of the trip following a driver switch. | ||
| If the entire trip is performed by a single driver, use the run_id in trips.txt instead.| |
There was a problem hiding this comment.
Because of the way Markdown works, this needs to be on the line above. Use <br><br> to add the appropriate line breaks in the text.
i.e., …following a driver switch.<br><br>If the entire trip is…
Added run_id field to both trips.txt and stop_times.txt