2019 1st & 2nd Quarters - MPD Stop and Search Data
Fire and Police CommissionAbout this dataset
Per the requirements in the settlement to Federal Case 17-CV-234-JPS the Milwaukee Fire and Police Commission (FPC) is required to publish particular stop and search encounter data in compliance with Sec. IV(A)(10-13).
Additional data sets will be added as they become available.
MPD stands for Milwaukee Police Department
To download XML and JSON files, click the CSV option below and click the down arrow next to the Download button in the upper right on its page.
Data and resources (36)
This document serves as a guide to the stop and search data.
1.0 MBUpdated Feb 19, 2020
The primary data set containing CAD call segments. Each CAD call can have many of these segments. The key that joins these segments is CADCALLKEY. Also it is important to note that some original call types that may start off as a stop, end up as something…
2.3 MBUpdated Feb 19, 2020Table and Data API available
This data set contains additional call segment information and has a 1:1 relationship with CADPCARSCALL1
1.6 MBUpdated Feb 19, 2020Table and Data API available
This data set contains the each squad (car) unit that responded to a given call. This table has a many:1 relationship with CADPCARSCALL1 and CADCARSCALL3.
2.4 MBUpdated Feb 19, 2020Table and Data API available
This data set contains each officer that responded to a given call and includes the unit key to link to. This table has a many:1 relationship with CADPCARSCALLUNIT.
2.6 MBUpdated Feb 19, 2020Table and Data API available
This is the primary data set where field interview data is stored. Each field interview will have one record in this data set. Important note: Any given field interview may have multiple persons involved in it.
107 KBUpdated Feb 19, 2020Table and Data API available
This data set contains additional field interview event data. This table was a 1:1 relationship with the InformFieldInterview table.
244 KBUpdated Feb 19, 2020Table and Data API available
This data set contains the each narrative that may have been entered for a given field interview.
126 KBUpdated Feb 19, 2020Table and Data API available
This data set contains the involved officer(s) for each field interview.
329 KBUpdated Feb 19, 2020Table and Data API available
This data set contains the person information for each individual involved in a field interview. For each field interview, there can be many FieldInterview persons. If the same person is involved in two separate field interviews, they will be entered into…
440 KBUpdated Feb 19, 2020Table and Data API available
This is the primary data set where no action encounter data is stored. Each no action encounter will have one record in this data set. Note: Similar to how the field interviews work, any given no action encounter can have multiple persons involved.
6.1 KBUpdated Feb 19, 2020Table and Data API available
This data set contains additional no action encounter event data. This table has a 1:1 relationship with the InformNoActionEncounter data set.
14 KBUpdated Feb 19, 2020Table and Data API available
This data set contains the each narrative that may have been entered for a given field interview.
1.5 MBUpdated Feb 19, 2020Table and Data API available
This data set contains the involved officer(s) for each no action encounter.
16 KBUpdated Feb 19, 2020Table and Data API available
This data set contains the person information for each individual involved in a no action encounter. For each no action encounter, there can be many NoActionEncounter persons. If the same person is involved in two separate no action encounters, they will be…
15 KBUpdated Feb 19, 2020Table and Data API available
- CSV
Inform ELCI
This data set contains imported citations that were matched to an MNI number in TraCS.
2.5 MBUpdated Feb 19, 2020Table and Data API available
This data set represents the primary table in Tracs. Each contact summary will contain a row in this data set.
4.6 MBUpdated Feb 23, 2021Table and Data API available
This data set represents additional header information for a given contact summary. It has a 1:1 relationship with the TracsPrdHeader table and includes information about the stop.
3.3 MBUpdated Feb 19, 2020Table and Data API available
This data set is needed to provide the agency space field, which is used to record the text-based justification for a stop. Has a 1:1 relationship with TracsPrdHeader.
1.6 MBUpdated Feb 19, 2020Table and Data API available
This data set is required to provide the CAD number for a given contact summary. Has a 1:1 relationship with TracsPrdHeader.
1.9 MBUpdated Feb 19, 2020Table and Data API available
This data set links each individual involved in a contact summary to the actual contact summary. It also contains a few additional fields as shown below. Has a many:1 relationship with TracsPrdHeader
3.4 MBUpdated Feb 19, 2020Table and Data API available
This data set links a given contact summary with a location. Has a 1:1 relationship with TracsPrdHeader.
3.6 MBUpdated Feb 19, 2020Table and Data API available
This data set contains the latitude and longitude of each stop. Each stop in TraC should have a single location.
5.0 MBUpdated Feb 19, 2020Table and Data API available
This data set links to each involved individual indicated in the TracsContactSummaryIndividual data set. It has a 1:1 relationship with it.
4.5 MBUpdated Feb 19, 2020Table and Data API available
This data set includes the text-based narratives for electronic citations.
1.2 MBUpdated Feb 19, 2020Table and Data API available
The data set is included to primarily indicate the outcome of the stop.
2.8 MBUpdated Feb 19, 2020Table and Data API available
This data set links electronic citations to locations.
2.8 MBUpdated Feb 19, 2020Table and Data API available
This data set links the defendant involved in the electronic citation to the individual record via the Defenant ColKey
2.8 MBUpdated Feb 19, 2020Table and Data API available
This data set is required to provide the CAD number for a given electronic citation. Has a 1:1 relationship with TracsPrdHeader.
1.5 MBUpdated Feb 19, 2020Table and Data API available
This data set has been included facilitate linking a badge number from a given contact summary or field interview to an officer.
64 KBUpdated Feb 19, 2020Table and Data API available
This data set represents the lookup table for contraband in TraCS
212 BUpdated Feb 19, 2020Table and Data API available
- CSV
TRACS V2RACE
This data set represents the lookup table for race in TraCS
152 BUpdated Feb 19, 2020Table and Data API available
This data set represents the lookup table for reasons in the contact summary form.
434 BUpdated Feb 19, 2020Table and Data API available
This data set represents the lookup table for the status of all forms in TraCS.
361 BUpdated Feb 19, 2020Table and Data API available
This data set represents the lookup table for summary outcomes in TraCS
154 BUpdated Feb 19, 2020Table and Data API available
This data set represents the lookup table for search basis in TraCS
206 BUpdated Feb 19, 2020Table and Data API available