📋 Daily Briefing🔍 Discover🔔 Smart Alerts🪨 Community Hub
Transparency

Data Sources

Every external signal PeakScout uses — who provides it, what it delivers, how it's ingested, and how reliable it is. No black boxes.

18
Data Sources
8
Categories
~15
Refresh (min)
100%
Attributed
Weather
Source What It Provides How Ingested Refresh Rate Reliability Type
NWS / National Weather Service ↗ Hourly forecasts, severe weather alerts, grid-point data (temp, wind, precip), fire weather forecasts, WFO alerts by county. API — NWS API v3 (api.weather.gov). Authenticated requests not required. Grid-point forecasts: hourly. Alerts: on-change, polled every 5 min. High Official Source
Open-Meteo ↗ Hourly/daily temperature, wind, precipitation probability, snow line, UV index, sunrise/sunset for any coordinate. API — Open-Meteo Forecast API. No API key required. Hourly forecast refreshed every hour. High Open Data
NOAA / National Centers for Environmental Information ↗ Climate normals, historical weather patterns, drought indices. Used for seasonal context and long-range planning. Public datasets, periodic batch updates. Monthly / annual updates. High Official Source
RainViewer ↗ Animated radar reflectivity tiles, precipitation accumulation layers, storm track history. API — RainViewer tile API. No auth required. Radar frames update every ~10 minutes. High Third Party

Known limitations: NWS / National Weather Service: Grid-point resolution is ~2.5km. Microclimate variation at high elevation not captured. · Open-Meteo: Not an official forecasting agency. Use as supplementary — NWS remains primary for official watches/warnings. · NOAA / National Centers for Environmental Information: Not real-time. Used for long-range seasonal briefings, not daily conditions. · RainViewer: Radar coverage gaps in mountainous terrain. Alaska and some rural areas have sparse radar penetration.

Avalanche
Source What It Provides How Ingested Refresh Rate Reliability Type
NAAE — North American Avalanche Exchange ↗ Unified GeoJSON feed of avalanche forecasts across 10 states + Alaska. Aggregates all regional forecast centers under one endpoint. API — api.avalanche.org/v2/public/products/map-layer. Polled every 1h, cached 1h. Morning and evening forecasts (2x daily) during season. High Official Source
CAIC — Colorado Avalanche Information Center ↗ CO-specific avalanche danger ratings (5-level scale), elevation bands, aspect distribution, avalanche activity, weather summary. Primary for CO OHV avalanche integration. NAAE primary; direct API fallback at api.avalanche.colorado.gov. 1–2x daily (morning + evening) during season. High Official Source
GNFAC — Gallatin National Forest Avalanche Center ↗ MT-specific avalanche danger, elevation bands, avalanche activity, weather. Primary for MT OHV avalanche integration. NAAE primary; direct GNFAC API fallback. Daily during season. High Official Source
BTAC — Bridger-Teton Avalanche Center ↗ WY avalanche danger ratings, snowpack summary, weather for Teton/Bridger zones. NAAE primary; direct BTAC API fallback. Daily during season. High Official Source
UAC — Utah Avalanche Center ↗ UT avalanche danger, snowpack observations, terrain ratings for Wasatch and statewide zones. NAAE primary; direct UAC API fallback. Daily during season. High Official Source
WCMAC — West Central Montana Avalanche Center ↗ West-central MT avalanche forecasts for the Bitterroot, Rattlesnake, and surrounding ranges. NAAE fallback via GNFAC aggregation. Daily during season. Medium Official Source
FAC — Flathead Avalanche Center ↗ Northwest MT avalanche forecasts for Glacier National Park and surrounding Flathead Range. NAAE fallback via GNFAC aggregation. Daily during season. Medium Official Source

Known limitations: NAAE — North American Avalanche Exchange: Off-season (typically May–Nov): no ratings published; NAAE returns no data for many zones. Individual center APIs used as fallback. · CAIC — Colorado Avalanche Information Center: Seasonal — operates approximately Nov–April. Summer CO has no active forecasts. · GNFAC — Gallatin National Forest Avalanche Center: Seasonal. GNFAC zones also covered by WCMAC (West Yellowstone) and FAC (Flathead). · BTAC — Bridger-Teton Avalanche Center: Seasonal. WY has partial coverage — some ranges lack formal forecasts. · UAC — Utah Avalanche Center: Seasonal. UDOT also operates UDOT Avalanche for highway corridor forecasts. · WCMAC — West Central Montana Avalanche Center: Seasonal. Limited coverage area. · FAC — Flathead Avalanche Center: Seasonal. Glacier NP terrain has limited field observer coverage.

Water & Hydrology
Source What It Provides How Ingested Refresh Rate Reliability Type
USGS — National Water Information System ↗ Real-time river and stream CFS (cubic feet per second) flow rates, gauge heights, historical hydrographs for 12,000+ sites. API — USGS NWIS Web Service. No auth required. ~15-minute intervals (USGS intentionally adds ~15 min quality-control delay). High Official Source
SNOTEL — NRCS Snow Telemetry Network ↗ Snow water equivalent (SWE), snow depth, accumulated precipitation, soil moisture, temperature at high-elevation sites. API — NRCS SNOTEL Metadata API and data retrieval. No auth required. Hourly at most sites. High Official Source
NRCS — Natural Resources Conservation Service ↗ Snowpack summaries, water supply forecasts, basin runoff projections for the western US. Public data portal — periodic batch updates. Daily during snow season. High Official Source

