OK, I think I 'get it'. :-)
You divide the day up into archive intervals (say, 5 minutes). Then you average the winds in those intervals. The max of those averages over the course of a day is the "Max Wind Speed." Right?
I'm not sure what the value is in such a statistic, as it would be highly sensitive to the averaging interval. For example, as the interval goes to zero, then there would be no difference between max wind speed (as defined above) and the gust speed. As the interval goes the other way, towards one day, the max wind speed becomes essentially the average wind speed.
Another way to think of it: suppose I told you that yesterday had an average wind speed of 5 m/s, a max wind speed of 10 m/s, and a max gust of 15 m/s. What would you have learned? Now suppose that today the average wind speed and max gust were the same, but max wind speed was 8 m/s. What have you learned? That yesterday was windier? Probably not.
If there was a physical basis for the averaging interval, such as a dominant time in the wind frequency spectrum (something like a "set" in ocean waves) then I could see it --- you'd want to know how much energy or speed there was in each interval.
In any case, the customer is always right. :-) The problem is that, right now, recording something like that in the stats database would require changing the schema --- something that I'm not very enthusiastic about because it would inevitably be a huge support headache.
So, bottom line: this becomes another good reason to do away with the stats database and extract everything from the archive database. Or, at least, just use the stats database as an optimization strategy.
As always, your thoughts are welcome.
-tk