Karen K <[email protected]> writes: > There is a comment in restx.py saying: > > # NB: The WU considers the archive with time stamp 00:00 > # (midnight) as (wrongly) belonging to the current day > # (instead of the previous day). But, it's their site, > # so we'll do it their way. That means the SELECT statement > # is inclusive on both time ends: > > That is also used for MQTT, but it seems not appropriate in the context of > MQTT. So I looked for a solution.
Assuming 5m archive interval, without loss of generality. Most observations in weewx are a value at a time, with temperature being the canonical example. 0000 is indeed part of the same day as 0001, so the temperature at 0000 should be used in min/max for "next day" rather than "previous day". But, rain is different. The rain value at 0000 is the rain that fell between 2355 and 0000. So that value belongs in the sum of the previous day. More pedantically, one can thing of rain as the number of clicks arriving >= 235500 and < 000000 or perhaps it's > and <=. It's hard to know, and it of course doesn't really matter. All of this is a long way of saying that I think considering rain that is reported at 0000 to belong to the previous day is sensible, always. I also don't really care personally, as whether daily rain is [0000,0000) or [0005,0005) doesn't matter to me, or the plants. -- 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/rmiee1sq8e1.fsf%40s1.lexort.com.
signature.asc
Description: PGP signature
