From 147260792914c29175c497f27a711dbb313e829b Mon Sep 17 00:00:00 2001 From: newtpatrol <61762912+newtpatrol@users.noreply.github.com> Date: Mon, 20 Nov 2023 08:35:02 -0800 Subject: [PATCH] elaborate on threat raster path definitions --- source/en/habitat_quality.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/en/habitat_quality.rst b/source/en/habitat_quality.rst index 8e70eac1..64a3df2b 100644 --- a/source/en/habitat_quality.rst +++ b/source/en/habitat_quality.rst @@ -160,6 +160,8 @@ Data Needs If possible, the baseline map should refer to a time when intensive management of the land was relatively rare. For example, a map of LULC in 1851 in the Willamette Valley of Oregon, USA, captures the LULC pattern on the landscape before it was severely modified by massive agricultural production. Granted, this landscape had been modified by American Indian land clearing practices such as controlled fires as well. - :investspec:`habitat_quality threats_table_path` + +.. note:: The file system locations for *cur_path*, *base_path* and *fut_path* are relative to the location of the **Threats Table**. For example, if *cur_path* is "threat1.tif", that means that "threat.tif" is located in the same folder as the **Threats Table**. If *cur_path* is "threat_folder/threat1.tif", that means that there is a folder "threat_folder" in the same location as the **Threats Table**, and "threat1.tif" is located inside "threat_folder". You may also provide absolute paths, such as "C:/HabitatQuality/threat_folder/threat1.tif". Columns: