​​CPDP Schema Documentation
​​See also ​+CPDP document types and entity relational model​ 
​​
​​See also: http://invisible.institute/download-the-data
​​
​​SchemaSpy relational map: http://users.eecs.northwestern.edu/~jennie/courses/cs339/lab1/cpdb-schema/relationships.html
​​Database dump here: http://users.eecs.northwestern.edu/~jennie/courses/cs339/lab1/cpdb.sql
​​
​​

​​Table: data_policeunit

  • ​​unit_name - Name of the unit usually consist of 3 to 5 numbers
  • ​​description - More descriptive name of the unit
  • ​​active - Whether this police unit is currently active. Sometime we have two units with the same unit_name but different description and one of them is an old inactive unit.
​​
​​Example rows:
​​
​​unit_name
​​description
​​active
​​000
​​Area 0
​​True
​​001
​​District 001
​​True
​​002
​​District 002
​​True
​​003
​​District 003
​​True

​​Table: data_officer

  • ​​first_name - First name of officer, in title case
  • ​​last_name - Last name of officer, in title case
  • ​​middle_initial - First character of middle name, in upper case
  • ​​middle_initial2 - First character of second middle name if any, in upper case
  • ​​suffix_name - Possible values are:
  • ​​“I”
  • ​​“II”
  • ​​“III”
  • ​​“IV”
  • ​​“V”
  • ​​“JR”
  • ​​“SR”
  • ​​gender - Gender of officer, possible values are:
  • ​​“M”
  • ​​“F”
  • ​​empty string
  • ​​race - Race of officer, possible values are:
  • ​​“Hispanic”
  • ​​“Black”
  • ​​“White”
  • ​​“Asian/Pacific”
  • ​​“Native American/Alaskan Native”
  • ​​“Unknown”
  • ​​appointed_date - The date that officer is appointed
  • ​​resignation_date - The date that officer resigned
  • ​​rank - Current rank of officer, in title case
  • ​​birth_year - Birth year of officer
  • ​​active - Current employment status of officer, possible values are:
  • ​​“Yes”