The backend needs lat & lon points for each county's jurisidction location
Outcome of this issue
we will be able to run a script that reads each line of a csv with scraped locations data and POSTs to the /dropoffs endpoint and saves the records to the db
action items
get the latest schema from #data-science and create the jurisdictions model and table and generaate a model and migration for this table
get the latest csv dump from airtable having all the locations of scraped jurisdiction dropoffs; then use the script that @Henrymarks1 wrote in ./backend/seeders to read each record in the csv, query the TAMU geocoding service.
for each geocode we then call /dropoffs api with a request body having all information we need to save
{
"address_1": "123 Maint St",
"county_fips": "044236",
"lat": 32.1556,
"long": 113.32
.... all other fields in the schema
}
Overview
The backend needs lat & lon points for each county's jurisidction location
Outcome of this issue
/dropoffs
endpoint and saves the records to the dbaction items
get the latest schema from #data-science and create the
jurisdictions
model and table and generaate a model and migration for this tableget the latest csv dump from airtable having all the locations of scraped jurisdiction dropoffs; then use the script that @Henrymarks1 wrote in ./backend/seeders to read each record in the csv, query the TAMU geocoding service.
for each geocode we then call
/dropoffs
api with a request body having all information we need to saveResources/Instructions
sequelize docs on migrations https://sequelize.org/master/manual/migrations.html#creating-the-first-model--and-migration-