New sounding with radiosonde measurements
The feature is amazing and designed in a much more convenient way than on other websites :)
Have you considered adding a calculation of CAPE and CIN? Also, I bet for some sub-tropical latitudes the tropopause might be higher than 150hPa, therefore extending the Y axis might be reasonable.
Super dumb question: I apologize, but what does the green line represent on the new model skew-t; I think it looks like it goes up the moist adiabats and involves mixing ratios, but I am way out of my element. Either way, thank you very much for your time and consideration. You guys are constantly updating and improving. Much much appreciated.
-Mike Aerographer's Mate USN
Here is really a great application that will allow in the blink of an eye to assess the air masses to come.
I have a question about its use. Maybe a silly question...
Weather models "smooth" the real terrain. This means that a real altitude of 1631m is indicated at ~1011m on the emagram (example).
As a result, the Iso-R curve begins its rise from the 1011m level and not 1631m. Also, it doesn't start from the dew point temperature curve as I learned to plot lifts. This means that it quickly crosses the dry adiabatic.
Is there a possibility to artificially modify the altitude of the base of the emagram? Going from 1011m to 1631m?
And make the line following the Iso-R curve start from the dew point temperature curve? Like in the picture below?
I may be using the tool incorrectly...
Thank you for your work and your clarifications.
@mikachu1983 Thank you for bringing it up! In fact, we have had some pretty fiery internal discussions about this issue. In short: it is currently not possible.
We dealt a lot with the following situations:
- If the terrain is lower than the model altitude, should we display the values? Even if they are interpolated?
- If the terrain is higher than the model altitude, should we clip the non-existing heights for that location?
- Or should we allow users to choose how they want to display it?
The result was: let's not deal with it for now, it is already too complicated. Let's wait for feedback and see how important it is for others.
Appreciate all the work done to bring this functionality online. Love the ability to arrow through the different soundings and the cursor read-out is a really nice feature. Have had some issues with low-level inversions not plotting in complex terrain. They show up for coarser model resolutions but not for the NAM or HRRR soundings. For example, here's a forecast sounding from Reno, NV from the NAM on a calm morning at 6am. I would expect some kind of inversion, but the plot is showing nearly dry adiabatic.
This is great. Would love CAPE, CIN, and MUCAPE calculations to be added!
nhoctieutient last edited by
Được đề xuất
airmalik | Premium last edited by
Has the radiosonde moved? I don't see it at the bottom of the sounding forecast anymore.
Steph Bond | Premium last edited by
Love the new tool. In the southern hemisphere the flags on the wind vectors usually point down Is it possible to correct this?. Eg
Are you sure that BOM always show soundings with barbs pointing down? (Barbs are what you call flag i.e. like barbs of feather on the arrow)
Here is an example with all barbs in fact on the right side of the arrows …. as your example above.
The convention is that the arrows/feathers on the wind barbs point towards the area of lower pressure.
In the case of the southern hemisphere (BoM image above), for a westerly wind, the lower pressure is to the right of the wind (down the page). And this is the opposite case for the northern hemisphere.
For us folk in the southern hemisphere, the wind barbs appear visually wrong.....it is still the right information - just not what we are used to viewing.
Can you adjust the code generating the image to account for +/- latittudes for the location?
Personally, the direction of the wind barbs is not a biggie for me :)
I was knowing this convention that the barbs of the arrow-feather, showing wind direction and speed, point to the low pressure area on a wind map.
Concerning a sounding diagram it seems you are right.
Here are 2 examples in North hemisphere shown at 500hPa level:
In South hemisphere, in Windy Sounding forecast, the barbs are shown pointing outwards the low pressure area, which is inconsistent. The wind direction is correct (clockwise in low pressure areas) but barbs should point to the opposite:
BTW speaking of wind barbs, a lot of people don't know why we use that word. Early weather maps showed the direction and speed of the wind by arrows with a tip and feather fletching. Weather map in 1888:
Nowadays the barbs are only on one side of the arrow and the tip is missing, replaced by a circle in surface analysis maps. Barbs point towards the low pressure zone as said in the previous posts.
Can you provide a solution to the wind barb/arrow direction within the sounding tool to follow the convention that the barb/arrows point towards the area of lowest pressure?
For the current Sounding Tool....when the latitude changes to -ve (Sth Hem), the barb/arrows need to be drawn on the opposite side to what is currently being displayed.
in the Nth Hem: point to the left (up - in sounding tool)
in the Sth Hem: point to the right (down - in sounding tool)
You can follow the discussion for added comments.
@airmalik Hi, thank you for the report. We will fix it in the next version.
Love the new zoomable sounding. Each time I close it down, I have to re-enable the paragliding spots toggle if I want to look at a new site. Don’t think I had to do this with the previous sounding and I don’t see an advantage to it. Is this a small bug?
@Mark-Mortimer Hello, it is correct since the new sounding is technically a POI overlay, so when you select it, the other overlay gets unselected.
Great job with the new sounding! Really love it. Only on my mobile device (Android) the time bar, were you can adjust day and daytime, disappears now. This makes it quite hard to check the development over the day. I hope you can make the time bar topmost or so :)
@fcrgb Hi, thanks for the feedback. I discussed this with our development team, and we will consider adding the timeline back into the future release.