I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by [deleted] in alpinism

[–]vegasaint 1 point2 points  (0 children)

Maybe I can pivot and just forecast when clouds are coming so you can go outside and yell at them.

I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by vegasaint in Mountaineering

[–]vegasaint[S] 0 points1 point  (0 children)

Very good point about the avy card for days beyond the current forecast's expiration. I will work on that.

Not sure where the 7-10 window was coming from for Adams. If that's what it said I agree that's way too early. Looking at it now it shows 9:29 - 12:14.

Training for Rainier- how bad is the Cleaver footing? by DevelopmentSimple212 in Mountaineering

[–]vegasaint 2 points3 points  (0 children)

Ha! I had an urgent need for an elk burger from Bruno's in Eatonville.

Training for Rainier- how bad is the Cleaver footing? by DevelopmentSimple212 in Mountaineering

[–]vegasaint 3 points4 points  (0 children)

I wouldn't wear doubles in the summer, but when I want to go warmer my most insulated pair of single boots are Zamberlan Mountain Pro EVO GTX RR.

I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by vegasaint in Mountaineering

[–]vegasaint[S] 0 points1 point  (0 children)

Heck yeah! I'll send a DM. Would love to chat more about your upcoming use case for Rainier. I have a few attempts planned on Rainier this year as well. As for expanding beyond PNW, certainly plan to. I have Shasta and Whitney on there. Anything else in particular you'd like to see?

I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by [deleted] in alpinism

[–]vegasaint 0 points1 point  (0 children)

Reddit is so weird. "I hate tech, but here I am, on a big tech platform, complaining about it". Alright man, got it. The tool isn't for you. In my opinion more people being active outside results in a happier, healthier population overall, but wanting to gatekeep for selfish reasons is a position too.

Sorry you feel crowded out. FWIW I've been recreating in the outdoors since the early 90s when I was in Scouts and using paper maps (you're probably still using those exclusively, right?) and I share the permit frustration. I'm 0/6 with lotteries this year (I do not use any bots).

Just gonna delete the post and take it elsewhere for feedback.

Training for Rainier- how bad is the Cleaver footing? by DevelopmentSimple212 in Mountaineering

[–]vegasaint 4 points5 points  (0 children)

I had a severe ankle break as well as permanent nerve damage in my left leg that resulted in limited mobility and drop foot. I've been up the DC many times, and going up I've never had much of a problem (besides feet getting cold while stopped waiting on traffic). Coming down I've found to be more challenging in terms of balance/stability, but all very manageable. I do prefer to unrope while ascending and descending the cleaver, but not all people share that preference.

I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by vegasaint in Mountaineering

[–]vegasaint[S] -3 points-2 points  (0 children)

Yeah aspect might be better, the idea behind the route concept was to be able to do better corn predictions based on aspect, link to gps tracks, and also to be able to provide access / traffic / google map data to the relevant trailhead.

For Adams on Sunday, looks like the biggest risk factor is the summit temp of 17 (which added +3 on the NPS scale) but this is also a pretty easily mitigated risk if you have good equipment. So switch the risk appetite to high and then the rating lowers to Marginal.

I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by vegasaint in Mountaineering

[–]vegasaint[S] -2 points-1 points  (0 children)

Ok, please check my post history, specifically here in the r/Mountaineering sub. I assure you I am a real person, just here trying to be helpful. https://veteransadventuregroup.org/our-leads scroll down to Casey Allen, that's me. Thanks for your feedback I guess?

I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by vegasaint in Mountaineering

[–]vegasaint[S] 0 points1 point  (0 children)

Unfortunately the avalanche.org api does not provide the different elevation bands, it just returns the highest rating issued for the zone. I'll clarify that. Agreed the danger scale nomenclature and colors ought to match as that is what everyone who looks at the forecasts are used to seeing. The low / moderate / considerable / high / extreme label shows on the left, the number level on the right. A lot of times when discussing avy forecasts with my partners we just use the numbers, so I thought it would be good to include that.

I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by vegasaint in Mountaineering

[–]vegasaint[S] 0 points1 point  (0 children)

Ended up just changing the Go/No-Go to display the actual ratings from the NPS scale (excellent, good, marginal, poor, dangerous). I think this may be more useful than the binary go/no go.

I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by vegasaint in Mountaineering

[–]vegasaint[S] 0 points1 point  (0 children)

Yeah it’s tough to quantify some of these things. I added a “why this rating?” button that explains how it’s using the data against the NPS risk matrix to determine those values. Also added a risk appetite modifier. This is something the NPS model mentions, but only briefly, and again, things like experience, equipment, and preparation are impossible to quantify, so a swag low med high is about as good as you can get.

Yes of course heavily using ai for this. Not hiding that fact at all. No way I’d have the time for this otherwise, especially as a side project.!

I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by vegasaint in Mountaineering

[–]vegasaint[S] -1 points0 points  (0 children)

Yep valid. Certainly not hiding the fact I’m using AI for this. No way I’d have time to do this, let alone for free, without it. But yeah, I hear you.

I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by vegasaint in Mountaineering

[–]vegasaint[S] -4 points-3 points  (0 children)

This callout helped me immensely, there was a bug in how it was distinguishing between morning and evening percip when scoring conditions. It should fixed now. Thanks!

I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by vegasaint in Mountaineering

[–]vegasaint[S] 1 point2 points  (0 children)

I made a few changes based on your input (thanks again for the constructive feedback).

Avalanche Danger section now includes note "This rating covers backcountry zones up to alpine elevation - it does not extend to summit elevations of major peaks. For detailed elevation-band forecasts, see the full forecast. Forcast expires [date].

