No description

Matt 53ffba5795 MVUM Layer 1: per-edge annotation + accurate closure counts ... Annotate each network-leg segment with its MVUM access status for the selected mode, using the Layer-0 MVUMSpatialIndex. No routing-decision or Valhalla changes. - mvum_annotate.py (new): annotate_network_edges(coords,(lat,lon)), mode, spatial_index, on_date) -> [EdgeAnnotation{coord_pair_index, matched_features, mvum_status}]. Walks consecutive pairs, queries the index (10m buffer), applies a parallelism filter (acute angle to the edge <=45deg, both directions), resolves per-mode access via the existing check_access/get_mode_field/symbol_to_access (worst/most-restrictive across matches). Mode map: foot->open (skip), 2w->e_bike_class1, 4w->atv, vehicle->highclearancevehicle; auto is already resolved to a concrete candidate upstream. - router.py: _route_D_network_only and _build_response annotate the network leg using the injected self.spatial_index (getattr-guarded; skipped + debug-logged if None), attach edge_mvum to the network feature, and add summary.mvum_closed_crossings + summary.mvum_segments_annotated. - offroute_route.py: inject app.config[MVUM_SPATIAL_INDEX] onto the router per request. - DirectionsPanel.jsx: warning row when mvum_closed_crossings>0. - tests/test_mvum_annotate.py: parallel match, perpendicular reject, seasonal closure, symbol fallback, summary count. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-26 01:18:03 +00:00
backend	MVUM Layer 1: per-edge annotation + accurate closure counts	2026-05-26 01:18:03 +00:00
frontend	MVUM Layer 1: per-edge annotation + accurate closure counts	2026-05-26 01:18:03 +00:00