Data Exports

Daily exports of records providing a view into the Boston Police Department (BPD)

These CSV files are produced daily from data in the Woke Windows database, all of which was originally sourced from public records provided by the City of Boston, the Commonwealth of Massachusetts, and other entities. These files are ready to be imported into Microsoft Excel or your preferred tool for data analysis.

You can also download an entire backup of our PostgreSQL database. See our GitHub project page for more information.

Have you done something interesting with this data and want to share? Do you need help or have questions? Reach out to us at or on Twitter. We would love to hear from you!

File Last Modified Size
citations.csv UTC 8.38 MB Docs
complaints_officers.csv UTC 3.56 MB Docs
contributions.csv UTC 1.58 MB Docs
details.csv UTC 37.3 MB Docs
field_contacts.csv UTC 31.3 MB Docs
field_contact_names.csv UTC 58.3 MB Docs
officers.csv UTC 914 KB Docs
overtimes.csv UTC 67 MB Docs

Citations

File citations.csv
Last Modified UTC
Size 8.38 MB

Export of the citations table. This file lists every traffic citation issued by Boston Police officers in 2019. See Traffic Citations for more information.

Each citation appears multiple times in this file, once for each offense recorded on the ticket.

These records have been joined with records from Officers, which reflect our latest information about the officer.

Column Description
ticket_number unique identifier for the citation; the same number will appear multiple times in the spreadsheet if the ticket is for multiple offenses
issuing_agency
officer_number the six-digit City of Boston employee id of the officer
ticket_type one of CIVIL, CRIM, or ARREST
source one of POLICE, COURT, ECITATION, or VIOLATOR
violator_type one of OPERATOR, OWN, PASS, or BIKE
cdl https://en.wikipedia.org/wiki/Commercial_driver's_license boolean
license_class e.g. "D" for Class D license
event_date
location_id
location_name city of Boston neighborhood
posted_speed
violation_speed
posted boolean
radar boolean
clocked boolean
race
sex
vehicle_color
make
model_year
sixteen_pass 16+ passenger vehicle
haz_mat
amount
paid
hearing_requested boolean
court_code see Trial Court codes for mapping
age
searched boolean
offense code for an offense; seems to correspond to a section in the Massachusetts General Laws e.g. "90160" is MGL c.90 §16
description description of the offense
assessment for the offense
expected_assessment for the offense
display_assessment for the offense
disposition of the offense e.g. NPC
disposition_description of the offense e.g. "No Probable Cause Found"
major_incident for the offense; boolean
surchargeable for the offense; boolean
sdip_points for the offense; see Safe Driver Insurance Plan (SDIP)
officer_ See Officers for all fields prefixed with officer_. If these fields are blank, that means we weren't able to unambiguously match the officer name to one in our database.

Complaints - Officers

File complaints_officers.csv
Last Modified UTC
Size 3.56 MB

Export of the complaint_officers table. This file lists every Internal Affairs (IA) allegation against a Boston Police Department officer or employee. See Complaints (Internal Affairs) for further information including the data sources used to compile these data.

These records have been joined with records from Officers, which reflect our latest information about the officer.

Column Description
ia_number identifier for the case; a given ia_number will appear multiple times in the file, once for each allegation against an officer. A case may include multiple officers.
case_number only appears in the 2001 to 2011 IA data file; may be a legacy identifier
incident_type one of Inquiry, Internal investigation, Citizen complaint, Preliminary Investigation, or General Inquiry
received_date
occurred_date only appears in 2014 Officer IA Log
summary only appears in 2014 Officer IA Log
name name of the officer as it appears in the allegation
title title of the officer as it appears in the allegation
badge badge number of the officer as it appears in the allegation; note that badge numbers change over time and may be reassigned
allegation e.g. "Neg.Duty/Unreasonable Judge"
finding current status of the allegation; sometimes old allegations are in non-final states e.g. "Pending" or "Filed"; this most likely means it only appeared in an older data source, and we haven't received an updated status
finding_date
officer_ See Officers for all fields prefixed with officer_. If these fields are blank, that means we weren't able to unambiguously match the officer name to one in our database.

Contributions

File contributions.csv
Last Modified UTC
Size 1.58 MB

