- Supported the display of various route types though design
- Enabled clearer route differentiation through visual styling
- Integrated both existing route data and future UGC into a single, scalable system
- Created a flexible design tl support various route styles
- Introduced design elements as groundwork for more complex future states

I worked with GIS engineers and paddling SMEs to define route logic for four major paddling categories:
- Whitewater routes (requiring rapid class, hazards, gage readings)
- River routes (non-technical flowing water)
- Lake routes (circular, open water with limited flow logic)
- Ocean routes (influenced by tides, wind, and surf conditions)
Each type informed how data was collected, visualized, and surfaced.

I built flows that supported route segments, loops, and out-and-backs while also integrating support for portage points.
Although portage routes (a distinct combination of routes and points) weren’t live yet, we introduced portage icons, metadata, and mapped take-in/take-out locations to prepare the system for more advanced trip planning.

I introduced subtle UI changes (text heirarchy, color, iconography, line styling) that helped differentiate between calm lake paddles and technical whitewater runs, so users could anticipate difficulty at a glance.

The system was designed to grow with the ability to filter by route type, difficulty, length, and user rating without needing to overhaul the submission or exploration flow later.

Designing for diverse paddling environments required more than just map styling, it meant understanding the mindset and safety needs of each paddler type.
Collaborating with GIS engineers and real-world guides helped me translate technical constraints into intuitive flows.
In the next steps of this feature, I’d focus on how to visually present multiple routes on the same body of water without overwhelming the user, whether that’s through layering logic, route clustering, or preview-based selection.