if you find any issues:
for the plugin please use https://github.com/rittels/windy-plugin-radiosonde/issues
if clearly in the skewt display code, please use https://github.com/rittels/skewt-js
for any backend functional issues and feature suggestions please file an issue at https://github.com/mhaberler/radiosonde-datacollector/issues and I'll look into it.
For operational issues, the DevOps Borat strategy applies:
johnckealy last edited by
Wow.... Amazing work guys!
Excellent work, very useful !!!
Few improvement. Added lines for LCL, CCL, TCON, and control of these lines.
The plugin is published on github: https://github.com/rittels/windy-plugin-radiosonde
the skew-t part is here: https://github.com/rittels/skewt-js
We're tracking a webserver issue with a certain german corporate environment - obviously their firewall mangles headers leading to a 404 on some data files
service will be shaky for an hour or two until the issue is nailed
back to normal
certain corporate firewalls like to strip any accept-encoding headers, killing the advantage of precompressed assets like brotli or gzip.
working on a fix
reported as fixed by users
Hello to all. This plugin is very useful for my work. I am the head of the air defense against hail and I need data for daily predictions .
The development of the program is an important acquisition for all of us who are engaged in activities that depend on good weather forecasts, and Windy is, in my opinion, a more complex meteo site that is accessible to the public. Thanks again to the groups that build and develop the products.
It would be great for my activity if we could integrate https://www.flightradar24.com/ as a layer in the program.
With regards Darko Kralj
Best plugin to display radiosoundings.
I use it in my job as a flight weather forecaster as well as for my hobby as a balloon pilot.
Deutscher Wetterdienst pc_met, €79,50.-/yr, no history/download
Windy Radiosonde, free, with history+download:
Germany: 14 vs 10 stations
British Isles: 8 vs 2
Austria: 3 of 4 not present
Spain: 6 versus 3
Slovakia: 1 vs 0
Hungary: 2 vs 1
Croatia: 2 vs 1
Italy: DWD - 2 out of 4 have "technical issues"
@rittels Thanks to you and the whole contributors, it's very usefull and easy tu use!!! and YES we enjoy it!
Just an issue: when I use AROME, in an available area of course, because there are not any altitude data, your plugin will use ECMWF without any mention on that. Despite AROME or ARPEGE are very accurate we missed until now this data...
Yes, geopotential height is not available for Arome, via Windy. I use calculated values, which is not ideal.
Would you recommend that I leave it out, or use ECMWF?
Hello, I'm not sure if this belongs in the Bug reporting topic or on here but ever since about a week or so ago, both the forecast and observed soundings look very compressed vertically compared to what they used to look like, no matter what web browser I use. Has this been intentionally changed recently?
I've attached a couple of before and after screenshots to illustrate my point:
The reason why altitude parameters are not shown with AROME is because Windy use the 1.3km version of this model. The 2.5km version includes altitude parameters. But difficult to imagine Windy showing both.
Thank you. I fixed the flat skewt a few days ago, but another bug crept into extra settings. Will fix later.
To the development team that put together this plugin "windy-plugin-radiosonde"....top shelf - great effort!!
From a Prof Met's perspective....this is a very useful tool and one I only recently discovered and now use continually....so a BIG thanks!
One issue: could you take a look at the numerical wind speed values within the Skew-T diagram when you mouse over a level. It appears the numerical values are displaying speed in metres/sec when there is a knots value displayed. For comparison, the wind barb notation is correct in units of knots.
Wind barb is ~60kts....numerical wind speed is 30.3 m/s (and not kts as displayed). Could you correct the numerical value to "knots"?
Otherwise, great work! Highly appreciated.
PS: If you could incorporate real-time sonde data (during the balloon flight) from Sondehub into the Skew-T diagram up until the completion of the sonde (with the data then replaced by completed sonde data - as currently displayed), then that would be a GOLD medal in my books.