Converting the Aspatial Model to the Forest Model

Now that we have finished building the spatial foundation of the Patchworks model, it is time to link the stand dynamics information to each block. We will want to know the growth and yield, natural succession, and response to treatment for each of the blocks we have just created. This is where the Forest Model comes in (see the section called “XML Forest Models”).

The Forest Model XML is the Patchworks language for expressing stand dynamics and silvicultural options. It is fully generalized and expresses a wide range of management possibilities. XML language is not very user friendly and usually we translate growth and yield and stand dynamics information from an aspatial model. The conversion tools can translate FSSIM, SFMM, Sylva-II and Woodstock aspatial files into Forest Model XML. This process automatically converts the growth and yield, silviculture, habitat and succession information you have already defined into a flexible XML format.

The sample dataset uses the stand dynamic information from a Woodstock aspatial model. We will use the Woodstock-XML conversion tool to translate this information into the Patchworks Forest Model XML. For more information about the Woodstock translator, and how woodstock modelling differs from Patchworks, see Woodstock Model Conversion.

[Note]Note
  1. Select "Woodstock-XML" from the Application Launcher within the Data Prep folder and click on "Go".

  2. At the first dialog box, click "Next".

  3. Use the defaults of current year as start year and a planning period equal to 5 years for the planning horizon information.

Figure 162. Woodstock conversion - planning horizon


[Note]Note
  1. As Patchworks can only assign one post harvest response for each block, we have a choice of two ways of handling this. The simplest is to assign the first possibility to the block.

Figure 163. Woodstock conversion - Response to treatment


[Note]Note
  1. We will use the mid point of the period to calculate yield curve values.

Figure 164. Woodstock conversion - Yield curve adjustment


[Note]Note
  1. Supply the input file and a filename and location for the resulting XML file.

    Woodstock input file: QuickTourIII/woodstock/C5_Feb02.pri

    XML output file: QuickTourIII/tracks/C5.xml

[Note]Note
  1. The default yield curve names are:

Figure 165. Woodstock conversion - Default curve names


[Note]Note
  1. Rename the yield curves to more meaningful names by double clicking in the rename field. Descriptors like yield and seral stage will be more helpful within the model. See the figure below.

    • Conif = %f.Yield.%m.Conif

    • Decid = %f.Yield.%m.Decid

    • Visual.disturb = %f.Visual.disturb

    • mature = %f.Seral.mature

    • old = %f.Seral.old

    • regen = %f.Seral.regen

    • young = %f.Seral.young

[Tip]Tip

The Forest Model XML has helpful attribute naming conventions that work well with other Patchworks data structures. The %f and %m will be automatically substituted by the Matrix Builder to create both features and products (%f), as well as managed and unmanaged (%m) attributes.

To learn more about the Forest Model language and attribute naming conventions read on to the section called “XML Forest Models”.

Figure 166. Woodstock conversion - Final curve names


[Note]Note
  1. THEME5 in the Woodstock file represents the area of each forest unit. If we would like to track this attribute, we need to include it in the xml file. information in this example. We will rename the Theme5 attribute %f.Area.%m. so that we will know for sure it represents area. Uncheck all the other themes except for THEME5.

Figure 167. Woodstock conversion - Theme area attributes


[Note]Note
  1. We have finished inputting all the necessary information. Click on "Finish" to convert the files. When the conversion is complete, your C5.xml file will be generated and can be found in the Systems\Patchworks\QuickTourIII\tracks folder

[Tip]Tip

For more information on the Forest Model see the section called “XML Forest Models”