@idefix37 Thanks for responding. MeteoBlue reports in UTC. Windy is local. We agree. However if you look at the actual numbers, windspeed. the NEMS matches meteoBlue at the same time 00utc == 00 local so it is offset.

example below sunday 00utc is 28kts , look at the compare figure at the bottom NEMS 28 kts at 00local

I think this is a problem, after I posted for a short time the wind time series was fixed, but the daylight was then out of whack. I did a screen grab - here it is. It was rolled back though, apparently.

see how time and daylight got offset after?

@tomslavkovsky, @Marienka Thanks for the replies.

@tomslavkovsky, @Marienka Thanks for the replies.

@idefix37 Thanks for responding. MeteoBlue reports in UTC. Windy is local. We agree. However if you look at the actual numbers, windspeed. the NEMS matches meteoBlue at the same time 00utc == 00 local so it is offset.

example below sunday 00utc is 28kts , look at the compare figure at the bottom NEMS 28 kts at 00local

I think this is a problem, after I posted for a short time the wind time series was fixed, but the daylight was then out of whack. I did a screen grab - here it is. It was rolled back though, apparently.

see how time and daylight got offset after?

I am looking at the "compare" for ECMWF, GFS, NEMS and I think NEMS may be offset. The location I am looking is 50N 145W (Ocean Station PAPA). I compare with MeteoBlue and the 3hrly winds match up, but the meteoblue times are UTC, while the windy/compare ones say they are UTC-10hr, so the NEMS time series appear to be offset 10hr.