An Automated Weather Database System

Transcription

1 An Automated Weather Database System F. Zhou, D.J. Smith and S. Khan CSIRO Land and Water, Canberra Technical Report 19/02, May 2002 CSIRO LAND and WATER

2 An Automated Weather Database System F. Zhou, D.J. Smith and S. Khan CSIRO Land and Water Technical Report 19/02, May 2002

3 Copyright 2001 CSIRO Land and Water. To the extent permitted by law, all rights are reserved and no part of this publication covered by copyright may be reproduced or copied in any form or by any means except with the written permission of CSIRO Land and Water. Important Disclaimer To the extent permitted by law, CSIRO Land and Water (including its employees and consultants) excludes all liability to any person for any consequences, including but not limited to all losses, damages, costs, expenses and any other compensation, arising directly or indirectly from using this publication (in part or in whole) and any information or material contained in it.

4 Table of Contents INTRODUCTION 1 WEATHER DATA COLLECTION AND REPORT NETWORK 1 WEATHER DATABASE 2 Database Structure 2 Weather Data Records 3 WEATHER DATABASE SYSTEM MANAGEMENT 4 System Installation 4 System Operation 4 Start-up and Shut-down 6 System Configuration 7 System Monitoring and Error Reporting 8 Weather Data Check and Patching 9 Weather Reports and Public Access 10 LIST OF FIGURES Figure 1: Weather data collection and report network 1 Figure 2: Overall structure of the weather database 2 Figure 3: Hourly data records 3 Figure 4: Data flow in the weather data collection system 5 Figure 5: Working procedure of weather database management program 5 Figure 6: Download waiting 6 Figure 7: System termination 7 Figure 8: Error log table 9 Figure 9: Report re-generation 10 LIST OF TABLES Table 1: Instruments and sensors for weather data measurement 2 Table 2: Tables in the weather database management system 3 Table 3: Data fields in the hourly weather data record 4 Table 4: Weather system table 7 Table 5: System configuration work 8 LIST OF APPENDICES Appendix 1: Sample Initialisation File 11 Appendix 2: List of Error Messages and Actions 13 Appendix 3: Data Patching Protocol 15 Appendix 4: Sample Weather Report to Bureau of Meteorology 16 Appendix 5: Sample 7 Day Weather Report 17 Appendix 6: Sample 14 Day Weather Report 18 Appendix 7: Sample Current Hour Weather Report 19 Appendix 8: Sample Last 12 Hour Weather Report 20 Appendix 9: Sample Yesterday Weather Report 21 Appendix 10: Sample Monthly Weather Report 22

5 INTRODUCTION The demand for more timely and localised weather data has resulted in the increasing use of Automatic Weather Stations (AWS). Data from these stations are commonly used to calculate daily reference evaporation and to predict disease and pest outbreaks. Data may also be transmitted to forecasting authorities if needed. As more descriptive biophysical models are developed to assist in land and water management and crop production, the need for high quality, contiguous weather data sets will increase. As major environmental issues such as climate change are monitored, weather data will continue to be invaluable. One of the first tasks that the CSIRO Griffith Laboratory undertook was to collect weather data. The weather data collection started in 1931 using manual observations. By 1970, a computerised system using punched cards had replaced the manual data collection. In October 1981, the weather collection system was upgraded to continuous automatic logging of hourly data. The weather data collection system could no longer serve its function in the new millenium and a new weather database management system was developed and commenced operation in October The automated weather database management system has the following features: Automatic scheduling of routine weather data collection and reporting Continuous system monitoring and error reporting Minimal human involvement High reliability Low development and operational cost The application is based on the widely used Microsoft Access and it is independent of the data logger software. Therefore, the weather database management system has the potential to be applied to other similar data collection tasks. WEATHER DATA COLLECTION AND REPORT NETWORK The weather data collection and report network consists of four AWS located at Griffith, Hay, Finley, Tullakool, and the weather database management system based in Griffith Laboratory, CSIRO Land and Water (Figure 1). Each weather station is equipped with one logger (manufactured by Campbell Scientific Inc, USA) sensors, instruments and a modem. The weather database management system consists of Microsoft Access application software and the data logger software (PC208W) running in a Windows NT environment installed on a dedicated weather server. The automated database management system retrieves the weather data, checks for any errors, updates the database and prepares the weather reports on an hourly or daily basis. The weather server communicates with the weather stations via a modem and phone link and communicates with the other servers through the Internet. Table 1 lists the sensors and instruments used for weather data measurement. Hay AWS National Weather Data Server Finley AWS Weather Database Management System Griffith AWS CSIRO L&W Web Server Tullakool AWS Figure 1: Weather data collection and report network 1