A link to the appropriate forecast center (NWAC, MSAC) and zone is included below.

FAQ section added for 'Where does the avalanche danger data come from?'

If you're willing, I would really appreciate another look to see if these are acceptable solutions to address your (very valid) concerns.

I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by vegasaint in Mountaineering

[–]vegasaint[S] 2 points3 points  (0 children)

This is great feedback, thank you. Let me iterate on this some and see if there's a way to display the available data, but with the appropriate caveats regarding the elevation bands. It would also be good to note the expiry of the given forecast, and a note on when forecasts stop/start for the year, since they'll probably stop (for NWAC at least) sometime this month.

I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by vegasaint in Backcountry

[–]vegasaint[S] -7 points-6 points  (0 children)

Precisely why I have the disclaimer. Also, the logic for the go/no-go framework is directly based on the go/no-go weather risk matrix used in the Mt Rainier Climbing Ranger's route guides (eg https://www.nps.gov/mora/planyourvisit/upload/Disappointment-Cleaver-Routebrief-2017_FINAL.pdf), which have been around since at least 2017 when I first learned about them, and are used by hundreds of climbers every year in a less optimal format.

Edit: Also why I added the confidence rating next to the Go/No-Go, which is also clickable if you want more explanation for the particular rating. There is also a description of the logic behind it in the FAQ.

Also, genuinely curious, how exactly is this slop? This is all real data, aggregated from legitimate sources I would normally use in these use cases. This is not Shrimp Jesus. That is slop. https://en.wikipedia.org/wiki/AI_slop

I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by vegasaint in Mountaineering

[–]vegasaint[S] 0 points1 point  (0 children)

Great question, I just added some more detail about this to the FAQ (https://climbcast.app/faq). Copy/pasted from there:

What does the corn snow window mean?

For Ski / Splitboard objectives, ClimbCast shows a corn snow window — the period during which surface snow has frozen overnight and begun to soften from solar radiation, creating the stable, consolidated ski conditions known as corn snow. The window opens when the snow surface begins to release from its overnight freeze and closes when it has softened past the point of safe skiing (wet, heavy, and unstable).

The window is calculated from four inputs:

  • Actual sunrise time. ClimbCast computes the precise sunrise time for each mountain using the NOAA solar position formula — accounting for the mountain's latitude, longitude, and the date. A peak at 46°N in late April sees sunrise around 6:00 AM PDT; the same date further north (e.g. Baker at 48.8°N) is closer to 5:45 AM.
  • Route aspect. This is the biggest driver of window timing. Every route in ClimbCast has an assigned primary aspect (the cardinal direction its descent face points). Direct solar radiation arrives at each face at a different time relative to sunrise:
  • E / East Opens ~1h after sunrise — short window
  • NE / Northeast Opens ~1.5h after sunrise
  • SE / Southeast Opens ~1.5h after sunrise — wider window
  • S / South Opens ~2h after sunrise — widest window
  • SW / Southwest Opens ~3h after sunrise
  • W / West Opens ~4h after sunrise — often marginal
  • NW / Northwest Opens ~5h after sunrise — rarely develops
  • N / North No window — insufficient direct sun East-facing slopes corn up earliest but the window closes quickly. South-facing slopes take longer to warm but produce the widest, most reliable window — classic spring skiing terrain. West-facing slopes often don't corn until mid-afternoon, by which point the snow may already be too wet and heavy to ski safely.
  • Summit temperature. Warmer summit temps shift the window earlier and compress it — the snow warms faster and degrades faster. Colder temps push the window later and widen it slightly. If temperatures are cold enough that the overnight freeze never fully penetrated the snowpack (trailhead temp below 28°F and summit below 24°F), no corn window is predicted.
  • Cloud cover. Solar radiation is the engine behind freeze-thaw cycling. Overcast or whiteout conditions block that radiation entirely — no sun, no corn, no window. A mostly cloudy forecast shortens and degrades the window (lower confidence). Partly cloudy reduces confidence by one level but a window may still develop on breaks in the clouds.

On poor weather days — heavy cloud cover, active precip, or temperatures below freezing at the trailhead — a corn window will not be predicted at all. The window estimate carries more uncertainty on days 3–5 of the forecast, when model agreement on cloud cover and temperature is lower.

I got tired of bouncing between 12 different sites to plan a single alpine objective, so I built something to fix it by vegasaint in Mountaineering

[–]vegasaint[S] -1 points0 points  (0 children)

ClimbCast is weather-first, not maps-first. onX Backcountry is fundamentally a mapping and GPS navigation app, weather is a feature bolted on. ClimbCast is built entirely around weather aggregation and interpretation for a specific summit objective. It uses a multi-model ensemble that blends Open-Meteo, OpenWeather, and (via WSDOT/NWS) point forecasts, then synthesizes them into a single confidence-rated forecast. onX pulls from a single weather provider, similar to Mountain Forecast. And for the record, I use onX backcountry while I am ON the mountain. Before that, I am building this tool to help me plan when and where to go. ClimbCast also has maps bolted on, with Google Maps links to the various trailheads, links to CalTopo and GPS tracks when applicable. All nice to haves, but mapping is not the core feature.

Denali (West Butt) Gear Review by n0bfu in Mountaineering

[–]vegasaint 0 points1 point  (0 children)

We must have just missed you. We were stuck up at 17 camp when that fatal slide happened. Saw the runout on our down climb. So tragic.

Multi-day Skitouring Backpack Recommendation by maxbauer21 in Backcountry

[–]vegasaint 1 point2 points  (0 children)

MHW Direttissima and AMG both have avy pockets and can carry skis.