Start a reporting workflow
- Build a city, ZIP, date-window, or severity view in the public map.
- Use “Embed this view” to create a responsive, read-only map.
- Download the accompanying record summary or use the text alternative.
- State the reporting window and coordinate coverage in the article.
- Link editorially to the relevant source page when it helps readers inspect the underlying data.
What we can help explain
- Why mapped and total record counts differ.
- How city labels, ZIP areas, roads, vehicles, severity, and hit-run fields are represented.
- Which location values come from source coordinates and which may be derived.
- Why raw crash counts do not establish danger, risk, fault, or causation.
Before publishing
Review the methodology and editorial standards. Confirm that the selected window is complete enough for the intended claim. For consequential or surprising findings, request a methodology check through the project contact channel.
Launch findings
Statewide · Data qualityWhy California’s public crash records still arrive fragmentedSouth Bay · ZIP 90504Where Crenshaw Boulevard and I-405 concentrated in one year of ZIP recordsOrange County · City comparisonSimilar totals, different recorded patterns in Anaheim and Santa AnaSan Diego · Vision Zero contextTwice the statewide vulnerable-road-user or motorcycle context