From 62c2c789d3385018ace8ee62ac87b1c1a827c63d Mon Sep 17 00:00:00 2001 From: Sassy-Tester Date: Mon, 2 Dec 2019 14:34:12 -0800 Subject: [PATCH 1/7] Added a description of run_id field Added run_id field to both trips.txt and stop_times.txt --- gtfs/spec/en/reference.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gtfs/spec/en/reference.md b/gtfs/spec/en/reference.md index 531135830..390389e17 100644 --- a/gtfs/spec/en/reference.md +++ b/gtfs/spec/en/reference.md @@ -171,6 +171,7 @@ File: **Required** | `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:

`0` or empty - No accessibility information for the trip.
`1` - Vehicle being used on this particular trip can accommodate at least one rider in a wheelchair.
`2` - No riders in wheelchairs can be accommodated on this trip. | | `bikes_allowed` | Enum | Optional | Indicates whether bikes are allowed. Valid options are:

`0` or empty - No bike information for the trip.
`1` - Vehicle being used on this particular trip can accommodate at least one bicycle.
`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. | #### Example: Blocks and service day @@ -205,7 +206,7 @@ File: **Required** | `drop_off_type` | Enum | Optional | Indicates drop off method. Valid options are:

`0` or empty - Regularly scheduled drop off.
`1` - No drop off available.
`2` - Must phone agency to arrange drop off.
`3` - Must coordinate with driver to arrange drop off. | | `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.
*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:

`0` - Times are considered approximate.
`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. ### calendar.txt From 289c76bf4973f23896ad016504d741a76217415f Mon Sep 17 00:00:00 2001 From: Sassy-Tester Date: Mon, 2 Dec 2019 14:57:07 -0800 Subject: [PATCH 2/7] Added changes suggested by Daniel James --- gtfs/spec/en/reference.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gtfs/spec/en/reference.md b/gtfs/spec/en/reference.md index 390389e17..4d4cd025d 100644 --- a/gtfs/spec/en/reference.md +++ b/gtfs/spec/en/reference.md @@ -171,7 +171,7 @@ File: **Required** | `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:

`0` or empty - No accessibility information for the trip.
`1` - Vehicle being used on this particular trip can accommodate at least one rider in a wheelchair.
`2` - No riders in wheelchairs can be accommodated on this trip. | | `bikes_allowed` | Enum | Optional | Indicates whether bikes are allowed. Valid options are:

`0` or empty - No bike information for the trip.
`1` - Vehicle being used on this particular trip can accommodate at least one bicycle.
`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. | +| `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. | #### Example: Blocks and service day @@ -206,7 +206,7 @@ File: **Required** | `drop_off_type` | Enum | Optional | Indicates drop off method. Valid options are:

`0` or empty - Regularly scheduled drop off.
`1` - No drop off available.
`2` - Must phone agency to arrange drop off.
`3` - Must coordinate with driver to arrange drop off. | | `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.
*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:

`0` - Times are considered approximate.
`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. +| `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. | ### calendar.txt From edd47e98ec16edcd4cefa699e098be007d9b751a Mon Sep 17 00:00:00 2001 From: Sassy-Tester Date: Tue, 3 Dec 2019 13:13:30 -0800 Subject: [PATCH 3/7] Adding Steve's request Add "Mid-trip driver changes are indicated in the stop_times.txt file.". --- gtfs/spec/en/reference.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gtfs/spec/en/reference.md b/gtfs/spec/en/reference.md index 4d4cd025d..aa09535e5 100644 --- a/gtfs/spec/en/reference.md +++ b/gtfs/spec/en/reference.md @@ -206,7 +206,7 @@ File: **Required** | `drop_off_type` | Enum | Optional | Indicates drop off method. Valid options are:

`0` or empty - Regularly scheduled drop off.
`1` - No drop off available.
`2` - Must phone agency to arrange drop off.
`3` - Must coordinate with driver to arrange drop off. | | `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.
*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:

`0` - Times are considered approximate.
`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. | +| `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. | ### calendar.txt From c8cd7fcd9fb85a1d21e5ad9fa172b7fa8be76314 Mon Sep 17 00:00:00 2001 From: Sassy-Tester Date: Tue, 3 Dec 2019 13:51:47 -0800 Subject: [PATCH 4/7] Put Steve's suggestion in the correct place. I put it in stop_times.txt instead of trips.txt. --- gtfs/spec/en/reference.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gtfs/spec/en/reference.md b/gtfs/spec/en/reference.md index aa09535e5..239e5491c 100644 --- a/gtfs/spec/en/reference.md +++ b/gtfs/spec/en/reference.md @@ -171,7 +171,7 @@ File: **Required** | `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:

`0` or empty - No accessibility information for the trip.
`1` - Vehicle being used on this particular trip can accommodate at least one rider in a wheelchair.
`2` - No riders in wheelchairs can be accommodated on this trip. | | `bikes_allowed` | Enum | Optional | Indicates whether bikes are allowed. Valid options are:

