Skip to content

routing: unify snapping/routing semantics across single-route and batch APIs#14

Merged
blackopsrepl merged 1 commit into
mainfrom
issue/2-unify-snapping-routing-semantics
Mar 21, 2026
Merged

routing: unify snapping/routing semantics across single-route and batch APIs#14
blackopsrepl merged 1 commit into
mainfrom
issue/2-unify-snapping-routing-semantics

Conversation

@blackopsrepl
Copy link
Copy Markdown
Contributor

Summary

  • make compute_matrix use the same node-snapped routing model as the existing public single-route APIs
  • keep the explicit edge-snapped path APIs available separately instead of mixing semantics implicitly
  • add a deterministic regression test proving matrix times match route(...) on the same input pair

Validation

  • cargo fmt --all -- --check
  • cargo clippy --workspace --all-targets -- -D warnings
  • cargo test matrix::matrix_matches_single_route_node_snapping --test integration
  • cargo test (blocked by a pre-existing routing::osrm_comparison::duration_matches_osrm failure also present on main)

Fixes #2

@blackopsrepl blackopsrepl force-pushed the issue/2-unify-snapping-routing-semantics branch from 7eeafe3 to 3cf782c Compare March 21, 2026 13:15
@blackopsrepl blackopsrepl marked this pull request as ready for review March 21, 2026 13:15
@blackopsrepl blackopsrepl merged commit 2d09dea into main Mar 21, 2026
3 checks passed
@blackopsrepl blackopsrepl deleted the issue/2-unify-snapping-routing-semantics branch April 3, 2026 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

routing: unify snapping/routing semantics across single-route and batch APIs

1 participant