Total laneStats docs
-
-
Historical Times
Internal review surface for laneStats and segmentStats.
Use it to validate “Tiempos típicos” coverage, spot stale legacy lanes, inspect day/hour buckets,
and compare snapshots over time before anything ships to mobile.
Admin Access
Total segmentStats docs
-
-
Last updated
-
-
Data source
-
-
Filters
Pick a crossing and lane, then drill into day-level and bucket-level coverage.
Snapshots & Comparison
Save the current historical stats locally, compare against a saved snapshot, or import previous JSON.
New Data Breakdown
Compare current historical stats against the selected saved snapshot to see where new data landed.
Why one segment only moved a little:
New reports are spread across many lanes, reference points, and time buckets. A single segment only increases when a valid report matches that exact lane + reference point + bucket.
Excluded Reports
Aggregate-only counts by exclusion reason. No raw report rows or user identifiers are exposed here.
Comparison Snapshot
Load a saved snapshot to rank the biggest lane and segment sampleCount changes.
Top Changed laneStats Docs
Compared by laneStats document ID.
| Lane | Current | Previous | Change |
|---|
Top Changed segmentStats Docs
Grouped by aggregateLaneKey + startZoneId + timeBucket.
| Segment | Current | Previous | Change |
|---|
Lane Detail
Select a lane to inspect overall stats and freshness.
Comparison
Saved snapshots and imported JSON compare against the currently selected lane.
Hourly Readiness
Checks whether each lane has enough clean reports to support true hourly estimates by day.
This is internal QA only.
Mobile apps should continue using 3-hour buckets unless a lane is marked Ready.
Lane Readiness
Coverage is grouped by day of week and hour of day using clean reports only.
| Lane | Eligible reports | Ready days | Usable hourly slots | Strong hourly slots | Status |
|---|
Lane hourly detail
Select a lane to inspect day-by-hour coverage.
Strong (15+)
Usable (10-14)
Thin (1-9)
Empty (0)
Day Summary
Each day needs at least 18 of 24 usable hourly slots to be considered hourly-ready.
| Day | Total reports | Ready slots 10+ | Strong slots 15+ | Hourly ready |
|---|
2-Hour Readiness
Checks whether each lane has enough clean reports to support 2-hour buckets instead of 3-hour buckets.
This is internal QA only.
Mobile apps should continue using 3-hour buckets unless a lane is marked Ready for 2-hour or hourly.
Lane Readiness
Coverage is grouped by day of week and 2-hour bucket using clean reports only.
| Lane | Eligible reports | Ready days | Usable 2-hour buckets | Strong 2-hour buckets | Status |
|---|
Lane 2-hour detail
Select a lane to inspect day-by-2-hour coverage.
Strong (15+)
Usable (10-14)
Thin (1-9)
Empty (0)
Day Summary
Each day needs at least 9 of 12 usable 2-hour buckets to be considered 2-hour-ready.
| Day | Total reports | Ready buckets 10+ | Strong buckets 15+ | 2-hour ready |
|---|
Day / Time Explorer
Use the chips for day-level coverage, then inspect each time bucket for median and sample count.
Zone Table
Farthest from the booth first. Lane-level zones are shown first and backfilled from segmentStats when needed.
| Zone name | Zone ID | Median minutes | Sample count | Confidence | Order | Route |
|---|