METHOD, SOURCES, LIMITS
No mystery score. No manufactured certainty.
Every briefing separates source facts from our planning synthesis, shows missing layers and links back to the authority.
1. National Parks with a curated Featured 5
The live NPS directory makes the planner available for every National Park currently returned by the official feed. Five featured parks add manually reviewed operations, seasonal context and deeper park pages; other parks use current NPS directory facts and clearly labelled generic official checks instead of thin generated pages.
2. Treat the visit date as a park-local date
“Today” is calculated in the selected park’s time zone, not in our server time zone or the visitor’s home time zone. That prevents a late-evening visitor from accidentally having today rejected because UTC has already moved to tomorrow. Dates up to 90 days ahead can produce an early plan; if the NWS forecast is not published yet, that absence is labelled and weather is never guessed.
3. Match NWS hourly periods to your actual visit window
We request NWS point metadata for the park coordinate, follow the official hourly forecast endpoint, and summarize the hours between your selected start time and duration. The full day remains visible for context. A representative point is still only a sample of a large park.
4. Compare weather windows without calling one “safe”
For complete forecast data, we compare 3-hour windows from 7 AM through 8 PM using the same transparent weather-friction inputs: precipitation probability, sustained wind, freezing-range temperature, high heat and stronger forecast wording such as thunderstorms, freezing precipitation, snow, fog, smoke or dust. The lowest sampled window is a planning comparison, not a recommendation to undertake an activity.
5. Only count NWS alerts that overlap the selected date
The NWS endpoint returns alerts active at retrieval time. ParkVisitCheck filters those alerts by their effective and expiry times before they can change the selected-date friction. An alert that expires before your chosen day is not treated as though it applies to that day.
6. Keep the NPS layer honest
NPS API access requires a private API key. When it is connected, we request current alerts and same-date events. NPS says the API load can lag NPS.gov by up to about two hours, so current conditions on the park website remain the final operational check. When the API layer is unavailable, ParkVisitCheck produces an explicitly labelled weather-only view instead of pretending there are zero park alerts.
7. Explain visit friction
The categories are product heuristics for trip planning, not official NPS/NWS categories, accident probabilities, crowd predictions or safety certifications.
8. Recheck close to departure
Forecasts change. Park alerts change. Roads, trails, fire restrictions and facilities can change independently. Use ParkVisitCheck to compare a real visit window and reduce tab-hunting, then use the linked official source for the exact feature you need.
9. Daylight is a derived planning input
Sunrise and sunset are calculated from the park’s representative coordinates and selected date. They help with arrival/exit timing and daylight overlap, especially for hikes and photography, but they do not account for terrain shadow, canyon walls, tree cover or trail travel time.
10. Park logistics stay park-specific
Weather cannot answer whether Tioga Road is open, whether Zion shuttle hours fit your day, whether a Smokies parking tag is required, or whether a Grand Canyon rim has seasonal limitations. Each park therefore has a curated set of official NPS checks for roads, transportation, permits, parking, operating dates and other high-impact logistics. Dated planning notices are shown only while their stated date range applies and always link back to NPS.
11. Visit style changes what we emphasize
The optional visit style—general day, family/easy day, day hike, scenic drive or photography—does not change official facts. It changes which planning considerations we surface most clearly so the same forecast is easier to use for a real itinerary.