Data required (biophysical table) to run INVEST SDR

Good day everyone,

I would like to know which data (in biophysical table) are required to run Invest SDR 3.8.9,
in SDR guide I found:
Biophysical table (required). A .csv (Comma Separated Value) table containing model information corresponding to each of the land use classes in the LULC raster. All LULC classes in the LULC raster MUST have corresponding values in this table. Each row is a land use/land cover class and columns must be named and defined as follows:

  • lucode : Unique integer for each LULC class (e.g., 1 for forest, 3 for grassland, etc.) Every value in the LULC map MUST have a corresponding lucode value in the biophysical table.
  • usle_c : Cover-management factor for the USLE, a floating point value between 0 and 1.
  • usle_p : Support practice factor for the USLE, a floating point value between 0 and 1.

Anyhow, i’ve tried to run a biophysical with only this data needs and the software didn’t run.

I’ve looked for a data base and found biophysical_table_Gura which have the following data:


However, these datas are also applied to nutrient model (NDR)

So, my question is:

Which data are required in SDR besides (description, lucode, usle_c, usle_p…) ?

Cheers and happy holidays to all of u.

(here is my log file)

InVEST-Sediment-Delivery-Ratio-Model-(SDR)-log-2020-12-10–15_44_45.txt (12.4 KB)

Hi @MuriloArima -

Only lucode, usle_c and usle_p are required to run SDR. In the sample data, the other columns are parameters required by other freshwater models. Often, when we’re running multiple models, we combine their landcover parameters into one table so it’s easier to manage.

The error you’re getting is a new one to me! And I don’t think is related to the biophysical table. Any ideas from the software team?

~ Stacie

1 Like

Hi @MuriloArima, that error is coming from Taskgraph, an underlying python library that manages some of the model’s subroutines behind the scenes. The very easiest thing to try could be running the model with a new workspace - if your workspace had prior model outputs in it already – especially outputs from a different version of invest – that could be a source of the problem.

Even better: I see you’re running invest 3.8.0 - there have been many bugfixes since then, both for invest and for Taskgraph. We are very soon to release 3.9.0, would you mind trying a pre-release of that version:

Thanks for your great support.