New Orleans Public Safety DashboardCity of New Orleans

About This Dashboard

Overview

The New Orleans Public Safety Dashboard provides daily tracking of public safety data across seven domains: crime incidents, police response times, calls for service, stop & search activity, use of force, 311 service requests, and traffic incidents. Built for the New Orleans City Council by AH Datalytics, the dashboard draws from the NOLA Open Data Portal and other official NOPD data sources to provide a comprehensive view of public safety in New Orleans.

Dashboard Pages

Crime

Tracks UCR-classified crime incidents based on Calls for Service with a Report to Follow (RTF) disposition. Includes year-to-date comparisons, rolling trends, and breakdowns by crime type, district, and neighborhood. Murder counts reflect victim totals (not incident counts) to account for multi-victim incidents.

Response Times

Analyzes NOPD call response times using dispatch and arrival timestamps. Filters to non-self-initiated calls with valid dispositions (NAT, RTF, UNF, GOA) and response times between 0 and 1,440 minutes. Shows median, average, and 90th percentile response times, percentage of calls exceeding 20-minute and 60-minute thresholds, and response time distribution histograms.

Calls for Service

Provides a complete view of all 911 calls received by NOPD, organized by a three-level hierarchy: Call Type (Medical, Service, Crime, etc.), CFS Type (Mental Patient, Disturbance, etc.), and Signal Code. Includes hour-of-day and day-of-week heatmaps, rolling trends, and an expandable breakdown table.

Stop & Search

Tracks NOPD field interviews and stops, including demographics (race, gender, age group), stop reasons, outcomes (arrests, citations, warnings), and district breakdowns.

Use of Force

Monitors use of force incidents reported by NOPD officers, including force type and level, officer and subject demographics, injury rates, and disposition outcomes.

311 Service Requests

Tracks non-emergency 311 service requests submitted by residents, broken down by request type, status, responsible agency, neighborhood, and council district.

Traffic

Monitors traffic-related calls for service, including accident types, dispositions, and geographic distribution across districts and neighborhoods.

Interactive Map

A neighborhood-level choropleth map showing crime density by area, with clickable neighborhoods that display detail panels with crime, 911, 311, and traffic counts. Incident dots are loaded from live NOPD data and can be filtered by crime type.

Data Sources

  • Calls for Service (SODA API) — Live feed from NOLA Open Data Portal for current and prior-year incidents
  • Historical CAD Records — Historical calls for service maintained by AH Datalytics
  • Electronic Police Reports (EPR) — Used to exclude unfounded incidents and reclassify certain assault types
  • Response Times (Parquet) — Call response time data with dispatch, arrival, and closure timestamps
  • Call for Service CSV — Complete CFS history including call type hierarchy and disposition data
  • Stop & Search (SODA API) — NOPD field interview / stop data (dataset kitu-f4uy)
  • Use of Force (SODA API) — NOPD use of force incident data (dataset 9mnw-mbde)
  • 311 Service Requests (SODA API) — Non-emergency service requests from the City of New Orleans
  • Traffic Incidents — Traffic-related calls for service from NOPD CAD data
  • CFS Lookup Table — Maps NOPD signal codes to UCR crime types and categories
  • Geocoded Addresses — Maps block addresses to neighborhoods and council districts

Methodology

Crime Incidents

Each crime incident represents a Call for Service with a Report to Follow (RTF) disposition matching a UCR crime category. Key processing steps:

  1. Historical and current CFS data are combined
  2. Manual type corrections and victim count overrides are applied
  3. CFS signal codes are mapped to UCR crime types
  4. Unfounded incidents (from EPR records) are excluded
  5. Geographic enrichment adds neighborhood and council district
  6. Misclassified murders are corrected
  7. Historical murders not in CFS are appended
  8. EPR signal exclusions remove certain reclassified incidents

Response Times

Response time is calculated as the difference between the arrival time (or dispatch time if no arrival) and the call creation time. Data is filtered to:

  • Non-self-initiated calls only (SelfInitiated = "N")
  • Valid dispositions: NAT, RTF, UNF, or GOA
  • Response time greater than 0 and less than 1,440 minutes (24 hours)

Response times are aggregated into histogram buckets (0-5, 5-10, 10-15, 15-20, 20-30, 30-60, 60+ minutes) for efficient percentile and threshold calculations.

Measures

  • Year-to-Date (YTD) — Count from January 1 to the most recent data date
  • YTD % Change — Comparison against same period in the prior year
  • Rolling N-Day — Trailing sum or average over N days from the as-of date
  • % Exceeding Threshold — Share of incidents exceeding 20-minute or 60-minute response time

Limitations

  • Crime counts are unofficial and based on CFS data, not final NOPD crime statistics
  • Data is refreshed daily at 4 AM CT via automated pipeline
  • Geographic assignment depends on block address geocoding accuracy
  • Some incidents may be reclassified or voided after initial report
  • Historical data quality varies by year and source system
  • Stop & Search and Traffic data may lag behind real-time by several months

Definitions

CFS (Calls for Service)
Records of calls received by NOPD dispatch, including the nature of the call, location, and disposition.
RTF (Report to Follow)
CFS disposition indicating a formal police report was filed, used as the primary filter for crime incidents.
UCR (Uniform Crime Report)
FBI classification system for crime types. Categorizes incidents into Part I (violent + property) and Part II offenses.
NAT (Necessary Action Taken)
Disposition indicating officers responded and took appropriate action but no formal report was required.
GOA/UNF (Gone on Arrival / Unfounded)
Dispositions where the subject was no longer present upon officer arrival or the incident was determined to be unfounded.
EPR (Electronic Police Report)
Detailed police report associated with a CFS. Used to identify unfounded incidents for exclusion.

Dashboard developed by AH Datalytics for the New Orleans City Council. For questions or feedback, contact info@ahdatalytics.com.