From ecbdc5b0d40dfc0faeabeba90d59636f410a86d8 Mon Sep 17 00:00:00 2001 From: Tom Date: Tue, 2 May 2017 23:20:47 -0700 Subject: [PATCH 1/4] Update reference.md --- 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 6bfd0884b..866b660c7 100644 --- a/gtfs/spec/en/reference.md +++ b/gtfs/spec/en/reference.md @@ -174,6 +174,7 @@ File: **Required** | bikes_allowed | Optional | 0 (or empty) - indicates that there is no bike information for the trip | | | | * **1** - indicates that the vehicle being used on this particular trip can accommodate at least one bicycle | | | | * **2** - indicates that no bicycles are allowed on this trip | +| vehicle_id | Optional | The **vehicle_id** field contains an ID of the vehicle used for the trip | #### Example showing blocks and service day @@ -426,4 +427,4 @@ The file contains information about the feed itself, rather than the services th | feed_lang | Required | The **feed_lang** field contains a IETF BCP 47 language code specifying the default language used for the text in this feed. This setting helps GTFS consumers choose capitalization rules and other language-specific settings for the feed. For an introduction to IETF BCP 47, please refer to http://www.rfc-editor.org/rfc/bcp/bcp47.txt and http://www.w3.org/International/articles/language-tags/. | | feed_start_date | Optional | The feed provides complete and reliable schedule information for service in the period from the beginning of the **feed_start_date** day to the end of the **feed_end_date** day. Both days are given as dates in YYYYMMDD format as for [calendar.txt](#calendartxt), or left empty if unavailable. The **feed_end_date** date must not precede the **feed_start_date** date if both are given. Feed providers are encouraged to give schedule data outside this period to advise of likely future service, but feed consumers should treat it mindful of its non-authoritative status. If **feed_start_date** or **feed_end_date** extend beyond the active calendar dates defined in [calendar.txt](#calendartxt) and [calendar_dates.txt](#calendar_datestxt), the feed is making an explicit assertion that there is no service for dates within the **feed_start_date** or **feed_end_date** range but not included in the active calendar dates. | | feed_end_date | Optional | (see above) | -| feed_version | Optional | The feed publisher can specify a string here that indicates the current version of their GTFS feed. GTFS-consuming applications can display this value to help feed publishers determine whether the latest version of their feed has been incorporated. | \ No newline at end of file +| feed_version | Optional | The feed publisher can specify a string here that indicates the current version of their GTFS feed. GTFS-consuming applications can display this value to help feed publishers determine whether the latest version of their feed has been incorporated. | From 5cc8429bf625dd5a1839674a05d365921c937ff6 Mon Sep 17 00:00:00 2001 From: Tom Date: Wed, 3 May 2017 23:26:47 -0700 Subject: [PATCH 2/4] Update reference.md --- gtfs/spec/en/reference.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/gtfs/spec/en/reference.md b/gtfs/spec/en/reference.md index 866b660c7..96d6385cc 100644 --- a/gtfs/spec/en/reference.md +++ b/gtfs/spec/en/reference.md @@ -174,7 +174,6 @@ File: **Required** | bikes_allowed | Optional | 0 (or empty) - indicates that there is no bike information for the trip | | | | * **1** - indicates that the vehicle being used on this particular trip can accommodate at least one bicycle | | | | * **2** - indicates that no bicycles are allowed on this trip | -| vehicle_id | Optional | The **vehicle_id** field contains an ID of the vehicle used for the trip | #### Example showing blocks and service day @@ -234,7 +233,7 @@ File: **Required** | | | * **0** - Times are considered approximate. | | | | | * **1** - Times are considered exact. | | | | | For stop-time entries without specified arrival and departure times, feed consumers must interpolate arrival and departure times. Feed producers may optionally indicate that such an entry is not a timepoint (value=0) but it is an error to mark a entry as a timepoint (value=1) without specifying arrival and departure times. | | - +| vehicle_id | Optional | The **vehicle_id** field contains an ID of the vehicle used for the trip | ### calendar.txt File: **Required** From f737f8af34719130ce7096d705614483d1691965 Mon Sep 17 00:00:00 2001 From: Tom Date: Wed, 3 May 2017 23:43:33 -0700 Subject: [PATCH 3/4] Update reference.md --- 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 96d6385cc..0dd3f21f2 100644 --- a/gtfs/spec/en/reference.md +++ b/gtfs/spec/en/reference.md @@ -233,7 +233,8 @@ File: **Required** | | | * **0** - Times are considered approximate. | | | | | * **1** - Times are considered exact. | | | | | For stop-time entries without specified arrival and departure times, feed consumers must interpolate arrival and departure times. Feed producers may optionally indicate that such an entry is not a timepoint (value=0) but it is an error to mark a entry as a timepoint (value=1) without specifying arrival and departure times. | | -| vehicle_id | Optional | The **vehicle_id** field contains an ID of the vehicle used for the trip | +| vehicle_id | Optional | The **vehicle_id** field contains an ID that identifies a vehicle or set of vehicles on a trip.| + ### calendar.txt File: **Required** From 6a9520198b0585a089d43bc3cb42415596808dcd Mon Sep 17 00:00:00 2001 From: Tom Date: Thu, 4 May 2017 01:30:27 -0700 Subject: [PATCH 4/4] Update reference.md --- 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 0dd3f21f2..68a6b7fe1 100644 --- a/gtfs/spec/en/reference.md +++ b/gtfs/spec/en/reference.md @@ -174,6 +174,7 @@ File: **Required** | bikes_allowed | Optional | 0 (or empty) - indicates that there is no bike information for the trip | | | | * **1** - indicates that the vehicle being used on this particular trip can accommodate at least one bicycle | | | | * **2** - indicates that no bicycles are allowed on this trip | +| vehicle_id | Optional | The **vehicle_id** field contains an ID that identifies a vehicle or set of vehicles on a trip.| #### Example showing blocks and service day @@ -233,7 +234,6 @@ File: **Required** | | | * **0** - Times are considered approximate. | | | | | * **1** - Times are considered exact. | | | | | For stop-time entries without specified arrival and departure times, feed consumers must interpolate arrival and departure times. Feed producers may optionally indicate that such an entry is not a timepoint (value=0) but it is an error to mark a entry as a timepoint (value=1) without specifying arrival and departure times. | | -| vehicle_id | Optional | The **vehicle_id** field contains an ID that identifies a vehicle or set of vehicles on a trip.| ### calendar.txt