Export of the contributions table. This file lists contributions to political candidates by Boston Police officers. See Contributions.

These records have been joined with records from Officers, which reflect our latest information about the officer.

Column Description
date contribution_receipt_date in the FEC data; date in the OCPF data
contributor the name of the contributor
zip the zip code the contributor provided as where they reside
employer the contributor's stated employer
occupation the contributor's stated occupation
amount the amount donated
committee_name the committee to which the contributor donated
cpf_id the ID used by OCPF to identify the committee
candidate_full_name name of the candidate as provided by OCPF
office_type office the candidate is seeking per OCPF
district district in which the candidate is running for office per OCPF
party_affiliation party affiliation of the committee; provided by OCPF for state data; for FEC data, determined manually by Woke Windows
committee_id the ID used by the FEC to identify the committee
memo_text from the FEC data
receipt_type_full from the FEC data
officer_ See Officers for all fields prefixed with officer_. If these fields are blank, that means we weren't able to unambiguously match the officer name to one in our database.

Details

File details.csv
Last Modified UTC
Size 37.3 MB

Export of the details table. This file lists paid details worked by BPD officers. See Paid Details for more documentation.

These records have been joined with records from Officers, which reflect our latest information about the officer.

Column Description
tracking_no unique id for each record from the Detail Records 2019 Spreadsheet
employee_number the six-digit City of Boston employee id of the officer
employee_name the name of the officer
employee_rank a number indicating the officer's rank
customer_number
customer_name
street_no
street
xstreet
start_date_time
end_date_time
minutes_worked
detail_type C or S which I believe stand for Construction and Security respectively
pay_hours the number of hours for which the officer was paid after taking into account rules that "round up"
pay_amount
pay_rate hourly rate; I believe this is based on the employee's rank
latitude latitude geocoded by Woke Windows based on the street_no, street, and/or xstreet fields
longitude also geocoded
officer_ See Officers for all fields prefixed with officer_. If these fields are blank, that means we weren't able to unambiguously match the officer name to one in our database.

Field Contacts

File field_contacts.csv
Last Modified UTC
Size 31.3 MB

Export of the field_contacts table. This file contains Field Interrogation and Observation (FIO) reports filed by Boston Police officers from mid-2015 through 2019. See Field Contacts (FIO) for more information.

These records have been joined with records from Officers, which reflect our latest information about the officer.

Column Description
fc_num unique identifier for this FIO
contact_date date and time of the FIO
contact_officer_employee_id six-digit City of Boston employee id of the officer who filed the report
contact_officer_name name of the officer
supervisor_employee_id six-digit City of Boston employee id of the supervising officer
supervisor_name
street street name; sometimes this is an intersection or even an address
city this is usually "boston" but sometimes this is a neighborhood
state almost always MA
zip zip code
frisked_searched true if any person was frisked/searched during this contact
circumstance one of: stopped, encountered, observed
basis one of: probably_cause, reasonable_suspicion, encounter, intel
vehicle_year
vehicle_state
vehicle_make e.g. "honda"
vehicle_model e.g. "civic"
vehicle_color
vehicle_style e.g. "hatchback, 4 door"
vehicle_type e.g. "station wagon"
key_situations this is a comma separated list of values
narrative prose description of the stop
weather e.g. "sunny"
field_contact_names_count the number of persons who were FIO'd as part of this encounter
stop_duration e.g. "ten_to_fifteen_minutes"
search_vehicle boolean indicating whether the vehicle was searched
summons_issued boolean
officer_ Additional information about the contact_officer. See Officers for all fields prefixed with officer_. If these fields are blank, that means we weren't able to match the officer name to one in our database.

Field Contact Names

File field_contact_names.csv
Last Modified UTC
Size 58.3 MB

Export of the field_contact_names table. This file contains one row for each individual who was FIO'd by Boston Police officers from mid-2015 through 2019. See Field Contacts (FIO) for more information.

These records have been joined with records from Field Contacts, and with records from Officers.

Column Description
fc_num the unique identifier of the associated field_contact
race race of the individual
age
build e.g. "muscular"
hair_style e.g. "braided"
skin_tone e.g. "brown"
ethnicity either "hispanic origin" or "not of hispanic origin"
other_clothing
license_state
license_type e.g. "class d"
frisked_searched whether the individual was frisked/searched; only appears in data starting Sep 29, 2019
gender
field_contact_ See Field Contacts for all fields prefixed with field_contact_

