Spike: Write up a proposal for handling zip codes, counties, and FIPS (oh my)

[MauriceReeves-usds]

Problem Statement

We have multiple different issues that relate back to how we handle zip codes:

1. If the sender does not provide a zip code we have no way to look up and fill in that data
2. If the sender provides us with an invalid zip code we have no way currently to validate
3. If the zip code provided by the sender does not exist in our zip code database, even if it is valid, we have no way to look up the correct county and FIPS code for the address
4. The zip code is the only value from the sender used to retrieve the FIPS County Code, so if a valid zip is received but the state received doesn't match the zip, the FIPS County Code is wrong.
5. Our current covid_result_metadata table is full of incomplete or incorrect data that limits its utility.

Acceptance Criteria

• The outcome of this case will be a proposal for a new process that will allow us to integrate with the SmartyStreets API and utilize its capabilities to have accurate data. The proposal should not advocate for any methods that would significantly slow the processing of incoming records, and it is preferred that we save the raw input we get from senders, and then convert or clean up before sending. It is important that we are able to look at what was originally sent vs what it was converted to.

References

• Here is the SmartyStreets API Documentation: https://www.smartystreets.com/docs/cloud/us-street-api

FYSA: @Adrian-Brewster @anshulkumar-usds @MikeC-A6 @jimduff-usds @RickHawesUSDS

[mlighdc]

Adding @emmastephenson for visibility for SR.