Real road travel times, not straight-line guesses

Straight lines lie

Two properties can look equally close on a map and be nothing alike to drive to. One is a two-minute hop; the other is across a river with the nearest bridge five kilometers away. A dispatch engine that scores on straight-line distance will happily send a tractor the wrong way.

Snowmass never guesses with straight lines. It scores on real road travel time.

Where the numbers come from

Snowmass uses OpenRouteService — a routing engine that knows the actual road network: one-ways, highways, bridges, and turn restrictions. Travel times between your properties are computed as a matrix — the real driving time from each point to every other point — and the swarm's scoring reads from that matrix on every decision.

Because it's real routing, the same road data also powers turn-by-turn navigation to the operator's next stop, with a straight-line fallback only if routing is briefly unavailable.

Why it matters

• Smarter next-stop choices — the engine favors what's genuinely quick to reach, not what merely looks near on the map.
• Honest ETAs — customer-facing arrival times are built on real drive times, so they're credible and they move.
• Geography-aware — rivers, highways, and dead-ends are respected instead of ignored.

Kept fresh

The travel-time matrix is refreshed in the background so the numbers stay current as your property list changes. You don't maintain any of it — you drop properties on the map, and the real road network does the rest under the hood.