On Tuesday, February 9, 2021 at 2:03:52 PM UTC+1 [email protected] wrote:
> Thank you :) > > so when I said: > > "For backfilling missing data would use an approach like: If there is data > available in weatherflow REST service, an if it is available on a time base > which is more frequent than archive_interval, I would try to backfill like > this: for every top of an weewx archive_interval that is missing, I'd get > all data available for this interval, calculate averages (take care with > vector data windSpeed/windDir!), check if minimum/maximum values of each > REST entry, if it is lower/higher than the min/max value in > archive_day_[archiveColumn], handle it." > > I'd now say: > > For a weatherflow driver I wouldn't set an archive_interval in the driver > itself. For backfilling, get the all records from the REST within the > current archive_interval to backfill, create a single record for that > interval, with the values being the average values of all the REST records > (with the right treatment for vector data). Losing precision of min/max > values and their timestamps is acceptable (at least for reasonable short > archive_interval settings) > I hope to look into it, but it is not at the top of the priorities list at the moment :) Cheers, Jan-Jaap -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/bebed45b-2852-4c84-b80e-a951269bb032n%40googlegroups.com.
