Hawkeyed reader Bob has sent in this example of the BoM August rainfall anomaly map for Victoria failing to reflect above average rain at BENDIGO AIRPORT (081123) 51.5 Norm, 56.4 in August , CASTLEMAINE PRISON (088110) 66.4 Norm, 66.6 in August. And then a little further south the anomalies contours make no sense either – DAYLESFORD (088020) 103.0 Norm, 111.4 in August, TRENTHAM (POST OFFICE) (088059) 124.8 Norm, 154.5 in August, and WOODEND (088061) 90.3 Norm, 91.3 in August. Larger map
The Daylesford daily data shows another type of error with rainfall left unrecorded in the gauge four times during the month – on the 8th the reading covered the previous 6 days. Well water evaporates so Daylesford rain for August was understated. Amazing with so much publicity about drought and wealthy Australia can not read a simple factor like rainfall to a proper standard.
But we are reading a lot about Roger Federer losing a game of tennis due to global warming.
In twenty years time, he will lose a lot more games of tennis. That will also be due to global warming.
Nothing whatsoever to do with age.
Marree in SA looks like another error.
www.bom.gov.au/web03/ncc/www/awap/rainfall/anomaly/month/colour/latest.sa.hres.gif
Three Marree stations all above the August norm not enough for the BoM rain anomaly contouring maths.
www.australianweathernews.com/data/DS0817.HTM
Maybe this is where the rainfall anomaly map contour discrepancies come from i.e on the BOM website "an optimised Barnes successive correction technique"? Sounds a bit like homogenization and adjustment of rainfall data?
Gridded high resolution rainfall metadata
Under: Data Quality/Lineage
Thanks Bob. Nobody expects contouring to perfectly reflect underlying point data. However there should not be a bias one way or the other. If anybody can find equivalent map areas where rain is equally “exaggerated” – I will take this blog down.