Known limitations: USGS — National Water Information System: Gauges in remote areas may have sporadic cell coverage, causing gaps. Some gauges are seasonal and go offline in winter. · SNOTEL — NRCS Snow Telemetry Network: SNOTEL sites are point measurements — conditions between sites vary. Not all trailhead elevations have nearby stations. · NRCS — Natural Resources Conservation Service: Forecast projections, not real-time observations. Accuracy degrades in extreme snow years.

Terrain & Trails
Source What It Provides How Ingested Refresh Rate Reliability Type
USFS — US Forest Service ↗ MVUM (Motor Vehicle Use Map) trail designations, trail closures and conditions, ranger district contacts, wilderness boundaries, campground status. ArcGIS REST API — USFS MVUM MapServer. Polled via ArcGIS arcx/catalog endpoints. Also direct USFS agency pages for closures. MVUM: annual updates. Closures: on-change, polled every 30 min. Medium Official Source
BLM — Bureau of Land Management ↗ Surface management agency data, OHV route designations, recreation site conditions, land status. ArcGIS REST API — BLM national surface management agency layer. Polled every 30 min. BLM updates on-change; route data annual. Medium Official Source
NPS — National Park Service ↗ National park conditions, alerts and closures, campground availability, entrance fees, shuttle status, trail conditions. API — NPS Developer API (developer.nps.gov). DEMO_KEY fallback for unauthenticated access. Alerts polled every 30 min. Campground availability via Recreation.gov. High Official Source
State DOTs — Dept of Transportation ↗ Road condition status (open/closed/seasonal), chain law requirements, road closures, travel restrictions, incident alerts, camera feeds. State-specific APIs and ArcGIS REST feeds. CDOT uses CAMS API; WYDOT uses v1 API; UDOT uses REST path; MDT uses v1; others via ArcGIS state portals. Varies: 5–60 min depending on state. Medium Official Source

Known limitations: USFS — US Forest Service: MVUM data lags trail status changes by weeks to months. Not all national forests publish real-time closure data. Some ranger districts lack digital closure infrastructure. · BLM — Bureau of Land Management: BLM field offices vary in digital data quality. Some routes are managed locally without central API updates. · NPS — National Park Service: NPS data coverage varies by park. Some smaller parks lack real-time condition feeds. Alerts are entered manually by park staff. · State DOTs — Dept of Transportation: No national standard — each state has its own data model, update frequency, and coverage depth. Rural state highways often lack real-time data.

Fire & Smoke
Source What It Provides How Ingested Refresh Rate Reliability Type
NIFC / InciWeb — National Interagency Fire Center ↗ Active fire perimeters, containment status, acres burned, evacuation zones, fire behavior narrative for major fires. API — WFIGS (Wildland Fire Incident Management) via NIFC ArcGIS REST. InciWeb for narrative content. Polled every 15 min. Perimeters update every 15–30 min during active fires. High Official Source
NASA FIRMS — Fire Information for Resource Management System ↗ MODIS and VIIRS satellite fire detection — thermal anomaly alerts from orbit. Near-real-time fire detection globally. API — NASA FIRMS Fire Alerts. No auth required for public endpoints. HEAD check availability. Satellite overpass-dependent: typically 1–3 detections per fire per day. High Official Source
EPA AirNow — Air Quality Index ↗ Real-time AQI by monitoring station, PM2.5 concentrations, ozone levels, health advisory categories. API — AirNow FireAir matrix and station data. Open-Meteo AQI used as fallback. Hourly at most monitors. High Official Source

Known limitations: NIFC / InciWeb — National Interagency Fire Center: Large fires only; small local fires may not appear. Perimeter updates lag field mapping by several hours. Historical fires removed from active feed. · NASA FIRMS — Fire Information for Resource Management System: Detects active thermal anomalies, not fire perimeters. Cloud cover blocks detection. Small/dim fires may be missed. Not a substitute for ground truth. · EPA AirNow — Air Quality Index: Monitors are sparse in mountainous terrain. Rural/wilderness AQI is interpolated, not measured. Wildfire smoke episodes may exceed monitor network coverage.

Aviation
Source What It Provides How Ingested Refresh Rate Reliability Type
FAA — Federal Aviation Administration (TFR/NOTAM) ↗ Temporary Flight Restrictions (TFRs) and Notices to Airmen (NOTAMs) affecting low-altitude airspace near wildfire zones, SAR operations, VIP movements, and special events. Parsed from FAA tfr.faa.gov via state bounding boxes. Polled every 15 min via ADDS/AWC/AWIPS cascade. On-change — FAA publishes TFRs as events occur. High Official Source
AWC — Aviation Weather Center (NOAA) ↗ METAR/SPECI surface observations, TAF terminal aerodrome forecasts, AIRMET/SIGMET for mountain weather hazards. API — ADDS (ADDSWeather.com) / AWC REST. Polled every 15 min. METARs typically every 30–60 min per station. High Official Source

