I'm now sending my data to Wunderground and using this program on my iPhone and iPad... Very nice way to display data from weewx...
http://pwsmonitor.blogspot.com/ http://www.wunderground.com/weatherstation/about.asp ~~ _/) ~~~~ _/) ~~~~ _/) ~~~~ _/) ~~ Tom Lafleur > On Feb 20, 2017, at 3:52 AM, [email protected] wrote: > > > [email protected] Google Groups > Topic digest > View all topics > Realtime Gauge-Data Extension 0.2.2 'gauge-data.txt' Issues - 1 Update > Steel Series Gauges and RealTime update - 2.5 second interval - how? - 2 > Updates > New User, New Install, no run - 1 Update > 10 min average wind - 1 Update > Realtime Gauge-Data Extension 0.2.2 'gauge-data.txt' Issues > tempus <[email protected]>: Feb 19 11:52PM -0800 > > It is customary in the U.S. to report barometric pressures adjusted to sea > level as inches of mercury (inHg) to two and sometimes three decimal digits > of precision. The default rtgd-0.2.2 string format for inHg appears to be > "%.3f", but that seems to be ignored in the code, because the pressure > value in 'gauge-data.txt' has only a single decimal digit of precision. > > For example, right now the pressure is 29.637, 'gauge-data.txt' contains > only, > > > *"press": "29.6"* > and the pressure gauge displays > * 29.60.* > Another issue that even though "*group_rain = inch*" is specified under > [[Groups]] in weewx.conf, 'gauge-data.txt' contains: > > *"rainunit": "mm"* > > Bob > Back to top > Steel Series Gauges and RealTime update - 2.5 second interval - how? > > tempus <[email protected]>: Feb 19 04:32PM -0800 > > This is a link to a page at a test-site if you want to see the gauges > updating at 3-second intervals. > > http://www.lablibrary.com/ss/ > > There are no developer-credits or anything else other than gauges on that > page, because access is normally blocked at the firewall. I am just playing > around with ideas with the general intention to eventually embed that page > within another one at a public website. > > The Wind Rose still needs attention, but otherwise the gauges seem to be > working. > > Bob > > On Sunday, February 19, 2017 at 3:26:42 PM UTC-8, tempus wrote: > tempus <[email protected]>: Feb 19 05:45PM -0800 > > Sorry if you aren't able load the test page. I have taken it down to fix an > issue. > > Bob > > On Sunday, February 19, 2017 at 4:32:38 PM UTC-8, tempus wrote: > Back to top > New User, New Install, no run > [email protected]: Feb 19 04:51PM -0800 > > duh... sorry, missed that > got driver loaded, reconfigured, and started without error :>) > off to figure out how to get skins running in my apache2 > > Thanks for your valuable assistance > > Geary > > On Saturday, February 18, 2017 at 2:39:00 PM UTC-8, gjr80 wrote: > Back to top > 10 min average wind > gjr80 <[email protected]>: Feb 19 03:56PM -0800 > > Hi, > > Wind speed can be a complex topic. The simple answer to your question *I'm > wondering if weewx calculates the average windspeed over 10 minutes* is *yes, > it can, but...*. Perhaps an explanation of what weeWX archives and reports > and a few points on the SteelSeries Weather Gauges might make it clear. > > The WeeWX archive field windSpeed holds the average wind speed over the > archive period. This might be calculated from loop wind speed data if using > software record generation or received directly from the station if > hardware record generation is used. On your install your windSpeed fields > would I expect be averaged over 2 minutes, I have a 5 minute archive period > so mine is a 5 minute average. Stations that use a 10 minute archive period > would indeed have a 10 minute average in their windSpeed fields. The daily > summary for windSpeed is just an optimisation holding aggregates and other > data on your archive windSpeed data, so they to refer to 2, 5 or 10 (in the > examples I cited) average values. That is the data storage aspect of weeWX. > > The other side of the weeWX coin is the reporting. WeeWX has a variety of > tags that allow generation of statistics over some period of time eg $day, > $week, $span etc. For windSpeed, $day.windSpeed.avg will give you the > average of all of the windSpeed values for the day so far. One could argue > that the average of an average is dangerous, though in the case where the > archive period is homogeneous the calculation is valid (or if your archive > period is non-homogeneous and you are using weeWX 3.7.0 or later with the > weighted summaries fix applied the calculation is also valid as the values > are appropriately weighted). The $span tag allows calculation of aggregates > over a user defined period of time, so $span($time_delta=600).windSpeed.avg > would allow you use the average windSpeed over the last immediate 10 > minutes in your reports, irrespective of your archive period (of course if > your archive period is 15 minutes, or some value that is not a factor of > 10, then the resulting value will likely be wrong). > > When you hover over the wind speed gauge in the SteelSeries Weather Gauges > the dialog that shows mentions 'Average wind speed (10min)', this is hard > coded in the SteelSeries Weather Gauges (why you would have to ask the > author, though I do seem to recall that Cumulus (once? now ?) defaulted to > what we would call a 10 minute archive period and the SteelSeries Weather > Gauges author is a Cumulus user - I may be wrong). The value that is > displayed against 'Average wind speed (10min)' comes from the wspeed field > in gauge-data.txt. The gauge-data.txt.tmpl file that is currently included > with the SteelSeries Weather Gauges fills the wspeed field using $ > hour.windSpeed.avg.raw which would result in the average windSpeed value > for the current hour; not the 10 minute average as labelled in the dialog. > Why? I don't know, it should be changed to > $span($time_delta=600).windSpeed.avg.raw. I will submit a PR to the > SteelSeries Weather Gauges. > > As for the reason why you are seeing a ridiculous wind speed, it is most > likely because the gauge-data.txt file has a null (weeWX None) value for > the wspeed field. When the error condition is showing up have a look at > your gauge-data.txt file and see what value is against wspeed. If it is > null then it is likely $hour.windSpeed.avg.raw is returning None for some > reason. Why would mean looking at your underlying windSpeed data for the > last hour, it may be there is no data and hence None is returned and > converted to null. > > Gary > > On Monday, 20 February 2017 02:22:02 UTC+10, Robert Mantel wrote: > Back to top > You received this digest because you're subscribed to updates for this group. > You can change your settings on the group membership page. > To unsubscribe from this group and stop receiving emails from it send an > email to [email protected]. -- 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]. For more options, visit https://groups.google.com/d/optout.
