Windy Community
    • Unread
    • Categories
    • Groups
    • Go to windy.com
    • Register
    • Login

    Missing Data for swell 1 on gfsWave

    Windy API v4
    2
    3
    458
    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.
    • B
      b.rochut | Premium
      last edited by

      Hello,

      We are experiencing some weird data with swell 1 values on gfsWave API.
      We're getting higher swell 1 than the total wave height.
      Ex :

      • Timestamp : 1681257600 (04-12 00:00 UTC)
      • Position : 29°N ; 89°30W
      • Wave Height : 1.0397
      • Wind Waves : 1.0397
      • Swell 1 : 2.5998

      We checked on windy and it seems there is missing data for swell 1 with gfs model (see picture)

      Capture d’écran 2023-04-11 à 12.56.28.png

      Is there an explanation for that ? Why is the API giving some weird value instead of a NaN or something like that ?

      Moreover, it seems that there is some difference between the API result and the windy picker for same timestamp and location.

      Capture d’écran 2023-04-11 à 12.57.28.png

      Regards,
      Basile

      idefix37I 1 Reply Last reply Reply Quote 0
      • idefix37I
        idefix37 Sailor Moderator @b.rochut
        last edited by idefix37

        @b-rochut
        I can’t verify what you observe in the API.
        In Windy these gray tiles show that the Swell is near 0ft (10cm if you set heights in metric). Same for Swell 2 and Swell 3 but on a larger area. I guess GFS don’t provide swell data in these gray areas where swell height is almost zero.
        While Waves layer is locally showing 1ft and Windwaves 1ft too. It means that the total sea (Waves) is only produced by the local wind right now and according to GFS prediction.

        7F039047-EB2E-4E41-ADA9-3DF37913B481.jpeg

        B 1 Reply Last reply Reply Quote 1
        • B
          b.rochut @idefix37 | Premium
          last edited by

          Hi @idefix37 and thanks for your quick answer !

          Yes that's what I was thinking for the website, missing values means 0 m.

          My question is then why the API is giving a different value for the same location and same timestamp ?

          Here is my API call code :

          Capture d’écran 2023-04-11 à 14.17.39.png

          And here is the result (I reduced it to get the last timestamp on the one we want 1681257600 (04-12 00:00 UTC) :

          Capture d’écran 2023-04-11 à 14.25.38.png

          1 Reply Last reply Reply Quote 0
          • 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