As noted in a number of previous treads, WD does not correctly handle daily and monthly reset systems used by the Australian Bureau of Meteorology for both live data and when converting corrected log files. Some key reset time challenges that WD needs to handle include:
- Rainfall: total from previous 24 hours to 9AM - recorded on the day of measurement
- Maximum Temperature : maximum value over previous 24 hours to 9AM - recorded on previous day
- Minimum Temperature : minimum value over previous 24 period to 9AM - recorded on the day of measurement
- Maximum Wind Gust: maximum value over previous 24 period to 12 midnight - recorded on the day covering the previous 24 hours
More information on reset times and data recording is provided at the following website: http://www.bom.gov.au/climate/cdo/about/about-stats.shtml
I have spent quite a lot of time trying to identify where and why various issues are occurring and how to use the existing WD functions to try and manually fix data problems as they happen. The following quick summary on rainfall issues may help others with similar problems in the short term and hopefully give Windy with some ideas on possible fixes to WD in the long term.
If anyone has come up with better solutions for fixing rainfall or any other data for the Australian reset times can you please provide.
As a start, when trying to enter or correct monthly data in WD using the Australian requirements you essentially need weather records from 9 am on the last day of the previous month to 8:59 am on the first day of the following month (at present WD logfiles generated using the Australian Reset Time only go from 9 am on the first day of the month).
Issue 1 - Monthly Rainfall Totals
The first issue is that WD incorrectly adds rainfall from 9 am on the last day of the month to 12 midnight to the previous monthly total (i.e. rainfall does not reset @ 9 am) For example for February:
28 2 2011 8 59 29 85 26.2 1015 0 2 145 0 85.7 944.2 1375.2 35.8 28 2 2011 9 0 29 85 26.2 1015 1 3 149 0 [color=red] 0 944.2[/color] 1375.2 35.9
Instead of 9 am, the monthly rainfall resets @ 12 midnight:
28 2 2011 23 59 23.6 89 21.7 1013 1 2 179 0 2.3 946.5 1377.5 23 1 3 2011 0 0 23.6 89 21.7 1013 0 2 177 0 [color=red] 2.3 0[/color] 1377.5 23
The new month then starts by missing the rainfall that fell from 9 am to midnight:
1 3 2011 8 59 25.5 89 23.6 1015 0 0 230 0 [color=red]3.3 1[/color] 1378.5 26.9 1 3 2011 9 0 25.5 89 23.6 1015 0 0 230 0 0 1 1378.5 26.9If you want to correct log and data files you will need to modify the log file using excel and then convert to data file.
In WD the monthly total is relatively easy to adjust using two options:
Rain to date screen - month manual entry
Control panel > offsets & initial rain
Windy, hoping that you can fix the issue with the monthly rainfall relatively easily to at least remove one step in this process.
To fix the daily rainfall records see the second issue.
Issue 2 - First Day of Month Rainfall
The second issue is that WD shows the incorrect rainfall for the first day of each month. In the monthly log files the rainfall for the first day is actually located at the end of the previous month. At the moment WD will substitute a 0 or random value until the end of the month when it will use the rainfall from the first day of the following month.
This can be seen in the following monthly summary tables:
Rain to date > Detailed Rain Chart
View > Averages/Extremes
So far I have identified a solution that can only fix one of these tables but not both at the same time. You need to decide which is more important. Follow these steps:
View > Averages/Extremes
correct/check data button
load the data or log file > select the month you are trying to correct > load the data file to correct the daily rainfall data button
It is important at this point to note that the raintall shown for Day 1 will actually be the value for Day 2 and so on until the last day of the month which will show the incorrect value for the real Day 1.
Enter the correct rainfall for the real first day of the month into the last day (i.e. for February this would be Day 28) and then:
may sure the last date is showing in the Date of Correction
Use the corrected amount button
Use the Save Changes button
If you look up the monthly summary tables you will see:
- Rain to date > Detailed Rain Chart (rainfall totals for the month you are trying to fix are now correct)
- View > Averages/Extremes (daily rainfall totals for month you are trying to fix will remain incorrect)
The alternative solution is to repeat the above but enter the correct daily total for the preceding month into that actual month you are trying to fix. Then following the remaining steps.
If you then look up the monthly summary tables you will see:
- Rain to date > Detailed Rain Chart (rainfall totals for the month will show an incorrect value -now preceding month)
- View > Averages/Extremes (daily rainfall totals for the preceding month will now be correct)
- View > Averages/Extremes (daily rainfall totals for month you are trying to fix will remain incorrect)
Windy, if you can get WD to fix both monthly summary tables in the one step that would also be a great improvement.
I am more than happy to trial any potential fixes for the rainfall or other data collection.