Windy Community

    • Register
    • Login
    • Search
    • Unread
    • Categories
    • Groups
    • Go to windy.com

    Solved Compare maybe have NEMS offset

    Fixed BUGs
    on monday
    5
    8
    1391
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • O
      oliveRidley last edited by Marienka

      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.

      idefix37 1 Reply Last reply Reply Quote 0
      • idefix37
        idefix37 Sailor Moderator @oliveRidley last edited by idefix37

        @oliveridley
        I am not sure to have clearly understood the trouble.
        Meteoblue express the time in UTC when Windy do it in local time, which is UTC-10h for your position. NEMS forecasts displayed by Meteoblue according to UTC time must be the same as the ones of Windy according local time (UTC-10h), e.g. Meteoblue forecast at 12:00 must be the same as Windy forecast at 02:00 local time.

        Gkikas LGPZ O 2 Replies Last reply Reply Quote 0
        • Gkikas LGPZ
          Gkikas LGPZ Moderator @idefix37 last edited by

          Also keep in mind that windy provides data from the "old" meteoblue model.
          https://community.windy.com/topic/4213/nems-weather-forecast

          1 Reply Last reply Reply Quote 0
          • O
            oliveRidley @idefix37 last edited by

            @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

            0_1534351784417_meteoblueForSunday.png

            0_1534351803884_windyCompareForSunday.png

            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.
            0_1534352009746_NEMSoffsetSortaFixed.png

            see how time and daylight got offset after?

            idefix37 1 Reply Last reply Reply Quote 1
            • idefix37
              idefix37 Sailor Moderator @oliveRidley last edited by idefix37

              @oliveridley
              You are right. There is a problem with NEMS at your position 50ºN 145ºW
              Here is the ECWMF forecast.
              Local time at your location is now 9:00

              0_1534360910635_4E463C06-FAC0-45D7-A28D-7D9A4357146A.jpeg

              And with NEMS
              Local time at the same moment is 19:00 !

              0_1534360969855_68FF885D-86C6-4214-89A1-E8DC14D09B4F.jpeg

              Then I get a black label « Not in sync ». Do you have it too?
              Obviously NEMS display is wrong at your location.

              1 Reply Last reply Reply Quote 1
              • Marienka
                Marienka last edited by Marienka

                Hi @oliveRidley @idefix37 @Gkikas-LGPZ , thanks for your reports and comments. The NEMS model really seems to be offset in ocean locations due to a problem with time zones. We will investigate this issue and find a solution.

                See also: https://community.windy.com/topic/7506/nems-forecast-detail-for-ocean-locations-is-displaying-utc-instead-of-local-time

                Best wishes
                ~ Marie

                1 Reply Last reply Reply Quote 1
                • T
                  TomSlavkovsky API developers last edited by

                  It seems that offset occurs only in the seas/oceans locations it is easily visible when selecting a location in distant time zone +/- 10. Recently, we have changed timezones API and I think this something related to it. @Ivo

                  O 1 Reply Last reply Reply Quote 1
                  • O
                    oliveRidley @TomSlavkovsky last edited by

                    @tomslavkovsky, @Marienka Thanks for the replies.

                    1 Reply Last reply Reply Quote 1
                    • First post
                      Last post
                    Windyty, S.E. - all rights reserved. Powered by excellent NodeBB
                    NodeBB & contributors, OSM & contributors, HERE maps
                    Terms of Use     Privacy Policy