From 2076413c4f5feaf099f0f92bb48281ada509b838 Mon Sep 17 00:00:00 2001 From: Pascal Rhod Date: Thu, 7 Apr 2022 17:32:04 +0200 Subject: [PATCH] fix PR review --- daylight_saving.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/daylight_saving.md b/daylight_saving.md index dce9bd6..afbccff 100644 --- a/daylight_saving.md +++ b/daylight_saving.md @@ -3,25 +3,25 @@ NTFS Timezones and Daylight saving ## Handling time-zones -The `network_timezone` field in file networks.txt sets the time zone for all `stop_times` of `trips` of the `network`. +The `network_timezone` field in file networks.txt sets the time zone for all `stop_times` of a `trip` in the `network`. -If a feed covers multiple time zones, a specific time zone information can be specified on a `stop_point` outside the `network_timezone` in the `stop_timezone` field. Set this optional field in file `stops.txt` (for stops with location_type = 0). If not set, the timezone of the network is used. Ensure that trip travel times remain accurate and consistent by providing departure and arrival times based on the `network_timezone` for stops that are out of that timezone. +If a feed covers multiple time zones, a specific time zone information can be specified on a `stop_point` in the `stop_timezone` field. Set this optional field in file `stops.txt` (for stops with location_type = 0). If not set, the timezone of the network is used. Ensure that trip travel times remain accurate and consistent by providing departure and arrival times based on the `network_timezone` for stops that are out of that timezone. Navitia presents time for departure and arrival times in the local time zone of each stop. \ Warnings: - Time in `stop_times.txt` should always increase along a trip. -- NTFS uses the local timezone at noon of the travel day of the trip. This is the implementation of the constraint specified on the (GTFS Time data format)[http://gtfs.org/schedule/reference/#field-types]: +- NTFS uses the local timezone at noon of the travel day of the trip, following the same rule as (GTFS Time data format)[http://gtfs.org/schedule/reference/#field-types]: > Time in the HH:MM:SS format (H:MM:SS is also accepted). The time is measured from "noon minus 12h" of the service day (effectively midnight except for days on which daylight savings time changes occur). For times occurring after midnight, enter the time as a value greater than 24:00:00 in HH:MM:SS local time for the day on which the trip schedule begins. \ Example: 14:30:00 for 2:30PM or 25:35:00 for 1:35AM on the next day. ## Daylight Saving Time Some trips may operate during the switch from or to Daylight Saving time and then continue to operate as normal. The NTFS format uses the same way of dealing with daylight saving than [the GTFS does](https://support.google.com/transitpartners/answer/7074707). -It is strongly recommended to explicitly define trips operating across time changes (not using multiple day calendar). +It is recommended to avoid services on multiple days (see calendar.txt) for trips that cross time changes. -### First modelization (recommanded) +### First modelization (recommended) -Model the trip using the previous day as the point of reference in stop_times.txt. The departure stop_time may exceed 24h to indicate the time on the next day (for example 25:30 to indicate 01:30 before the changing time). +Model the trip using the previous day as the point of reference in `stop_times.txt`. The departure `stop_time` may exceed 24h to indicate the time on the next day (for example 25:30 to indicate 01:30 before the changing time). Make the departure times consistent with vehicle travel time. ### Second modelization @@ -39,9 +39,9 @@ A bus starts on October 2 at 1:50 AM the night the switch happens (for example, stop_sequence | Departure_times (1st model) | Departure_times (2nd model) | displayed departure time in Navitia --- | --- | --- | --- 1 | 25:50:00 (October 1) | 02:50:00 (October 2) | 01:50 AM (October 2) -2 | 26:10:00 (October 1) | 03:10:00 (October 2) | 03:10 AM (October 2) * -3 | 26:50:00 (October 1) | 03:50:00 (October 2) | 03:50 AM (October 2) -4 | 27:30:00 (October 1) | 04:30:00 (October 2) | 04:30 AM (October 2) +2 | 26:40:00 (October 1) | 03:40:00 (October 2) | 03:40 AM (October 2) * +3 | 27:20:00 (October 1) | 04:20:00 (October 2) | 04:20 AM (October 2) +4 | 27:50:00 (October 1) | 04:50:00 (October 2) | 04:50 AM (October 2) _\* Time starting here use the new time display_ @@ -52,8 +52,8 @@ A bus starts on October 2 at 1:50 AM the night the switch happens (for example, stop_sequence | Departure_times (1st model) | Departure_times (2nd model) | displayed departure time in Navitia --- | --- | --- | --- 1 | 25:50:00 (October 1) | 00:50:00 (October 2) | 01:50 AM (October 2) -2 | 26:10:00 (October 1) | 01:10:00 (October 2) | 02:10 AM (October 2) -3 | 26:50:00 (October 1) | 01:50:00 (October 2) | 01:50 AM (October 2) * -4 | 27:30:00 (October 1) | 02:30:00 (October 2) | 02:30 AM (October 2) +2 | 26:40:00 (October 1) | 01:40:00 (October 2) | 02:40 AM (October 2) +3 | 27:20:00 (October 1) | 02:20:00 (October 2) | 02:20 AM (October 2) * +4 | 27:50:00 (October 1) | 02:50:00 (October 2) | 02:50 AM (October 2) _\* Time starting here use the new time display_