Open trevorcampbell opened 3 years ago
So beat number is already given with the complaint and TRR data, so this is not strictly necessary as far as beat numbers are concerned. But more generally, I agree that some form of normalization and/or geocoding of the addresses across datasets would be nice. Rather than the above source, I think this one is more authoritative: https://data.cityofchicago.org/Public-Safety/Boundaries-Police-Beats-current-/aerh-rz74
Also, the dataset of building footprints looks very useful: https://data.cityofchicago.org/Buildings/Building-Footprints-current-/hz9b-7nh8
I think in most cases, we can just lookup the address in the building data and get the gps coordinates directly from there, without using a geocoding service.
[Just an idea for future improvement]
ChicagoPoliceBeats (1).zip found here: http://edrub.in/ARE212/Spring2017/section12.html
a shapefile of beats. We could include this info to convert beats / districts into rough lat/long coordinates.
Another idea is to geocode the addresses in the complaint/TRR data to attach them to districts/beats.