24-hour search clock
Observed search frequency by hour of day.
Longer spokes mean a larger share of searches in the currently filtered audit records.
Explore when searches happened, who the audit log identifies as the suspect, what plates were queried, why searches were run, and how widely they reached.
Checking public data API…
Every visualization below responds to these filters.
Observed search frequency by hour of day.
Longer spokes mean a larger share of searches in the currently filtered audit records.
Busiest 15-minute windows.
See when searches cluster across the week.
Map repeated relationships among suspects, plates, stated reasons, and search types. Click any node to inspect its strongest links.
Top suspects crossed with their most common stated reason categories.
The strongest exact Suspect → Plate → Reason paths in the filtered records.
Daily search volume across the selected period.
Most frequently appearing Name values.
Stated reasons grouped by leading category.
Lookup, search, mobile, and other modes.
How broadly each query searched connected networks.
Repeat patterns grouped by queried license plate.
Loading records…
| Search time | Suspect | Plate | Reason | Type | Networks | Filters |
|---|---|---|---|---|---|---|
| Loading… | ||||||
The source CSV field named Name is displayed here as Suspect according to the archive interpretation used for this project. That label describes the imported record field; it is not a finding of guilt or a statement that a person was charged or convicted.
The clock and heatmap describe the frequency of searches inside the selected audit records. They are useful for seeing historical patterns, but they do not predict that any particular person or vehicle will be searched at a future time.