Public safety analytics demo: Olathe, Kansas
A working example of the reporting Blue Peak builds for police departments, on real records the Olathe Police Department publishes for the public. Nothing on this page is modelled or simulated, and every number can be checked against the source.
Data window: crimes and traffic accidents ; calls for service .
Monthly crimes by class
Class is the department's own NIBRS grouping. Unclassified records are real reports that carry no NIBRS code, mostly city ordinance violations. They are counted, never hidden.
When it happens: day of week by hour
Hour is the reported time on the record, which is not always the time the event happened. Whole window for the feed shown.
Top 10 NIBRS offenses
Records without a NIBRS code (the Unclassified class) are not ranked here.
Traffic accidents by month and severity
Severity is read from the incident description on each record, because the source's class field files fatal collisions under "non-injury". Hit and run counts are in the tooltip and the table.
Calls for service: top 20 call types
Calls for service by month
Where it happens: by City Council ward (derived)
"Outside city wards" records geocode beyond the ward boundaries. Most are "All Other Offenses" at locations consistent with warrant service and prisoner handling outside city limits. They are kept, not dropped.
Where it happens on the map
What this would look like on your data
Start from the export your RMS or CAD already produces, on a schedule, with no direct access to the records system required. Your categories, your beats and your counting rules replace the derived ones used here, so the dashboard number and the number you submit come from one definition. It runs inside your own Microsoft tenant with row level security, so command staff see everything, a supervisor sees their squad, and a public view carries no case detail.
What it covers and how it is priced: crime statistics dashboards in Power BI.
Send us the report you hate producing