6 Sensor or instrument Weather data Accuracy Unit recorded Three-cup anemometer Wind speed ±1.5% km Tipping bucket rain gauge Rainfall ±0.25 mm mm Silicon solar cell Solar irradiance ±3.0% MJ/m 2 Semiconductor temperature Dry-bulb temperature ±0.1 o C o C sensor Copper-constantan thermocouple Wet-bulb depression ±0.3 o C o C Table 1: Sensors and instruments for weather data measurement WEATHER DATABASE Database Structure Data in the weather database is organised and contained in tables, as shown in Figure 2. Data tables hold the hourly weather data collected from the weather stations and are updated hourly or daily when the system is running. System tables contain the parameters used for system management and the messages generated in the process. Table 2 lists the tables in the current weather database. Figure 2: Overall structure of the weather database 2

7 Table Name Type Comment Comm Parameters System Communication parameters (for record only) Error Log System Error messages Event Log System Events of the weather database system. Currently, only the start-up event is recorded. Event Type System Description of the events Long Term Weather Data System Average long term weather data Weather System System Weather system parameters Weather Club System People involved in the weather system management Weather Data (Finley) Data Hourly weather data from Finley station Weather Data (Griffith) Data Hourly weather data from Griffith station Weather Data (Hay) Data Hourly weather data from Hay station Weather Data (Tullakool) Data Hourly weather data from Tullakool station Table 2: Tables in the weather database management system Weather Data Records Figure 3 shows the hourly weather data records in a data table and Table 3 lists the data fields in the record. The Date field is set as the primary key and identifier of a unique record in the data table. If the weather data of a particular hour is not available for some reason, a blank record will be appended to the table and a warning message sent out. Therefore, there will always be a unique record for each hour. The blank records will be automatically filled later when the data become available. The most likely reason for a blank record is that a communication link cannot be established with the data logger when the database is to be updated. The blank records will be filled at the next scheduled update time if the communication link is resumed. An unfilled blank record after re-establishment of the communication link and data collection means that the data for the hour was not in the memory of the data logger and is subsequently lost. However, the data for the hour can easily be patched in by the weather administrator. Figure 3: Hourly data records 3

8 Field Name Comment Date A date and time identifier (dd/mm/yyyy hh:00) of the hourly weather data record Wind Speed (At 2m) Spot wind speed, recorded (km/hr) Wind Speed (Max) Maximum wind speed in the hour, recorded (km/hr) Rain Total rain in the hour, recorded (mm/hr) Solar Irradiance Total solar irradiance in the hour, recorded (Mj/m 2 /hr) Dry Bulb Temperature (Hourly) Spot dry-bulb temperature on the hour, recorded ( o C) Dry Bulb Temperature (Max) Maximum dry-bulb temperature in the hour, recorded ( o C) Dry Bulb Temperature (Min) Minimum dry-bulb temperature in the hour, recorded ( o C) Dry Bulb Temperature (Mean) Mean dry-bulb temperature in the hour, calculated ( o C) Relative Humidity (Hourly) Relative humidity, calculated (%) WB Wet-bulb temperature, calculated ( o C) DP Dew point temperature, calculated ( o C) Comment Add the comment if any field is patched Table 3: Data fields in the hourly weather data record WEATHER DATABASE SYSTEM MANAGEMENT System Installation The weather database management system consists of a compiled Microsoft Access database file (MDE), a Windows DLL file (dllweather.dll ) and an initialisation (INI) file. It was developed in a Windows NT environment and it can run in both Windows NT and Windows 95 operating systems. The initialisation file has the same file name as the MDE file but with the INI extension name. The weather database management system requires that Microsoft Access, Microsoft Outlook and the PC208W logger software be installed on the system. Edit the INI file to include system-specific paths to these software applications. To install, copy the MDE and INI file into the working directory of the weather database management system. Copy the DLL file into the Windows system directory and make sure that the MFC42d.dll file exists in the system directory. System Operation The weather database management system consists of the database management program and the data logger program. Microsoft Access hosts the database management program and the PC208W logger software communicates with the data loggers at the weather stations. At a specified frequency, the data logger software sends the data request to the weather stations through the modem and phone line and the weather stations send back the weather data if the telecommunication is successful. Figure 4 shows the data flow between different parts of the system. At the same time, the database management program will determine the data record to be added for the hour in the case of an hourly update, extract the data, check if the data is in a reasonable range and fill each field of the record. This will happen to a set of records at the updating hour in the case of a daily update comprising 24 hourly records. At the same time, the program will try to fill any blank records from previous hours, if any. Once the database is updated, the program will prepare the weather reports. Since the database and the data logger software act on the same system clock, their operations are synchronised. Figure 5 shows the working procedure of the database management program. 4

