washingtonpost / data-police-shootings Goto Github PK

The Washington Post is compiling a database of every fatal shooting in the United States by a police officer in the line of duty since 2015.

License: Other

data-police-shootings's Introduction

Fatal Force Database

In 2015, The Post began tracking details about each police-involved killing in the United States — the race of the deceased, the circumstances of the shooting, whether the person was armed and whether the person was experiencing a mental-health crisis — by manually culling local news reports, collecting information from law enforcement websites and social media, and monitoring independent databases such as Fatal Encounters and the now-defunct Killed by Police project. In many cases, The Post conducts additional reporting.

In 2022, The Post updated its database to standardize and publish the names of the police agencies involved in each shooting to better measure accountability at the department level.

The 2014 killing of Michael Brown in Ferguson, Mo. began a protest movement culminating in the Black Lives Matter movement and an increased focus on police accountability nationwide. In this data set, The Post tracks only shootings with circumstances closely paralleling those like the killing of Brown — incidents in which a police officer, in the line of duty, shoots and kills a civilian. The Post is not tracking deaths of people in police custody, fatal shootings by off-duty officers or non-shooting deaths in this data set.

The FBI and the Centers for Disease Control and Prevention log fatal shootings by police, but officials acknowledge that their data is incomplete. Since 2015, The Post has documented more than twice as many fatal shootings by police as recorded by federal officials on average annually. That gap has widened in recent years, as the FBI in 2021 tracked only a third of departments’ fatal shootings.

The Post seeks to make records as comprehensive as possible; the database is updated regularly as fatal shootings are reported and as facts emerge about individual cases. At times, there may be a lag between the date of the shooting and its inclusion in the database because of delays in reporting and data verification.

To provide information about fatal police shootings since Jan. 1, 2015, send us an email at [email protected].

Explore the interactive database

Data Versions

Version 2:
- Version 2 includes changes to improve the data schema, increase transparency around research methodology, and add data on law enforcement agencies.
- Documentation and data formatted in the v2 data stucture can be found in /v2.
- Details on the changes between v1 and v2 can be found in v2/README.md.
Version 1:
- Data formatted in the v1 data structure can be found in /v1.

Note:

As of the official v2 release, the data files in /v2 include all records since 2015; historic records have been transformed into the new data schema.
The /v1 data is static as of the migration to v2; the data is no longer updated. Only the /v2 datasets are updated.

Contact & Contributing

We welcome assistance in making the our data as complete and accurate as possible.

Please reach out with any questions about the data, feedback, updated information or corrections. Before you do, take a moment to review the Code of Conduct.

The best way to contribute to the data, make suggestions or provide information about fatal police shootings since Jan. 1, 2015, is to send us an email at [email protected].

Please note that we do not accept pull requests as the data file is automatically generated from our internal database.

Licensing

The data is published under an Attribution-NonCommercial-ShareAlike 4.0 International CC BY-NC-SA 4.0 license.

Credits

Research and reporting: Jennifer Jenkins, Monika Mathur, Razzan Nakhlawi, Steven Rich and Andrew Ba Tran.

Design and development: Chris Alcantara, Katlyn Alo, Emma Baker, Aaron Brezel, Armand Emamdjomeh, Jake Kara, Paige Moody, James O’Toole and Leslie Shapiro.

Editing: Sarah Childress, David Fallis, Reuben Fischer-Baum, Meghan Hoyer and Courtney Kan.

Past contributors: Keith L. Alexander, Sophie Andrews, Jason Bartz, Amy Brittain, Swetabh Changkakoti, Hong Sen Du, Kennedy Elliot, Linda Epstein, Holden Foreman, Joe Fox, Wendy Galietta, Kaeti Hinck, Laris Karklis, Kimberly Kindy, Whitney Leaming, Emily Liu, Wesley Lowery, Ted Mellnik, Lori Montgomery, Deblina Mukherjee, John Muyskens, Erik Reyna, Danielle Rindler, Kavya Sukumar, Julie Tate, Susan Tyler, Divya Verma, Aaron Williams.

