Windy Community
    • Unread
    • Categories
    • Groups
    • Go to windy.com
    • Register
    • Login
    1. Home
    2. SMA IT Solutions
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 4
    • Groups 0

    SMA IT Solutions

    @SMA IT Solutions

    1
    Reputation
    1
    Profile views
    4
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online
    Website www.eaware.io
    Location Avenida Água Verde, 1535

    SMA IT Solutions Unfollow Follow

    Best posts made by SMA IT Solutions

    • RE: Map Forecast - Accumulations Bars

      @Suty Of course, it is in our used project, but it is not in production for use yet, we are first using the free version and analyzing if everything will work out, if it does, we will use the paid version, we have already paid for the Point Forecast plan, so don't worry

      But anyway, thanks for your attention.

      posted in Windy API v4
      SMA IT SolutionsS
      SMA IT Solutions

    Latest posts made by SMA IT Solutions

    • Incorrect temperature data?

      Hello, I pay for the Point Forecast API, we use the data to improve our agricultural production, so the values ​​need to be correct and as accurate as possible, but I noticed a very large inconsistency in the temperature of the city of São Paulo, lat: 23.5489 lon: 46.6388.

      When searching the API with these parameters:
      {
      "lat": 23.5489,
      "lon": 46.6388,
      "model": "gfs",
      "parameters": ["temp", "cape", "ptype", "dewpoint"],
      "levels": ["surface", "1000h"],
      "key": "secret key"
      }

      the ts value: [
      1744880400000,
      1744891200000,
      1744902000000,
      1744912800000,
      1744923600000,
      1744934400000,
      1744945200000,
      1744956000000,
      1744966800000,
      1744977600000,
      1744988400000,
      1744999200000,
      1745010000000,
      1745020800000,
      1745031600000,
      1745042400000,
      1745053200000,
      1745064000000,
      1745074800000,
      1745085600000,
      1745096400000,
      1745107200000,
      1745118000000,
      1745128800000,
      1745139600000,
      1745150400000,
      1745161200000,
      1745172000000,
      1745182800000,
      1745193600000,
      1745204400000,
      1745215200000,
      1745226000000,
      1745236800000,
      1745247600000,
      1745258400000,
      1745269200000,
      1745280000000,
      1745290800000,
      1745301600000,
      1745312400000,
      1745323200000,
      1745334000000,
      1745344800000,
      1745355600000,
      1745366400000,
      1745377200000,
      1745388000000,
      1745398800000,
      1745409600000,
      1745420400000,
      1745431200000,
      1745442000000,
      1745452800000,
      1745463600000,
      1745474400000,
      1745485200000,
      1745496000000,
      1745506800000,
      1745517600000,
      1745528400000,
      1745539200000,
      1745550000000,
      1745560800000,
      1745571600000,
      1745582400000,
      1745593200000,
      1745604000000,
      1745614800000,
      1745625600000,
      1745636400000,
      1745647200000,
      1745658000000,
      1745668800000,
      1745679600000,
      1745690400000,
      1745701200000,
      1745712000000,
      1745722800000,
      1745733600000
      ],
      the temp-surface value: [
      299.76771779434154,
      303.0753916178455,
      302.03165707353776,
      298.84618915369936,
      295.5777375211752,
      293.56991440206457,
      291.3074733986962,
      295.49562903892354,
      301.06644108326043,
      304.30960003967994,
      303.04159882243994,
      299.6753438975066,
      296.9356797913315,
      295.476492644686,
      293.9709182850323,
      297.86143624000283,
      303.14484634483773,
      305.55893956393487,
      303.9866103406619,
      300.81111114712394,
      298.82319581178615,
      297.7903348930412,
      296.60571791766876,
      300.0633825025181,
      305.3395830820822,
      307.21686335678174,
      305.47318181580533,
      301.91875234753644,
      299.94058322228693,
      298.76550477520493,
      298.0083562776216,
      303.31516025355154,
      307.4132858343778,
      308.9236665442121,
      307.4892677035906,
      304.2441209356766,
      302.486406038926,
      301.0333455053194,
      299.4301903694685,
      304.9686782253996,
      309.8906626641859,
      310.9350795915439,
      308.57757966238177,
      306.05814726849354,
      303.2670670829174,
      301.216357672535,
      300.4134746761655,
      305.51508903574415,
      308.9383971174508,
      310.4486146487295,
      307.8471776134886,
      304.39388918080977,
      301.5093966894093,
      299.3244506654957,
      298.44687639394334,
      305.1767160492654,
      309.58557810303205,
      310.77706341215014,
      308.49517449184737,
      304.61606420134876,
      302.3515463800011,
      301.1495583056734,
      300.7994512976118,
      307.79331385575483,
      311.5091714186692,
      312.19321592338247,
      309.3365379584899,
      306.4341996668818,
      303.8719699882065,
      302.1676886511796,
      300.1197977794833,
      307.85331906094166,
      312.1994018740778,
      312.6382186786822,
      309.7972800271897,
      306.0609658071796,
      303.624398450664,
      297.93120248969194,
      296.1543808675321,
      301.1710237029306
      ]

      Searching for the current time that I am sending this message 12:00 UTC-3 15:00 (UTC) we would have the 3rd position of the array index 2 (1744902000000) and the equivalent value in the temp-surface would be (302.03165707353776) K

      Since I am in Brazil, I need to convert to Celsius, which would give me an approximate value of 28.881657073538 °C. But when comparing this temperature with what is shown on your official map, the value is not the same. You present the temperature as 25 °C, which is a considerably different value from what is presented in the API.

      windy wrong temp.png

      I would like to know why this difference exists, if it is supposed to be like this, and if so, a prediction of when this could be resolved.

      posted in Developers
      SMA IT SolutionsS
      SMA IT Solutions
    • RE: Map Forecast - Accumulations Bars

      @Suty Of course, it is in our used project, but it is not in production for use yet, we are first using the free version and analyzing if everything will work out, if it does, we will use the paid version, we have already paid for the Point Forecast plan, so don't worry

      But anyway, thanks for your attention.

      posted in Windy API v4
      SMA IT SolutionsS
      SMA IT Solutions
    • RE: Map Forecast - Accumulations Bars

      @Suty We are using it in a private project, so it would not be possible for you to have access, the project is exclusively for the desktop version, this accumulation bar is hidden by css style, so I brought it back to the screen, and I thought that maybe it would only be available in the paid version.

      posted in Windy API v4
      SMA IT SolutionsS
      SMA IT Solutions
    • Map Forecast - Accumulations Bars

      I'm using the free version of the Windy map, and I would like to know if there is any way to make the accumulation bar work.

      I looked at the documentation but I didn't find anything talking about it. Would I have access to this on the paid map?

      4e15ae50-cd7a-4ec7-a097-34ddd6c9e0dc-windy forum map.png

      posted in Windy API v4
      SMA IT SolutionsS
      SMA IT Solutions