The peak problem is eliminated ( solved ?) MariaDB [weewx_eco]> SELECT 'windSpeed' FROM `archive` WHERE `windSpeed` > 100;
I have reduced the value 100 in steps to the value 10. MariaDB [weewx_eco]> SELECT 'windSpeed' FROM `archive` WHERE `windSpeed` > 10; 2 rows in set (2.307 sec) and set the windspeed value to NULL in these two rows. The two peaks have now disappeared from the annual chart. I do not understand why the extreme values were only displayed at threshold 10 in the query. Joachim gjr80 schrieb am Freitag, 14. Januar 2022 um 23:06:58 UTC+1: > It's pretty clear from the original post that the issue is with windSpeed > not windGust (unless you live in an area where over time windSpeed is > always equal to or higher than windGust :) ). > > Plus the following would indicate that the two bogus/extreme values have > been found and nulled: > > > I had already executed the command > > mysql> UPDATE archive SET windSpeed=NULL WHERE windSpeed>100; > > with the result that the two extreme values disappeared in the season > year query. > > A quick look at the Belchertown code shows that that daily summaries are > not used for Highcharts plots, besides they will be 'fixed' when you > drop/rebuild them. Further looking at the Belchertown code it appears that > a similar approach is used to WeeWX in that Highcharts data files that > cover longer periods (eg year) are not generated every archive cycle. Given > this you might want to go through your Belchertown output and delete all of > the .json files. This should force regeneration. > >> > Gary > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/ff5d505e-e396-4e39-a06e-e3d1f0143f91n%40googlegroups.com.
