Fit selected vehicles without zooming out across the entire planet
A synthetic depot near the date line has vans at longitudes 179.8 and -179.7. Fit selection zooms to the whole world because the bounding box takes the long route.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Geospatial reasoning · Boundary cases · Map UX
Estimated field mix
- Frontend100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
The fictional Cedar delivery depot dispatches vans through a browser map and accessible list. Synthetic telemetry arrives through a gateway with device sequence numbers. This is operational fleet software practice; no real driver tracking, employee scoring, or routing safety guarantee is part of the project.
Setup prerequisites
- Synthetic vehicle telemetry with device sessions and sequence numbers
- Dispatch assignment and authorized region API contracts
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Viewport fitting chooses the intended minimal longitude span for the selected valid points.
- One-point and empty selections use documented zoom/fallback behavior.
- Unknown-location vehicles remain listed but do not distort geographic bounds.
Implementation constraints
- Bound this task to viewport fitting; route calculation and global projection replacement are excluded.
Verification to include
- Fit points on both sides of the date line and verify a local view contains both.
- Fit an empty selection, one point, and a mix containing invalid fixes; no invalid bounds or extreme zoom occurs.
Deliverables
- Dateline-aware bounds helper and geographic edge-case fixtures
Rollout and recovery
Enable for selection fitting only; retain a manual reset-to-depot control if bounds calculation fails.
Value of the work
For the engineer: Practice geospatial boundaries, stream ordering, snapshot recovery, and concurrent operational commands.
For the team: Inspect whether a developer keeps dispatch decisions grounded in current authorized data and exposes uncertainty during outages.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.