@Gkikas-LGPZ

Thanks! All is clear now! I supposed the forecast was fresh, the mistake was only in one place, concerning reference time...

@Korina ,

if you look on the "reference time" for NEMS, for example hier, https://www.windy.com/multimodel/44.107/15.326?44.108,14.248,8
you'll see for METEOBLUE (NEMS) :

Updated: 2020-02-27T07:27:42000Z
Reference time: 2020-02-25

Or, I don't understand something?

Thanks!

@Gkikas-LGPZ

Thanks! All is clear now! I supposed the forecast was fresh, the mistake was only in one place, concerning reference time...

@Korina ,

if you look on the "reference time" for NEMS, for example hier, https://www.windy.com/multimodel/44.107/15.326?44.108,14.248,8
you'll see for METEOBLUE (NEMS) :

Updated: 2020-02-27T07:27:42000Z
Reference time: 2020-02-25

Or, I don't understand something?

Thanks!

Hi, Korina!

But, then it is something wrong by NEMS! When I look on it, comparing models, I see big time difference between reference and update data!(?)

Yes, that's what I wanted to say...thanks!

NEMS model update is delayed 24 hours, according compare section...Why?

Well done!!!! Can you do it in skew-T/log-p, please?

Regards,

Matija