New sounding with radiosonde measurements
-
@DMByass Hello, thank you for your suggestion. We are currently not planning to bring light version of the app, but in case you would really need light version of sounding, there is a Plugin released by our community - just look for flyXC Soundings. But please keep in mind this is developed by community and not by our Team. Thank you and hope this helps! Niki
-
Hi just noticed an error with the name on one of the sounding sites.
The location and data for Tocal look OK however they are labelled as Ri Point Judith, which is an old site from Rhode Island. Tocal and Ri Point Judith have almost the same ID so I can see how they got mixed up.
-
Please can someone suggest a good source for tutorials for interpretting the skew T charts ?
thank you and kind regards
Gavin -
-
The radiosonde for Vernon, BC Canada is displaying that is the San Diego Miramar, US location. The Lat Lon is correct but the label is not. -
What a great tool! Would it be possible to add in a CAPE value also?
-
@bizhertzberg Hi, thanks for the suggestion. For a more detailed evaluation of atmospheric instability, it would definitely be useful to include the CAPE index value in the sounding. I’ll check with my colleagues to see if that would be possible. Have a nice day, Jari
-
Dear Windy Team,
I will appreciate so much if clouds simbols were added when moving temperature selector.
Many Thanks in Advance,
Juan Carlos -
There is still a problem with scrolling the sounding chart in 47.1.3 on a Mac Sequoia. I have tried it on both Safari and Chrome. While it is possible to pinch zoom the chart using a track pad that puts the current temps off screen. I have not figured out a way to zoom the temperature axis. Horizontal scroll does not work. If you have be careful with pinch zoom on a trackpad as that also invokes another mac function.
I seem to recall that before about last month when you zoomed the sounding zoomed to full screen. That no longer happens
-
R Robert Hawley referenced this topic on
-
@Robert-Hawley Hello, it will be fixed in the version 48. Our devteam is already aware of this.
