fix(traffic): stop a few matched roads reading as "no matches"

The live flow status derived its wording from the rounded coverage
percent, so 1 matched dot among 300 rounded to 0% and read
"SIMULATED ... (no matches)", and 1 simulated dot among 300 rounded to
100% and dropped "Unmatched: simulated". Coverage now stays within 1-99%
whenever both matched and simulated dots are shown.
This commit is contained in:
Aditya committed 2026-10-28 15:34:51 +05:30
1 parent a4d3701c3c
commit c6f437ed52
3 files changed
+38 -5

No files matched your search

+5 -3
View File
@@ -5810,9 +5810,11 @@ easier to meet (detection is now on more often), but does not create it.
OSM choice), so Hybrid fill is never replayed as OSM roads. Failed flow
refreshes clear old matches and report simulation. `flowCoveragePct` is the
percentage of shown dots on roads with flow, including all unmatched dots in
the denominator and excluding dots hidden by closures. The OSM keyed status
reads `LIVE · Roads: OpenStreetMap · Flow: TomTom · N% cov`. Road fetch
coverage follows a 5×5 ellipsoid sample of the central screen square.
the denominator and excluding dots hidden by closures. It reads 1–99 whenever
both matched and simulated dots are shown, so rounding never turns a few
matches into `(no matches)` or a few simulated dots into full coverage. The
OSM keyed status reads `LIVE · Roads: OpenStreetMap · Flow: TomTom · N% cov`.
Road fetch coverage follows a 5×5 ellipsoid sample of the central screen square.
Horizon rays are capped at 10 km from nadir (reduced if necessary to fit
16 z12 tiles); polygon-intersecting tiles load nearest first. Up to 16 z14
tiles provide near detail, with z12 roads beyond them. Cached tiles serve