Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include Crime data for 2020 #172

Open
moldybeats opened this issue Mar 5, 2020 · 2 comments
Open

Include Crime data for 2020 #172

moldybeats opened this issue Mar 5, 2020 · 2 comments
Assignees

Comments

@moldybeats
Copy link
Collaborator

The new dataset for 2020 Crime data can be found here:

https://data.kcmo.org/Crime/KCPD-Crime-Data-2020/vsgj-uufz

We need to include this in the crime stats.

@moldybeats moldybeats self-assigned this Mar 5, 2020
@moldybeats
Copy link
Collaborator Author

moldybeats commented Mar 17, 2020

@AmandaWilsonKC - thought this was going to be a quick task, but I hit a snag. Looks like the 2020 Crime data doesn't include the lat/lon coordinates we need to map crime reports. This was included in previous crime datasets.

I'll include an example of a query from the 2019 data and the 2020 data. You can see how the "location" field in the 2019 query includes latitude and longitude properties while the 2020 data does not:

2019: https://data.kcmo.org/resource/pxaa-ahcm.json?$where=report_no=%27KC19019730%27
2020: https://data.kcmo.org/resource/vsgj-uufz.json?$where=report_no=%27KC20001739%27

This is probably related to the fact that the addresses in the 2020 dataset don't have zip codes.

Is there someone involved in the Open Data KC datasets who could help us get that fixed?

@moldybeats
Copy link
Collaborator Author

We're going to leave this issue unresolved for the moment. Sounds like KCPD switched to a new platform for public crime data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant