How Road Checks, Freshness & Comparisons Work
Inspect the source retrieval, record validation, freshness thresholds and honest comparison rules behind an AusRoadAlerts trip brief.
Scope first
A source profile provides an official destination and a workflow. An automatic adapter additionally retrieves named datasets. The current report panels include WA WebEOC incidents and roadworks, six NSW hazard categories, two Victorian disruption feeds and QLDTraffic events. Missing NSW/Victoria application keys prevent retrieval; QLD public-key access has a shared quota. ACT, SA, Tasmania and NT are not integrated live data. The site does not infer missing events for the other regions or combine partial sources into a nationwide count.
Retrieval and validation
WA adapters check the field schema and record IDs, then read bounded batches in WGS84. Regional connectors validate GeoJSON and namespaced identities; Victorian pages are read sequentially and unexpected pagination remains partial. Responses are size-limited and WA retrieval has a 12-second deadline and regional retrieval an 18-second deadline. A snapshot is marked partial when expected records are missing, duplicated, malformed or exceed the 6,000-record safety cap. A failed request returns an unavailable status and a null count, not zero.
Freshness is not road safety
Retrieval time and dataset edit time are displayed separately. “Available” requires a complete retrieval plus a source-edit time within 24 hours for incidents or 72 hours for roadworks. Regional feeds use a separate whole-document publication timestamp, with a 24-hour threshold. The newest individual event update is displayed separately and never certifies the whole feed. Provider quotas pause checks until the retry time; there is no automatic retry loop. These are our conservative product thresholds, not provider guarantees. A quiet but unchanged source can fail this freshness test; its snapshot is labelled “freshness unconfirmed” instead of being promoted as current traffic. Future or missing edit timestamps also fail the test.
Text and time matching
All entered search words must occur in a report’s road/location, description, type or restriction text. No route geometry or travel-time calculation is performed. Alternate names may not match. Explicit ISO timestamps with a timezone and numeric epoch timestamps are parsed automatically. Documented local Victorian planned timestamps are converted only when the local clock time has a unique interpretation; DST gaps and overlaps remain unknown. Ambiguous provider dates remain visible as source text and are not silently filtered out.
Comparisons and local snapshots
A comparison requires complete, freshness-confirmed snapshots of the same feed. Namespaced source IDs distinguish records. The labels are “newly listed” and “no longer listed”—never “new hazard” or “reopened road” without source evidence. Failed and partial new snapshots cannot clear prior events. Saved snapshots have a size cap, and capped snapshots are excluded from comparisons.
Human checks remain separate
Manual ticks are session-specific, made by the user and visibly timestamped. Opening a saved brief does not reinstate old ticks as current confirmations. A completed checklist is not a safety score. Source profiles were reviewed on 2026-10-10; this review date does not indicate live road status.