Use geocoder API to geocode during ETL

[potash]

Currently the ETL process relies on already geocoded data (blood lead tests). That data was geocoded by CDPH. There are two issues:

1. for future refreshes of the data we should not rely on CDPH to do the geocoding
2. for the existing data, the geocoding that CDPH was not great. I reran some of the bad addresses through the geocoder API manually and they were recognized. So we will benefit by doing this for all addresses.

[tomschenkjr]

Architecturally, do you think you’ll “bake-in” the code into lead-ETL or create a separate package that is called by lead-etl? From: Eric Potash [mailto:notifications@github.com] Sent: Monday, November 27, 2017 3:25 PM To: Chicago/lead-etl <lead-etl@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [Chicago/lead-etl] Use geocoder API to geocode during ETL (#6) Currently the ETL process relies on already geocoded data (blood lead tests). That data was geocoded by CDPH. There are two issues: 1. for future refreshes of the data we should not rely on CDPH to do the geocoding 2. for the existing data, the geocoding that CDPH was not great. I reran some of the bad addresses through the geocoder API manually and they were recognized. So we will benefit by doing this for all addresses. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#6>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABkC0RW30yD4OuJ1fo4_CvK4cMdi49MWks5s6yiNgaJpZM4QsURK>.

…

________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail (or the person responsible for delivering this document to the intended recipient), you are hereby notified that any dissemination, distribution, printing or copying of this e-mail, and any attachment thereto, is strictly prohibited. If you have received this e-mail in error, please respond to the individual sending the message, and permanently delete the original and any copy of any e-mail and printout thereof.

[potash]

Yes, I was thinking it would live in this repo. But it would work in such a way that we do not need to re-geocode millions of addresses everytime we run the ETL. What do you think?

[tomschenkjr]

Sounds great. Just wanted an idea on the direction. From: Eric Potash [mailto:notifications@github.com] Sent: Tuesday, November 28, 2017 1:48 PM To: Chicago/lead-etl <lead-etl@noreply.github.com> Cc: Schenk, Tom <Tom.Schenk@cityofchicago.org>; Comment <comment@noreply.github.com> Subject: Re: [Chicago/lead-etl] Use geocoder API to geocode during ETL (#6) Yes, I was thinking it would live in this repo. But it would work in such a way that we do not need to re-geocode millions of addresses everytime we run the ETL. What do you think? — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#6 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABkC0fjCwFDVzQtxM_848i1_pbxqG_P7ks5s7GNdgaJpZM4QsURK>.

…

________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail (or the person responsible for delivering this document to the intended recipient), you are hereby notified that any dissemination, distribution, printing or copying of this e-mail, and any attachment thereto, is strictly prohibited. If you have received this e-mail in error, please respond to the individual sending the message, and permanently delete the original and any copy of any e-mail and printout thereof.