2020 4th Quarter - 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).
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 (38)
This document serves as a guide to the stop and search data.
583 KBUpdated Apr 14, 2021
191 KBUpdated Apr 14, 2021
179 KBUpdated Apr 14, 2021
174 KBUpdated Apr 14, 2021
This data set represents the use of force incidents for both field interviews and traffic stops.
16 KBUpdated Apr 14, 2021Table and Data API available
This data set contains the entry segment narratives for each of the regular traffic stops. This is defined as all calls with CALLTYPEORIG of traffic stop, as long as the call does not have the value ‘SUB’ (Subject Stop) as CALLTYPEFINAL. For the majority of…
24 KBUpdated Apr 14, 2021Table and Data API available
This data set contains the dispositions for each CAD call associated with each no-action encounter.
1.5 KBUpdated Apr 14, 2021Table and Data API available
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…
965 KBUpdated Apr 14, 2021Table 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 CADPCARSCALLJOINED
843 KBUpdated Apr 14, 2021Table 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. Some stops may not include a row in this data set (e.g. may not contain a PERSID/Peoplesoft ID…
782 KBUpdated Apr 14, 2021Table and Data API available
This data set contains the entry segment narratives for each of the regular traffic stops. This is defined as all calls with CALLTYPEORIG of traffic stop, as long as the call does not have the value ‘SUB’ (Subject Stop) as CALLTYPEFINAL. For the majority of…
1.4 MBUpdated Apr 14, 2021Table and Data API available
This data set contains imported citations that were matched to an MNI number in TraCS. Note: an individual that has two MNIs with the same ethnicity, race, age, and date of birth may not reflect the same person.
1.3 MBUpdated Apr 14, 2021Table 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.
55 KBUpdated Apr 14, 2021Table and Data API available
This data set contains the involved officer(s) for each field interview. Data set has a many:1 relationship with InformFieldInterviewJoined.
214 KBUpdated Apr 14, 2021Table 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…
732 KBUpdated Apr 14, 2021Table 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.
4.4 KBUpdated Apr 14, 2021Table and Data API available
This data set contains the involved officer(s) for each no action encounter.
8.5 KBUpdated Apr 14, 2021Table 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 No Action Encounter persons. If the same person is involved in two separate no action encounters, they will be…
28 KBUpdated Apr 14, 2021Table and Data API available
This data set has been included facilitate linking a Peoplesoft number from a given contact summary or field interview to an officer.
64 KBUpdated Apr 14, 2021Table 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
1.7 MBUpdated Apr 14, 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.
2.8 MBUpdated Apr 14, 2021Table and Data API available
This data set represents information related to any vehicle search in regards to a given stop. Has a many:1 relationship with TracsPrdHeader and TracsContactSummaryJoined.
1.6 MBUpdated Apr 14, 2021Table and Data API available
This data set includes the text-based narratives for electronic citations. It has a 1:1 relationship with the TracsPrdHeader table and includes information about the stop.
2.5 MBUpdated Apr 14, 2021Table and Data API available
This data set links to each involved individual indicated in the data sets for each of the four form types (Contact Summary, ELCI, NTC and Warning). Each form entry will usually have one entry in this table. However, one exception to this is when a Contact…
2.0 MBUpdated Apr 14, 2021Table and Data API available
This data set contains the latitude and longitude of each stop. Each stop in TraCS should have a single location.
2.5 MBUpdated Apr 14, 2021Table and Data API available
This data set includes the text-based narratives for non-traffic citations that occurred as a part of a traffic, targeted traffic or subject stop. It has a 1:1 relationship with the TracsPrdHeader table and includes information about the stop
55 KBUpdated Apr 14, 2021Table and Data API available
This data set represents the primary table in Tracs. Each contact summary, electronic citation (ELCI), non-traffic citation (NTC), or warning will contain a row in this data sets.
4.1 MBUpdated Apr 14, 2021Table and Data API available
This data set represents the lookup table for contraband in TraCS
205 BUpdated Apr 14, 2021
This data set represents the lookup table for individual entity type in TraCS.
100 BUpdated Apr 14, 2021Table and Data API available
This data set represents the lookup table for summary outcomes in TraCS
149 BUpdated Apr 14, 2021Table and Data API available
This data set represents the lookup table for race in TraCS
152 BUpdated Apr 14, 2021Table and Data API available
This data set represents the lookup table for reason for a stop in TraCS.
428 BUpdated Apr 14, 2021Table and Data API available
This data set represents the lookup table for reasons in the contact summary form.
427 BUpdated Apr 14, 2021Table and Data API available
This data set represents the lookup table for search basis in TraCS
199 BUpdated Apr 14, 2021Table and Data API available
This data set represents the lookup table for the status of all forms in TraCS.
375 BUpdated Apr 14, 2021Table and Data API available
This data set includes the text-based narratives for warnings. It has a 1:1 relationship with the TracsPrdHeader table and includes information about the stop.
1.2 MBUpdated Apr 14, 2021Table and Data API available
The data set is included to primarily indicate the outcome of the stop. Note: This table was not joinable, as it involves a 1:many relationship with each Tracs warning.
430 KBUpdated Apr 14, 2021Table and Data API available
Provides information to assist in the linking of Police Document Number (CAD) with Person ID numbers,
700 KBUpdated May 11, 2021Table and Data API available