Closed fungjj92 closed 5 years ago
There also seems to be a CI failure.
Thanks for the QC! I relayed the WV data question to @dboyer and cleared out "pesticide" labelled files in the staging bucket.
There's always a CI failure unless the workspace is cleared out before running a job. Just reran with a cleared workspace, and the build is green.
I'm going to wait to merge this until WV followup but meanwhile make a followup card about production deployment with notes on clearing out the scores
column of the apiary
table and copying over data from the staging to production s3 bucket.
WV was confirmed by the client to have mostly 0 values. WV is apparently very forested. Go WV?!
Overview
The client provided raster data for 5 new states, and updated PA, IL, and IN data too. This PR updates the VRT generation script. Also, I unified the code around the indicator label 'insecticide' formerly 'pesticide'. We had an in-between hybrid solution before to avoid renaming & regenerating data.
Connects #522
Demo
Data completes a full corridor between NY and MI :D
Data coming in from all included states, screenshot from my local instance
Staging:
Notes
I updated data in the staging data bucket in s3; staging will not return insecticide data until its code is updated to accomodate
insecticide
. Production will be a bit tricky. Either we upload the new VRTs and layers before the updated code is deployed, or after -- in both cases we'll get no data for the insecticide field for a few minutes. I don't think this is ultimately a huge deal, so long as we flush saved apiary indicator data after all the updates are made to ensure fresh, complete data is shown to users.Testing Instructions
Pull down this branch and you should get data for all 8 included states when clicking the map.