Skip to content
Open Snotel home
Data

Resort registry

Where the ski resort registry comes from, how a resort keeps a stable id and slug, which of its fields are derived, and the ODbL license and attribution to show.

The resort registry is Open SNOTEL's own list of North American downhill ski areas, served by the resorts API. It is a separate dataset from the SNOTEL observations: a resort record holds no station data, and no station is treated as representative of a resort because it is nearby.

Sources

SourceWhat it givesLicense
OpenSkiData (OpenSkiMap.org)Every ski area, built daily from OpenStreetMap and Skimap.org: name, places, status, activities, website, operating area, mapped lifts and runsODbL 1.0
WikidataItems linked to a Skimap.org area (property P6400), and their official websitesCC0

Both are listed, with their exact terms, under data sources and licenses. The registry is rebuilt weekly from the current OpenSkiData build. Nothing is scraped from commercial resort directories. Each rebuild is recorded with the build it read, its checksum and format version, so any record can be traced to the file it came from.

What is included

Ski areas in the United States, Canada and Mexico that record downhill skiing, or record no activity at all. Areas that are nordic only are left out for now. Every operating status is kept, and an area with no status is unknown rather than dropped; a website or locality is included when a source has one.

Identity

A resort is identified by the stable upstream ids behind it: an OpenStreetMap way or relation, a Skimap.org area, a Wikidata item. They are listed in each resort's identifiers. OpenSkiData's own generated feature id changes when it regroups ski areas, so it is kept for tracing only and never decides which resort a record is.

  • When OpenStreetMap maps one ski area twice (a relation and a way that share a Skimap.org id), the two become one resort. Neighbours that Skimap.org happens to give one id, such as Alta and Snowbird, stay separate resorts.
  • A resort keeps its id and slug through renames and new upstream ids. If upstream merges two resorts, the older one continues and the other's slug resolves to it; if upstream splits one, the new piece is a new resort.
  • A resort the sources stop listing is marked removed, never deleted, and comes back with the same id and slug if it reappears.

Fields and precedence

Canonical fields come from OpenSkiData. Wikidata fills a website OpenSkiData lacks. A reviewed correction overrides both; to report a wrong field, write to support@opensnotel.com. fieldSources on each resort says which one supplied each field.

Elevations are meters. The base, summit and vertical, and the lift and run counts, are derived from the lifts and downhill runs mapped in OpenStreetMap, not published by the resort; they are null when nothing is mapped. The representative point is the mapped point, or the centroid of the mapped operating area. See provenance for how Open SNOTEL labels derived values.

Download

The whole registry is available as CSV, JSON and GeoJSON, with a Frictionless data package that describes the files: see download the registry. Each file says, or links, which OpenSkiData build it came from and the license it carries, and has a version that changes only when a resort does, for pinning a download.

License and attribution

The registry is derived from OpenStreetMap through OpenSkiData, so it is licensed under the Open Database License (ODbL) 1.0:

  • You may use it for anything, commercial use included.

  • Show this attribution wherever you show the data:

    Data from OpenSkiData / OpenSkiMap.org, © OpenStreetMap contributors (ODbL), Skimap.org, Who's On First, © Mapterhorn; Wikidata (CC0)

  • If you distribute a database derived from it, share it under the ODbL too.

Where space is short, the Terms accept Resort data: OpenSkiData contributors, ODbL, next to Data: USDA NRCS, NOAA/NWS via Open Snotel for the snow and weather data.

Every resort response and dataset carries the same terms: in its license block, or, for the CSV, in the Link header and the data package.