CPD Contact Cards

Data Description: This dataset captures all Cincinnati Police Department Contact Carrds. This data includes time of incident, officer assignment, race/sex of stop subject, and outcome of the stop ("Action taken"). Individual contact cards may populate multiple data rows to account for multiple outcomes or multiple items of contraband: "interview number" is the unique identifier for every one (1) stop.

Data Creation: This data is created when CPD completes a pedestrian or traffic stop and logs the interview via Contact Cards. Contact Cards are a result of the Collaborative Agreement. Contact Cards are manually entered and may experience lags in data entry.

Data Created by: This data is created by the Cincinnati Police Department.

Refresh Frequency: This data is updated daily.

Data Dictionary: A data dictionary providing definitions of columns and attributes is available as an attachment to this dataset.

Processing: The City of Cincinnati is committed to providing the most granular and accurate data possible. In that pursuit the Office of Performance and Data Analytics facilitates standard processing to most raw data prior to publication. Processing includes but is not limited: address verification, geocoding, decoding attributes, and addition of administrative areas (i.e. Census, neighborhoods, police districts, etc.).

Data Usage: For directions on downloading and using open data please visit our How-to Guide: https://data.cincinnati-oh.gov/dataset/Open-Data-How-To-Guide/gdr9-g3ad

Disclaimer: In compliance with privacy laws, all Public Safety datasets are anonymized and appropriately redacted prior to publication on the City of Cincinnati’s Open Data Portal. This means that for all public safety datasets: (1) the last two digits of all addresses have been replaced with “XX,” and in cases where there is a single digit street address, the entire address number is replaced with "X"; and (2) Latitude and Longitude have been randomly skewed to represent values within the same block area (but not the exact location) of the incident.

Querying over HTTP

Splitgraph serves as an HTTP API that lets you run SQL queries directly on this data to power Web applications. For example:

curl https://data.splitgraph.com/sql/query/ddn \
    -H "Content-Type: application/json" \
    -d@-<<EOF
{"sql": "
    SELECT *
    FROM \"cincinnati-oh-gov/cpd-contact-cards-svan-pass\".\"cpd_contact_cards\"
    LIMIT 100 
"}
EOF

See the Splitgraph documentation for more information.