The following files are designed to be run using the Path Landscape Model software, version 3.0.4. Later versions of the software cannot run these files. To get a copy of this software, please contact Apex RMS at path@apexrms.com. These files will open in the Path Landscape Model, version 3.0.4 or later. 1) In "Path Model" folder, path models MUST be run with the provided MCM mulitplier files to apply the required transition probability adjustments for procesess such as insect outbreaks, wildfire, and climate change trends. Each Path database is set up with three folders: - The 'Common' folder contains a single Path scenario (also named 'Common'). The Transitions tab within the Common scenario contains the climate-smart STM. - The 'Multipliers' folder contains multipliers specific to each ownership-allocation to activate or deactivate transitions (both climate change and management). Actual treatments are input in the Treatments tab for each stratum in the 'Runs' folder. - The 'Runs' folder contains one Path scenario per modeling stratum, with initial conditions specific to each stratum (combination of watershed and ownership-allocation). The models are stored as a dependency from the 'Common' folder and the multipliers as a dependency from the 'Multipliers' scenario. For the scenarios that have management activities (current and restoration management), a specified number of acres for each treatment is shown in the Treatments tab for treated stata. There are 6 databases, one for each combintation of management and climate scenario run in southwest Oregon. Climate scenarios include: - HadGEM global circulation model, representative concentration pathway 8.5 (Hadley) - NorESM global circulation model, representative concentration pathway 8.5 (NorESM) - MRI global circulation model, representative concentration pathway 8.5 (MRI) Management scenarios include: - Current Management - estimate extracted from LandTrendr dataset - Restoration management - a restoration scenario designed to help preserve owl habitat and diminish landscape susceptibility to catastrophic fire. 2) This "lookup tables" folder contains files necessary for providing definitions and context for the information located in other folders. 3) The 'Spatial' folder contains the SWO region stratum map, called Modeling_Strata.tif. This map can be joined to output from the climate-informed state-and-transition models to map projected future condition or northern spotted owl habitat, on the "Strata" field. Modeling strata consist of the intersection of watershed (Hydrologic unit code [HUC]) and ownership-allocation map. Watersheds are three digit codes starting at 101. Ownership-allocation categories are a two-character label, and are described in the attribute table through the fields "Ownership", and "Allocation". The field ScenarioID indicates the internal ID number used by the Path software to link results for modeling strata to its Scenario names. 4) The 'Results' folder contains summarized modeling results that can be viewed on their own, or displayed across mapped modeling strata. The .tif file within the 3Spatial folder shows the spatial distribution of modeling strata. There are 3 subfolders: ClassesSummary, TransitionSummary, and HabitatSummary. The csv files within ClassesSummary contain summaries of state class area (in Acres) for each timestep, over monte carlo repetitions, within each modeling stratum. Those within TransitionSummary are summarized in the same manner, but contain summaries of area affected by each Transition Type. The csv files within HabitatSummary are designed to be joined ot the grid mentioned above, to allow for a spatial depiction of habitat projections. There is one column per modeled year, containing a summary that indicates the proportion of each modeling stratum that is comprised of potential northern spotted owl habitat (averaged over monte carlo repetitions). Sample queries outlining how to build new summaries of output data for mapping from the ClassesSummary files and lookup tables are included in the database: SWO_Summaries.accdb