Why do I want rapidly changing gauge data?
a) Because I can.
b) So I can sit with my ipad in my lounge and watch the dials move during
gusty/stormy conditions and not have to stand at my console to see the same.
c) When I am away from home, I can watch them from afar.
Not worried whether anyone
Sorry, I neglected to provide this link to the development site in the post
above.
http://www.lablibrary.com/ss/
Bob
On Monday, February 20, 2017 at 2:09:20 PM UTC-8, tempus wrote:
>
> The gauges show both average and gust data, neither of which are 'fake
> weather.' Peak gusts are important
The gauges show both average and gust data, neither of which are 'fake
weather.' Peak gusts are important to aircraft pilots and mariners. They
also are important to analyzing and predicting changing weather
conditions. Wind speeds and directions averaged over various past time
intervals,
@ tempus:
1. Windspeeds do indeed change rapidly, which is why there is usually a 10
minute averaging period to cover reported wind speeds.
Measuring gusts and wind intensity
Because wind is an element that varies rapidly over very short periods of
time it is sampled at high frequency
On Monday, February 20, 2017 at 9:33:27 AM UTC-8, tempus wrote:
>
> This is merely a suggestion for consideration.
> 173 bytes doesn't seem like much. However, with 3-second updates there
> will 86400 / 3 = 28,800 file transmissions per day to each concurrent
> user. 28,800 x 173 bytes =
1) Wind speed and direction data tends to change radically from
second-to-second and is interesting to watch, especially in coastal areas
where high wind speeds often cause significant property damage and even
loss of life.
2) Rapidly changing gauges quickly demonstrate to website visitors
I would prefer to ask the questions - why am I providing 3 second updates?
What practical value do 3 second updates have for most users?? What is the
point??
On Monday, 20 February 2017 19:33:27 UTC+2, tempus wrote:
> This is merely a suggestion for consideration.
>
> Space characters are
This is merely a suggestion for consideration.
Space characters are commonly used within and between key-value pairs in
associative arrays to improve human readability. Because 'gauge-data.txt'
human-readability isn't important, the file could be reduced in size 158
bytes, plus another 15
Typo was the cause of the rain issue, as for the pressure issue, seems I
changed the structure of config options for formatting but neglected to
change the code. Should be fixed now in v0.2.4.
Note that the digital display on the pressure gauge will display 2 decimal
places when using inHg,