data-police-shootings's People

Contributors

Stargazers

Watchers

Forkers

metasyn mjirv christophersalam jbwhit elizabethlorde aidenyang kayiwa jcglaw1007 keita1 bobwat binaricorn stevenrich-zz bsinclairmph tdetzel ldt0909 kostasx juliasilge marielclark jc4p atmontague billyehrenberg jarvmiller hamedbh adamgibbons yankev cocoonventures decision-stats whaletail skatelyn 7moses momof3babies bradyds enboyd nreddy216 jameslabundis aphor cparoiss pbntx lgenin mahoffman reidoffringa katielong mhespo elmeauxyo orug diguabo akshata92 cmmyers chrisshea13 heckealgebra erinsiodmak pauljaeger chubbyprincess prutha28 mlfurman cl-op stryker28 hermionewy kevinrak9 vipassana wallygauze wgerecht smitty1788 roadsewhouse nickdiakopoulos crebs kstack885 mrajendiran nickkimer emekanwosu hkatz11 lebaron-sims jaxinye barbarasm51 christopherjenness campkels jamielaird ktargows nathanhassanzadeh jayonez bespokebenji mike562 adiamb miakd restrellado limasol shduttacheezit rgreisemer-cn dswah leannemcg tinacious thuthazack larsh0103 stiles aniruhil rtjeannier rmays1 isaacweathers jonkiparsky fesp21

data-police-shootings's Issues

Geography errors for wapo ID 1623

Your lat/long is in Vancouver (45.63873, -122.6615), as is your City.

This article identifies the block:
http://www.oregonlive.com/clark-county/index.ssf/2016/06/vancouver_bank_robbery_suspect_2.html

This block is in Duluth, with lat/long (45.7838051 ,-122.6888937)

https://washington.hometownlocator.com/cities/map,n,duluth-wa,fid,2629757.cfm

Why was the person shot?

Why is there no indication as to whether the shooting was related to a crime?

I wrote an iOS app using your data. See your email Washington Post People.

When human is a Junior, do not use a comma. It messes up my parsing.

I want to work with you on this.
You should want to work with me on this.

timezone on `date` column

Hello! I noticed Breonna Taylor's death is listed on March 12th, but news reports seem to say she was killed shortly after midnight on March 13th. I'm just wondering if the date column is being reported out from a certain timezone or if all the dates are based on local time. If it is in a particular timezone, I figured that could be added to the README. Thanks!

Race Data incomplete.

Is there an issue with the dataset? It seems that there is a tremendous change in the data starting in 2021 with race not being reported.

There was a slight trend upward in previous data, but it has nearly made the data unusable for analytics.

File format again XML, not CSV.

You're again assigning .csv as a file extension to an XML file (as was done in a closed issue from 2016). .csv files are "flat" and contain only data and commas.

suggestions for "type" variable in agency file

There is no "county-other" category, so several county-level agencies are designated "local-other". County level police are governed by different bodies than local police, so it might be worth creating a distinct category for "county-other".
Consider creating a category for tribal police.
Consider creating a category for campus police (school, college, university)
Some apparently local police departments are missing the type variable (notably, Savannah Police Department). Should these be classified as local police?

Possible duplicate case

Cases # 8416 and 8617 may be the same case.

8617 is identified as Derrick Ameer Ellis-Cook 9/9/2022
8416 was unnamed until the V2 dataset, where he is now identified as Christopher Rudolf 9/10/2022.

Both are reported shot by Burien Police Dept.

I believe there is only one case in Burien in that time frame, Derrick Ameer Ellis-Cook 8617. News reports were inconsistent about the date, one saying "Friday" (9/9) but others saying "Saturday" (9/10). Both his gofundme site https://www.gofundme.com/f/justice-for-derrick-ameer-ellis-cook and the official Burien PD report to the WA CJTC say 9/10/2022, so I believe that is the correct date.

