3D Destination Map

Terrain, route context, and labels in one fast local scene.

A destination map can do more than show where things are. This 3D terrain surface uses local data, 1.25x relief, water, roads, rivers, trails, lift lines, and projected labels to communicate scale and visitor context.

Building terrain

Quality

Balanced 575 KB JSON · 288 x 216 elevation grid + source layers Balanced is the mobile-first default.

Static Export

The same map story can ship without runtime weight.

The static version keeps the route model, landmark priorities, water bodies, and terrain treatment available for fast pages, printable guides, and offline publishing outputs.

Static Map System

Same-origin data, no map SDK, no runtime dependency.

Shaded relief is rendered from local elevation data at build time, and the routes below are snapped to the real trail and road network before they are drawn. No map library loads on the page; the routes on the map match the colors in this list.

Classic First Look

Village arrival, Chateau edge, lakefront, and a short shoreline orientation.

Moraine Morning

Rockpile first, shoreline second, with Larch Valley as the longer option.

Tea House Morning

The classic climb from Lake Louise to Mirror Lake, Lake Agnes, and the Beehives.

Skoki Approach

From the Fish Creek parking area toward Skoki Lodge via Boulder Pass, Ptarmigan Lake, and Deception Pass.

Map Product Thinking

Layered like a system, not drawn like a one-off.

The value is what the map can keep doing after the first render: local data, reusable layers, clear performance tiers, and outputs that can support pages, guides, and demos.

Layer Budget

Every visible layer has a job.

Terrain, roads, rivers, trails, water, and labels are separated so the map can support a web page, guide export, weather overlay, or client prototype without redrawing the work.

Base geography

Local bounds, projected labels, roads, rivers, official trail geometry, lift lines, and water polygons.

Local JSON + reusable layers

Terrain treatment

A 1.25x relief scene gives the landscape scale without turning the map into a misleading illustration.

Three.js terrain scene

Visitor context

Route records, destination corridors, photo context, weather exposure, and offline guide anchors.

Reusable route records

Overlay-ready data

Weather windows, road access, smoke, visibility, closure notes, and source freshness can layer onto the same base.

Same-origin data surfaces

Terrain Tiers

Choose how much terrain to load.

Balanced loads first for a fast standard view. Lite is available for older devices; High and Ultra are opt-in when the map itself is the work.

3D terrain quality

Balanced 575 KB JSON · 288 x 216 elevation grid + source layers Balanced is the mobile-first default.

Static SVG export 0 KB runtime JS

Build-time shaded relief + snapped routes

case studies, PDF export, fallback pages

Route Context

Map data that can become visitor information.

Routes are treated as structured records with purpose, mode, distance labels, map anchors, and caption context. That lets the same map data support case studies, guide-style pages, cards, and offline artifacts.

29 water bodies

Water polygons are generated from the same source payload as the 3D scene.

224 road lines

Roads keep their source alignment instead of being redrawn by hand.

202 trail lines

Official trail geometry is treated as data, not placeholder art.

8 river lines

Curated river polylines give the map recognizable valley structure.

visitor Classic First Look

Route range: 2-4 km
Route anchors: 5

Village arrival, Chateau edge, lakefront, and a short shoreline orientation.

photo Moraine Morning

Route range: 3-9 km
Route anchors: 6

Rockpile first, shoreline second, with Larch Valley as the longer option.

visitor Tea House Morning

Route range: 7-11 km
Route anchors: 5

The classic climb from Lake Louise to Mirror Lake, Lake Agnes, and the Beehives.

backcountry Skoki Approach

Route range: 15-16 km each way
Route anchors: 4

From the Fish Creek parking area toward Skoki Lodge via Boulder Pass, Ptarmigan Lake, and Deception Pass.

Route distances are broad presentation ranges. Route anchors are lightweight map geometry for context, not turn-by-turn navigation.

Same-Origin Artifacts

Small data outputs make the map inspectable.

Map preview summary /data/field/map-preview.json

Feature counts, layer list, projection, and treatment notes.

Layer budget /data/field/map-layers.json

Static layer groups, terrain tiers, and performance direction.

Route context /data/field/route-metrics.json

Distance ranges, map anchors, and reusable route metadata.

Map System

Built to become more than a screenshot.

The same source data can support static pages, downloadable guides, route summaries, photo planning, and later live overlays when the data justifies it.

Structured content

Case studies, placements, notes, resume data, and downloads live in predictable structures instead of one-off pages.

Data surfaces

Live API data is normalized into compact same-origin snapshots that are easy to cache, inspect, and reuse.

Decision context

Weather, roads, visibility, terrain, freshness, and confidence are grouped around the decisions visitors actually make.

Offline outputs

The same source material can support web pages, downloadable PDFs, EPUB-style exports, and field-guide packages.

Operational clarity

Freshness labels, status checks, source timestamps, and fallbacks make live systems understandable when conditions change.

Deployment discipline

Private storage, CDN delivery, cache rules, link checks, privacy scans, performance budgets, and repeatable deploys.

Read terrain map notes

Publishing

One data model, multiple outputs.

The map is intentionally data-backed so it can move into a static page, a PDF, a guide, or a richer interactive surface without recreating the content from scratch.

Structured content Markdown, metadata, imagery, and reusable fields

Web publishing Fast static or hybrid pages with clear ownership

Offline output PDF, EPUB, or field-guide packages from the same source

Operational updates Repeatable builds, checks, and documented deploys