Officers

File officers.csv
Last Modified UTC
Size 914 KB

Export of the officers table. This file lists every officer and civilian employee of the Boston Police Department along with fields collected from multiple sources. See Officers & Employees.

Column Description
active whether the employee is currently employed at BPD; if the employee appears in 2020 Alpha Listing or in a later public journal, they are considered active
employee_id City of Boston employee id; useful for joining to other datasets
name Officer's name taken from earnings reports or alpha listing
organization The organization for which the officer works within the department
title Officer's title, taken from earnings reports or alpha listing
doa Date of Appointment. Officer's start date
badge badge number from most recent alpha listing where officer appears. This is not a unique identifier; the numbers may be re-used overtime.
zip_code five-digit zip code where officer resides
city city where officer resides (derived from zip code)
state two-letter abbreviation for state where officer resides (derived from zip code)
neighborhood neighborhood where officer resides or blank if officer does not reside in Boston (derived from zip code); see Zip Code and Neighborhood
regular 2019 regular earnings; this and other earnings columns are sourced from Employee Earnings Reports
retro 2019 retroactive earnings
other 2019 other earnings
overtime 2019 overtime earnings
injured 2019 injured pay earnings
detail 2019 earnings from working paid details
quinn 2019 earnings from education incentive
total 2019 total earnings
rank officer rank e.g. sergt for Sergeant; the title column also often has this information
ia_score metric calculated by Woke Windows based on the officer's Internal Affairs (IA) record; a number from 0 (least concerning) to 5 (very concerning); see IA Score
ia_sustained_conduct_unbecoming number of cases with the sustained allegation "Conduct Unbecoming"
ia_sustained_neg_duty number of cases with the sustained allegation "Neg.Duty/Unreasonable Judge"
ia_sustained_respectful_treatment number of cases with the sustained allegation "Respectful Treatment"
ia_sustained_self_identification number of cases with the sustained allegation "Self Identification"
ia_sustained_use_of_force number of cases with the sustained allegation "Use of Force"
ia_sustained_details number of cases with sustained allegations related to paid details. This allegation only appears in the 2001 to 2011 IA Data; it's unclear how this type of allegation is coded after 2011.
ia_sustained_cases number of cases with at least one sustained allegation
ia_sustained_allegations total number of sustained allegations
ia_cases total number of "Internal Investigation" and "Citizen Complaint" cases
ia_allegations total number of allegations in "Internal Investigation" and "Citizen Complaint" cases
field_contacts_count total number of FIO records where this officer is the contact officer; see Field Contacts (FIO)
incidents_count total number of incidents filed by this officer (note: this is most likely an undercount because we don't know the filing officer for many incidents)
complaints_count total number of Internal Affairs complaints
swats_count total number of SWAT reports
details_count total number of paid details
citations_count total number of traffic citations
articles_officers_count total number of articles where this officer is mentioned
retirement_date when the employee retired per data from the Boston Retirement System
retirement_amount gross monthly amount the employee is being paid in retirement
lead_added the date the officer was added to Law Enforcement Automatic Discovery (LEAD)
lead_entry information on why the officer was added to LEAD
url link to the page for the officer on Woke Windows

Court Overtime Shifts

File overtimes.csv
Last Modified UTC
Size 67 MB

Export of the overtimes table. This file lists court-related overtime worked by police officers and detectives. See Court Overtime 2014 to 2019 for more information regarding these records and their origin.

These records have been joined with records from Officers, which reflect our latest information about the officer.

Column Description
employee_id six-digit City of Boston employee id of the officer who filed the report
name name of the officer
rank rank of the officer
assigned this corresponds to the organization the officer is assigned to
charged the name of an organization, usually the same as assigned
date the date when the overtime was worked
code code for the type of overtime
description description of the type of overtime
start_time
end_time
worked_hours difference between start_time and end_time as provided in Court Overtime 2014 to 2019
ot_hours worked_hours after rounding-up logic is applied (e.g. anything under four hours is rounded up to four)
officer_ Additional information about the contact_officer. See Officers for all fields prefixed with officer_.