NOAA Reports - High Wind (my observation)

[Nottub]

Just a comment here regarding the NOAA Reports and the values for Hi Wind Speed.

When the report is initially generated, the most recent entry/ entries include a figures to one decimal point, however, after a few days this figure is rounded to the nearest whole number, without any intervention.

Note the 23rd (17.1), and 24th (19.5), all previous entries for the month are whole numbers. These too when initially created were generally to one decimal point.

Code: Select all

19  23.0  30.1   15:41  15.9   03:21   0.5   5.0   0.0   1.9  20.0   14:42   SSW
20  18.9  23.7   13:47  14.2   05:44   0.9   2.2   0.0   3.1  16.0   08:36   SSW
21  16.6  21.8   15:57  11.3   01:08   2.2   0.7   0.0   1.7  18.0   08:35   WSW
22  17.5  24.6   15:01  10.4   05:38   2.0   1.8   0.0   2.0  16.0   12:16   WSW
23  17.6  23.6   15:00  11.7   04:47   2.0   1.7   0.0   1.9  17.1   10:50   NNE
24  19.7  23.4   14:46  15.9   05:34   0.8   1.3   0.4   3.9  19.5   17:15   SSW

Just wondered if anyone else has noticed this?


Thanks

Martyn

[Dennisdg]

I notice that whole numbers changed on Feb 2012 in my system. Long before V4

[freddie]

Have you checked in your Dayfile? Perhaps the earlier days this month genuinely had high wind speeds that were 20.0, for example.

[Nottub]

I will check.

But for now, if I Re-generate a monthly Report where there were values to one decimal point, these change to a rounded whole number.

Martyn

EDIT: Looking at the Dayfile Viewer/Editor, the Max Gust is recorded as a whole number.

For Example the max gust on the 24th is recorded as 20mph, whilst the NOAA Report shows 19.5mph.

[freddie]

One for @mcrossley I think.

[PaulMy]

Hi,
I presume it is the same on your local Dashboard > Reports as on your website. Only the last 2 days show xx.x and all others going back years are xx.0. Mine going back to 2008 are all xx.x. Are you saying the 2 that are xx.x will change to xx.0 after a few days?

Enjoy,
Paul

[mcrossley]

I'm really puzzled because the Davis only reports wind gust speeds to whole mph. Not sure how it could ever be 19.5 for instance? It's limited by the wind sensor which only sends an integer value. The average can be decimal though.

[Nottub]

Hi,
I presume it is the same on your local Dashboard > Reports as on your website. Only the last 2 days show xx.x and all others going back years are xx.0. Mine going back to 2008 are all xx.x. Are you saying the 2 that are xx.x will change to xx.0 after a few days?

Enjoy,
Paul

Yes that’s exactly it. April 2024 had two entries at the end of the month that were to one decimal place, when re-generated these reappeared as whole numbers.

EDIT:
June 2024 currently on my website:

Code: Select all

26  22.1  27.0   15:29  17.3   07:11   0.1   3.5   0.0   1.9  18.0   09:27   SSE
27  18.2  22.6   12:59  13.9   02:29   1.9   1.1   0.0   4.0  21.0   08:45   WSW
28  14.3  19.6   16:13   9.0   04:49   3.6   0.1   0.0   1.7  18.3   14:47   WSW
29  17.4  22.4   15:18  12.3   05:26   2.0   0.8   1.2   2.3  15.9   08:07    NW
30  14.2  18.3   09:58  10.1   04:01   4.1   0.0   0.0   1.5  14.6   10:10    NW

June 2024 after re-generating (Iocal view)

Code: Select all

26  22.1  27.0   15:29  17.3   07:11   0.1   3.5   0.0   1.9  18.0   09:27   SSE
27  18.2  22.6   12:59  13.9   02:29   1.9   1.1   0.0   4.0  21.0   08:45   WSW
28  14.3  19.6   16:13   9.0   04:49   3.6   0.1   0.0   1.7  18.0   14:47   WSW
29  17.4  22.4   15:18  12.3   05:26   2.0   0.8   1.2   2.3  16.0   08:07    NW
30  14.2  18.3   09:58  10.1   04:01   4.1   0.0   0.0   1.5  15.0   10:10    NW

I’m not concerned with it but trying to understand why it does it.

Martyn

[mcrossley]

Do you (or did you) have a calibration configured for wind speed?

[Nottub]

Do you (or did you) have a calibration configured for wind speed?

Yes I do Mark. Does that make a difference?

Martyn

[Nottub]

Mark,

Reset wind calibration settings back to the default of 1, to see if that changes things.

Martyn

[freddie]

It will make all your readings in to whole numbers - the calibration factor was responsible for the unexpected non-whole numbers. But it doesn't explain why previous values were reverting to whole numbers.

[mcrossley]

When creating the NOAA reports the gust value is read from the day file (actually from an in-memory copy of the file) and used unchanged.