Compare resorts — vertical structure

Compare one model and one valid instant across two to four mountains. Every visible chart uses the same linear height, temperature and relative-humidity domains; profiles stay in separate aligned panels so differences remain legible.

Full column includes genuine surface-through-500 hPa data where supplied. Mountain detail stops its drawing above 700 hPa, while the table continues to diagnose the complete profile and marks a DGZ that sits outside the detail viewport.

Resorts 2 of 4 selected

Select two to four resorts. The same model and valid instant are used for every chart.

Model
View

72-hour profile evolution

Complete supplied-profile diagnostics at every six-hourly valid time. Full column and Mountain detail use the same values here.

Moist shading: relative to the deepest selected layer DGZ C · covered P · partly covered O · outside supplied profile — · unavailable

Complete supplied-profile diagnostics

Every row uses the full genuine profile, even when Mountain detail omits the 600 and 500 hPa drawing.

Resort Grid terrain Lifted base–top Lowest lapse Inversions Moist layer DGZ

Comparison scope

These are sparse model profiles, not soundings. Every level and table diagnostic comes from the existing buildProfile() and deriveProfileDiagnostics() path, including pressure-aware wet-bulb temperature and removal of pressure levels below each model grid point. The browser only selects and draws this build-derived data; it makes no weather-provider request.