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

    Correct decoding of raw values for the 'currents' overlay

    Scheduled Pinned Locked Moved Developers
    1 Posts 1 Posters 76 Views 1 Watching
    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.
    • I Offline
      icechoual | Premium
      last edited by

      Hi, I'm building a plugin that needs actual current speed/direction (not just display). Using getLatLonInterpolator() after switching store.set('overlay', 'currents') ?
      I get a 3-value array back per the documented RGBNumValues type. For the 'wind' overlay, docs/community posts confirm the format is [U, V] in m/s. For 'waves', it's documented as [U, V, size] where U,V are direction-only vectors and size (m) is the real magnitude. Which convention applies to 'currents' — the wind-style velocity vector, or the waves-style direction+magnitude? Is there a metrics/Metric module call needed to get real-world m/s or kt from the raw values, and if so, what's the correct usage pattern ? Thanks !

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Windy Community  |  Powered by excellent NodeBB
      Terms of Use     Privacy Policy     Windy.com