• Home
  • /
  • Blog
  • /
  • Averaging by Convention – or Not
Information

Averaging by Convention – or Not

By jennifer
October 17, 2017
Averaging by Convention – or Not

FOR some time, weather enthusiasts across Australia have been noticing rapid temperature fluctuations at the ‘latest observations’ page at the Australian Bureau of Meteorology’s website. For example, Peter Cornish, a retired hydrologist, wrote to the Bureau on 17 December 2012 asking whether the 1.5 degrees Celsius drop in temperature in the space of one minute at Sydney’s Observatory Hill could be a quirk of the new electronic temperature sensors. Ken Stewart, a retired school principal, requested temperature data for Hervey Bay after noticing a 2.1 degrees Celsius temperature change in the space of one minute on 22 February 2017.

So, begins my article to be published later today at The Spectator online, perhaps to be entitled ‘More Hot Days Caused by Purpose-Designed Temperature Sensors’. [That article was eventually published at both The Spectator and WUWT.]

But if you read a bit beyond the headline you will see that my issue is not so much with the temperature sensors as the way in which the Bureau is not averaging according to calibration. In particular, and to paraphrase some more from the article…

Beginning some twenty years ago, electronic sensors have progressively replaced mercury thermometers in weather stations across Australia. The sensors can respond much more quickly to changes in temperature, and on a hot day, the air is warmed by turbulent streams of ground-heated air that can fluctuate by more than 2 degrees on a scale of seconds. So, if the Bureau simply changed from mercury thermometers to electronic sensors, it could increase the daily range of temperatures, and potentially even generate record hot days simply because of the faster response time of the sensors.

Except to ensure consistency with measurements from mercury thermometers there is an international literature, and international standards, that specify how spot-readings from sensors need to be averaged – a literature and methodology being ignored by the Bureau.

To be clear, the UK Met office takes 60 x 1 second samples each minute from its sensors, and then averages these. In the US, they have decided this is too short a period, and the standard there is to average over a fixed 5-minute period. In Australia, however, the Bureau takes not five-minute averages, nor even one-minute averages, but just one second spot-readings.

Check temperatures at the ‘latest observations’ page at the Bureau’s website and you would assume the value had been averaged over perhaps 10 minutes. But it is dangerous to assume anything when it comes to our Bureau. The values listed at the ‘observations’ page actually represent the last second of the last minute. The daily maximum (which you can find at a different page) is the highest one-second reading for the previous 24-hour period: a spot one-second reading in contravention of every international standard. There is absolutely no averaging.

Then again, how many of you knew that the mean daily temperature as reported by meteorological offices around the world is not an average of temperatures recorded through the day but rather the highest and the lowest divided by two – as is the convention.

This convention developed because (surface) temperature measurements were originally instantaneous measurements from mercury thermometers recorded manually each morning (providing the minima) and afternoon (providing the maxima).

So, in the UK the daily maximum from a weather station with an electronic sensor will be the highest value derived from the averaging of 60 samples over that one minute interval, while in Australia, the daily maximum will be the highest one-second spot reading.

And, the method for averaging from the sensors does matter, as shown in the attached spreadsheet using synthetic values to illustrate this point, and summarized in Figure 1.

Scroll to the end of this post to download the entire spreadsheet with all 60 numbers for each worked example.

The values shown in the three-worked example fall well within the general range of variation possible within a one-minute interval considering highest, lowest and last second values as shown in some of the datasets purchased by Ken Stewart from the Bureau earlier this year.

In the first example, which could be symptomatic of ‘sensor noise’, there is a single outlier of 22.1 in the 60 one-second readings from the sensor. If these are averaged, as is done by the UK Met office, then the recorded temperature measurement for that minute is 20.1 degrees Celsius. If, however, the highest one-second value is recorded, which is the method applied in Australia, the recorded temperature would be 22.1 degrees Celsius. There is a whole 2 degrees of difference. If we apply the meteorological convention for generating mean daily values, then the difference is 1 degrees Celsius (0.9666 rounded).

