DOCUMENTATION
Weather and go/no-go review
Read forecast timestamps, distinguish seasonal context, and set weather review thresholds.
Content updated
What weather am I looking at?
Collection cards show current model weather near the trailhead. Trip weather samples mapped stops around their planned arrival times. Forecast, historical weather and seasonal averages are labeled separately. Seasonal averages can help compare dates, but they are not a prediction for a particular day.
When was the data refreshed?
Weather displays a readable refresh date, time and timezone. Current conditions also distinguish observation time from refresh time. A refresh time means the app pulled the data then; it does not mean a person checked the trail. Offline or stale copies retain their labels. If no refresh timestamp is available, do not assume the data is fresh.
Ask for review triggers
Ask a connected assistant to propose maximum/minimum temperature, sustained wind, gust or hourly rain thresholds for your plan. Review the proposal in Account before saving. Thresholds are inclusive: a maximum-temperature rule is reached at or above that value. Only a fresh, complete forecast can report within threshold. Missing, stale, seasonal and historical data keep the assessment unknown.
- Example: “For this shared plan, propose a review trigger at 85°F or above and gusts at 30 mph or above.”
- Example: “Check expected weather for this plan and tell me when it was refreshed, with the timezone.”
Fire, smoke, closures and access
These are not checked automatically. Open the official route source links and review notices for your date. Before you go keeps these checks visible. Go/no-go results are planning prompts, not a safety clearance, and there is no background monitoring or automatic notification service.
Next step
Still have a question? Email project support. Include the control and what you expected; keep private trip links and credentials out.