Develop a solution to ensure every entry in our Airtable database has latitudes and longitudes.

[charliehoffs]

Context/Motivation: When entries in our database do not have latitudes and longitudes, it prevents them from appearing in our UI. If we are striving towards a standard in which our database is the most updated, accurate, complete listing of Bay Area social service resources, we cannot fulfill that promise unless all our UI accurately displays all the data in our database. "Tamiscal High School" for example, is serving meals and is fully entered in our database, but does not have lats and lons and thus doesn't appear. We should prioritize adding lats and lons for existing sites in our database (school meals, CalFresh stores, legal, mental health, medical, cash) but also develop a sustainable system to ensure that all addresses automatically populate lat/lons and we are notified or can easily find instances where they don't!

Definition of Done:

• When all entries in our Airtble database have a latitude and longitude.
• When our Airtable includes an automated script that adds lats and lons to each newly added row with an address.

Estimate of time: [To be filled out by engineer investigating this!]

Next steps:

• Wentao identified and quantized the problem on Page 3 of this document! https://docs.google.com/document/d/1QRPXI_jE7vJJcfWTGjIFr3cov6yPyqixiXiWRzmMnAw/edit
• Wentao has written a script into the BAC TEST Database ( 'LOCATIONS - auto-populate latitude & longitude' )to automatically populate Airtable with lats and lons! Here is her instructional video on the process: https://drive.google.com/file/d/1bXhuukIoUNeP3A9CIpyXNR1g2sj1IxPG/view?usp=sharing
• Maybe we can upload that script to this mega-map repo Github and link to it in this issue?
• Than we can make a plan for safely implementing this script in our full database (not the "test" database!)
• Then we can run the script on our database, and check if it worked in the UI!

[mtw812]

Since getting lat/long values via API calls require address information, we probably also want to fix the known issues in the ADDRESS table as well.