I have not been able to verify that anyone named Christopher Rudolf was shot by police in WA, or that anyone else was shot by Burien PD in September 2022. No one by that name appears in the Mapping Police Violence dataset. So I think that 8416 may have initially been a duplicate entry caused by the inconsistent dates reported in the media for Ellis-Cook, before he was identified. But I don't know where you would have sourced the name Christopher Rudolph and age 39.

If you do have evidence for case 8416, please let me know. That would mean the Burien PD has not reported this case to the WA CJTC, which they are required by law to do.

Otherwise this case should be deleted.

Data

Police Department Information

Could you add information indicating whether the officers involved were part of the federal, state, county, or city police force? I would like to study differences in training & polices between departments. Thanks

Incidents with empty armed field

The incidents with the following ids currently have an empty armed field, and if it isn't known whether they were armed or not undetermined ("it is not known whether or not the victim had a weapon") would seem to be the appropriate value to assign by default rather than leaving them empty.

Armed info missing?

Does that indicate that the victim was unarmed or was the data unavailable?

Gather data on all police shootings, not just fatalities.

Would be a much larger task, but I think it would be valuable data. We're not seeing the whole picture if we focus only on fatalities. The difference between fatal or non-fatal may a millimeter. If we want to understand why and under what circumstances police are drawing their weapons and firing, we're only looking at a portion of the applicable data.

Use Sex instead of Gender

The data attribute originally referred to as Gender seems to actually indicate Sex, as it only has the options of M/F/NULL.

Switching the label to Sex would better adhere to the ISO/IEC 5218 standard for representing human sexes based on the actual data.

Text summaries

Is there any way to include a text summary with each case as is shown on the website? Something like this would be great for trying to indicate justification.

Improperly formated .csv

Your download is an XML doc .. not a .csv doc ..
Please address .. the data is of import and worthwhile but of little use to many in it's current format

Officer Information

When will the officer data be made available?

Bodycam == Tasercam

I noticed in David Kassick's case. Bodycam technically is False. However the encounter was recorded on a Taser cam. Perhaps body cam should be less specific to include other police recording devices? ie Dash cam, etc...? Or include other columns to pertain to that piece of info?

I like the specificity of Bodycam, especially as more and more departments are beginning to use them. However, I feel like the knowledge or evidence that it implies is equally true in the case of a taser cam.

Didn't even know that was a thing til I saw David Kassick's vid.
https://www.youtube.com/watch?v=jP-xXO1vuaw

"city" column is occasionally incorrect.

A few entries in the "city" column are actually counties, and not cities. For example, id: 598, city: Josephine County

Incorrect Data

Manner of death

