Data changelog

What changed, and when

This log records material public-product, methodology, and source-presentation changes. Routine source-record revisions remain possible between entries.

See the latest records ↗

Last updated November 5, 2026

November 5, 2026

  • Added labeled street maps to the homepage’s local crash examples so readers can locate the study areas.
  • Expanded mobile navigation, source guidance and research links across public pages.
  • Reduced unnecessary map downloads and map-layer updates; retained text evidence and clear loading states.

September 1, 2026

  • Renamed the public project from The Crash Data Project to Evidence for Zero.
  • Adopted the position “Zero is the goal. Evidence is how we get there.”
  • Published a data-quality position describing vehicle-label fragmentation and a partnership proposal for better field collection and validation.

June 30, 2026

  • Published launch findings for ZIP 90504, Anaheim and Santa Ana, and San Diego with maps, data downloads, methodology, limitations, and citations.
  • Added restricted, read-only map embeds with source, methodology, reporting-window, and coverage context.
  • Added direct “Embed this view” handoff from the public map.
  • Changed public map positioning from acquisition language to neutral research language.
  • Added institutional standards, corrections, newsroom, and reuse documentation.

June 29, 2026

  • Added responsible applications page describing field-tested aggregate-data workflows and ethical boundaries.
  • Expanded static metadata, canonical URLs, structured data, and sitemap coverage for public routes.

Ongoing source revisions

California Crash Reporting System records may be created, amended, or completed after an incident. Counts for a historical window can therefore change after publication. Public pages should be treated as versioned analytical views, not immutable official totals.