@hangInThere Hello, thanks for reaching out. We've identified the problem and are currently working on a fix. I'll write here again when the fix will be released.

The fix is live, you can check out the radiosonde here https://www.windy.com/radiosonde/yRqyNj7r?3.771,103.211,9,p:radiosonde.

Hello Pieter,

Windy doesn't have historical data so calling the API every time wouldn't help. Check out Point Forecast API docs for more information.

Generally speaking, the way for you is to have a backend that calls Windy API and stores current measurements when a fire event occurs.

Good luck with your project!

@Makules Hello Markules,

after taking a closer look to your query I see the issue: you send baromin: 1014.7 which doesn't make any sense, since it's 35421 mbars. Try publishing pressure measurements to mbar field.

Moreover, it's important to keep 5 min interval between measurements as we ignore such requests.

For further request debugging please refer to the response you receive from the API. You'll be able to pinpoint exact reason why your request fails with detailed error messages.

Hello, thanks for reaching out.

The airfield you mentioned is actually on the map (https://www.windy.com/airport/ESNC?62.411,13.747,11,p:metars).

However, because it doesn't report any weather observations, it's not visible on lower zoom levels. Try zooming in and you will see the point.

Moreover, for better experience you can add it to favourites using heart icon. This helps to find desired stations much faster.

@northviewsp Hello, thanks for reaching out. We've implemented a fix and TAFs should be reported correctly now.