There are only two values in the 'manner of death' column ('shot' 'shot and tasered'), while there are case (such a George Floyd's, which is not found in the table by the way) that the victim was strangled.

Am I missing something?
BTW, you can check out my repository for a shallow analysis.

George Floyd missing from dataset

George Floyd is missing from the dataset.

Misspelling of Megan Hockaday

Hello,

I believe that "Megan Hockaday", ID 245, is more commonly spelled as "Meagan Hockaday" (see the Wikipedia page). Thanks.

Several geography errors for wapo ID 1145

The coordinates you have are in Seattle (47.60621, -122.3321) and your city is "Olympia".

The incident happened in Tumwater, and the FE coordinates are consistent with that (46.95281, -122.9079)

Is this data no longer being updated?

I created twitter.com/poshootingsbot when this repository first went live, and recently noticed that the bot had stopped tweeting in February. Is this list no longer being updated?

Missing color information on recent data

I would like to know why there is no information about a lot of lines without color information. Is it just because they are all white people? I hope this is not the case because my Machine Learning analysis shows that more than 50% of killed people are white, and 26% are black people.

Same person with multiple ID's.

The ID numbers 6672 and 7880 refer to the same person, and all the information except the race and the body camera status are the same. The race for 6672 is White and the body camera status is False, but the race for 7880 is blank and the body camera status is True.

Off by one field for a few ids

It looks like the data is off by one field for all of the following as for some reason date has JR, and there is a shift down by one field for each. I found when using a script I wrote and I thought the data looked strange.

get_years(){ jq -rM ' .[] | select(.date | contains("20") | not) .id ' data.json | while read id; do grep $id data.csv done }

1591,"Hubert Thomas Burns, Jr.",2016-06-03,shot,knife,34,M,N,Parker,AZ,False,other,Not fleeing,False,-112.139,33.863,True 4116,"Neico Crooks, Jr",2018-10-19,shot,vehicle,21,M,B,Miami,FL,False,attack,Car,False,-80.203,25.948,True 4145,"Jose Centeno, Jr.",2018-10-31,shot,toy weapon,17,M,H,Houston,TX,False,attack,Car,True,-95.53,30.027,True 4189,"Jack Fields, Jr.",2018-11-15,shot,knife,25,M,B,Augusta,GA,True,attack,Not fleeing,False,-82.083,33.48,True 4648,"John Stewart, Jr.",2019-04-17,shot,knife,46,M,W,Pentress,WV,True,attack,Foot,True,-80.17,39.708,True 4732,"Donald Davis, Jr.",2019-05-17,shot,gun,40,M,B,New Orleans,LA,False,attack,,True,-89.999,30.024,True 4778,"Vincense Williams, Jr.",2019-06-10,shot,gun,24,M,B,Oklahoma City,OK,False,other,Not fleeing,True,,,True

{ "id": "1591", "name": "\"Hubert Thomas Burns", "date": " Jr.\"", "manner_of_death": "2016-06-03", "armed": "shot", "age": "knife", "gender": "34", "race": "M", "city": "N", "state": "Parker", "signs_of_mental_illness": "AZ", "threat_level": "False", "flee": "other", "body_camera": "Not fleeing", "longitude": "False", "latitude": "-112.139", "is_geocoding_exact": "33.863" } { "id": "4116", "name": "\"Neico Crooks", "date": " Jr\"", "manner_of_death": "2018-10-19", "armed": "shot", "age": "vehicle", "gender": "21", "race": "M", "city": "B", "state": "Miami", "signs_of_mental_illness": "FL", "threat_level": "False", "flee": "attack", "body_camera": "Car", "longitude": "False", "latitude": "-80.203", "is_geocoding_exact": "25.948" } { "id": "4145", "name": "\"Jose Centeno", "date": " Jr.\"", "manner_of_death": "2018-10-31", "armed": "shot", "age": "toy weapon", "gender": "17", "race": "M", "city": "H", "state": "Houston", "signs_of_mental_illness": "TX", "threat_level": "False", "flee": "attack", "body_camera": "Car", "longitude": "True", "latitude": "-95.53", "is_geocoding_exact": "30.027" } { "id": "4189", "name": "\"Jack Fields", "date": " Jr.\"", "manner_of_death": "2018-11-15", "armed": "shot", "age": "knife", "gender": "25", "race": "M", "city": "B", "state": "Augusta", "signs_of_mental_illness": "GA", "threat_level": "True", "flee": "attack", "body_camera": "Not fleeing", "longitude": "False", "latitude": "-82.083", "is_geocoding_exact": "33.48" } { "id": "4648", "name": "\"John Stewart", "date": " Jr.\"", "manner_of_death": "2019-04-17", "armed": "shot", "age": "knife", "gender": "46", "race": "M", "city": "W", "state": "Pentress", "signs_of_mental_illness": "WV", "threat_level": "True", "flee": "attack", "body_camera": "Foot", "longitude": "True", "latitude": "-80.17", "is_geocoding_exact": "39.708" } { "id": "4732", "name": "\"Donald Davis", "date": " Jr.\"", "manner_of_death": "2019-05-17", "armed": "shot", "age": "gun", "gender": "40", "race": "M", "city": "B", "state": "New Orleans", "signs_of_mental_illness": "LA", "threat_level": "False", "flee": "attack", "body_camera": "", "longitude": "True", "latitude": "-89.999", "is_geocoding_exact": "30.024" } { "id": "4778", "name": "\"Vincense Williams", "date": " Jr.\"", "manner_of_death": "2019-06-10", "armed": "shot", "age": "gun", "gender": "24", "race": "M", "city": "B", "state": "Oklahoma City", "signs_of_mental_illness": "OK", "threat_level": "False", "flee": "other", "body_camera": "Not fleeing", "longitude": "True", "latitude": "", "is_geocoding_exact": "" }

What is name TK TK?

Some of the names in the dataset are TK TK. What does this mean?

Body Camera Variable Definition

I really like this data set, I do however have a question regarding the body cam variable, I cannot locate a code book for it. How is False and True determined? For instance, when you put 'false' is it a definite they did not have it on, or is it possible it is not known? Also case 1399 is labeled as "Not f" which does not align with the rest of the cases.

Please include other killing methods

like chokings, etc...

Shootings are not inclusive enough, we need chokings and all other causes of death

Typos

I sent an email August of last year to [email protected] and haven't heard back, so I'm making an issue here:

The dataset claims that Eduardo Navarrete was shot on 2017-08-12 in Frederickstown, WA. I believe this is a typo, and the location should be Frederickson, WA. According to this article the shooting happened in Pierce County on 189th St. Court East, which is presumably here
(new) Line 5873 has "Bewster County,TX" and should be "Brewster County, TX"

Misspelling of Lynnwood Washington in agency names file

for row 1719 id 1573

should be Lynnwood with two "n's", not one

https://www.lynnwoodwa.gov/Home

Age?

Can we get ages or age ranges as well?

Column options?

Could you update the readme with the list of possibilities for all the columns?

I see it has some, but armed, threat_level, and flee are missing.

Sources

Excellent work. Of a similar nature to theviolenceproject.org.

My request: I'd like to work with this data, plus find and associate additional data. For example, parse & NLP the articles appearing after "Sources:" on the interactive database, to extract additional attributes.

However, it doesn't appear that those article links are present in your repo.

Can you a) add them, or b) supply them to me? Seems like it's public info that would help other data journalists and researchers who are leveraging your database to perform complementary research.

