Expand description
What a route is, before any question of where it lives.
A route is a named, ordered list of waypoints, nothing more. Signal
K’s own Route resource carries none of IEC
61174 (RTZ)’s per-leg richness – no per-leg cross-track corridor,
planned speed, safety-contour override or rhumb/great-circle choice,
only name/description/distance/a line – and no client needs
that richness either, recomputing a whole route from one global
vessel-settings struct rather than per leg. See crate::signalk’s
own doc for the rest of that reasoning.