#30DayMapChallenge · 03 November 2026 · Polygons
Where the ski kilometers are.
Ten reviewed Austrian resort areas: place on the left, mapped downhill kilometers on the right. Hover, focus or tap to link the two views.
Vorarlberg · Tirol · Salzburg
The longest mapped ski networks
Downhill kilometers across ten reviewed resort areas.
Mapped kilometers, not advertised piste totals. Four areas use reviewed 2011 planning outlines; Ischgl–Samnaun coverage is partial.
How the comparison was made
Length definition. Sum of mapped downhill statistics across difficulty classes; Nordic trails and lifts excluded. Full cross-border resort areas are retained, not clipped to Austria.
10 reviewed areas shown. Source: OpenSkiData / © OpenStreetMap contributors, snapshot downloaded 2 November 2026 (ODbL). 355 of 375 qualifying records have downhill-length statistics; 20 missing values are not zero. Tirol’s planning polygons are not used for these lengths.
Which records count as a resort area?
Named resort/destination areas are compared, not entire ticket alliances. Ski amadé, the broader Schladming–Dachstein and Oberstdorf–Kleinwalsertal regions, and the combined Damüls–Mellau–Faschina record are excluded. Lech/Zürs is not counted again alongside Ski Arlberg. The Austrian association of the Drei Zinnen record is uncertain, so it is excluded. These are editorial unit decisions, not an automatic or universally accepted resort classification.
Mayrhofen–Hippach includes its different mountains; inclusion does not imply all pistes connect by lift. Point-only records such as Sölden and SkiWelt remain eligible. All numerical totals come from the cached source’s downhill difficulty categories, not current marketing claims.
Grouping references: Ski amadé · Schladming–Dachstein · Kleinwalsertal · Damüls / Faschina.
Download chart data (CSV) · Values, calculation and candidate audit (JSON) · Record-by-record review decisions
Loading the local map…
Sources, boundaries and polygon matching
An outline is not a piste.
The map emphasizes the same ten resort areas as the chart: six OpenSkiData outlines and four manually reviewed associations with five original Tirol planning polygons. These planning envelopes date to 2011 and are not equivalent current resort boundaries. Ischgl–Samnaun has partial planning coverage without the Swiss extent; its chart length still includes the full cross-border resort. Other OpenSkiData and Tirol polygons are muted context. The accent color is reserved for the selected resort. The neutral political basemap shows Austria and neighboring countries, with fine dashed Austrian state boundaries and scale-aware country, state and city labels. The fixed view frames Vorarlberg, Tirol and Salzburg. All ten resort names and their leaders remain visible and stationary. Ski Arlberg is selected initially; hover, keyboard focus or tapping a ranking row changes highlight color only. Escape selects the first resort. Point-only source records use the reviewed planning polygons for display; no boundary is invented. Source geometry and ranking values remain unchanged. Pan and zoom remain disabled. Selection persists between rows and on horizontal exit; leaving above or below the ranking selects its first or last resort respectively.
A ski-area outline can include forest, rock, buildings and land between pistes. It is not a measurement of skiable terrain, cleared land, ownership, or a legal resort boundary. Some records overlap or represent parts of larger connected areas.
Missing geometry is not missing skiing. Of 375 source records tagged as operating downhill areas with an Austrian country association, 188 have Polygon or MultiPolygon geometry. The other 187 are points and are not converted into invented polygons. Some of those ski areas can be represented by the independent Tirol layer. Neither source’s record count is a count of unique resorts; overlaps are retained, not deduplicated.
Sölden is included through Tirol. The official polygon is named Ötztaler Gletscher. It contains OpenSkiData’s Sölden reference point; 219 of 223 associated piste records intersect it. This supports the association—not a claim that the older planning envelope equals today’s operational footprint. The original source name is retained in the downloadable data.
The source is imperfect. Country and region classification may be coarse or inconsistent, including for areas near or across borders. All selected source polygons are shown in full; the generalized Austrian border is context, not a tool for validating, clipping or reclassifying them. “Operating” does not mean lifts or pistes are open today.
Sources, licensing and method
Data from OpenSkiData / OpenSkiMap.org, © OpenStreetMap contributors (ODbL), Skimap.org, Who’s On First, © Mapterhorn.
The reduced ski-area dataset is distributed under ODbL 1.0. Geometry is retained as supplied: no convex hulls, artificial buffers or generated substitute boundaries. The four reviewed display fallbacks reference original Tirol features without altering either source file. Official resort boundaries have not been independently verified.
Official planning boundaries: Land Tirol – tiris, Schigebietsgrenzen, CC BY 4.0. All 102 supplied polygons are valid and retained without clipping or geometric union. The source layer’s STAND field is 30 October 2011; this is not a current piste survey.
Political basemap: shared Austrian state boundaries, country outlines and reference labels from Natural Earth, public domain. This locally rendered map requires no external tiles or data API. Shared state edges are drawn once; administrative lines are generalized context, not surveyed boundaries.
Design follows Datawrapper’s guidance on restrained backgrounds, clear legends, useful labels and narrow-screen testing. Source colors are categorical; fill does not encode resort size, quality or activity.
OpenSkiData polygons (ODbL) · Tirol polygons (CC BY 4.0) · OpenSkiData coverage · Tirol dates and Sölden match · Manual polygon matching review · Reviewed crosswalk · Spatial audit · Full method and reproduction
AI assistance: source inspection, preparation, implementation and checks. Static HTML, CSS, JavaScript and local Leaflet. Permanent SVG labels use measured text and dedicated leader gutters. No visitor-time OpenSkiData queries.