I'd rather not have to scrape your UI to get the article links, or pull the combined json from your CDN! Keep it on the up-and-up so that if I offer additional data back to you, you're cool about it.

Thanks.

Feature wish list

If there is such a wish list growing I would love to see the following characteristics added to the data.

Officer race
Officer age
Years of experience
Did the deceased have a prior criminal record?

VBA script to analyze data

I'd be interested in seeing how this data is being used and the macros used to do the analysis.

Here's a VBA script used to create a table showing the percentage of unarmed individuals killed sorted by race. The table starts in column 25.

Public Sub CreateTableofUnarmedByRace()
Dim NumOfRecords As Integer
Dim W, B, H, A, O
Dim Armed, Unarmed, UnarmedW, UnarmedB, UnarmedH, UnarmedA, UnArmedO
Dim SC ' StartColumn
SC = 25
NumOfRecords = Range("A1048576").End(xlUp).Row
B = WorksheetFunction.CountIf(Range("H2:H" & NumOfRecords), "B")
W = WorksheetFunction.CountIf(Range("H2:H" & NumOfRecords), "W")
A = WorksheetFunction.CountIf(Range("H2:H" & NumOfRecords), "A")
H = WorksheetFunction.CountIf(Range("H2:H" & NumOfRecords), "H")
O = WorksheetFunction.CountIf(Range("H2:H" & NumOfRecords), "O")
Cells(2, SC) = "Total Records"
Cells(2, SC + 1) = NumOfRecords
Cells(4, SC) = "White"
Cells(4, SC + 1) = W
Cells(5, SC) = "Black"
Cells(5, SC + 1) = B
Cells(6, SC) = "Hispanic"
Cells(6, SC + 1) = H
Cells(7, SC) = "Asian"
Cells(7, SC + 1) = A
Cells(8, SC) = "Other"
Cells(8, SC + 1) = O

