steve wrote:
You're not going to like my explanation, because I've tried to explain this to others before and failed, and I can't give you a 'scientific' explanation, but... it's because for the lowest max and highest min, the time they occurred isn't really significant, it's the whole day which is significant.
There, I said you wouldn't like it.
The time can actually be significant - especially when the max or min was also related to a major event. For example, the Black Saturday bushfires in Victoria (nearly 200 killed and many many hundreds of homes and properties destroyed in one afternoon) had a later than normal extreme temperature peak - in my case 46.2 C at 1733 and stayed within .3 C for nearly an hour afterwards - normally, even in summer, our peak temperatures are reached between about 1500 and before 1700 and then start to drop off quite significantly, even on very hot days. Even the minimum temperatures over this 4-5 day period were reached abnormally late in the morning - on a few of the days during this heat wave, they were reached *after* 9am.
Not 'arguing' with your thinking, but for some events, these times can be important.
So whilst I understand your belief about them 'not being important' if the information is available, why not have a webtag for it - this way, the user gets to decide if they want to use it or not? Currently I parse all of my data to display this info whenever an annual, monthly or daily page is displayed.
(As an aside to this, when I was contacted by our Water Authority recently about them accessing all of my rain data for the past 27 years, one of the things they wanted to know was whether my rainfall data was broken down during each 24 hour period and to what resolution it was available.)
Login 
Register
Enhancement requests
Search
)
