Thanks for the pointers everyone. The datetime function comes in handy, and I appreciate the schema and other references. I have cleared out the bad data, although I followed an example and set the value to NULL, perhaps I should have gone with 0. Now when I try to find the NULL values (where rain=NULL) I do not get any hits, but they show up in other queries. I was thinking about setting them to 0.
Most of the reports look better now. The annual report is still showing a peak rain rate for the data I deleted, I'm not sure where that comes from. I deleted the daily summaries and they have been recreated. Its raining here in Southern California, second set of storms for the season. I don't get much opportunity to test the rain collector but it appears to be working. Dana On Sunday, December 22, 2019 at 1:51:41 PM UTC-8, Dana Roode wrote: > > Hello, > > I've had some issues with the rain collector on my Vantage Pro2 this year, > I replaced it a few weeks back. There were some spurious high readings, > plus my testing generated false readings. The data indicates over 60 > inches of rain in my desert location this year. I'd like to find the bad > values and zero them out, and I see how to do this with sqlite3 on the > database if I understood the data fields. "rain" is the field in the > archive tables, but I don't know what time period thats for. The dateTime > field has numbers like 1539650100 and I don't know how to convert to > something meanful. > > Is there documentation on the database schema and fields somewhere? I > haven't found it in the wiki information. > > Any pointers would be appreciated. > > Dana Roode > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/dd10c094-3958-4dfb-8134-67de37cd432b%40googlegroups.com.