`0` or empty - No bike information for the trip.
`1` - Vehicle being used on this particular trip can accommodate at least one bicycle.
`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. | +| `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. Mid-trip driver changes are indicated in the stop_times.txt file. | #### Example: Blocks and service day @@ -206,7 +206,7 @@ File: **Required** | `drop_off_type` | Enum | Optional | Indicates drop off method. Valid options are:

`0` or empty - Regularly scheduled drop off.
`1` - No drop off available.
`2` - Must phone agency to arrange drop off.
`3` - Must coordinate with driver to arrange drop off. | | `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.
*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:

`0` - Times are considered approximate.
`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. | ### calendar.txt From b5d7fca8c14a986af9534e5f42552d8e5dca0a61 Mon Sep 17 00:00:00 2001 From: Sassy-Tester Date: Tue, 3 Dec 2019 15:20:09 -0800 Subject: [PATCH 5/7] Second round of changes 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 | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gtfs/spec/en/reference.md b/gtfs/spec/en/reference.md index 239e5491c..2f4967ded 100644 --- a/gtfs/spec/en/reference.md +++ b/gtfs/spec/en/reference.md @@ -206,7 +206,8 @@ File: **Required** | `drop_off_type` | Enum | Optional | Indicates drop off method. Valid options are:

`0` or empty - Regularly scheduled drop off.
`1` - No drop off available.
`2` - Must phone agency to arrange drop off.
`3` - Must coordinate with driver to arrange drop off. | | `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.
*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:

`0` - Times are considered approximate.
`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. | +| `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.| ### calendar.txt From 3af4fba02033a45a23fa303cb70b62ce504c4694 Mon Sep 17 00:00:00 2001 From: Sassy-Tester Date: Thu, 5 Dec 2019 11:59:37 -0800 Subject: [PATCH 6/7] Made last round of changes suggested by Steve and Daniel. --- gtfs/spec/en/reference.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/gtfs/spec/en/reference.md b/gtfs/spec/en/reference.md index 2f4967ded..65f77a978 100644 --- a/gtfs/spec/en/reference.md +++ b/gtfs/spec/en/reference.md @@ -171,7 +171,7 @@ File: **Required** | `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:

`0` or empty - No accessibility information for the trip.
`1` - Vehicle being used on this particular trip can accommodate at least one rider in a wheelchair.
`2` - No riders in wheelchairs can be accommodated on this trip. | | `bikes_allowed` | Enum | Optional | Indicates whether bikes are allowed. Valid options are:

`0` or empty - No bike information for the trip.
`1` - Vehicle being used on this particular trip can accommodate at least one bicycle.
`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. Mid-trip driver changes are indicated in the stop_times.txt file. | +| `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. Mid-trip driver changes are indicated in the `stop_times.txt` file. | #### Example: Blocks and service day @@ -206,8 +206,7 @@ File: **Required** | `drop_off_type` | Enum | Optional | Indicates drop off method. Valid options are:

`0` or empty - Regularly scheduled drop off.
`1` - No drop off available.
`2` - Must phone agency to arrange drop off.
`3` - Must coordinate with driver to arrange drop off. | | `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.
*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:

`0` - Times are considered approximate.
`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. 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.| +| `run_id` | ID | Optional | This value overrides the default `trips.run_id` 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_time`s 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.| ### calendar.txt From 47d43ecc6a5144fb0ce8c28c9960cdf2d674311b Mon Sep 17 00:00:00 2001 From: Sassy-Tester Date: Fri, 6 Dec 2019 16:12:57 -0800 Subject: [PATCH 7/7] Another round of changes. --- gtfs/spec/en/reference.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gtfs/spec/en/reference.md b/gtfs/spec/en/reference.md index 65f77a978..fa63df210 100644 --- a/gtfs/spec/en/reference.md +++ b/gtfs/spec/en/reference.md @@ -171,7 +171,7 @@ File: **Required** | `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:

`0` or empty - No accessibility information for the trip.
`1` - Vehicle being used on this particular trip can accommodate at least one rider in a wheelchair.
`2` - No riders in wheelchairs can be accommodated on this trip. | | `bikes_allowed` | Enum | Optional | Indicates whether bikes are allowed. Valid options are:

`0` or empty - No bike information for the trip.
`1` - Vehicle being used on this particular trip can accommodate at least one bicycle.
`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. Mid-trip driver changes are indicated in the `stop_times.txt` file. | +| `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. Mid-trip driver changes are indicated with `stop_times.run_id`. | #### Example: Blocks and service day @@ -206,7 +206,7 @@ File: **Required** | `drop_off_type` | Enum | Optional | Indicates drop off method. Valid options are:

`0` or empty - Regularly scheduled drop off.
`1` - No drop off available.
`2` - Must phone agency to arrange drop off.
`3` - Must coordinate with driver to arrange drop off. | | `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.
*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:

`0` - Times are considered approximate.
`1` or empty - Times are considered exact. | -| `run_id` | ID | Optional | This value overrides the default `trips.run_id` 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_time`s 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.| +| `run_id` | ID | Optional | This value overrides the default `trips.run_id` 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_time`s 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 `trips.run_id`. | ### calendar.txt