HOME

OZ-ENERGY-ANALYSIS.ORG   -   open science for the new millennium

THE STORIES   |   DATA   |   ANALYSIS   |   MODELS   |   LITERATURE   |   DISCUSSIONS

status: [2nd March 2011] awaiting overhaul

Wind Speed and Direction Data


[fc: 1st March 2011]
This page has a history, and much of the development has occurred in the comments.
The Round One data is now finalised, and the entire page (including comments) could do with a major reconstruct... .
Apart from the figures and the table, you probably want to be looking at the Simulated Wind Farms from Broome to Cooktown analysis that follows from the data here.




Introduction

This is the wind data page, and is currently focused on The BtCC. Earlier work and data (the initial five) is here in supplementary materials.

The wind is a major source of renewable power, due principally to its lower cost relative to other renewable energy sources (putting aside Hydro Power). It is also a highly variable source of power. The Australian Bureau of Meteorology (BoM) has a large store of wind data.

While not entirely straightforward, BoM wind data can be used to estimate the (variability of) power that might be obtained if a Wind Farm were built in the vicinity of the BoM station. Unfortunately, BoM stations are not generally located in the places that Wind Farm builders would choose; BoM stations are generally located in or near towns and airports, while the ideal positioning for a wind farm is on the top of a ridge that runs perpendicular to the prevailing wind. None-the-less, we work with what we have keeping in mind the limitations.

The primary use of Wind Data in the OzEA project is to examine spatial smoothing, that is, the extent to which geographically distributed wind farms balance out each-others lull periods.

Figure (DWSF) 01: Locations of the 825 BoM stations with wind speed data covering 2009. This small image file is for fast page load, and links to a pdf file (only 90 KB). This PDF file allows you to zoom in and in, until you can see the station ID numbers. In some cases stations are so close that the numbers overlap - a problem we may attempt to resolve at a later date.

If you go to: http://www.bom.gov.au/climate/cdo/about/sitedata.shtml and select "Wind Speed" you can obtain a list of 1838 BoM stations [June 2010]. These are interesting to look at in general, but here we restrict immediately to those stations with data covering 2009; this reduces the list to 825 stations, as plotted in the Figure above (be sure to click on the image so as to obtain the pdf version - into which you can zoom and zoom).


Data Selection - BtCC - Round 1

This work is complete, as below, for now [July 2010]. However, the purpose of the Round-1 data selection is as 'a start'. As work proceeds the weakness and limitations of this particular selection can be expected to become more apparent, and in time we will return to this step and make an improved selection for processing through the workflow we are currently developing. That is, the current analysis is focused on: (i) understanding the data, and (ii) developing a pipeline for data processing and analysis. Of course, the Round-1 work will also provide a first tentative look at the results of this project.

The following figure (and linked PDF) now represents the conclusion of the (round 1) data selection. We have obtained the Wind Speed data for the 40 selected BoM stations (red crosses, and as listed in the table following) and these data are now [July 2010] being examined and characterised. This selection was aided by using the generators data from which we extracted the locations of the current and proposed Wind Farms (lime green and cyan blue respectively), and with a lower cutoff of 20 MW (exception made for Windy Hill in QLD).

Figure (DWSF) 03: The Round 1 selection of 40 BoM stations with wind speed data covering 2009 (red crosses). Shown also are the current and proposed sites for Wind Farms of capacity 20+ MW (an exception for Windy Hill in Qld, which is only 12). The magenta crosses represent BoM stations that were candidates for consideration, but which do not form part of the current data processing. This small image file (for fast page load) links to a (100 KB) pdf file. This PDF file allows you to zoom in and in until you can see the station ID numbers.

Using the PDF it was possible to identify (somewhat roughly) a selection of BoM stations that trace out the coast (and now include some inland areas) from Broome to Cooktown (and a little further). Any given latitude and longitude can easilly be copy and pasted into Google Earth, and this was the primary mechanism for sanity checking the selections and comparing them with nearby alternatives. In this way the Round One Selection was developed. Note that the locational precision given in the BoM data is not usually high enough to give a direct hit onto the stations. In addition to the table following (the selection), a further table listing those BoM stations that were part of these considerations, but that did not end up in the following selection, can be found on supplementary materials page.

BoM Station Name BoM ID Latitude longitude
WA
BROOME AIRPORT 3003 -17.9475 122.2353
LEARMONTH AIRPORT 5007 -22.2406 114.0967
GERALDTON AIRPORT 8051 -28.7953 114.6975
GINGIN AERO 9178 -31.4628 115.8642
CAPE LEEUWIN 9518 -34.3728 115.1358
ALBANY AIRPORT 9741 -34.9414 117.8022
ESPERANCE AERO 9542 -33.6825 121.8275
EUCLA 11003 -31.6797 128.8792
SA
MINNIPA DPI 18195 -32.8427 135.1515
CUMMINS AERO 18217 -34.2524 135.7135
CLEVE AERODROME 18116 -33.7081 136.5026
EDITHBURGH 22046 -35.1121 137.7395
PARAWA (SECOND VALLEY FOREST AWS)23875-35.5695 138.2864
SNOWTOWN (RAYVILLE PARK) 21133 -33.7676 138.2182
NURIOOTPA VITICULTURAL 23373 -34.4761 139.0056
CAPE JAFFA (THE LIMESTONE) 26095 -36.9655 139.7164
MOUNT GAMBIER AERO 26021 -37.7473 140.7739
TAS
LOW ROCKY POINT 97080 -42.985 145.5022
TASMAN ISLAND 94155 -43.2397 148.0025
CAPE GRIM BAPS 91245 -40.6828 144.6900
EDDYSTONE POINT 92045 -40.9928 148.3467
VIC
PORTLAND (CASHMORE AIRPORT) 90171 -38.3148 141.4705
WARRNAMBOOL AIRPORT NDB 90186 -38.2867 142.4522
PYRENEES (BEN NEVIS) 79101 -37.2281 143.2006
REDESDALE 88051 -37.0194 144.5203
YARRAM AIRPORT 85151 -38.5647 146.7479
COMBIENBAR AWS 84143 -37.3417 149.0228
NSW
COOMA AIRPORT AWS 70217 -36.2939 148.9725
ULLADULLA AWS 69138 -35.3635 150.4827
GOULBURN AIRPORT AWS 70330 -34.8085 149.7312
TAREE AIRPORT AWS 60141 -31.8896 152.5120
BROKEN HILL AIRPORT AWS 47048 -32.0012 141.4694
MURRURUNDI GAP AWS 61392 -31.7416 150.7937
ARMIDALE AIRPORT AWS 56238 -30.5273 151.6158
QLD
GOLD COAST SEAWAY 40764 -27.9390 153.4283
OAKEY AERO 41359 -27.4034 151.7413
RUNDLE ISLAND 39322 -23.5293 151.2763
ALVA BEACH 33295 -19.4569 147.4833
MAREEBA AIRPORT 31210 -17.0672 145.4283
COOKTOWN AIRPORT 31209 -15.4461 145.1861
Table DWST01: The Round One Selection; 40 AWS Wind Speed measuring stations from Broome to Cooktown. Note that the locational precision given in the BoM data is not high enough to give a direct hit onto the stations.

