Building AndesMap: Designing a Focused Tool for Mountain Exploration
The Andes are one of the most dramatic mountain systems on Earth—long, remote, complex, and wildly diverse. Yet when it comes to digital tools for exploring ski routes, volcanoes, and backcountry terrain, most maps feel generic, cluttered, or optimized for cities instead of mountains.
AndesMap began as an experiment: what would a map look like if it were designed specifically for mountain travel in the Andes? Not navigation. Not commerce. Just clarity.
You can explore the live project at andes-ski.vercel.app.
The Problem: Too Much Data, Not Enough Context
Most mapping platforms prioritize roads, businesses, and dense labeling. In mountainous regions, this creates noise instead of insight. When planning backcountry travel, the questions are different:
- Where are the actual ski routes and alpine access lines?
- Which peaks and volcanoes are meaningful objectives?
- Where are trailheads, parking, and access points?
- How does terrain shape movement and decision-making?
AndesMap focuses on answering these questions directly—nothing more, and nothing less.
A Calm-First Design Philosophy
The guiding principle behind AndesMap was simple: calm first, detail on demand.
Instead of showing everything by default, the map starts quiet and legible. Layers like routes, volcanoes, protected areas, and ski resorts are opt-in. As users zoom or toggle features, detail appears gradually, always in context.
- Labels appear only at meaningful zoom levels
- Icons scale gently to avoid visual dominance
- Overlap is allowed selectively, never globally
- Terrain shading supports orientation, not spectacle
The result is a map that feels stable, readable, and intentional—even when exploring complex terrain.
Designing with Real Geospatial Constraints
AndesMap is built using MapLibre GL with custom vector and raster data. This allowed full control over styling, interaction, and performance. Every layer—routes, peaks, protected areas, parking, snow—was treated as a design problem, not just a data problem.
One of the most valuable parts of the process was visual debugging. When labels collided, disappeared, or repeated, the map itself revealed exactly where assumptions broke down. Iteration happened directly in the canvas.
You can see this philosophy reflected throughout the live map at andes-ski.vercel.app.
Experimenting with Snow and Weather Layers
As an experiment, AndesMap includes an early snow overlay based on ERA5 data. The goal wasn’t visual flair—it was to explore whether static environmental layers could support better situational awareness.
Even in early form, the experiment surfaced important questions: how often should snow data update? When does weather add value versus noise? How should uncertainty be communicated visually?
These questions now inform the project’s roadmap and future iterations.
What AndesMap Is (and Isn’t)
AndesMap is not trying to replace turn-by-turn navigation tools or full-featured trip planners. Instead, it aims to be:
- A situational awareness tool
- A regional exploration interface
- A visual thinking aid for mountain travel
It’s a map you open to understand where you’re going—before you decide how to get there.
Closing Thoughts
Building AndesMap reinforced a belief that applies far beyond mapping: the best interfaces don’t show everything—they show the right things, at the right time.
Mountains demand respect, clarity, and humility. A map built for them should too.
Explore the project at andes-ski.vercel.app.