Known limitations: FAA — Federal Aviation Administration (TFR/NOTAM): TFR data is airspace-centric, not trail-centric. NOTAMs are text-based and require parsing. Some military TFRs have restricted access. · AWC — Aviation Weather Center (NOAA): ASOS stations are at airports, not at trailheads. Mountain weather often differs significantly from nearest airport. Alaska has sparse METAR coverage.

Wildlife
Source What It Provides How Ingested Refresh Rate Reliability Type
State Fish & Wildlife Agencies ↗ Hunting season dates, game management unit boundaries, wildlife conflict alerts, fish stocking reports, bear activity advisories. State agency web pages and periodic data feeds. CPW, MT FWP, WY G&F most actively monitored. Others via ArcGIS state layers. Seasonal (annual updates for hunting). Wildlife alerts: on-change, polled daily. Medium Official Source

Known limitations: State Fish & Wildlife Agencies: Hunting data is seasonal. Wildlife alerts are opportunistic — dependent on field reports to agency. Not all states publish real-time wildlife data.

Recreation & Camping
Source What It Provides How Ingested Refresh Rate Reliability Type
Recreation.gov ↗ Federal campground availability and reservations, timed-entry permit availability (Rocky Mountain NP, Zion, etc.), boat launch reservations, cabin rentals. API — Recreation.gov public availability API. No auth required for availability queries. Availability polled every 15 min for subscribed sites. High Official Source
Colorado Parks & Wildlife (CPW) ↗ CO state park campgrounds, fishing regulations, hunt boundaries, state wildlife areas, trail conditions. CPW web pages and ArcGIS REST. Polled daily for availability; alerts on-change. Availability: 15 min. Alerts: daily. High Official Source

Known limitations: Recreation.gov: Reservation data is forward-looking; last-minute cancellations appear with a delay. Not all federal campgrounds are on Recreation.gov — some are managed by local agencies. · Colorado Parks & Wildlife (CPW): CO-specific. Some CPW data requires web scraping vs structured API.

Additional & Experimental
Source What It Provides How Ingested Refresh Rate Reliability Type
ArcGIS Living Atlas / National Map ↗ Terrain elevation data, slope/aspect layers, trailhead locations, wilderness boundaries, OHV route overlays. ArcGIS REST API — various feature services (USFS MVUM, BLM surface, NIFC fire). Polled via catalog endpoints. Varies by layer: annual for MVUM; on-change for fire/closures. Medium Third Party
Third-Party Webcam Feeds ↗ Visual confirmation of current conditions at trailheads, passes, and viewpoints. Used for live-mode bar and briefing radar strip. Embedded iframe/stream from third-party providers. No ingestion — rendered directly via URL. Dependent on provider stream quality. Low Third Party

Known limitations: ArcGIS Living Atlas / National Map: Esri maintains these layers; update frequency depends on source agency. Not all layers are authoritative for real-time conditions. · Third-Party Webcam Feeds: Not all areas have webcam coverage. Streams can go offline without notice. Webcam images are visual only, not machine-readable.

Frequently Asked Questions

Why does PeakScout link to authoritative agencies instead of hosting source data directly?
PeakScout is a decision-support aggregator — we process and normalize data from agencies that own the authoritative source of truth. Hosting copies of NOAA weather or CAIC avalanche data would introduce staleness and sync drift. We always link to the issuing agency so users can verify current conditions independently.
A data source went down — how does PeakScout handle it?
Each data type has a fallback path. If the primary source fails, PeakScout falls back to a secondary source (e.g., NAAE → individual avalanche center APIs → community reports). When a source is unavailable, affected signals show a "data unavailable" badge and the score confidence drops accordingly. See individual source rows for their fallback chain.
Does PeakScout pay for any data licenses?
All data sources used by PeakScout are either public APIs (no key required) or services available under government open-data mandates. We do not license proprietary data feeds. Recreation.gov campsite availability is queried against their public API. No paid data licenses are currently in use.
Can I request a new data source be added?
Yes — use the "Report an Issue" link in the Trust Center to suggest a new data source. Include the agency name, data type, and authoritative URL. Our team reviews all requests and prioritizes sources that improve decision-critical signals for mountain recreation.
How does PeakScout handle seasonal data sources that go dormant?
Seasonal sources (avalanche forecasts, hunting seasons, snowpack) are flagged with a seasonal status indicator. During off-season, the data card shows "Out of season — resumes [month]" instead of stale data. Avalanche forecasts typically end in late April for most centers; hunting data updates are annual.
What is the difference between "high", "medium", and "low" reliability ratings?
"High" = government agency with consistent uptime, structured API, and clear versioning. "Medium" = either the data is reliable but the API is informal (e.g., flat files, scraping), or the data is authoritative but updates infrequently. "Low" = data is useful but from sources with inconsistent availability, informal access methods, or significant gaps. "Experimental" = novel signal still being validated.