[23rd July 2010] Here is the base round-one wind speed data for the above BoM stations for 2009:


[fc: 3rd August 2010] Am now providing a csv version of the data here, BUT these files are not really human readable, and I strongly recommend that you always look at data with your own eyes before feeding it into machines.


The data for all stations is given in a single flat file, in the OzEA 'line per day' format; the data points correspond to hour values (i.e. 12am, 1am, ... 11pm) in AEST, have units of m/s, and with missing data given as 'NaN' (Not a Number). As described in what follows the above data includes interpolated values for isolated missing data points.

For anyone who is interested, the following sequence of steps and files outline the process of transforming the data provided by the BoM into the data file given above.

First, here is a zip file containing 40 individual files (for the 40 BoM stations), each giving the June 2009 data, in half hourly steps, as given by the BoM: BtCC_sample_BoM_data_v1.zip [280 KB].

Second, here is the very same data transformed into the 'Line per Day' format that we use here for such data: BtCC_sample_LpD_data_v1.zip [58 KB].

Third, here is the same data again, now expanded to include all of 2009 and consolidated into a single flat file: BtCC_R1_RAW_30min_2009.txt.gz [510 KB gziped flat file]. This is the raw data; it is numerically identical to the BoM data, but in a different format.

And now the above data is processed to give the Base Data according to the following three step process: (i) using this half hourly data interpolate any single missing value (as the average of the adjacent values); (ii) discard the half hour values, leaving only the on-hour values; and (iii) interpolate again as above, but now with the hourly data, before writing out.


Wind Data Characterisation


[fc: 23 July 2010] This is where it's at - more here soon.
[fc: 3rd August 2010] This has started in the comments.



[Jump to bottom]

DISCUSSION: (on the BoM wind data)

2

OzEA_DBWD0002

John Morgan
Subject: Statistical characterization
Date: 2010-05-21 (at 20:45:44)


Lots of data, lots of questions. Some statistical characterization would be nice:

* How well does the wind velocity fit the Rayleigh distribution?
* Does the data show extended outages? If so, is their frequency as predicted by the Rayleigh distribution? Something else?
* Spatial and temporal correlation functions
* Daily and seasonal periodicity

Mainly to test existing assumptions about wind variability, get a handle on what its actually doing. But a wind model with the same stats as the real thing might be handy for building the power model.

4

OzEA_DBWD0004

Stephen Gloor (Ender)
Subject: Wind Modelling for NREL studies
Date: 2010-06-02 (at 13:03:13)


Perhaps we need to start at the beginning and develop a wind model for SA that is independant of actual wind sites. In this way a proper study of wind farm siting and the ELCC for the connected wind farms can be developed.

The model used by the EWITS study is here:

http://www.nrel.gov/wind/integrationdatasets/eastern/methodology.html

Maybe this methodology can be applied so we can have the same quality dataset as the NREL and comparisons can therefore be made.

5

OzEA_DBWD0005

Francis
Subject: Wind Data
Date: 2010-06-03 (at 23:03:05)


re: John Morgan / Statistical characterisation

lots of questions indeed - I have much the same ones. Doing the relevant characterisation work is on a 'need to do it basis'.

You may be interested to dig up a 2003 CSIRO report called SOUTH EAST AUSTRALIA WIND POWER STUDY by Robert Davy and Peter Coppin.
There is also work around by John Boland (University of South Australia) along these lines.
+ see following comment:

re: Stephen Gloor (Ender) / Wind Modelling for NREL studies

Interestingly, this is where we did start six months ago (thinking we should develop a wind model for SA). But it quickly becomes clear that this is a bog, and an unnecessary bog at that.

While the data given here is a good start for anyone who wants to characterise SA wind data, I am sitting on a whole pile more SA wind data that I can stump up as needed.

So; I did start by comparing WF generation data with the wind speed data from nearby BoM stations, and you can see the basic problem. When the BoM station is measuring much the same wind as the WF is experiencing, then the correspondence is good. But, BoM wind stations are more often situated at airports in valleys, or such, while Wind Farms are on the tops of hills.

Maybe one could proceed by stepping back and developing a general wind model, but, apart from holding everything back for ?twelve months, is this really necessary?

