Police Killings

FilesSizeFormatCreatedUpdatedLicenseSource
1129 kBcsvover 6 years agoFiveThirtyEight - Police Killings

This directory contains the data behind the story Where Police Have Killed Americans In 2015. We linked entries from the Guardian's database on police killings to census data from the American Commun...

Read more

Data Files

FileDescriptionSizeLast modifiedDownload
police_killings
129 kBover 6 years ago
police_killings

Data Previews

police_killings

Schema

nametypeformat
namestringdefault
ageintegerdefault
genderstringdefault
raceethnicitystringdefault
monthstringdefault
dayintegerdefault
yearintegerdefault
streetaddressstringdefault
citystringdefault
statestringdefault
latitudenumberdefault
longitudenumberdefault
state_fpintegerdefault
county_fpintegerdefault
tract_ceintegerdefault
geo_idintegerdefault
county_idintegerdefault
namelsadstringdefault
lawenforcementagencystringdefault
causestringdefault
armedstringdefault
popintegerdefault
share_whitenumberdefault
share_blacknumberdefault
share_hispanicnumberdefault
p_incomeintegerdefault
h_incomeintegerdefault
county_incomeintegerdefault
comp_incomenumberdefault
county_bucketintegerdefault
nat_bucketintegerdefault
povnumberdefault
uratenumberdefault
collegenumberdefault

Police Killings

This directory contains the data behind the story Where Police Have Killed Americans In 2015.

We linked entries from the Guardian's database on police killings to census data from the American Community Survey. The Guardian data was downloaded on June 2, 2015. More information about its database is available here.

Census data was calculated at the tract level from the 2015 5-year American Community Survey using the tables S0601 (demographics), S1901 (tract-level income and poverty), S1701 (employment and education) and DP03 (county-level income). Census tracts were determined by geocoding addresses to latitude/longitude using the Bing Maps and Google Maps APIs and then overlaying points onto 2014 census tracts. GEOIDs are census-standard and should be easily joinable to other ACS tables – let us know if you find anything interesting.

Field descriptions:

HeaderDescriptionSource
nameName of deceasedGuardian
ageAge of deceasedGuardian
genderGender of deceasedGuardian
raceethnicityRace/ethnicity of deceasedGuardian
monthMonth of killingGuardian
dayDay of incidentGuardian
yearYear of incidentGuardian
streetaddressAddress/intersection where incident occurredGuardian
cityCity where incident occurredGuardian
stateState where incident occurredGuardian
latitudeLatitude, geocoded from address
longitudeLongitude, geocoded from address
state_fpState FIPS codeCensus
county_fpCounty FIPS codeCensus
tract_ceTract ID codeCensus
geo_idCombined tract ID code
county_idCombined county ID code
namelsadTract descriptionCensus
lawenforcementagencyAgency involved in incidentGuardian
causeCause of deathGuardian
armedHow/whether deceased was armedGuardian
popTract populationCensus
share_whiteShare of pop that is non-Hispanic whiteCensus
share_bloackShare of pop that is black (alone, not in combination)Census
share_hispanicShare of pop that is Hispanic/Latino (any race)Census
p_incomeTract-level median personal incomeCensus
h_incomeTract-level median household incomeCensus
county_incomeCounty-level median household incomeCensus
comp_incomeh_income / county_incomeCalculated from Census
county_bucketHousehold income, quintile within countyCalculated from Census
nat_bucketHousehold income, quintile nationallyCalculated from Census
povTract-level poverty rate (official)Census
urateTract-level unemployment rateCalculated from Census
collegeShare of 25+ pop with BA or higherCalculated from Census
Note regarding income calculations:

All income fields are in inflation-adjusted 2013 dollars.

comp_income is simply tract-level median household income as a share of county-level median household income.

county_bucket provides where the tract's median household income falls in the distribution (by quintile) of all tracts in the county. (1 indicates a tract falls in the poorest 20% of tracts within the county.) Distribution is not weighted by population.

nat_bucket is the same but for all U.S. counties.

This dataset was scraped from FiveThirtyEight - police-killings

© 2024 All rights reservedBuilt with DataHub Cloud