There is no such time as 24:00; after 23:59:59 the next second is 00:00:00 the next day.
Very occasionally, UTC goes 23:59:59, 23:59:60, 00:00:00. It next happens on June 30, 2015.
http://en.wikipedia.org/wiki/Leap_second

There is no such time as 24:00; after 23:59:59 the next second is 00:00:00 the next day.
Funnily enough I was reading this thread at work earlier and thought nothing of it.
However later in the evening I ended up in Huddersfield and got back for the train to York at 23:52.
Just after the ticket barriers there is a screen showing departures and it went in this order :
00:21 YORK
02:43 AIRPORT
23:52 YORK
23:55 AIRPORT
So due to the 00 it had put the later trains at a higher priority than the trains actually closer to the current time![]()
How brilliant must our computers be. A single system can handle traffic at speeds of 125mph all day on the WCML, they are capable of flying aircraft safely around the world yet they can't cope under pressure of the next day approaching.
Try explaining the difference between 0000 and 2400 to the general public. And I've also seen times reported as 24nn which is even more confusing. Can't remember where, mind (but I didn't dream it!).
What will happen at year 10,000??
I bet that will mess my computer up.
What does the automated voice say with 00 hours departures?
Zero-zero? Oh oh? Hundred? Or just midnight??
There is no such time as 24:00; after 23:59:59 the next second is 00:00:00 the next day.
The timetable program for the local PTE has times going as far as 2700 for the last routes of a working day, I believe -- internally, at least. They're displayed to the user as 0000-0300.
Easier to work with because the timetable of such day routes often depends on what the previous day was, rather than what the new day is.
That must get confusing as people have to work out that 28 means 4am? After midnight in the grave yard slot they probably don't care as much.In the broadcasting world, internally they use 30 hour days - they day ends at 29:59 (05:59) as the broadcasting day runs 06:00 - 06:00.
When timetables in the U.K. started going over to a 24 hour clock in the 1960s and 1970s I can only ever remember midnight expressed as 24.00. It is computerisation which has unnecessarily brought us 00.00.Anyone who can read a 24 hour timetable will know that 24.00 is midnight, whereas 00.00 means the world has ended. No doubt the same kind of geniuses who brought us 00.00 are responsible for our railway ticketing shambles. In 1948, the year of my birth, second class rail travel anywhere in Britain cost 2d a mile and all rail distances were accurately measured. Bring back that system, saving the railways millions in administrative staff, lawyers and ticket inspectors and allowing the BTP to get on with sorting out the criminally anti-social if they can be arsed to.
That must get confusing as people have to work out that 28 means 4am? After midnight in the grave yard slot they probably don't care as much.
What about those working 05.00 to 06.30, as Steve Allen does on LBC? Under this he works from 29.00 to 06.30.
I really, really hope this is sarcasm.
If it isn't, I'd invite you to vote for that nice Mr. Farage in May - he seems determined on taking the UK back to some rose-tinted memory he had of the UK in the olden days.
Surely you must like the idea of rail fares being set at two pence a mile.![]()
I really, really hope this is sarcasm.
If it isn't, I'd invite you to vote for that nice Mr. Farage in May - he seems determined on taking the UK back to some rose-tinted memory he had of the UK in the olden days.
It might, however, confuse some members of the public especially at the beginning and end of the week when timetables are different; having a time of 00.00, while logically at the start of the day, could be misinterpreted by some as being at the very end of the previous day.
23.59 and 00.01 remove that risk of confusion completely.
TFLs way of dealing with the 0000 is continuing as the day hasn't finished until about 5am, even with routes that don't have a night service, couple of examples
http://mjcarchive.www.idnet.com/schedules/100to149/Schedule_121-34528-MF-MN-1-1.pdf
http://mjcarchive.www.idnet.com/schedules/1to49/Schedule_25-34742-MT-TN-1-1.pdf
http://mjcarchive.www.idnet.com/schedules/1to49/Schedule_N25-34742-MTNt-TN-1-1.pdf
I thought the railway day started at 4am, so that day returns would still work on trains past midnight, for example?
I thought the railway day started at 4am, so that day returns would still work on trains past midnight, for example?
I was refering to the risk of members of the public turning up 24 hours too early or too late for the train they think they are going to be catching; a particular risk at either end of a Sunday!![]()
There is no such time as 24:00; after 23:59:59 the next second is 00:00:00 the next day.
And talking of Y2K, the consequences of not handling the "century" correctly do still cause some issues with computer systems even today; I know of at least one application that used just DD.MM.YY and went from 31.12.2014 to 01.01.1915. And for Microsoft applications, the next date after 31.12.2029 is 01.01.1930, so there are 15 years left to solve that one if the century is not used and you rely on the "default" processing...
But as is shown here, there is scope for confusion so for most public use, 00:00 & 24:00 don't exist in schedules....
The way I see it is 00:00:00 is the start of a new day and its is how we are all used to it, but the real law of the clock suggests the new day actually starts at 01:01:01, just imagine the clock if the '00' was removed and replaced with '60'
There are 24 hours in day, 60 minutes in an hour and 60 seconds in a minute so the 60th second on the 60th minute at the 24th hour of the day is 24:60:60 which in our time is 01:00:00. After 24:60:60 all the values return to '01' so the time now on the start of the new day would be 01:01:01.
whats noticable is the 1st of the month is always declared as '01' on the start of each month and not '00'. If the time on the clock says 00:00 is midnight then shouldn't January 1st 2015 be declared as 0/0/15
The way I see it is 00:00:00 is the start of a new day and its is how we are all used to it, but the real law of the clock suggests the new day actually starts at 01:01:01, just imagine the clock if the '00' was removed and replaced with '60'
There are 24 hours in day, 60 minutes in an hour and 60 seconds in a minute
so the 60th second on the 60th minute at the 24th hour of the day is 24:60:60 which in our time is 01:00:00.
whats noticable is the 1st of the month is always declared as '01' on the start of each month and not '00'. If the time on the clock says 00:00 is midnight then shouldn't January 1st 2015 be declared as 0/0/15
There is no such thing as "the real law of the clock", just 2 different systems which are related. All that matters is that the numbering is universal and understood.