THE REPORT, IN PLAIN LANGUAGE
Know what the label means.
Sixteen useful definitions explain what the route report measures, what it estimates and what still needs an official check.
No terms match. Clear the search to see every definition.
- Arrival-time forecast
The forecast period matched to the estimated time you reach one selected checkpoint. It is not the forecast for every point on the road and it is not a live traffic arrival estimate.
See it in context- Checkpoint
A deliberately selected location in a curated corridor. Six returned checkpoint forecasts do not imply continuous coverage between them; a local problem can occur in an unsampled stretch.
See it in context- Planning baseline
A rounded distance or driving duration stored in the corridor catalogue. It is useful for consistent calculations, but does not include measured congestion, a current closure delay or an address-to-address route.
See it in context- Stop allowance
The total extra time you add for stops. The weather checker spreads it across checkpoints; the private break planner also shows individual time blocks. Neither verifies an actual stopping location.
See it in context- Departure sample
Your selected departure and the +3, +6 and +9 hour departures, calculated with the same corridor settings. The gaps between samples are not a minute-by-minute forecast or an optimized departure schedule.
See it in context- Weather-concern category
A product heuristic based on the report’s stated weather inputs. It is not an official NWS warning category, a probability of an accident, or a safe-to-drive verdict. Read the reason and missing-data labels together.
See it in context- Incomplete data
One or more required forecast inputs or alert responses are unavailable for the comparison. An incomplete sample cannot win because a potentially important checkpoint is missing.
See it in context- Not integrated
The site has no active adapter for that data layer on that corridor. An official link is still useful, but it must not be counted as imported live closure, pavement or traffic-speed data.
See it in context- No matching records
A successfully read feed contains no record matching the selected geographic and highway filter. It is not proof of no restrictions, an open road or a complete statewide search.
See it in context- Retrieval time
When the data was obtained by the application. This is different from when a provider issued a forecast or when a road report’s status last changed. A new retrieval can contain an older observation.
See it in context- Source timestamp
A time supplied by the provider, whose meaning depends on the particular feed. A camera metadata timestamp does not necessarily identify the capture time of the displayed image.
See it in context- Local arrival clock
The clock at the checkpoint’s own time zone. A time-zone change affects the wall clock, not the elapsed amount of driving. Check the route-local departure alongside your device-local input.
See it in context- High-profile vehicle setting
A more sensitive wind indicator for an RV or similar vehicle. It does not establish a vehicle-specific operating limit, legal exemption, certified crosswind tolerance or permission under current restrictions.
See it in context- Saved report
A snapshot explicitly stored in this browser. Reopening it is not a new source check. The application withholds current departure advice from a saved report and provides a way to check again.
See it in context- Route preset
A saved public corridor, direction, vehicle profile and stop allowance. Presets do not save a departure time or forecast and use storage separate from the private trip plan and saved weather report.
See it in context- Private trip workspace
The local budget, break allowances and checklist you build from explicit assumptions. It does not fetch current energy prices, find chargers or certify driver readiness. Saving and deletion are deliberate actions.
See it in context
Need the exact method?
See the inputs, thresholds and missing-data rules behind the weather comparison.