Find your mountain

Map tiles and map data © OpenStreetMap contributors, used under the ODbL. Loading a map -- here, or the smaller one on the home page -- asks tile.openstreetmap.org for tiles, which is the one request a page on this site makes to anyone else unless you switch on the piste overlay. That overlay is piste overlay © opensnowmap.org, CC-BY-SA — OpenStreetMap's own piste ways, rendered by a project running on donated server costs, so nothing is asked of tiles.opensnowmap.org until you press the button.

A solid marker with a continuous outline is a resort with prices on this site — click it for the link. A hollow marker with a dashed outline is a resort with no pricing collected; its popup says so in the same words the guides use. The two differ by fill and by outline as well as by size, so the distinction survives greyscale and does not depend on telling colours apart. Colour carries the region grouping only, and the lists below carry it in words. Everything in a popup also appears in the resort list. “Show on map” selects the same resort with a keyboard.

The shaded areas are ski area boundaries as OpenStreetMap holds them — the same object each resort's coordinate already cites, fetched once and kept in this repository. A priced resort is shaded, with a continuous boundary; an unpriced one is barely shaded, with a dashed boundary — the same fill-and-outline pair the markers use, and readable in greyscale for the same reason. 48 of the 60 have a boundary; 12 do not. Each resort's location sources state the recorded reason; missing evidence is never replaced by an invented boundary.

No piste maps. A resort's trail map is its own copyrighted artwork, so none is reproduced here or linked as an image. The base tiles are OpenStreetMap's standard style. The optional overlay is OpenStreetMap piste data under CC-BY-SA, which is a different thing from a resort's artwork, and it stays off until asked for.

Location evidence

A coordinate is a fact about a place, not a published price, so it is kept out of the pricing data entirely: it carries its own source and its own read date, and it is never seeded alongside a figure or traced against the pricing documents. Nothing on this page was positioned from memory. Where no source could be retrieved for a resort, no coordinate is shown, no marker is drawn, and the resort says so.

Read from: Japanese Wikipedia (45 resorts) · OpenStreetMap (11 resorts) · Wikidata (4 resorts).

Each resort records the date its coordinate was read. Each position was read from the source named for its resort and then re-read independently to confirm the citation carries the figure. Where a second source was available it is recorded with the distance between the two. Nothing here was written from memory: a resort whose position could not be retrieved is a recorded absence, not a guess. The twenty resorts added on 2026-08-27 were located by a script that takes two independent sources per resort from Japanese Wikipedia, OpenStreetMap and Wikidata, records the distance between them, and writes nothing for a resort whose sources disagree by more than 6 km or where fewer than two answered. Four resorts were refused by that rule and resolved by hand; each says in its note what the cross-check object actually is, because in every one of the four the obvious article describes the plateau or village the resort sits on rather than the resort.

The 48 boundaries were fetched from OpenStreetMap; each resort records its own retrieval date. They were collected by a script that reads the OSM object each coordinate already cites and takes its geometry unaltered. ODbL. © OpenStreetMap contributors. They are stored in the repository and served from it; no page fetches geometry.

The map is drawn by Leaflet, served from this site rather than from anyone else's CDN, over OpenStreetMap's tiles. The markers are exactly the 60 coordinates above — the script places them, and computes nothing.