How it works
Risk, weighed before you drive.
Tsamaya layers a risk model on top of ordinary turn-by-turn routing. Here’s the whole pipeline — from the moment you pick a destination to the route on your screen.
The pipeline
From destination to lower-risk route, step by step
-
1 · Fetch the fastest route
We start with a standard Mapbox Directions route — the same fast line any map app would give you. That’s the baseline we test.
-
2 · Sample & test against risk zones
Every third coordinate of the route is ray-cast against all active danger zones for the current time band. Only red and elevated-orange zones count — caution-yellow is shown but never forces a detour.
-
3 · Already on a safe corridor?
If the route is already running along a curated safe corridor through a zone, that’s a pass-through — no detour needed. Corridors are the local knowledge that stops the app over-reacting.
-
4 · Find bypass waypoints
For genuine danger, Tsamaya picks the closest safe-corridor point to each hotspot and injects up to two waypoints — nudging the route around the area rather than through it.
-
5 · Re-route & sanity-check
We re-fetch with those waypoints. If the safer line ends up more than 30% longer than direct, we don’t pretend it’s reasonable — we hand back the direct route, clearly flagged as risky, and let you decide.
-
6 · Drive it your way
Follow along with in-app turn-by-turn navigation, or hand off to Google Maps — Tsamaya seeds it with the bypass waypoints so it follows the lower-risk line instead of recomputing its own.
Time-aware
The same road isn’t equally risky all day.
Every zone carries three separate risk bands. Tsamaya reads the clock — or your manual override — and routes against the band that actually applies right now.
Want the engineering detail?
Architecture, data pipeline and the exact thresholds are on the technical page.