How do we store / link to InVEST model results?

natcap / urban-online-workflow

This repository hosts the beta implementation of the Urban Online ES Workflow. The project is intended to give urban planners the ability to create and assess scenarios using InVEST Urban models.

1 stars 5 forks source link

How do we store / link to InVEST model results? #70

Closed dcdenu4 closed 1 year ago

dcdenu4 commented 1 year ago

When working on InVEST endpoint API #62 it's not yet clear what the worker should return to the api endpoint and what should be tracked in the db.

Is it the location to a unique Google Bucket tag? Is it a path to specific output files? Should we have InVEST model tables in the db with columns representing outputs?

dcdenu4 commented 1 year ago

Currently the workflow for is:

Frontend passes Scenario to endpoints API to queue InVEST runs
Worker runs InVEST models on a given Scenario
Worker does some post processing of those InVEST model results
Worker saves results as JSON file alongside InVEST model outputs
Worker relays the path to JSON back to the endpoints API

Then the endpoint API needs to store those results for the frontend. Possible solution:

Update jobs per usual
Update InvestResults table with JSON path for each InVEST model column
When frontend requests results, read JSON from paths and return JSON objects for each model

dcdenu4 commented 1 year ago

I think we have a handle on this for the moment, with the data we are choosing to provide users from InVEST runs. Currently the backend is doing some post processing and saving the results we're interested in.

We might want to have the ability to download InVEST results in the future or display change maps from certain raster outputs, but those can be specific issues if they come up.