Agreed, especially if graphing the 10-min average wind - which is a pretty standard definition of “wind speed”. See loc.cit.: “A better measure of the overall wind intensity is defined by the average speed and direction over the ten minute period leading up to the reporting time.”
And thanks for explaining the gust line on the graph 
Agreed, but for FreshWDL it’s not Brian you have to convince to change anything: clientraw is OK as it stands (although one decimal place for #140 would be good!).
I am using #1 for “wind” and #140 for “gust” on my old PWS Dashboard, in spite of the discussion that has been going on over there.
Thanks Brian - and that’s the “under the hood” (“under the bonnet” for the UK) of WD that I didn’t know. If the average is a rolling average and not the same 60-second sample as the gust is derived from, then yes, the gust could sometimes be lower.
When you say the gust line on the graph in WD is the maximum current speed over the last minute, I assume you’re referring to Field 140, which is called “Max Gust In Last Min” in clientraw.txt and not from Field 2, which is “Current Windspeed”? If so, that would be the correct Field to plot for gust.
To avoid the gust from ever being lower than the average, both the average and gust would have to be from the same 60-second period instead of using a rolling average, if it was possible to code it that way in WD, and it would fit the definition of gust. Just a suggestion and that’s typically how a gust is derived from the average.
For @bitsostring, yes, I know for FreshWDL, Brian is not the author, and clientraw.txt is correct, it’s just how the wind fields are used from clientraw.txt that’s important. For FreshWDL, Field 140 should be used for the “max” column and not Field 2 as you mention for your old PWS Dashboard.
And, by the way, WD is excellent software that I’ve been using for 17 years and Brian does a great job supporting it and working with us!
I still do not get it, if WD does what youre wanting it to do, then some of the gusts will be a lie, they will have to be if you want it to always be higher than the average speed. during lulls the gusts will be lower, they have to be or else the gust speed will stick at one amount until it goes higher than the average, thats basically what youre wanting?
For the pws dashboad as mentioned in reply 21, that was a bad idea in my opion and Wim reverted it, at least for me, not sure as a whole though. The reason why is because the gust speed dial stuck for ages (many, many minutes, perhaps an hour), it didnt move, i think it was worse when the speeds were low all round. the current moved ok, but for the gust, it just stayed put for ages, that was just wrong imo especially for a Davis that updates every few seconds, i really dont want that to happen in WD.
For those that have stations where the wind only updates around every minute, your idea might be ok, i just cant see it being ok for those that update much quicker.
Or perhaps i am misunderstanding what youre after, if so then apologies, my brain aint wired for complexities higher then 2+2 lol
I don’t want WD to do anything, I was making a suggestion based on the accepted definition of a wind gust by NOAA NWS, UKMO, WMO, etc. that the gust is always the maximum of the average wind speed in a given period. That’s it. And the WD plot, as Brian stated, doesn’t display that because WD uses a moving average in the graph.
During a “lull”, the wind gusts will still be higher than the average for that period. By definition and mathematically they have to be - math doesn’t lie. Even if a 60-second period of average wind speeds are very week, say 3 mph (we could call this period a “lull”), the gust still has to be greater than 3 mph. And it’s true, on a day with very weak winds, like < 5 mph for hours on end, if you had several 60-second periods where the average wind was 4 mph, then it’s possible the gust could be “stuck” at some value just above 4 mph, maybe “the needle would stick” at 6 mph for a few minutes until the average speed moved off of 4 mph. But that’s truth. So, your example mentioned in reply 21 that the gust speed dial stuck for many, many minutes is possible under very weak winds, but that is the correct way to display the wind gust. Yes, in your scenario, the “current speed” should move slightly because it is the instantaneous wind speed (3-sec wind for Davis) that is used to calculate the 60-sec average, but, again, by definition, the “current speed” is not the gust.
Look at the attached image from WU on a weak wind day. The highest average was 4.5 mph and the highest gust was 6 mph. The gust (orange dots) was never plotted below the average and the gust did get “stuck” at one wind speed many times that day as you can see examples in the two red rectangles I added. But that’s the correct way to plot average versus gust.
I do like that my Steel Gauges work off of the current wind speed, as they should. Having a WD measurement every 3-sec is cool to watch the dial bounce around. And a dial should mimic the constantly changing wind speed.
I would like to see FreshWDL plot all three winds from clientraw.txt: average, current, and gust using three separate columns and label them accordingly. Then we could watch the 3-sec wind moving up and down like the Steel Gauge and also see the true gust and average.
It would be more accurate for WD not to use a moving average for the wind chart, like WU does, so that the gust is never displayed less than the average.
But hey, we’re all doing this for fun. Nobody is making operational decisions on this data (I hope), so none of this is critically important.
OK, I see what you’re saying re 3 separate readings.
That was using #133, max gust last hour. I didn’t agree with that, either.
I think that once we come to realise and it sinks in that its actually the current speed and not the gust and only have that one shown on the dial and have the gust last min shown in a side box, all will make sense. at the minute folks are misinterpreting it as the gust, even though it actually is, but because of the lulls you think its incorrect and to be fair, Joe public doesntly really care and probably doesnt even notice whats going. Its the OCD in us thats making it feel like its all wrong.
I really dont think gust last minute should be on the dial itself, becaus its not instantaneous or as close as it is forother stations, 20secs, 40secs, Davis 2.7secs and there are 1 or 2 stations that are 1sec wind updates. Thats what fell I feel, the dial should be for quick fire updates, and if there is just the 1data point that does that, i.e Current wind, that it should just be that on the dial, any other thats used as an average should be on its own little box. pretty much like how youve got your pws setup, bitsostring, exceot for the single data point for the dial speed.
Good job you don’t have a Met Office anemo, they sample windspeed 4 times/sec
And they report 10-min averages 
Now that would be cool
Yeah but I bet the 10 min average isn’t on the windspeed dial though
Bump.
I did hear from Yerren that he might set an option for using #140 in the config file, and then people can choose what they’d like to display for gust.
Hi all,
Apologies for the delay in getting back to everyone on this.
You now should be able to switch between using clientraw 2 (current wind speed), and clientraw 140 (max windspeed in the last minute), for the wind speed gauge.
To adjust, this, you’ll need to edit the gaugeSettings in your config file as follows (just the windSpeed section is new, leave the other gauges as you had them previously):
gaugeSettings = { //Gauges: apparent temperature barometer windChill graphHandlerBarometer graphHandlerRainfall graphHandlerTemperature graphHandlerWindSpeed humidity moonSun solar status rainfallTitle rainfallDay rainfallMonth rainfallYear UV windDirection windSpeed
solar: {
enabled: true
},
UV: {
enabled: true
},
windChill: {
mode: "windchill", //The default mode, either "heatIndex" or "windchill" (note: lowercase c)
autoSwitch: true //If true, will switch between heat index/wind chill depending on what is appropriate.
},
windSpeed: {
enabled: true,
gustMode: "current" //Set to "current" for the gust to display the current windspeed, or to "max" for it to display the maximum windspeed in the last 60 seconds.
}
},
By default it is set to “current” (e.g., clientraw 2), but if you want to change it, set the gustMode field of the windSpeed gauge to “max”.
P.s. don’t forget to ctrl+F5 to make sure the browser cache is cleared if there are any issues.
Working here, Yerren. Many thanks
For the avoidance of doubt, this is for the Gust on the wind speed gauge. I presume that Wind still uses clientraw #1 (average last minute).
Great!
Yes, you are completely correct. This only modifies the gust reading on the wind speed gauge, nothing else.
Yerren - thank you for giving us the option to use the clientraw 140 max windspeed in the last minute. I implemented your code in my config file and it’s working with the “max” option (https://novawx.dscloud.me/freshwdl.php). Unfortunately, the “Gust” can still show as less than the “Wind” because the max windspeed only updates every minute and the “Wind” updates more frequently as shown in the attached image file. Obviously, there’s not much wind today but it will be breezy on Friday this week, so I’ll see what it looks like then. But you can only use what’s available in clientraw.txt. Once again, thanks for providing the option.
Bill
Looks good on a day with a bit more wind!