If you look at the analysis of gross variability of the wind resource you will see that the large scale patterns (when it is windy, when it is not) are large scale (with the interesting observation that WOOLNTH1 in Tasmania appears to be a substantially more even resource that the other WF's considered).

Maybe we will get to a point where we need to look at the finer scale variability and spatial smoothing, but first we have a perfectly respectable problem to solve at the grosser level. It is the logical way to proceed so far as I can see.

So, the best data we have is the output from the wind farms themselves. Certainly there are some wrinkles, but so far as I can see this data allows us to proceed in a useful way without getting bogged in this wind data.

7

OzEA_DBWD0007

John Morgan
Subject: Broome to Cooktown
Date: 2010-06-10 (at 00:33:51)


Here's an early entry in the Broome to Cooktown challenge. It may be running in the wrong direction, and probably doesn't have much staying power.

I was looking at the Cleve_Aerodrome data, since it seems well behaved. Plots are in Fig 1, attached.

Fig 1

Data is for one year, and 250 hours. There seems to be a daily cycle, so lets look at the autcorrelation. I calculated the autocorrelation function as the Pearson correlation coefficient for the windspeed array against itself with a time lag, using a periodic boundary condition, ie, assuming each year is a repeat of the last. I can get six months of autocorrelation this way, see Fig 2.

Fig 2

Looking in at the ACF the daily correlation is nicely resolved. What I wanted to see was the underlying decorrelation. Wind speeds at this station appear to decorrelate over about four days. Looking at just the daily peaks, the decorrelation time constant is about 19 hours (running an exponential through the peaks), so call it 60 hours for decorrelation. (I tried to filter out the periodic component but wasn't very successful - its been a long time since I've done this sort of data analysis.)

I take this decorrelation time as the synoptic timescale. I assume a large scale weather system takes approximately 60 hours to pass across this monitoring station. How fast is it travelling?

The average wind (ground)speed over the year was 5.5 m/s. Assume this is a lower bound for the weather system speed. Then we can estimate the synoptic correlation length constant as being not smaller than ~380 km, or, the size of a weather system as not smaller than 1200 km.

This is quite consistent with the correlation length constant reported by Kempton et al. in PNAS as ~430 km, as determined from wind farm power output along the US eastern seaboard.

Windspeed at modest height is estimated by the Hellman equation as log(v) = a . log(h), with a value of a~0.3 typical. Assuming the BOM station heights are 10 m, the velocities are 2, 4 and 8 times faster at 100m, 1000m, and 10000m. (Why not extrapolate beyond the bounds of validity - lets go for gold!) So the synoptic weather system size is about a small integer multiple of my minimum estimate.

So, from a single weather station, I've deduced the spatial smoothing scale is at a minimum ~1200 km, consistent with the PNAS study, though more likely several times that. Lots of dodgy assumptions, but I'll bet its about right.

Another quick point from the ACF - any spatial smoothing over a large scale is going to have to take account of the time differences between regions,


fc: thanks John, and a note to all that you get figs up by mailing them to me (for now)

16

OzEA_DBWD0016

Francis
Subject: Processing Wind Data
Date: 2010-06-14 (at 14:52:38)


I reckon it helpful to outline my vision for this work; of course, how this does actually unfold might be quite different.

First, how will the wind data be used? I see two paths. First, one can take the wind data as a physical measurement at 10m, make the necessary physical (and geographical) assumptions to extrapolate to 80m, and then apply some 'suitable' power curve to obtain the output of a hypothetical Wind Farm built over the top of the BoM station. This is do-able, but I do not think it is the smartest way to proceed, at least as a first pass.

Alternatively, one can note that competent Wind Farm builders generally choose locations that are different to those of BoM stations, and they set up the turbines to effectively extract power from the wind resource. It is predominantly the variability information we want from the wind speed data. Given reasonably selected stations (see below) I am inclined (as a first pass) to skip the extrapolation to 80m and to simply apply a heuristic transformation to convert Wind Speed data to the output of a hypothetical Wind Farm. This approach needs good sanity checks - the main one I envisage being a reasonable Capacity Factor.

SO, while I like Stephen's suggestion of fishing for the good wind sites, I think it is more important to use this stage as a data gating exercise. Others are welcome to follow other paths; myself, I am not interested in number crunching any stations that have not undergone basic vetting (i.e. someone doing a 5 minute sanity check using Google Earth). Always, always, always look at your data.

The current, preliminary, list of 30 stations is missing Tasmania, and the NSW tablelands (thanks Neil). Filling in these sorts of gaps could get our list up to 50 easily enough. Also, I think it could be good to 'double up', so that for most stations we have an 'alternative' station (when there is a suitable nearby alternative). This will help a lot with robustness testing later.

My pledge is that when we have a suitable list of up to about 100 stations (all vetted by human eyes), we will obtain the data, and I will do the messy cleaning work to convert the BoM data into data files of the form we already have here for the 5 example cases. If, in a couple of weeks, this list has not developed, I might get in and sort it out myself, but at such a point I'd be giving up on this as a group project. )-:

17

OzEA_DBWD0017

Neil Howes
Subject: additional sites
Date: 2010-06-15 (at 09:39:14)


Francis,
My suggestions for TAS are: 91245,97085,97080,94041 and 94155. This is just based on geographical separation along the high wind west and south coasts, likely to receive lows arriving from southern ocean tracking SE of mainland Australia when a high pressure system is over central Australia.

Should also have a site at Broken Hill(cant read ID).

According to CSIRO wind resources map, southern and mid north coast of QLD is poor, but far north( Cooktown region is much better), so more sites north of 20 latitude rather than 20 to 30 latitudes along east coast.

21

OzEA_DBWD0021

Francis
Subject: Broken Hill
Date: 2010-06-16 (at 22:50:54)


I've now had a look at the two current Broken Hill sites (47048 and 47007), and the former seems better; it is at the airport just south of town (elevation 283m). As a regional alternative there is the Menindee Post Office (47019), and the Fowlers Gap AWS. I remember Menindee having some reasonable trees around town, and it is in any case at only 65m (by the Darling River), whereas Fowlers Gap (~100 km N) is at 185m. As is usually the case, they haven't put the BoM station where you'd try for a Wind Farm. The Broken Hill and Fowlers Gap stations have been added to the list.

22

OzEA_DBWD0022

John Morgan
Subject: exploration of wind properties
Date: 2010-06-24 (at 17:05:49)


I was noodling around with the Cleve Aerodrome data I analysed above since I wanted to answer the questions I raised at the top of the thread, namely, does the data conform to the Rayleigh distribution, and what does the distribution of lulls look like? ie, how often does this station show extended durations of low wind.

This is somewhat tangential to the aim here, but, I think its worthwhile doing a deep dive into wind at a single site because it should help inform the analysis when putting multiple sites together. And because I'm curious.

So, are the windspeeds Rayleigh distributed? You get the Rayleigh distribution if the x- and y- components of the wind velocity are (i) independent, and (ii) normally distributed. It would be handy if true, since a simple closed form expression for the wind probability makes for easy analysis. The distribution is often used for windspeeds, so I'd like to see how well it stacks up.

First up, are the x- and y- components independent? I plotted all hourly wind vectors on polar axes, to show speed and direction (Fig 3).

Fig 3 - wind speed and direction

Units are degrees from true north, and m/s.

It looks pretty uncorrelated to me. I expected to see a prevailing wind, especially so close to the coast, but there is no evidence at all of such.

Next, lets look at the velocity distribution (Fig 4):

Fig 4 - velocity distribution

The windspeeds look to be pretty well fit by the Rayleigh distribution (red line, least squares fit of Rayleigh function to data), except at the lowest speeds. The number of hours of zero wind is much higher than the model. So maybe using the Rayleigh distribution would miss the lulls. But up to about 2.5 m/s counts are lower than the model by an amount that compensates. So unless you're interested in the detail at the lowest speeds, the Rayleigh distribution looks good.

Another way to visualize this is sort all the data into order and plot them over the interval [0,1). For the Rayleigh distribution this should be fit by sigma*sqrt(-2*ln(1-x)). This shows the quality of the fit more clearly than the histogram. The red line is the same distribution as in Fig 4. The fit is good except at the lowest speeds (Fig 5).

Fig 5 - Rayleigh distribution fit

Finally, how are those low wind events distributed? Are they grouped together into extended lulls, which would be a problem for power production? Our are they shortlived transient lows, which aren't?

I counted the number of lulls of different durations and plotted them in Fig 6. A 'lull' is a group of adjacent windspeed measurements less than some threshold. Lulls that are completely becalmed are interesting, but if your windfarm can't generate power below 3 m/s, then thats the threshold of interest. I plotted thresholds of 0, 3 and 6 m/s, though 6 m/s is not really a lull.

Fig 6 - distribution of lull lengths

So for instance, there were 11 occasions in 2009 where the wind at this site was less than 3m/s for (exactly) 9 straight hours. There was one occasion where it was less than 3 m/s for 21 hours. In theory, it should be possible to calculate the 3 m/s curve from the Rayleigh distribution, but not the 0 m/s curve.

So, for this site,

Things I'm interested in looking at next are correlations between two sites and whether the lull distribution for a site can be calculated from the Rayleigh parameters.

23

OzEA_DBWD0023

Francis
Subject: Re: exploration of wind properties
Date: 2010-06-24 (at 17:07:03)


Many thanks John; the BtCC yellow jersey is yours right now. A couple of short points from me:

1. Data and distributions: This approach you (and others) are taking to the data is useful and helpful because it compliments the approach I am taking. As much as possible I simply work with data and avoid supposing any particular distributions.

2. The topography around Cleve Aerodrome: The lack of dominant direction perplexes me too -- if you drop "-33.708 136.503" into Google Earth you can see the layout, and see that Cleve Aerodrome is at about 180m elevation, with higher ground to the NE. It appears to be -mostly- sloping down to the S and W, but there is high ground (quite a range it seems) about 80 km to the the SW (where I would expect the prevailing wind to come from), and perhaps this is chopping things up. I'm not able to pinpoint the Mount Millar Wind Farm exactly, but it is probably at around twice this elevation (and about 20km to the ENE) - perhaps it sees the prevailing wind more clearly.

44

OzEA_DBWD0044

Francis
Subject: BoM data
Date: 2010-07-12 (at 20:51:48)


Today we received the requested data from the BoM, in effect giving us 39 Wind Stations from Broome to Cooktown.

This data is in a very amenable format compared to last time, and it should not take more than a couple of days to get 2009 data for these 39 stations up onto the site. And then the fun can begin!

Here are my initial notes:


1. The Initial Data
===================
[Mon 12 Jul 2010]
Received the data today in three files:

52789862 12 Jul 13:18 0021 hourly.zip
260662798 12 Jul 13:18 0021 minute.zip
19138858 12 Jul 13:18 0021 synoptic.zip

The Hourly Data
---------------
These are all AWS stations, with data file names taking the form:

HM01X_Data_######_999999995907925.txt

For the following 39 / 40 BoM station numbers:

003003 005007 008051 009178 009518 009542 009741 011003 018116 018195
018217 021133 022046 023373 023875 026021 026095 031209 031210 033295
039322 040764 041359 047048 056238 060141 061392 069138 070217 070330
079101 084143 085151 088051 090171 090186 091245 092045 094155 *097080*

With the final one 097080 'dead on arrival' (empty).

Most of these files go back into the nineties, although some start as late as 2007.
On first apperences this is half-hourly data, but with some empty records, including
in particular periods where the data is hourly.


The Minute Data
---------------
These are a subset of 15 stations from the above hourly data, with file names as:

HD01D_Data_######_999999995907923.txt

for stations:

003003 005007 008051 009741 011003 026021 039322 040764
041359 047048 070217 088051 090171 091245 094155

These contain between one and nine years data at one minute intervals.


The Synoptic data
-----------------
This is a superset of the hourly data, with data file names taking the form:

HC06D_Data_######_999999995907926.txt

for all 52 BoM stations we requested, being the 40 above (including 097080), plus:

009114 011017 018069 019062 031108 033257
039314 056229 060013 070080 070091 084070

Some of this data goes back fifty or a hundred years;
most of the more recent data is 3 hourly, with some (especially older) data on other
incriments (e.g. 12 hr, 24 hr).

45

OzEA_DBWD0045

Francis
Subject: What State is that in?
Date: 2010-07-14 (at 01:26:11)


For the record:
After doing it the hard way, I worked out that BoM station numbers have a well defined correspondence with State:

http://www.bom.gov.au/climate/cdo/about/site-num.shtml

47

OzEA_DBWD0047

Stephen Gloor
Subject: Correlation Analysis of 12 WA Wind Stations
Date: 2010-07-14 (at 10:26:25)


Report on 12 WA wind sites correlating wind speed with distance. I conducted this mainly to learn Python so that I could participate in some meaningful way to this investigation however, the data is quite interesting.

Stephen's Correlation Analysis [324 KB PDF]

48

OzEA_DBWD0048

Francis
Subject: Sample of BoM data
Date: 2010-07-14 (at 23:10:52)


Here is a sample (June 2009) of BoM Data for the 40 AWS Stations that we will be working with here: BtCC_sample_BoM_data_v1.zip [280 KB].

This is just so those who are interested can follow the data processing -- in the coming days I will extract out into an amenable format Wind Speed data for all of 2009 for these stations.

Note that these data here are all in Local Time (the processed version will give all data in AEST); there are some missing data points (will fill in for isolated cases, record as NaN otherwise). Note also that while most data is half hourly, some is hourly. Expect we will proceed with hourly data (until, that is, we revisit the entire process -- once we know what that process looks like). More soon.

49

OzEA_DBWD0049

Stephen Gloor
Subject: Is this the original data format?
Date: 2010-07-20 (at 15:55:15)


Hi Francis,

Is this the original file format from the BOM. If so then every data extraction so far from the BOM that I have seen has been different.

The ones I got recently had this format:
hm,Station Number,Day/Month/Year Hour24:Minutes in DD/MM/YYYY HH24:MI format in Local time,Day/Month/Year Hour24:Minutes in DD/MM/YYYY HH24:MI format in Local standard time,Time used for closest observation in DD/MM/YYYY HH24:MI format in Local standard time,Wind speed in km/h,Wind direction in degrees true,Speed of maximum windgust in last 10 minutes in km/h,AWS Flag,#

hm, 9741,01/01/2008 01:00,01/01/2008 00:00,,0,0,0,1,#

and the original ones I got had this format:

Date Time Drn Kph Gst
20000101 0000 90 31 43

Mind you I cannot remember if I pre-processed the second set of files.

Makes it a bit hard to standardise on a conversion script.

50

OzEA_DBWD0050

Francis
Subject: Re: original data format
Date: 2010-07-20 (at 16:04:17)


Yes, what I posted is a sample of the BoM data. And I'm in the same boat -- right now working on the parsing. The last BoM data I worked on required very careful parsing to catch missing days and all sorts -- this seems a lot cleaner, but I'm still processing all the checks. Will have up in "OzEA" format soon.

51

OzEA_DBWD0051

Francis
Subject: Sample data - in the OzEA LpD format
Date: 2010-07-20 (at 17:57:27)


Following from the sample data given in #48, here is the same data (June 2009) transformed into the Line per Day (LpD) OzEA format. This data is given as half hourly, in AEST, in m/s, and it can be seen from the missing data (NaN = Not a Number) that it is going to be simpler to work with hourly values. I'll also look at patching up some of the missing values. Here is the data: BtCC_sample_LpD_data_v1.zip [58 KB]

52

OzEA_DBWD0052

Francis
Subject: The BoM Wind Speed data (raw)
Date: 2010-07-21 (at 13:36:19)


For the 40 selected Round-1 BoM stations, here is the RAW 2009 wind speed data: BtCC_R1_RAW_30min_2009.txt.gz [510 KB gziped flat file].
The data values are as given in the BoM data (hence raw); the times are adjusted to be in AEST for all data. I have adopted the flat file format to keep things orderly. Happy to help with any issues reading / parsing - just ask.

This Data will be followed by a cleaned set where I will fill in some of the missing values and set the temporal resolution to 1 hr. This data will then be what we need to characterise before we make some decisions about how to proceed with analysis of spatial smoothing.

57

OzEA_DBWD0057

Francis
Subject: Base Wind Data - Round One
Date: 2010-07-23 (at 16:06:52)


This is the BASE Wind Data for Round One; what we will work with for a while now. It is hourly data, in AEST, with isolated missing values interpolated, and is derived from the above (#52) RAW data in the following way:

* in the 30 min data, interpolate any single missing value (as the average of the adjacent values);
* discard the half hour values, leaving only the on-hour values;
* interpolate again as above;

To get: BtCC_R1_BASE_hr_2009.txt.gz [332 KB]

This file (when uncompressed) is a plain text flat file containing 2009 data for the 40 selected BoM stations, and using 'NaN' (not a number) to signify missing values.

60

OzEA_DBWD0060

Francis
Subject: Initial data characterisation
Date: 2010-08-04 (at 18:10:14)


Have now had a good first look at the Round One wind data. Just looked at the overall histograms for each site (worked through 4 times refining my impressions and judgements each time). First thing to note is that the wind speed measurements come in ~0.5 m/s increments (i.e. the precision of these data is not 0.1 as might naively be assumed). Most of the wind data distributes as given in #22 (Fig. 4). That is, the bulk of cases were (more-or-less) distributed with mode at ~4 m/s, tails out to around 15 m/s, and with (the most variable part) a few hundred (of 8760) zero wind data points. In what follows I quickly detail the more exceptional sites; first the three stand outs, and then the nine problematic ones (using Google Earth to reexamine the sites).

The stand out strong wind sites:
* BoM 091245; Cape Grim BAPS. The pick of the bunch (a NH pick): NW of Tas, very exposed, local high point at 84m, with only ~200 to the water.
* BoM 097080; Low Rocky Point. Lower west coast of Tas. Perhaps only 20m elevation, but very exposed.
* BoM 061392; Murrurundi Gap AWS. Looks as if the wind is getting funnelled up through the gap here.

The problematic cases:
* BoM 031209; Cooktown Airport. Low lying with high stuff (100-300m) less that 10km to the SW. No great surprise here.
* BoM 031210; Mareeba Airport. Has some elevation (~470m), but there is much higher stuff (~1000m) 10-20 km away to the S and E.
* BoM 060141; Taree airport. Low lying and close to the coast, but with an arc of higher stuff (100+ m hills) to the S and SW, ~15 km away... Maybe some sort of local effects in play.
* BoM 084143; Combienbar AWS (Vic). Not obvious; about 50 km inland at ~635m. Some higher stuff to the SW, and a fair bit of lumpiness around.
* BoM 003003; Broome Airport. Low lying (10m), with protection from the town etc (at ~20m) to the immediate S/SW. No great surprise here.
* BoM 005007; Learmonth Airport. Clearly well protected.
* BoM 009178; Gingin Aero. Not so obvious this one, but perhaps 'over the lip' (in the shadow) of the rise from the coast.
* BoM 009741; Albany Airport. Again not so obvious, but getting more so! There is a ~10m lip right there beside the airport.
* BoM 011003; Eucla. Something of a surprise; this one looks exposed.

These latter 5 are WA (5 of 8 in our selection). It is also noteworthy that Airports are often (presumably) situated to be protected from ground winds. Will rework these cases in the Round Two data selection, but simply manage them for now as we proceed to look more deeply at the Round One data.

Finally, for the record, the cases with more than 100 missing data points:
333 NaNs - BoM_021133
242 NaNs - BoM_094155
200 NaNs - BoM_091245 - Cape Grim
169 NaNs - BoM_018217
139 NaNs - BoM_023875
135 NaNs - BoM_026095
114 NaNs - BoM_033295
111 NaNs - BoM_041359
109 NaNs - BoM_022046
106 NaNs - BoM_009741 - Albany Airport

ps - Am now providing a CSV version of the base data, and will continue this in future. However, these files are not human readable, and I strongly recommend that you always look at data with your own eyes before feeding it into machines.

61

OzEA_DBWD0061

Stephen Gloor
Subject: What are we looking for?
Date: 2010-08-05 (at 18:30:56)


I am now at the point where I can do multi site simulations of selected sites using the reference wind turbine. I have produced some nice graphs however what parameters should I be looking for?

I started on a lull analysis however with all 40 sites combined there is never at time where the output is zero. There are a few events less than 2MW.

My thought is to add sites and see if the low wind events decrease in frequency and also do a ramp rate analysis and extended low wind events. I was thinking of looking at when the power output rises and falls and record the amount of times it drops by say 50% in in hour. In this way adding more sites should decrease this value if the spatial smoothing is correct.

BTW I agree with your list. I used CF as a quick assessment tool. The
bottom sites you mentioned have the following characteristics


LEARMONTH AIRPORT 4.47 2.18 12
GINGIN AERO 4.20 2.45 12
ALBANY AIRPORT 4.27 2.27 11
EUCLA 4.71 1.74 11
NURIOOTPA VITICULTURAL 4.02 2.37 10
REDESDALE 4.09 2.27 10
ULLADULLA AWS 4.17 2.18 10
COOKTOWN AIRPORT 3.88 2.32 9
BROOME AIRPORT 3.85 2.02 7
TAREE AIRPORT AWS 3.11 2.08 5
MAREEBA AIRPORT 3.33 1.90 5
COMBIENBAR AWS 1.68 1.56 1

I wont bother trying to format it however Comienbar has 1% CF - clearly not a good wind site.

62

OzEA_DBWD0062

Francis
Subject: Re: #61 - What are we looking for?
Date: 2010-08-05 (at 23:17:24)


Stephen, some thoughts, but no simple answers I'm afraid.
I'm still on data characterisation, but please do forge ahead.
More general discussion on what we seek to achieve here is probably best on the BtCC story page.
The question of lulls is key, and the question of how we quantify them open.
My idea for having a first look was to do pairwise comparisons and for each 'wind farm' to identify which other/s best compensate for its lulls. In this way a network structure is produced, and the topology of this structure may give insight.

To expand a little on this (just thinking out loud): supposing our hypothetical wind farms are 'well constructed', their output can be normalised between [0,1], and for a comparison between A and B, with output A(t) and B(t), one might simply consider the total area for which A(t) > B(t), and use this as a measure of how much A covers the low periods of B. One might consider 'normalising' this value (division by total area under A(t)). Maybe this is not a good measure, or maybe there are better ones; it's a matter of trying things and always seeking to understand -why- the obtained results are as they are. In the end one usually works out how to carve the problem at the joints.

66

OzEA_DBWD0066

Nic J
Subject: Comments on BoM wind data
Date: 2010-08-19 (at 22:31:35)


Hi, just a couple of comments:
About me, I worked as a wind engineer for ~7 years and have used BoM data a bit.

BoM wind data is standardised to 10 degrees and 1 knot (0.544m/s) intervals.

Re:22, the wind rose doesn't show a prevailing wind as the frequency in each direction is hidden in the plot. see http://www.bom.gov.au/clim_data/cdio/tables/pdf/windrose/IDCJCM0021.018116.9amJan.pdf for an example of how frequency can be represented
Re:58, You can see Cape Grim from the Woolnorth wind farm ;)
Re:60, Combeinbar is in the forest, hence low wind speed.

When purchasing BoM data you can request the station reports, like this http://www.bom.gov.au/clim_data/cdio/metadata/pdf/siteinfo/IDCJMD0040.084143.SiteInfo.pdf, but including plans, skyline diagrams and maintenance records (helps explain odd data) and often includes site photos (good for checking exposure).

67

OzEA_DBWD0067

Francis
Subject: Re #66 Comments on BoM wind data
Date: 2010-09-01 (at 19:02:08)


Thanks for these comments NicJ,
We now have the station reports for the sites being considering. The layout for Combienbar does clearly show the 25 to 30 m trees nearby! Otherwise, no particular revelations -- the Eucla site is surrounded by scrub to two meters, and maybe that has more of an influence than I imagine (I've been to Eucla and it's a wind-swept place; that the wind data is so mild for this station continues to bug me).
I'm not posting the reports en masse, but happy to provide on request to anyone who is interested.

68

OzEA_DBWD0068

Alex
Subject: BoM station replacements
Date: 2010-09-15 (at 12:01:58)


For the problomatic BoM stations here is a list of replacements to be ordered shortly. I have plotted these using a .kml file in Google Earth. If this is of interest to you send me an email.

* BoM 031209; Cooktown Airport.
>> Replaced by 31213, CAPE FLATTERY - Some higher ground to the East, but not much inhibiting the prevailing wind.

* BoM 003003; Broome Airport. Low lying (10m), with protection from the town etc (at ~20m) to the immediate S/SW. No great surprise here.
>> Replaced by 003096; WEST ROEBUCK - Flat surroundings.

* BoM 005007; Learmonth Airport. Clearly well protected.
>> Replaced by 5016; Onslow - Potential shielding from residential housing... will see.
and 6072; EMU CREEK - Higher ground to the East, this should not effect the prevailing wind.

* BoM 009741; Albany Airport. Again not so obvious, but getting more so! There is a ~10m lip right there beside the airport.
>> Replaced by 9581; MOUNT BARKER - Has some higher ground to the west which should not effect the prevailing wind.

* BoM 011003; Eucla. Something of a surprise; this one looks exposed.
>> Replaced by 11052; FORREST - Higher ground with no apparent wind blocks.
and 11053; RED ROCK - On the coast

The following replaced stations were replacements in their own right, see comment #43 for previous development.

* BoM 031210; Mareeba Airport. Has some elevation (~470m), but there is much higher stuff (~1000m) 10-20 km away to the S and E.
>> Replaced by 31034; KAIRI RESEARCH STATION - Some higher ground surrounding the site, but generally flat agricultural lands

* BoM 060141; Taree airport. Low lying and close to the coast, but with an arc of higher stuff (100+ m hills) to the S and SW, ~15 km away... Maybe some sort of local effects in play.
AIRPORT AWS
>>Replaced by 61054; NELSON BAY - Around 80km south of Taree, the best alternative available.

* BoM 084143; Combienbar AWS (Vic). Not obvious; about 50 km inland at ~635m. Some higher stuff to the SW, and a fair bit of lumpiness around.
>>Replaced by 69137; GREEN CAPE AWS - right on the tip of Green Cape, see nothing inhibiting wind here.

* BoM 009178; Gingin Aero. Not so obvious this one, but perhaps 'over the lip' (in the shadow) of the rise from the coast.
>>Replaced by 9215; SWANBOURNE - Top of a 30m hill, surrounded an open area 

69

OzEA_DBWD0069

francis
Subject: replacement data: BtCC R1 2009, 5 sites
Date: 2011-02-28 (at 16:05:52)


Here are data files for the 5 replacement sites:
raw half hour data (57 KB gziped flat / text file)
processed hour level data (41 KB gziped flat / text file)

003096 (West RoeBuck) is meant to replace 003003 (Broome Airport)
009215 (SwanBourne) replaces 009178 (Gingin Aero)
011052 (Forrest) replaces 011003 (Eucla)
031213 (Cape Falttery) replaces 031209 (Cooktown Airport)
069137 (Green Cape) replaces 084143 (Combienbar)

In the first case (West RoeBuck), the wind histogram is very low with mode at ~2.5 m/s and I tentatively conclude that this area does not have a useful wind resource.

For SwanBourne and Forrest the histograms are modest, with the mode ~ 4-5 m/s, and tail up around 10 m/s. These may not be great sites, but we will persevere with them for now.

Cape Falttery and Green Cape display strong wind histograms for the considered data.

In all cases there are some missing days or parts of days, but these NaN runs are very modest (compared to the solar data at least).

Note: a wrap up of the entire data output for the Round One (R1) 2009 will be put in place in coming weeks. Right now need to get on with the 2003 data.

70

OzEA_DBWD0070

francis
Subject: Final Round One Wind Data (2003)
Date: 2011-03-01 (at 16:53:43)


After the selection of the initial 40, rejection of 9, obtaining replacement data for 5 (and rejecting one of these), we have 35 BoM stations with wind speed data as what I am calling the final round one selection. These are:

BoM_047048 NSW (-32.0012,141.4694) BROKEN HILL AIRPORT AWS
BoM_056238 NSW (-30.5273,151.6158) ARMIDALE AIRPORT AWS
BoM_069137 NSW (-37.2622,150.0504) GREEN CAPE AWS
BoM_069138 NSW (-35.3635,150.4827) ULLADULLA AWS
BoM_070217 NSW (-36.2939,148.9725) COOMA AIRPORT AWS
BoM_070330 NSW (-34.8085,149.7312) GOULBURN AIRPORT AWS
BoM_061392 NSW (-31.7416,150.7937) MURRURUNDI GAP

BoM_033295 QLD (-19.4569,147.4833) ALVA BEACH
BoM_039322 QLD (-23.5293,151.2763) RUNDLE ISLAND
BoM_040764 QLD (-27.9390,153.4283) GOLD COAST SEAWAY
BoM_041359 QLD (-27.4034,151.7413) OAKEY AERO
BoM_031213 QLD CAPE FLATTERY

BoM_018116 SA (-33.7081,136.5026) CLEVE AERODROME
BoM_018195 SA (-32.8427,135.1515) MINNIPA DPI
BoM_021133 SA (-33.7676,138.2182) SNOWTOWN (RAYVILLE PARK)
BoM_022046 SA (-35.1121,137.7395) EDITHBURGH
BoM_023373 SA (-34.4761,139.0056) NURIOOTPA VITICULTURAL
BoM_023875 SA (-35.5695,138.2864) PARAWA (SECOND VALLEY FOREST AWS)
BoM_026021 SA (-37.7473,140.7739) MOUNT GAMBIER AERO
BoM_026095 SA (-36.9655,139.7164) CAPE JAFFA (THE LIMESTONE)
BoM_018217 SA (-34.2524,135.7135) CUMMINS AERO

BoM_091245 TAS (-40.6828,144.6900) CAPE GRIM BAPS
BoM_092045 TAS (-40.9928,148.3467) EDDYSTONE POINT
BoM_094155 TAS (-43.2397,148.0025) TASMAN ISLAND
BoM_097080 TAS (-42.9850,145.5022) LOW ROCKY POINT

BoM_088051 VIC (-37.0194,144.5203) REDESDALE
BoM_090171 VIC (-38.3148,141.4705) PORTLAND (CASHMORE AIRPORT)
BoM_090186 VIC (-38.2867,142.4522) WARRNAMBOOL AIRPORT NDB
BoM_085151 VIC (-38.5647,146.7479) YARRAM AIRPORT
BoM_079101 VIC (-37.2281,143.2006) PYRENEES (BEN NEVIS)


BoM_008051 WA (-28.7953,114.6975) GERALDTON AIRPORT
BoM_009215 WA (-31.9558,115.7619) SWANBOURNE
BoM_009518 WA (-34.3728,115.1358) CAPE LEEUWIN
BoM_009542 WA (-33.6825,121.8275) ESPERANCE AERO
BoM_011052 WA (-30.8453,128.1092) FORREST

The current focus is 2003, as presented below (other years processed as needed), and for 2003 there are five stations (italicised) that do not cover this year (085151, 079101, 018217, 061392 and 031213), leaving 30.

Here is the 2003 data: OzEA_wind_BtCC_R1_final_hr_2003.flat.gz (0.3 MB gziped flat / txt file)

For these 30 stations, I have eyeballed the data, and note in relation to missing data that:

026095 SA CAPE JAFFA missing most of July
021133 SA SNOWTOWN somewhat sketchy / patches of missing data
039322 QLD RUNDLE ISLAND some patches of missing data in Feb and March
069138 NSW ULLADULLA AWS a few modest runs (of days) of missing data
069137 NSW GREEN CAPE AWS missing data in march and in Oct/Nov

Also, I have plotted and examined histograms of the 2003 wind speed data from the 30 stations, and note that:

WA: all ok; 009518 (Cape Leeuwin) strong
TAS: while all four stations measure strong winds, and the NW (Cape Grim) station is very strong with the mode at ~8 m/s, the two southern stations (097080 & 094155) have low modes (down around ~2 m/s).
SA: mostly ok, except perhaps 026021 (Mt Gambier Areo), where there are some 1500 zero values. It appears that 022046 (Edithburgh) has the strongest data, and 023373 (Nuriootpa Viticultural) the weakest.
VIC: all ok. An obvious state for establishing more stations: strongest -> weakest: 090186, 090171, 088051
NSW: 070330 (Goulburn Airport) and 070217 (Cooma Airport) both have a lot of zeros, otherwise all ok, and with 069137 (green cape) strong.
QLD: all ok, but with 041359 (Oakey Aero) having lots of zero values, and with 033295 (Alva Beach) slightly bi-modal. 039322 (Rundle Island) is strong.

Recall that we are focused on this data for its variability information as much as (if not more than) the absolute values. This is because a BoM wind station is not necessarily placed where a wind farm builder might build. But, there is a balance between these considerations that we will need to consider further.

71

OzEA_DBWD0071

Wayne Cook
Subject: Prevailing winds Mt Barker WA
Date: 2011-09-30 (at 14:39:19)


Hi,
I'm might be posting inappropriately here but I have a wind question fir Mt. Barker WA. Can anyone tell me what are the prevailing winds in mt barker. I'm aware they get strong southlies in the winter. What about summer or other times of the year? Please email to waynecoo@yahoo.com or post here.Many thanks.

Cheers


Wayne

72

OzEA_DBWD0072

Francis
Subject: Response to #71
Date: 2011-10-03 (at 10:00:23)


Wayne, this data is not to hand here. You could look at the Albany data we have processed here, or you could look around on the BoM website (e.g. http://www.bom.gov.au/climate/averages/wind/selection_map.shtml). For Mt Barker exactly, BoM has a station there (station number 009581, been there since 1886!) and you will be able to obtain historical wind data from BoM if their web based stats don't give you what you need.

[Show Full Lists]


Post Comment:

A name or alias, email and concise subject are required. Your email will not be abused.
Comments are required to be polite and on topic (commenting etiquette)

Name:*
Email:*
Website:
Subject:*
What is the longhand for 'Oz'? :*


fc - 16th June 2010