ArmedGun = WorksheetFunction.CountIf(Range("E6:E" & NumOfRecords), "gun") ' Total Armed w/ gun
Cells(9, SC).Value = "Armed with a non-toy gun"
Cells(9, SC + 1).Value = ArmedGun
Cells(9, SC + 2).Value = ArmedGun / NumOfRecords
ArmedKnife = WorksheetFunction.CountIf(Range("E6:E" & NumOfRecords), "knife") ' Total Armed w/ knife
Cells(10, SC).Value = "Armed with a knife"
Cells(10, SC + 1).Value = ArmedKnife
Cells(10, SC + 2).Value = ArmedKnife / NumOfRecords
Unarmed = WorksheetFunction.CountIf(Range("E6:E" & NumOfRecords), "unarmed") ' Total Unarmed
Cells(11, SC).Value = "Unarmed"
Cells(11, SC + 1).Value = Unarmed
Cells(11, SC + 2).Value = Unarmed / NumOfRecords
ToyWeapon = WorksheetFunction.CountIf(Range("E6:E" & NumOfRecords), "toy weapon") ' Total with toy weapon
Cells(12, SC).Value = "Toy Weapon"
Cells(12, SC + 1).Value = ToyWeapon
Cells(12, SC + 2).Value = ToyWeapon / NumOfRecords
Undetermined = WorksheetFunction.CountIf(Range("E6:E" & NumOfRecords), "undetermined") ' Total Undetermined
Cells(13, SC).Value = "Undetermined"
Cells(13, SC + 1).Value = Undetermined
Cells(13, SC + 2).Value = Undetermined / NumOfRecords
UnarmedW = WorksheetFunction.CountIfs(Range("H3:H1" & NumOfRecords), "W", Range("E3:E1" & NumOfRecords), "unarmed")
Cells(14, SC).Value = "Un-Armed and White"
Cells(14, SC + 1).Value = UnarmedW
Cells(14, SC + 2).Value = UnarmedW / NumOfRecords
UnarmedB = WorksheetFunction.CountIfs(Range("H3:H1" & NumOfRecords), "B", Range("E3:E1" & NumOfRecords), "unarmed")
Cells(15, SC).Value = "Un-Armed and Black"
Cells(15, SC + 1).Value = UnarmedB
Cells(15, SC + 2).Value = UnarmedB / NumOfRecords
Cells(15, SC + 2).Value = UnarmedB / NumOfRecords
UnarmedA = WorksheetFunction.CountIfs(Range("H3:H1" & NumOfRecords), "A", Range("E3:E1" & NumOfRecords), "unarmed")
Cells(16, SC).Value = "Un-Armed and Asian"
Cells(16, SC + 1).Value = UnarmedA
Cells(16, SC + 2).Value = UnarmedA / NumOfRecords
UnarmedH = WorksheetFunction.CountIfs(Range("H3:H1" & NumOfRecords), "H", Range("E3:E1" & NumOfRecords), "unarmed")
Cells(17, SC).Value = "Un-Armed and Hispanic"
Cells(17, SC + 1).Value = UnarmedH
Cells(17, SC + 2).Value = UnarmedH / NumOfRecords
UnArmedO = WorksheetFunction.CountIfs(Range("H3:H1" & NumOfRecords), "O", Range("E3:E1" & NumOfRecords), "unarmed")
Cells(18, SC).Value = "Un-Armed and Other"
Cells(18, SC + 1).Value = UnArmedO
Cells(18, SC + 2).Value = UnArmedO / NumOfRecords
ActiveSheet.Columns(SC + 2).NumberFormat = "##.#0%"
End Sub

Typo in ID 5536

The city name in id 5536 should be "Anchorage" not "Achorage"

Duplicate entries

I just downloaded and browsed this data out of curiosity and I noticed some duplicate entries. They may not affect the overall count by much, but I think WaPo should give these rows some further scrutiny considering that these numbers are cited by many other publications as an accurate accounting of police shootings. Not to mention that each row represents a human life, so it's not exactly some small matter. Do it for journalistic integrity if nothing else.

These four are most likely definite duplicates:

5603 Terry Hasty 2/25/2020 shot gun 56 M Dalzell SC
5572 Terry Hasty 2/25/2020 shot gun 56 M Sumter County SC

