I attempted to edit the data in the dbase.csv file as there doesn't seem to be a SIMPLE way to either edit or remove data that is incorrect.
I found the columns that had the bad data, removed it by setting those values to zero and adjusting the total rainfall numbers sequentially down to correct the error. However, when i saved the file it somehow changed the byte size and apparently some formatting because the edited dbase.csv file would not load into VMS. I tried several more attempts including importing the data into a paradox (dos based) database (of which i am an expert user) but couldn't duplicate the actual format vms needs.
In the Davis Weatherlink software, its EASY to fix a bad data point by simply finding it in the database and changing it as all reports in weatherlink are generated from a SINGLE database. Apparently, VMS has several non-linked databases and this is the source of the problem i think.
I think it is virtually impossible to take out a bad datapoint that other calculations are dependent on. In the rain problem i am having, the bad data STARTS at a single 15 minute period. One should be able to remove that single datapoint, or edit it to the proper value, then ALL OTHER values that are dependent on that data would be automatically recalculated and fixed. But i don't think vms is structured this way and hence once you get bad data one must use all sorts of convoluted ways to fix it while not actually going to the source of the problem.
Yes it is difficult to edit dbase.csv file.
There is a program that will allow you to do this, but I have not tried it. But basically it is best not to mess with that file, and use the "convoluted" ways to edit out the data.
........
In addition to what I posted last night. You also need to go to "recall daily, monthy and yearly archive" and edit out the bad rain values. This will keep them from appearing in any future reports you may output.
There is a individual file for the Year, a individual file for the Month, and a individual file for the Day (that the error occurred). They are
.bin files that you will be looking for. I also recommend that you backup those files and/or VWS as a whole, before you start tinkering with them.
IE: If your rain error occurred on Feb 14, 2010, then you will need to edit the 2010.Bin, 2010_02.bin, 2010_02_14.bin files.
Once you start to edit them you need to reduce the "total rain max" value to the correct amount (current amount minus your correction) for those three files.
Here is another older thread on the subject that I authored.
http://www.wxforum.net/index.php?topic=2726.0