9 weather data weather station modem modem data request data logger software weather database management system Windows NT server Figure 4: Data flow in the weather data collection system Initialisation Start the and data logger software if they are not running Start the loop and timer Determine the record(s) to be added Extract and check the data Update the database Prepare the reports Figure 5: Working procedure of weather database management program The system is designed to run unattended. It has the potential to automatically handle the switch between daylight saving time and Australian eastern standard time. It has a built-in diagnosis function for error conditions, which will be discussed later. If the system is shut down for a period of time and re-started, it will calculate how many record(s) need to be added into the database. 5

10 Start-up and Shut-down Starting the weather database management system is just like starting any other Windows applications or opening their files, for instance, by double clicking the icon of the MDE file. Once the weather database management system is started, it will detect if the program and the data logger program are already running. If these programs are not running, the weather database management system will start the programs. The and the data logger program are specified in the initialisation file. If the data logger program is started by the database management system, a dialog will pop up and display how long it will wait for the logger program to retrieve the data (Figure 6). The waiting time is specified in the initialisation file and can be adjusted. If the data logger program has been running while the database management system is shut down, the dialog can be immediately closed. A timer will run continuously once the weather database management system is started. To shut down the system properly, open the Terminate Scheduler dialog and click the Termination button (Figure 7). Close the dialog and then the database. If the Close button of the database is accidentally clicked while the timer is running, the weather database management system must be re-started. Terminate the Microsoft Access process associated with the weather database from the Windows Task Manager and then restart the database. Figure 6: Download waiting 6

11 Figure 7: System termination System Configuration The behaviour of the weather data management system may be tailored by modifying the system parameters in the initialisation file (see the sample INI file in Appendix 1) and the Weather System table in the database (Table 4). The database management system must be shut down and re-started for any change to be effective. Field Name Comment Site ID Site Description Longitude Latitude MetBureau ID Station ID Data Table Data File Update Frequency Update Hour Table 4: Weather system table Unique ID for each site of the system If a site is an active weather station, the site name will be used for report name generation. Longitude of a site Latitude of a site Station identifier used in the weather report (METARAWS format) for Bureau of Meteorology Station identifier used in the weather report (SYNOPTIC format) for Bureau of Meteorology Data table name for storing the hourly weather data Data file name for storing the unprocessed weather data Either hourly or daily. Hourly is the default setting. The hour must be specified if weather data from a site is updated daily An active weather station, or the weather station being used, is represented by one record with both data table and data file specified in the Weather System table. The default update frequency for the data records from a weather station is hourly unless otherwise specified. The system parameters should only be changed when it is really necessary. Table 5 serves as a road map for system configuration changes. 7

