An Automated Weather Database System
F. Zhou, D.J. Smith and S. Khan
CSIRO Land and Water, Canberra Technical Report 19/02, May 2002
C S I R O L A N D a n d W AT E R
An Automated Weather Database System
F. Zhou, D.J. Smith and S. Khan
CSIRO Land and Water Technical Report 19/02, May 2002
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.
Table of Contents INTRODUCTION
1
WEATHER DATA COLLECTION AND REPORT NETWORK
1
WEATHER DATABASE Database Structure Weather Data Records
2 2 3
WEATHER DATABASE SYSTEM MANAGEMENT System Installation System Operation Start-up and Shut-down System Configuration System Monitoring and Error Reporting Weather Data Check and Patching Weather Reports and Public Access
4 4 4 6 7 8 9 10
LIST OF FIGURES Figure 1: Weather data collection and report network Figure 2: Overall structure of the weather database Figure 3: Hourly data records Figure 4: Data flow in the weather data collection system Figure 5: Working procedure of weather database management program Figure 6: Download waiting Figure 7: System termination Figure 8: Error log table Figure 9: Report re-generation
1 2 3 5 5 6 7 9 10
LIST OF TABLES Table 1: Instruments and sensors for weather data measurement Table 2: Tables in the weather database management system Table 3: Data fields in the hourly weather data record Table 4: Weather system table Table 5: System configuration work
2 3 4 7 8
LIST OF APPENDICES Appendix 1: Sample Initialisation File Appendix 2: List of Error Messages and Actions Appendix 3: Data Patching Protocol Appendix 4: Sample Weather Report to Bureau of Meteorology Appendix 5: Sample 7 Day Weather Report Appendix 6: Sample 14 Day Weather Report Appendix 7: Sample Current Hour Weather Report Appendix 8: Sample Last 12 Hour Weather Report Appendix 9: Sample Yesterday Weather Report Appendix 10: Sample Monthly Weather Report
11 13 15 16 17 18 19 20 21 22
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 1999. 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. National Weather Data Server
Hay AWS Weather Database Management System
Finley AWS
CSIRO L&W Web Server
Griffith AWS Tullakool AWS
Figure 1: Weather data collection and report network 1
Sensor or instrument
Weather data recorded Wind speed Rainfall Solar irradiance Dry-bulb temperature
Three-cup anemometer Tipping bucket rain gauge Silicon solar cell Semiconductor temperature sensor Copper-constantan thermocouple Wet-bulb depression
Accuracy
Unit
±1.5% ±0.25 mm ±3.0% ±0.1 oC
km mm MJ/m2 o C
±0.3 oC
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
Table Name
Type
Comment
Comm Parameters Error Log Event Log
System System System
Event Type Long Term Weather Data Weather System Weather Club
System System System System
Weather Data (Finley) Weather Data (Griffith) Weather Data (Hay) Weather Data (Tullakool)
Data Data Data Data
Communication parameters (for record only) Error messages Events of the weather database system. Currently, only the start-up event is recorded. Description of the events Average long term weather data Weather system parameters People involved in the weather system management Hourly weather data from Finley station Hourly weather data from Griffith station Hourly weather data from Hay station 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
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/m2/hr) Dry Bulb Temperature (Hourly) Spot dry-bulb temperature on the hour, recorded (oC) Dry Bulb Temperature (Max) Maximum dry-bulb temperature in the hour, recorded (oC) Dry Bulb Temperature (Min) Minimum dry-bulb temperature in the hour, recorded (oC) Dry Bulb Temperature (Mean) Mean dry-bulb temperature in the hour, calculated (oC) Relative Humidity (Hourly) Relative humidity, calculated (%) WB Wet-bulb temperature, calculated (oC) DP Dew point temperature, calculated (oC) 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
weather data weather station
modem
data logger software
modem data request
weather database management system
Windows NT server
Figure 4: Data flow in the weather data collection system
Initialisation
Start the e-mail 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
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 e-mail 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 e-mail 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
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
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
Longitude Latitude MetBureau ID Station ID Data Table Data File Update Frequency Update Hour
Table 4: Weather system table 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
Task
Where
Parameter
Switch the update frequency between hourly and daily Change the update hour for the station where daily data record update is applied. Include (or remove) a weather station in (or from) the routine management work Change the station identifier Change the data file name Change the data table name Change the e-mail addresses
Weather system table
Update Frequency. Specify either 1 or 24. Update Hour. Enter a value between 0 and 23.
Weather system table
Weather system table
Weather system table Weather system table Weather system table INI file
Turn the e-mail function on/off Change the e-mail or data logger software Start the data logger software from the weather database management system or not Change the minute when the database is updated
INI file
Change the hour when the 7 day and 14 day report are prepared Change the report names.
INI file
Change the data format Change the reasonable data range
INI file INI file
INI file INI file
INI file
Data Table and Data File. To include, specify the data table and data file. To remove, leave these two fields blank. MetBureau ID or Station ID Data File Data Table cMailWeatherAddress or cMailBureauAddress cMailErr or cBOMMailOn 1 on, 0 off cMailProgramExe or 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. cLatestDailyReport or cLast12HoursReport or cCurrentHoursReport Data format section Data range section
INI file
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
[email protected] 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
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
Weather Reports and Public Access Weather reports are generated hourly, daily and monthly. Weather data is sent to the Bureau of Meteorology by e-mail 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 5-10. Daily and hourly weather data is available on the web site (http://www.clw.csiro.au/services/weather/) 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
Appendix 1: Sample Initialisation File [Weather system] ; weather server name cWeatherServer = Weather Server ; e-mail program and mailing list cMailProgram = Microsoft Outlook cMailProgramExe = C:\Program Files\Microsoft Office\Office\outlook.exe cMailWeatherAddress =
[email protected] ; send error message via e-mail. 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 e-mail cBOMMailOn = 1 ; mail address cMailBureauAddress =
[email protected]
11
[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
Appendix 2: List of Error Messages and Actions
Error Message The ini file {file name} could not be found.
Comment The INI file is not in the directory where the weather database resides.
Failed to read the ini file completely. Zero TimeDivider in the ini file.
The parameter cTimeDivider in the INI file is zero.
No system data available in the weather system table.
No active weather station is specified 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}.
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.
Could not add the record of duplicated date {date time} in the table {table name}.
Action 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.
Check the computer time
13
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.
Basically, the database could not be updated for some reasons.
Check the database.
The identifier(s) for the weather stations could not be found for creating the weather report.
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.
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.
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.
Zero count of data items. The reports are not created.
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.
No record found for last 12 hours (back from {date time} in the table {table name}.
Field(s) for active weather stations is blank. Specifically, the field of Site Description is blank.
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.
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}.
Same as above.
Check the data tables. Delete the block of records up to the last continuous record. Restart the database. Same as above.
Same as above.
Same as above.
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}.
The data item is not retrieved from the weather station.
Just a reminder.
The data item fails in the data range check.
A reminder accompanying the error message for out-of-range irradiance.
14
If the error message is repeated for the subsequent hours, check the measuring sensor or instrument. Patch the data. Check the data logger.
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 oC 9.00am 10.00am 11.00am 12.00am 14.0 oC
would become 8.00am 9.00am 10.00am 11.00am 12.00am
10.0 oC 11.0 oC 12.0 oC 13.0 oC 14.0 oC
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
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 11014 94705 46/// ///08 10261 20107 555 44777= METARAWS FILX 0100 ///06/09KT //// 27.6/10.2 ////// RMK RF//.//000.0= FILX AAXX 11014 94876 46/// ///06 10276 20102 555 44777= METARAWS HAYX 0100 ///07/09KT //// 29.1/12.5 ////// RMK RF//.//000.0= HAYX AAXX 11014 94701 46/// ///07 10291 20125 555 44777= NNNN
16
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 C
MinT C
Wind km/hr
Sun Mj/Sqm
04-Jan-2000 05-Jan-2000 06-Jan-2000 07-Jan-2000 08-Jan-2000 09-Jan-2000 10-Jan-2000
24.9 24.2 25.9 28.6 30.1 30.9 31.3
15.0 10.1 11.0 10.8 16.4 17.5 17.0
17.4 14.4 9.0 7.2 11.3 9.2 9.2
32.2 32.1 32.4 32.5 31.7 27.2 26.5
Average Total
28.0
14.0
Rain mm
ET mm
0.0 0.0 0.0 0.0 0.0 0.0 0.0
11.6 9.4 9.1 9.3 10.6 9.5 9.2
0.0
68.7
Abbreviations: MaxT MinT Wind Sun Rain ET
-
Maximum temperature of the day Minimum temperature of the day Average hourly wind speed of the day Total solar irradiance of the day Total rainfall of the day 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 (1962-1998) collected by CSIRO.
17
Appendix 6: Sample 14 Day Weather Report
19.2 19.4 19.2 17.7 19.0 21.2 24.4 20.7 17.3 18.5 20.4 23.3 23.9 24.1
Mean 15.9 12.6 12.6 11.3 11.3 13.5 15.5 15.0 10.1 11.0 10.8 16.4 17.5 17.0
Dry bulb (Deg C) Max Min 24.2 26.6 25.0 23.5 26.0 28.7 31.6 24.9 24.2 25.9 28.6 30.1 30.9 31.3
Griffith Laboratory CSIRO Land & Water
99 87 86 80 78 83 77 64 98 78 77 67 73 73
56 33 26 29 28 21 20 22 26 26 23 24 20 25
Rel. humidity (%) Max Min
Mean 78 61 55 52 49 49 44 42 54 51 49 45 48 50
15.0 11.1 8.8 7.0 7.1 8.5 9.8 6.7 6.9 6.8 8.0 9.9 10.9 12.2
DewPt (Deg C)
291 237 272 295 250 201 211 417 345 217 172 272 222 220
Wind (Km)
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Rain (mm)
Weather Summary (14 days) for Griffith NSW
Report generated on 11-Jan-2000
Date
28-Dec-1999 29-Dec-1999 30-Dec-1999 31-Dec-1999 01-Jan-2000 02-Jan-2000 03-Jan-2000 04-Jan-2000 05-Jan-2000 06-Jan-2000 07-Jan-2000 08-Jan-2000 09-Jan-2000 10-Jan-2000
Sun (Mj/Sqm)
21.3 28.1 30.3 32.0 27.2 31.8 29.1 32.2 32.1 32.4 32.5 31.7 27.2 26.5
ET (mm)
5.6 7.9 9.0 9.2 8.7 9.6 10.2 11.6 9.4 9.1 9.3 10.6 9.5 9.2
18
Appendix 7: Sample Current Hour Weather Report
Time AEST
11-01-2000 11:00 11-01-2000 11:00 11-01-2000 11:00
Date
Report generated on 11-Jan-2000
Site
Griffith Finley Hay
Griffith Laboratory CSIRO Land & Water
Rain mm
Sun Mj/Sqm
DBT C
38.0 33.8 35.8
RH %
Latest Hourly Weather Report Wind Km/h
26.1 27.6 29.1
Sun Mj/Sqm
3.1 3.3 3.3
Rain mm
8.3 9.9 9.8
0.0 0.0 0.0
Wind Km 0.0 0.0 0.0
14.7 11.3 13.4
Site
118 69 99
Total (since midnight)
Griffith Finley Hay
19.3 17.2 16.9
DewPt MaxWind C Km/h 10.7 10.2 12.5
19
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
11-01-2000 11-01-2000 11-01-2000 11-01-2000 11-01-2000 11-01-2000 11-01-2000 11-01-2000 11-01-2000 11-01-2000 11-01-2000 11-01-2000 Total Max Min
Time AEST 00:00 01:00 02:00 03:00 04:00 05:00 06:00 07:00 08:00 09:00 10:00 11:00
Wind Km/h
Rain mm
Sun DBT Mj/Sqm C
RH %
7.6 7.2 7.9 5.4 5.4 8.6 10.0 11.4 14.5 17.4 15.1 14.7
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.3 0.9 1.7 2.4 3.1
21.1 19.9 18.9 17.3 18.1 17.5 17.5 18.8 21.0 22.9 24.7 26.1
61.2 66.3 69.3 81.4 74.3 78.1 79.8 73.5 61.0 52.3 45.9 38.0
13.4 13.5 13.1 14.1 13.5 13.6 13.9 14.0 13.2 12.6 12.3 10.7
125.2
0.0
8.3 26.1 17.3
81.4 38.0
14.1 10.7
20
DewPt C
Appendix 9: Sample Yesterday Weather Report
Date
10-01-2000 10-01-2000 10-01-2000 10-01-2000
24.1 25.2 25.0 25.9
Avg
Report generated on 11-Jan-2000
Site
Griffith Finley Hay Tullakool
DBT C Max 31.3 33.5 33.4 34.9
Griffith Laboratory CSIRO Land & Water
Min
50 49 47 46
Avg
73 82 74 87
RH % Max
25 19 26 19
Min
Daily Weather Report
17.0 18.1 17.4 18.1
12.2 12.0 12.2 11.2
DewPt C
220 216 192 217
Wind km
0.0 0.0 0.0 7.4
Rain mm
26.5 28.6 20.9 24.0
Sun Mj/Sqm
ET mm
9.2 10.0 8.4 9.6
21
Appendix 10: Sample Monthly Weather Report
23.7 26.9 19.8 24.4 23.8 25.1 26.1 29.4 35.9 27.1 22.1 26.1 24.1 27.4 27.7 25.6 31.7 16.1 20.8 21.5 27.6 20.7 18.6 20.8 24.4 22.8 24.8 25.5 29.0 24.0 20.5
Dry bulb (Deg C) Mean Max 14.5 17.2 16.5 17.2 15.3 15.4 17.9 20.6 26.2 19.6 17.1 18.4 19.0 20.2 20.0 16.1 19.2 13.5 12.9 13.1 18.2 14.6 11.4 14.4 16.1 16.3 15.7 17.0 20.1 19.5 15.7
24.6 35.9 16.1
Mean
Griffith Laboratory CSIRO Land & Water
93 99 76
99 97 98 97 98 94 91 87 76 98 95 96 92 94 91 95 94 95 94 98 85 88 98 97 97 95 95 91 76 87 94
32 76 15
33 42 76 31 29 19 25 23 15 49 42 30 36 47 25 22 16 73 29 30 15 21 26 36 32 24 25 22 19 45 21
Rel. humidity (%) Max Min
Min 69 80 91 68 67 61 58 51 42 80 71 66 61 76 64 58 55 84 63 65 43 50 67 70 66 64 58 58 46 63 56
64 91 42
3.6 10.7 14.0 10.3 8.0 4.4 9.4 10.3 16.7 14.3 12.8 12.0 13.4 15.3 11.4 6.6 6.3 10.6 5.1 4.3 6.2 8.1 3.3 9.3 6.4 9.1 4.9 8.2 10.7 16.8 9.2
9.4 16.8 3.3
Wind (Km)
0.0 31.4 5.8 0.0 0.0 0.0 0.0 0.0 0.0 16.6 0.2 0.0 0.4 0.2 0.6 0.0 0.0 7.8 0.2 0.0 0.0 0.0 18.2 14.8 0.0 1.0 0.0 0.0 0.0 1.0 0.0
Rain (mm)
23.1 16.9 7.5 24.3 25.0 25.4 24.7 24.0 20.4 13.4 18.1 25.9 9.0 18.7 20.8 27.0 26.9 4.4 27.1 26.6 27.5 26.7 16.3 20.6 20.8 23.5 28.8 29.0 25.0 7.3 28.8
Sun (Mj/Sqm)
5.1 1.6 4.7 6.3 6.1 6.5 7.0 9.1 6.1 5.1 5.9 4.8 4.8 5.8 7.4 7.2 3.8 5.5 6.3 7.3 8.6 5.9 5.3 5.3 5.9 6.9 7.4 7.9 4.7 7.3 7.3
ET (mm)
DewPt (Deg C)
122 174 184 269 224 118 171 215 274 231 276 119 243 107 295 175 131 241 376 218 214 294 253 365 169 235 167 165 157 168 355
188.9 6.1 9.1 1.6
7.8 13.1 14.9 10.1 8.0 5.9 8.0 8.5 10.2 15.5 11.2 10.7 10.5 15.3 11.5 5.8 7.3 10.7 4.7 5.3 2.6 3.0 3.9 8.3 8.7 8.0 5.9 6.8 6.7 12.0 5.0
98.2
663.5 21.4 29.0 4.4 31.4 0.0
8.6 15.5 2.6
6705 216 376 107
Weather Summary (Oct 1999) for Hay NSW
Report generated on 01-Nov-1999
Date
01-Oct-1999 02-Oct-1999 03-Oct-1999 04-Oct-1999 05-Oct-1999 06-Oct-1999 07-Oct-1999 08-Oct-1999 09-Oct-1999 10-Oct-1999 11-Oct-1999 12-Oct-1999 13-Oct-1999 14-Oct-1999 15-Oct-1999 16-Oct-1999 17-Oct-1999 18-Oct-1999 19-Oct-1999 20-Oct-1999 21-Oct-1999 22-Oct-1999 23-Oct-1999 24-Oct-1999 25-Oct-1999 26-Oct-1999 27-Oct-1999 28-Oct-1999 29-Oct-1999 30-Oct-1999 31-Oct-1999
17.1 26.2 11.4
in the month: 31
Monthly Summary Number of days Total Mean Max Min
22