5548 Timothy Leroy Harrington 2/14/2020 shot gun 58 M W Polkton NC
5537 Timothy Leroy Harrington 2/14/2020 shot gun 58 M W Polkton NC

5889 David Tylek Atkinson 5/13/2020 shot gun 24 M B Raleigh NC
5835 David Tylek Atkinson 5/13/2020 shot gun 24 M B Raleigh NC

5191 Benjamin Diaz 11/1/2019 shot box cutter 22 M H Alamogordo NM
5150 Benjamin Diaz 11/1/2019 shot sharp object 22 M H Alamogordo NM

These are questionable:

4237 Roderick McDaniel 11/20/2018 shot vehicle 33 M B Magnolia AR
4195 Roderick McDaniel 11/19/2018 shot gun 33 M B Magnolia AR

5515 Miguel Mercado Segura 1/21/2020 shot gun 31 M H Fountain Valley CA
5389 Miguel Mercado Segura 1/20/2020 shot gun 31 M H Fountain Valley CA

5135 Clayton Andrews 10/26/2019 shot gun 40 M W Creek County OK
5128 Clayton Andrews 10/25/2019 shot gun 40 M W Kansas OK

Typos in agency file

id	agency name	problem
2491	U.S, Marshal's Service	"," should be "."
1747	Sabine Parish Sherrif's Office	Sheriff
1259	Plymouth County Sherrif's Department	Sheriff
2543	Braselton Polie Department	Police
3490	White Mountain Apache Police Department	should be White Mountain Apache Tribe Police Department for consistency with 2734, both have the same ORI

Data entry

Noticed there are 46 rows where the victims name is listed as 'TK TK'. Is there a reason for this?

id #1591

This case is always off by one column when I download the data, because there is a quotation mark ahead of the victim's name (Hubert Thomas Byrnes, Jr.).

How is it possibly ethical to hard paywall this content on mobile browsers?

Title. The webpage link is accessible by passerbys on web but not on mobile Firefox. The interruption isn't a soft paywall nudge, it's a hard lockout where I have to sign up to your website, i.e. compensate you with my user data to be able to see the content. Democracy dies when rags owned by Bezos prioritize money over data access?

Missing data field

The "fleeing" field is not filled in for several 2015 & 2016 entries:
1007 Ernesto Gamino
1020 Randy Allen Smith
1042 Zachary Grigsby
1083 Roy Carreon
1086 Efrain Villanueva
1093 Hector Alvarez
1103 Trayvon Scruggs
1123 Bettie Jones
1136 John Randell Veach
1338 John Alan Chamberlain
1376 Scott Bennett
1605 James Allen Nickol
1676 Kawme Dejuan Patrick
1692 Joshua Bolster

Please add a FIPS field to this table

It would be very helpful to have FIPS data added to this table.

Currently,

4855 records lack county data.
373 rows have the word "county" in the city field; 297 of these rows have no value in the county field. This suggests that about 300 records were entered incorrectly.

Adding FIPS values would solve this confusion and make the data far more useful, since there are a lot of datasets that record information at the county level and include FIPS values.

For the rows that have lat/long data, adding FIPS is easy. (I did this in python by reading the Census dept's county map file and doing a geopandas.join() on the two tables).

But about 10 percent of the rows don't have lat/long data, which makes identifying the FIPS number more complex. Matching the county+state can be done, but there is no uniform way to record this information (is it 'Fairfax' or "Fairfax county') and typos will cause glitches.

Doubtless, there will be some rows for which this data remains unknown. But adding FIPS numbers to all the rows where possible would greatly facilitate cross-referencing this data with other data that is collected at the county level.

about the item "manner_of_death"

Thanks for providing us such comprehensive data!
According to the README doc, "the Post is documenting only those shootings in which a police officer, in the line of duty, shoots and kills a civilian."
However, the item "manner_of_death" is of two values, "shot" and "shot and Tasered." Could you clarify the differences between these two? And is it means that the shotted was not necessarily killed?

ID 4803 Kevin Pudlik

Need to verify if the race of this individual

County in city field: case 1084

city should be Olympia