Repository navigation
Conversation
… midnight, so it's consistent with all other providers; make indentations consistent
|
Only had a few minutes to scan the code. Does this code cache the last three days of observations from a local weatherstation? Just curious ('cause that's what I need for my installations). |
|
It stores the last 7 days (as opposed to before where only the last day was stored). The most recent 3 of those 7 days would be used when that feature is enabled |
|
Thank you very much!!! |
|
It caches up to the past 7 days. When you send a query, it will use as many days of data as there is available. For example, if you do have all 7 days of data, it can return an array of size 7. If there is only 1 day of data available, the return is of size 1. |
|
Retain eight days of local PWS observations and return up to seven contiguous complete calendar days for interval-program averaging. Time-weight irregular samples across day boundaries while preserving optional wind and solar data. Normalize all provider history newest-first, reject duplicate or noncontiguous days, validate hourly slots across DST transitions, and correct Pirate Weather handling of 23- and 25-hour days. Extend deterministic and live local-PWS coverage accordingly. Reimplements #170 against the current provider architecture.
|
Multi-day local-provider history has now been implemented in an updated form through #180 and released in Weather Service 3.1.0, including calendar-day normalization and persistence across restarts. Closing this superseded PR. |
This branch add multiday support for the
localweather provider. It's similar to #169 but the implementation might be a bit different. It splits the data such that each whole day is midnight to midnight, which is consistent with all other providers.