On Friday, August 10, 2018 at 3:19:57 PM UTC+1, gjr80 wrote:
>
> In the daily summaries the 'max' field stores the max value of the obs for 
> the day (the row of the daily summary table) concerned. So for point in 
> time obs like temperature, humidity etc $year.outTemp.max will indeed 
> give the max outTemp value seen since 1 January of the current year and 
> $year.outTemp.maxtime will give the date-time it occurred. The same tag 
> will certainly work with rain, ie $year.rain.max but what that tag is 
> returning is not the max daily rainfall in the year to date but rather the 
> max rainfall seen in an archive period in the year to date, you are 
> treating rainfall more as a point in time observation. The $year.rain.sum 
> tag will give you the total rainfall in the year to date so it does not 
> help (it sums the daily summaries sum field). If you are looking for the 
> max daily rainfall in the year you want to look at the max of the sum 
> fields and to find the max value of the sum field you use the .maxsum 
> aggregation type in your tag ie $year.rain.maxsum. Date-time wise 
> $year.rain.maxtime may well provide the correct date-time that the 
> highest daily rainfall occurred (chances are high that the highest archive 
> period rainfall occurred on the day of highest total rainfall) but the 
> corresponding 'time' aggregate for .maxsum is .maxsumtime ie 
> $year.rain.maxsumtime.
>
> This may make a bit more sense if you refer to the Aggregation types 
> <http://weewx.com/docs/customizing.htm#aggregation_types> appendix in the 
> Customization Guide.
>
> Assuming you are using the alltime period provided by the xstats example 
> search list extension, the $alltime portion of the tag simply allows the 
> underlying query to use the entire daily summary table rather than just the 
> current year, month etc so $alltime.rain.maxsum and 
> $alltime.rain.maxsumtime should give you the results you are after.
>
> Gary
>

Have checked my weewx.sdb and ALL rain records have a lot of decimal 
places, not just the historical records but live records to
As an example 0.2mm looks always to be 0.00787405....
0.4mm = 0.015748031.... 
Is this expected ????
Temp 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to