search

Grasslands-2 / GrazeScape

The Django implementation of GrazeScape
1 stars 0 forks source link

Implement permanent storage solution for mapped model outputs(pngs) #196

Open zhassler opened 2 years ago

zhassler commented 2 years ago

Currently model outputs are stored locally, and can not be referenced between sessions in the app. Store the model result PNGs outside of the containers, and have the app reference them at their remote location. Update them when new models are run, and delete them when the associated fields are deleted via manual deletion, or from the farm or scenario being deleted.

Google cloud might provide a solid solution for this. research how their overwriting files, and remote requests work. Also keep in mind any cost increases.

zhassler commented 2 years ago

I was able to set up a google clould storage bucket to upload raster results to, download them for new model runs, and delete them if a field is deleted. Further testing is needed to be done, and the rest of the raster outputs need to be put in place, but the basic infrastructure for storing model result rasters outside of the container is in place.

zhassler commented 2 years ago

Added a time stamp to png outputs based on universal time. This is causing issues with google cloud upload functions being able to find the new pngs and upload them. Looking into this with just ploss. Once I have this working again, as well as the remove old pngs from the container I will copy my work for erosion and yield.