12 Task Where Parameter Switch the update frequency between hourly and daily Weather system table Update Frequency. Specify either 1 or 24. Change the update hour for the station where daily data Weather system table Update Hour. Enter a value between 0 and 23. record update is applied. Include (or remove) a weather station in (or from) the routine management work Weather system table Data Table and Data File. To include, specify the data table and data file. To remove, leave these two fields blank. Change the station identifier Weather system table MetBureau ID or Station ID Change the data file name Weather system table Data File Change the data table name Weather system table Data Table Change the addresses INI file cmailweatheraddress or cmailbureauaddress Turn the function on/off INI file cmailerr or cbommailon 1 on, 0 off Change the or data INI file cmailprogramexe or logger software Start the data logger software from the weather database management system or not Change the minute when the database is updated Change the hour when the 7 day and 14 day report are prepared INI file INI file INI file cloggerprogramexe crunloggerprogram 1 on, 0 off cupdateminute. This should be set to the beginning of an hour as required by the Bureau of Meteorology c7and14daysreporthour. This should be set to an early hour of the day. Change the report names. INI file clatestdailyreport or clast12hoursreport or ccurrenthoursreport Change the data format INI file Data format section Change the reasonable data range INI file Data range section Table 5: System configuration changes System Monitoring and Error Reporting Occasionally, the weather stations may not function properly or the measured weather data may be out of range. Therefore, one of the functions of the weather system is to monitor the condition of the weather stations continuously. If the weather system detects an error condition, it will send an error report to the mailing list weather.data@grf.clw.csiro.au for attention or action depending on the type of the error. The weather system can automatically correct some types of errors in the data received after it sends out a reminder. In addition, the weather system has a function to indicate if itself is still working and this may be activated by modifying the initialisation file. The error messages are stored in the Error Log table for reviewing and data patching (Figure 8). A comprehensive list of error messages and the corresponding actions are given in Appendix 2. 8

13 Figure 8: Error log table Weather Data Check and Patching Before it is added into the database, each weather datum is checked against its reasonable range, which is specified in the initialisation file. If the data is out of range, an error message will be sent out and this may require a trip for a maintenance check of the instrument used for measuring the data. Therefore, the error report from rigorous data checking may serve as an early warning of an error condition before it becomes chronic. The reasonable data range may need to be adjusted in different seasons of a year to reflect seasonal variation. For instance, the upper temperature limit could be lowered in the winter season. Although the automatic check function has proved to be capable of filtering out the abnormal weather data for most of time, a quick look at the weather reports is worthwhile to pick up erroneous but within range data. For example, a large rainfall event on a seemingly dry day (high radiation, low humidity) was actually from a sprinkler operating near a weather station! When a weather datum is out of range, the weather system will not update the relevant data field if it cannot determine an appropriate value for the field. This will leave a blank field in the data record, which needs to be patched manually. During working hours, the patching can be done within an hour after the error is reported and the daily weather reports calculated in the early morning of next day will contain the patched data. The patched data may be estimated from the data record of the closest weather station in the same hour or from the data record of a previous hour of the same station when sound data was available. In the database, the only original data set is the hourly data stored in the data tables of the weather stations. Therefore, the patching should only be applied to the blank fields in the data tables and the derived data is re-calculated from the patched data set. This will ensure data quality and consistency between different reports. A comment should be added to the comment field of the data record to indicate what kind of change has been made. The manual data patching protocol is described in Appendix 3. 9

