Compare the same valid instant across two to four mountains and multiple models at once. Every visible chart uses shared height, temperature and relative-humidity domains; profiles stay in aligned small multiples so model and resort 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.
Each row isolates one atmospheric ingredient through time. Select a date heading or any value to move every chart to that valid instant.
Relationships derived from each model’s existing supplied profile—not a snow score.
Every row uses the full supplied profile, even when Mountain detail omits upper levels.
| Resort | Model | Moist layer | Resort coverage | Moisture + DGZ | Base / top T · Tw | Warm layers |
|---|
Exact grid terrain, lowest-layer lapse rate, raw DGZ coverage and supplied-profile notes.
| Resort / model | Grid terrain | Lifted base–top | Lowest lapse | Moist bounds | Raw DGZ coverage |
|---|
Moist layer shows how deep the modelled humid, potentially cloud-bearing column is. It is not a freezing level or snow level.
Dendritic growth zone (DGZ) is the cold altitude range especially favourable for dendritic crystal growth. The highlighted overlap asks whether the diagnosed moisture actually reaches that range.
Dry-bulb / wet-bulb describes the thermal path falling precipitation encounters. Their difference shows evaporative-cooling headroom; when they are close, the air is already near saturation.
Resort band separates upper and lower mountain conditions and marks any part below model terrain as unavailable—not dry. Warm inversion markers show layers where modelled temperature rises with height.
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. Resort, moisture and DGZ coverage are interval intersections;
base/top temperatures are straight interpolation only between genuine adjacent levels.
Nothing is extrapolated beyond the supplied profile.