Epic: M2 — Personal pace in planner (plugin) #3
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
public/wanderer#3
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal: planner shows your moving-time and true D+ from the
trail-analyzeengine (IGN LiDAR-HD 50 cm + Minetti, fitted to 2.75 m/s from 260 runs) instead of Valhalla's generic pedestrian time — the Komoot-beating feature.Architecture: WASM plugin (no fork coupling) that on route change calls
trail-analyze /analyzewith the drawn lonlats, then renders personalized time + D+ + splits, plus a pace override.plugins/sdkoss/wanderer-pluginstrail-analyze /analyzeon route change; map result → planner UIM2 shipped — 2026-07-27 (deploy
deploy-4c34d9fd)Personal-pace is now live in the route editor. When you draw a route (≥2 anchors) a "My pace (LiDAR + your runs)" card appears with an Estimate button that POSTs the drawn GPX to the
trail-analyzeengine and shows:The estimate is invalidated automatically on any route change.
/analyzeis CORS-enabled (ACAO: *) so the browser calls it directly.End-to-end verified against a Mercantour mini-route: 846 m / D+ 188 m / ~12.5 min / 100 % LiDAR.
Scope note: built inline in the fork (
web/src/routes/trail/edit/[id]/+page.svelte) rather than as a WASM plugin. Plugin-ification (so it can ride upstream's plugin system /oss/wanderer-plugins) remains a follow-up — tracked under M0.4 (#9). Not upstreamable as-is since it depends on our private trail-analyze engine + IGN LiDAR.Closing this epic as delivered; plugin migration continues in #9.