14 Weather Reports and Public Access Weather reports are generated hourly, daily and monthly. Weather data is sent to the Bureau of Meteorology by at the beginning of each hour for national weather reporting and aviation control. The weather report contains the data in METARAWS format and it also contains the data in SYNOPTIC format every three hours. Sample weather data reports for Bureau of Meteorology are included in Appendix 4. The daily weather reports are generated at 6:00 am for the Griffith, Finley and Hay stations and at 5:00 am for the Tullakool station. The daily reports provide weather data for the last 7 and 14 days and a comparison with the long-term average weather data (Griffith only). The current hour and last 12 hour (Griffith only) weather reports are also prepared at the beginning of each hour. The yesterday weather report contains the daily weather data for all the weather stations. The monthly report is created on the first day of each calendar month for all the stations. Samples of these weather reports are included in Appendices Daily and hourly weather data is available on the web site ( for public access. The web server of CSIRO Land and Water in Perth retrieves the weather reports every hour. For the convenience of the users of weather reports, two files are created for each report. The file of DAT extension name is ready for viewing while the file of CDT extension name is purely a data file, which may be used for further analysis (for example, importing into an excel spreadsheet). The daily or hourly weather data may also be extracted from the database using the Generate Daily Report or Generate Hourly Report functions. Figure 9 shows the Daily Report dialog from which the daily data report may be created. Figure 9: Report re-generation 10

15 Appendix 1: Sample Initialisation File [Weather system] ; weather server name cweatherserver = Weather Server ; program and mailing list cmailprogram = Microsoft Outlook cmailprogramexe = C:\Program Files\Microsoft Office\Office\outlook.exe cmailweatheraddress = weather.data@grf.clw.csiro.au ; send error message via . 1 yes, 0 no. Same below. cmailerr = 1 ; send a message to indicate that the database has been updated cmailupdaterep = 0 ; data logger program cloggerprogram = PC208W cloggerprogramexe = D:\PC208W\BIN\PC208W.EXE ; start the logger program from the weather program crunloggerprogram = 1 ; waiting time for data download before updating the database cdownloadwaitingminutes = 10 ; the minute when the database is updated every hour cupdateminute = 2 ; the data files are updated in the previous hour cadvancedfileupdatehour = 1 ; the hour when the daily reports are generated c7and14daysreporthour = 6 ; the Julian day when the 7 day report starts to provide the comparison ; with long term weather data cfirst7dayreportdayno = 7 ; the name of the weather reports, generated hourly clatestdailyreport = yesterday.dat clast12hoursreport = last12hours.dat ccurrenthoursreport = currenthour.dat ; 7 day and 14 day report name consists of the first three characters ; of the site name plus 7 or 14, ; eg gri7.dat and gri7.cdt is the 7 day report for Griffith ; monthly report name consists of the first three characters ; of the site name plus _m plus the number of the month, ; eg gri_m10.dat is the October report for Griffith [Met Bureau] ; the file which records the data sent to the Bureau cbomfile = Bureau.dat ; send the weather report to the Bureau via cbommailon = 1 ; mail address cmailbureauaddress = nswcomms@bom.gov.au 11

16 [Campbell Logger] ; Data format cdefaultnumberofcomma = 19 cnoofcomma_griffith = 20 cnoofcomma_finley1 = 28 cnoofcomma_finley = 19 cnoofcomma_hay = 19 cnoofcomma_tullakool = 19 cposloggersingnature = 1 cposyear = 2 cposday = 3 cposhour = 4 cposrain = 5 cposchksum = 6 cposwindrun = 7 cpospaneltemp = 8 cposbatteryvol = 9 cposirradiance = 10 cposambtemp = 11 cposrh = 12 cposmaxta = 13 cposmaxrh = 14 cposminta = 15 cposminrh = 16 cposspotta = 17 cposspotrh = 18 cposdepress = 19 cposmaxwind = 20 ; Data range cmaxrain = 25 cminrain = 0 cmaxwindspeed = 75 cminwindspeed = 0 cmaxirradiance = 4.2 cminirradiance = 0 cmaxtemperature = 45 cmintemperature = -4 cmaxrh = 100 cminrh = 10 cmaxwbdepress = 20 cminwbdepress = 0 ; Conversion factors 12

17 Appendix 2: List of Error Messages and Actions Error Message Comment Action The ini file {file name} could not be found. Failed to read the ini file completely. Zero TimeDivider in the ini file. No system data available in the weather system table. The update hour {hour} in the weather system table is out of range. The update hour has not been set in the weather system table for the daily update of {table name}. File {file name} is not found. The system time is behind the date of last record in the table {table name} Update hour for {table name} is earlier than the changing hours of daylight saving time. Update hour for {table name} is smaller than the difference between standard time and daylight saving time. The date of last record {date time} in the table {table name} was unexpected. No bureau file {date time} would be created due to the unexpected record date. File {file name} {date time} was not created in the expected hour. If similar message is received next hour, check the system. Add blank record {date time} to the table {table name}. The INI file is not in the directory where the weather database resides. The parameter ctimedivider in the INI file is zero. No active weather station is specified in the Weather System table. If the data records of a weather station is to be updated daily, the update hour must be specified. The data file specified in the Data File field of Weather System table could not be located. The system time is earlier than the time stamp of the last record. This is to avoid creating two records of the same time stamp when the clock moves back after the daylight saving. Inconsistency between the expected time stamp of last record and the actual time stamp of the last record. Warning message. No weather data would be sent to the Bureau of Meteorology. This message accompanies the above message. The data file was not updated. Maybe the phone line is busy, or the weather station is not working, or the data logger program is not running. This message accompanies the above message. The hourly weather data is not available so a blank record is added with only the date field filled. Copy the required INI file to the directory. Copy a correct INI file to the directory. Change the parameter to a positive non-zero integer. Check the weather system table. Change the parameter to a value between 0 and 23. Specify the update hour of the weather station in the weather system table. Check the path or the file name. Check the system time of the computer. Specify an update hour which is later than the switching hour, eg from 4:00 am in AEST time zone. Same as above. Check the computer time. If it is right, check the time stamp of last record of the table. Same as above. Often, this message is due to failure to connect the weather station temporarily. Check the mentioned components of the system if the error messages continue. Same as above. Could not add the record of duplicated date {date time} in the table {table name}. Check the computer time 13

18 Unknown error in adding the record of the date {date} in the table {table name}. No bureau file would be created because the bureau station data was not found in the system table. No entry would be created in the bureau file for the station {identifier} because of the unexpected date of last record. No bureau file was created for the hour {date time} because of the unexpected date of last records in all relevant tables. System information not found in the weather system table. Site name unknown in the weather system table. Zero count of data items. The reports are not created. No record found for last 12 hours (back from {date time} in the table {table name}. No hourly record is found between {date time} and {date time} in the table {table name}. Less than 24 hourly records are found between {date time} and {date time} in the table {table name}. Update blank record for the record {date time} in the table {table name}. {data field} {number} out of range for the record {date time} in the table {table name}. Missing {data field} for the record {date time} in the table {table name}. Negative Irradiance set to 0 for the record {date time} in the table {table name}. Basically, the database could not be updated for some reasons. The identifier(s) for the weather stations could not be found for creating the weather report. This is an accompanying message of The date of last record {date time} in the table {table name} was unexpected. Same as the above except it applies to all the weather stations. Field(s) for active weather stations is blank. Specifically, the field of Site Description is blank. The weather data field(s) of a group of hourly records used for daily calculation is blank. Missing records. This should not happen if the database is upgraded by the database management system all the time. Same as above. Same as above. Just a reminder. The data item fails in the data range check. The data item is not retrieved from the weather station. A reminder accompanying the error message for out-of-range irradiance. Check the database. Specify the identifiers for the weather stations which are included in the weather report to the Bureau. Same as the action for the message that it accompanies. Same as above. Check the weather system table. Check if Site Description field has been filled for the active weather stations. Check the data records and patch the data. Check the data tables. Delete the block of records up to the last continuous record. Restart the database. Same as above. Same as above. If the error message is repeated for the subsequent hours, check the measuring sensor or instrument. Patch the data. Check the data logger. 14

19 Appendix 3: Data Patching Protocol The patching protocols are the same for all weather variables, with the exception of rainfall. Often it is not a whole record (all data for the hour) that is missing, but just one parameter which is flagged in the error log. Obviously, if a sensor is down, it is imperative that the problem be rectified as soon as possible to capture real data and to minimise patching. The patching protocols are as follows: Up to three hours missing on an individual parameter or whole record: Extrapolate between the last known and the next good reading. For eg 8.00am 10.0 o C 9.00am 10.00am 11.00am 12.00am 14.0 o C would become 8.00am 9.00am 10.00am 11.00am 12.00am 10.0 o C 11.0 o C 12.0 o C 13.0 o C 14.0 o C Where there are more than three hours missing on an individual parameter or whole records: Copy the appropriate parameter or whole record as follows. Missing data from Griffith are patched with good data from Hay and vice versa. Missing data from Finley are patched with good data from Tullakool and vice versa. Rainfall patching protocol is as follows: In the majority of instances the patched data will most likely be zero for each hour not recorded. This will be the case for the three remote stations (Hay, Finley and Tullakool). If unsure, have a look at RH, WB, DP and radiation. If RH is close to 100, WB and DP are similar and radiation is low, there may have been rain. Also have a look at the similar station (Hay and Griffith, Finley and Tullakool) and see if any rain was recorded there. The best we can do for the remote stations is manual rainfall for the day from nearby properties. This has not been needed to date. The Griffith rainfall can be patched more confidently from the manual rain gauge reading, by subtracting the amount already recorded by the AWS and filling in the missing hours, giving equal weight to each hour. 15

20 Appendix 4: Sample Weather Report to Bureau of Meteorology ZCZC METARAWS GTHX 0100 ///08/10KT //// 26.1/10.7 ////// RMK RF//.//000.0= GTHX AAXX /// /// = METARAWS FILX 0100 ///06/09KT //// 27.6/10.2 ////// RMK RF//.//000.0= FILX AAXX /// /// = METARAWS HAYX 0100 ///07/09KT //// 29.1/12.5 ////// RMK RF//.//000.0= HAYX AAXX /// /// = NNNN 16

21 Appendix 5: Sample 7 Day Weather Report Report generated on 11-Jan-2000 Griffith Laboratory CSIRO Land & Water Weather Summary (7 days) for Griffith NSW Date MaxT MinT Wind Sun Rain ET C C km/hr Mj/Sqm mm mm 04-Jan Jan Jan Jan Jan Jan Jan Average Total Abbreviations: MaxT - Maximum temperature of the day MinT - Minimum temperature of the day Wind - Average hourly wind speed of the day Sun - Total solar irradiance of the day Rain - Total rainfall of the day ET - Evaporation of the day Comparison with long term average: Average temperature is 1.9 degree(s) below normal. ET is 12 percent above normal. Rain for January (to last midnight in the 7 day period) is 0.0 mm. Average for the same period is 11.2 mm. Rain for this year is 0 mm. Average for the same period is 11 mm. Comparisons are based on average weather data ( ) collected by CSIRO. 17

22 Appendix 6: Sample 14 Day Weather Report Report generated on 11-Jan-2000 Griffith Laboratory CSIRO Land & Water Weather Summary (14 days) for Griffith NSW Date Dry bulb Rel. humidity DewPt Wind Rain Sun ET (Deg C) (%) (Deg C) (Km) (mm) (Mj/Sqm) (mm) Mean Max Min Mean Max Min 28-Dec Dec Dec Dec Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan

23 Appendix 7: Sample Current Hour Weather Report Report generated on 11-Jan-2000 Griffith Laboratory CSIRO Land & Water Latest Hourly Weather Report Site Date Time Wind Rain Sun DBT RH DewPt MaxWind AEST Km/h mm Mj/Sqm C % C Km/h Griffith : Finley : Hay : Total (since midnight) Site Wind Rain Sun Km mm Mj/Sqm Griffith Finley Hay

24 Appendix 8: Sample Last 12 Hour Weather Report Report generated on 11-Jan-2000 Griffith Laboratory CSIRO Land & Water Weather Data (Griffith) for 12 Hours Date Time Wind Rain Sun DBT RH DewPt AEST Km/h mm Mj/Sqm C % C : : : : : : : : : : : : Total Max Min

25 Appendix 9: Sample Yesterday Weather Report Report generated on 11-Jan-2000 Griffith Laboratory CSIRO Land & Water Daily Weather Report Site Date DBT RH DewPt Wind Rain Sun ET C % C km mm Mj/Sqm mm Avg Max Min Avg Max Min Griffith Finley Hay Tullakool

26 Appendix 10: Sample Monthly Weather Report Report generated on 01-Nov-1999 Griffith Laboratory CSIRO Land & Water Weather Summary (Oct 1999) for Hay NSW Date Dry bulb Rel. humidity DewPt Wind Rain Sun ET (Deg C) (%) (Deg C) (Km) (mm) (Mj/Sqm) (mm) Mean Max Min Mean Max Min 01-Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Monthly Summary Number of days in the month: 31 Total Mean Max Min