In the second example, which could reflect a wind direction change, or jet plane exhaust, the difference between the UK Met office method of averaging over 1 minute versus the Australian method of taking a one second spot reading is the rather large 2.9 degrees Celsius.

In the third example, where there is a step change, the difference between the UK and Australian methods for treatment of sub-minute readings is 1.8 degrees Celsius.

More recently the Bureau have attempted to suggest yet another method of averaging, as detailed in their Fast Facts. But this is really just obfuscation, in more recent correspondence with me CEO Andrew Johnson has used the correct term when calculating how long it takes a sensor to adjust to a step change in temperature, which is 'time constant'.

*****

The spreadsheet detailing the different averaging methods can be downloaded here: Averaging-NF-JM

I am blessed to be part of an Alt-Met network that includes Kneel (who sent me a first version of this spread sheet), Ken Stewart, Lance Pidgeon, Phill and others... thanks for the conversations.

Good Causes

Comments

  1. Jennifer you deserve a medal for this work. This is the most appalling scientific fraud I have ever heard about and i cannot believe our media will not run with it. Don't stop.

  2. EM Smith. That idea of comparable readings sounds good to me. Ian George, I agree with you about rainfall readings. Unless the local airport is in a rain shadow.

  3. Thanks, Jen, for this much-needed beam of light.

    What a wonderful tool these AWSs are to generate the necessary warmth.

    Just think of the money that will flow from the private sector to the public sector as a result.

    What's not to like?

    Just ask T Smit above.

    The fakery at the bakery is in robust health.

  4. Thanks for your work JM.

    We also have rain gauge problems at our local BOM (Geelong Racetrack).

    On numerous occasions we have have biggish falls ( > 15 mm ) that are recorded as 0 mm or significantly less than what actually occurred. I used to write to BOM who advised the mechanism may not be optimally located.

    The problem is compounded because we often have long spells without any rain (which is what BOM tell me cause the problem with the gauge) and then 10+ mm a day for several days contiguously - the whole event can be missed before they get round to fixing it. I can't be bothered contacting BOM anymore, but they are well aware that it is a recurring problem spanning many years. Some of the events that I contacted them over represented > 10% of annual rainfall *each* - BOM did not seem at all concerned...

  5. My wife and I tend to ‘peek’ at our iPads many times during the day and living in the Blue Mountains (about three kilometres from the Mt Boyce weather station, perched on the escarpment at just over 1000m and directly above the Megalong Valley) we check the weather (from Oz Weather) very frequently. It always used to puzzle us that we would observe that the max temperature being shown was nowhere near the forecast maximum and yet, at the end of th day there it was - the maximum temperature was close to the forecast. It is now clear what is happening. It is very common up here, on warm days, to get bursts of warm air from the valley almost 300m below and about 2 degrees warmer, coming up the escarpment in the afternoon. One can actually feel them if walking along the escarpment top. This obviously is what is providing the short term spike which is recorded as “the hottest evaaah”. Thanks Jennifer and team.

  6. Excellent, most excellent work, Jennifer.

    It is unfortunate that the SOP at the BOM tosses away readings.We get better results if the data are recorded, then transmitted and saved centrally. With the appropriate compression methods, its not an unmanageable quantity of data.

    If nothing can be done about the 'tossed' data, then the next best thing (in terms of approximating the actual temperature) is to develop an algorithm that takes the data that ARE saved, (the min, max and last) seconds of each minute, and treats them something like the sliding-window averages that are used for Arctic sea ice. Even a 10-minute average of the mins, a 10-min average of the max and a 10-min average of the last would give a sense of the trend for that time period of the 3 values. Yes, it would be a homogenized trio of values, but it would set the range for the min and max for the sliding window of time, and show trends that would call out the outliers, while also showing the effect of squall line fronts, the beginning of a snow storm, strong rain outflow, etc.

    All the best.

Write a Comment

Leave a Reply

Your email address will not be published. Required fields are marked *