It doesn't solve the problem though, the journey planners shown all have departure time, arrival time and duration. If the schedules skipped an hour the duration would be wrong. It would also break existing journey planners as they assume the whole schedule runs in the time zone of the start time and adjust the display times for clock changes. Any trains on the skipped hour run an hour later. Adjusting the schedule times is more problematic when the clocks go back as there are two 0100 to 0200 hours one in each time zone so journey planners would need enhancement to avoid offering invalid connections.
The error in the journey planners looks to be applying both directions of clock change on the same day. The 0:11 GMT to 2:06 BST 55 mins South Western Railway and 2:21 BST to 2:26 BST 5 mins Thameslink have both been forwarded the hour correctly. When the time passes 2:00 GMT/3:00 BST the times are incorrectly showing as an hour earlier. The Thameslink one shows the clock change icon indicating the duration is different due to a clock change, but there shouldn't have been one for this journey.
The industry practice in scheduled airlines is to always display the local time as applicable to the calling point. I see no reason why this can't be adopted in railways. For comparison, in Russia, the past practice was to publish only Moscow time for long-distance trains, but local time in suburban trains, but since 2018 it has also moved to local time in line with airlines as well.
By adopting this practice, it will not be wrong to "skip the hour" when showing trains running through the time change (e.g. 00:52 St Pancras, then 02:02 Blackfriars). It will also not be wrong when the clock goes back as it's obvious from the schedule, unless the train in question runs wholly within the repeated hour.
The reason why journey planner forwards the hour is that, in the standard date / time library in UNIX systems, when we enter times between 2022-03-27 01:20 in Europe/London time zone, it will be translated to 01:20 UTC if it is handled as a time stamp, where it is represented as a simple integer internally as the number of seconds from 1970-01-01 00:00:00 UTC, excluding leap seconds. And when it is displayed back to the user, the UTC time falls into British Summer Time in Europe/London, so it shows 02:20.
If you want longer summer evenings then go to work earlier.
This is my point as well. I actually prefer office hours starting at 08:00 and ending at 16:00 while staying at GMT year round. Office hour ending at 17:00 or even 17:30 is a waste of daylight in winter.
Agreed; it's a real problem.
Not a major problem at this time of year but it is much more problematic in the Autumn.
Those who claim the railway should do nothing are not thinking about this from a customer service point of view; furthermore, how do these people explain that some services did have alterations?
It is less problematic in autumn in my view, as trains can simply stop at a station for the hour when the clock repeats.
And as someone has brought office hours into the discussion, let's take Xinjiang as an example. All of China currently runs on a single time zone at UTC+8 although it geographically spans across UTC+5 to UTC+9. The fact that the whole country runs on a single time zone massively simplifies scheduling, unlike in the USA where television channels are separated. Xinjiang is physically located in UTC+6 and, "officially", times are in the national time (Beijing time), and all public transport schedule is shown only in the official time. However, there is also an "unofficial" time zone UTC+6 in use, called Xinjiang time or Ürümqi time, used almost exclusively within the Uyghurs where few Hans know its existence. In general Hans use Beijing time and Uyghurs use Xinjiang time, and the television channels reflect this usage by scheduling the Chinese channel in Beijing time and Uyghur and Kazakh channels in Xinjiang time. Therefore in cross-cultural communication the time zone has to be specified to prevent ambiguity. In Xinjiang summer, sun doesn't set before 22:00 (Beijing time), while in Shenzhen and Shanghai, it's already completely dark in late night.
And on top of that,
the government office hours also change by season:
- summer office hours: 09:30 - 13:30 / 16:00 - 20:00 Beijing Time
- winter office hours: 10:00 - 14:00 / 15:30 - 19:30 Beijing Time
i.e. the lunch break is an hour longer in summer compared to winter. And while most Chinese in the "mainland" works 8-17, those in Xinjiang works 10-19 instead even if they observe Beijing time to compensate for the solar time difference. As the national news is broadcast in at 19:00, the "prime time" in "mainland" China, people in Xinjiang think that the news is broadcasted so early (19:00 is the "evening commute" hour there when people normally just leave work, comparable to 17:00 in "mainland" China), and local channels will repeat the news recording again later in the evening.
It is actually comparable, where the summer time there is also 2 hours ahead of solar time, with a long lunch break as well. So it's always solar time to decide the work pattern in a community, and when noon isn't 12:00 people will compensate for it, as Xinjiang shows us.
If we, the UK, moves to GMT all year round, people may compensate for making the office hour 8 - 16 in summer, and 9 - 17 in the winter, and government offices, schools, and railways may standardise the "schedule change" to be at Easter holiday and October half-term. In such case the benefit of summer evening can be retained with minimal disruption while removing the complicated planning work needed for clock change (as in this case it is just simply a winter - summer or summer - winter timetable transition planned in the normal way, taking the advantage it's always on school holiday as well)