Skip to content
Open Snotel home
Start

Overview

Start here: what Snotel is, what data it serves (SNOTEL observations, NWS weather context, a ski resort registry), how to reach it over REST or MCP, and which page answers which task.

Snotel serves the public observations of the NRCS SNOTEL network, automated snow stations in the mountains of the western United States, as reported, in one consistent shape. It is an independent project with closed-source code, not affiliated with or operated by NRCS or NOAA. Credit data from it as "Data: USDA NRCS, NOAA/NWS via Open Snotel" (and "Resort data: OpenSkiData contributors, ODbL"); see Terms, section 2.

What it serves

DataWhat it isKind
StationsEvery SNOTEL site: its triplet, location, elevation and the measurements it reports.Source metadata
ObservationsSnow water equivalent, snow depth, precipitation, air temperature and more, daily and hourly, since each began.Observed
Snowpack ContextRecent change, comparison with each station's own WY1991–2020 history, accumulation events and rankings.Derived, versioned
Weather around a stationThe newest National Weather Service forecast for its grid cell, nearby NWS observations and active alerts.Forecast, and observed elsewhere
Ski resortsA registry of North American downhill ski areas, built from OpenSkiData and Wikidata.Source records, normalized

Observations are stored exactly as the source reported them: their units, flags and timestamps are the source's, a missing reading is null and never zero, and nothing calculated is mixed in. Anything that is not a measurement at the station is labeled as what it is; see provenance.

How to reach it

  • REST API at https://opensnotel.com/api/v1: public, read-only, no key. Start with the API overview.
  • MCP server at https://opensnotel.com/mcp, for agents: the same data through tools. See the MCP overview.
  • Downloads: the ski resort registry as CSV, JSON and GeoJSON (resorts). There is no bulk download of observation history; read it in bounded ranges through observations.

Both the API and MCP read the same stored data through the same functions, so they always agree. To give Snotel to an agent, see agents.

Where the meaning is defined

The data pages are the authority on what a value means, and every other page defers to them:

  • Measurements: what each element is, and its unit.
  • Quality: the source's flags and what they do and do not guarantee.
  • Freshness: which time answers "how recent is this".
  • Provenance: observed, derived, inferred and forecast values, and why a change in snow depth is not snowfall.
  • Time and dates and station IDs: timestamps, the water year, and the identifier to store.

Start with your task

ToRead
Make a first request and connect an agentQuickstart
Get the latest snow water equivalent at a stationObservations
Find the stations near a coordinateNearest stations
Know which identifier to store for a stationStation IDs
Understand a null, a flag or a provisional valueQuality
Tell whether a value is currentFreshness
Read a season or more of historyObservations over a range
Compare today's snowpack with the station's pastSnowpack Context
Use Snotel from an agentAgents
Look up a ski resort or download the registryResorts