Page Comparison

...

• Excluding fields - if a field is present in the Esri data model which is not desired in the export (e.g., OBJECTID) it can be left out of the config file and will not be exported.

• Reordering fields - if fields in the config file are listed in a different order than in the Esri data model, they will be exported in the order of they are listed in the config file, not the order they occur in the data model.

• Renaming fields - the export field name is independent from the Esri field name, thus a field named ‘DBH’ can be exported as ‘diameter’.

• Adding fields - if a field is not present in the Esri data model, but is needed in the export file as an input to another process, it can be inserted in the desired field order in the export file.  If a default value is provided for that field, that value will be inserted for all output records.  An example might be the field ‘Measurement Year’, which could be included at the Stand level in the export configuration file with a default value set to the current year. In this scenario, the Stands tab in the exported Excel file would contain a column called ‘Measurement Year’ and each Stand record would contain the current year in that column, even though that field the Esri data model.

• Removing fields - if a field is in the Esri data model but you do not wish to include it in the export, simply omit the entire row from the export file.

Export Functions

To support specific data manipulation tasks during export, InventoryManager Export includes a small number of functions that can be run during the export to transform data into the desired format. These functions are listed below:

...

Auto-numbered fields - if the export file should have an auto-numbered field (e.g., unique plot numbers from 1 to n) this can be set using the name 'AUTOINCREMENT' as the Esri field name

...

Parent/Grandparent fields - if an export field is not available on the matching table, it can be copied in from the parent or grandparent table.  For example, if Stand ID is desired on the Trees tab of the export Excel file, but is not stored on each tree (not included in the Esri data model for Trees), it can be copied from the Plot or Stand table.  To do this, prefix the Esri field name with “STANDS.” or “PLOTS.”, depending on which layer should be used to lookup the desired value.

...

The table below lists the available functions. In each case, the function would be entered in the ‘esriName’ column of the export config to indicated that the source is a function rather than simply copying the value from an existing field in the ArcGIS data model.

...

Subtract one valu

...

Function

...

Description

...

Example

...

ADD

...

Adds the values of 2 fields together. If one or both fields are text then fields are concatenated

...

AUTOINCREMENT

...

Auto-numbers output rows

...

EXCLUDE

...

Exclude records based on some attribute value. Note, this has only been implemented for Trees so far.

...

EXCLUDE(Cut_Leave:Cut) - this example will exclude any trees for which the ‘Cut_Leave’ field contains a value of ‘Cut’

...

FVSGROUPS

...

Calculate the ‘Groups’ field in the ‘FVS_StandInit' table of the FVS SQLite database export. The groups value will always contain the phrase 'All_Stands’. Adding this function can include additional groups based on hard-coded values or the values of any field(s)

...

FVSGROUPS(variant=SN;Cover_Type={Cover_Type};) - this example would include the following groups:

• All_Stands

• variant

• Cover_Type

...

LOOKUP

...

Lookup values from list - if the export value should come from a list of allowed values, but that list does not match the Coded Value Domain list for that field, a custom lookup table can be provided in the config file.

...

LOOKUP(Cruise_Type:S=0;C=1) - this If the MobileMap Cruise_Type field on the Trees table (S=standard cruise, C=check cruise) needs to be cross-walked to the field RECTYP (used by TCruise), the following syntax can be used: LOOKUP(Cruise_Type:S=0;C=1).  This example will apply the custom ‘lookup’ function and use the value found in the Cruise_Type field, replacing all instances of ‘S' with the value 0, and all instances of 'C' with the value 1. Another example where we have seen this used is to translate between log lengths recorded in 1/2 logs (e.g., 0.5, 1, 1.5,…) to feet (e.g., 8, 16, 24,…) using the following LOOKUP(Length:0.5:8;1:16;1.5:24;…).

...

PLOTS

...

Lookup value from an existing or new field in the Plots layer

...

PLOT.Plot_Size - this example could populate a Strata field in an output Plots table with the Strata value of that Plot’s parent Stand.

...

STANDS

...

Lookup value from an existing or new field in the Stands layer

...

STANDS.Strata - this example could populate a Strata field in an output Plots table with the Strata value of that Plot’s parent Stand.

...

SUBTRACT

...

Subtract the values of 1 field from the value of another field.

...

SUBTRACT(Inventory_Year-Origin_Year) - this example could calculate a stand ‘Age’ field as the origin subtracted from the cruise year.

Stands To Export

...

In addition to the original selection of stands described above, the stands to be exported can be further constrained using the Stands to Export setting on the Inventory Export tab.

Choose the category of stands to be exported from the drop-down menu.

• Selected stand(s) - will export all of the stands that are currently selected in the map.

• Cruised stands - will only select those stands where the status field has been set to cruised (requires that the system has been properly configured to identify the status attribute field and the values that qualify as cruised (e.g., ‘Cruised’ and ‘Checked’)

• All cruised (not checked) stands - similar to above, but will omit stands that have been checked

• All checked stands - similar to above but includes only those stands that have been checked

• Stands updated on/after… - will apply a starting date constraint on the last_modified_date field in order to only export the most recent data. An example of this would be if you need to export only those stands that were updated in the last 2 weeks. When using this option the date field below must be set to a valid date.

Export Codes Or Descriptions

For attribute fields that use coded value domains, it is possible to export either the codes or their descriptions. For example, if the species field uses 2-letter species codes, selecting Export codes would export the code ‘DF’ for Douglas fir, while selecting Export descriptions would export ‘Douglas fir’. This is a global setting and thus will use either codes or descriptions for all fields for all tables. It is typical to use descriptions when performing ad hoc review as they may be easier to interpret when scanning for data quality issues. When exporting data for other forest information systems, however, it is often necessary to export the codes for compatibility.

...

Calculate Check Cruise Score

Check cruise score calculation can be performed during the Inventory Export process. Check cruise score calculation requires that a Check_Rules table is present in the data model and is populated with one or more check cruise score rules. These rules define the quality control tests that should be applied and the point deductions that should be calculated. Below are some example check cruise score rules, written in a human readable format:

• If species is incorrect, deduct 5 points

• If the total height is off by more than 15%, deduct 3 points

• If plot was not properly flagged, deduct 2 points

When check cruise score calculation is applied, the general logic is as follows:

• Score calculations occur at the tree and plot levels

• Tree level calculations are performed first

• For each tree, the sum of its deductions is recorded, along with a comma separated list of tree rules that were violated

• Tree deductions for all trees on a plot are summed together as one component of the plot deductions

• Additional plot deductions are applied if plot level check score rules are violated

• The final set of plot deductions (plot level + sum of tree level) and subtracted from 100 to achieve a plot score

• For each plot, the plot score is recorded, along with a comma separated list of tree and plot rules that were violated

• The plot level score is written back to the Plots table to the fields ‘Check_Score’ and ‘Check_Details’ (these fields must be included in the Plots table for this functionality

To enable check cruise score calculating during export, check the Calculate check cruise score checkbox prior to clicking Export. When the export completes, if data were successfully written back to the Plots table a notification window will display the results of this process.

...

FVS Export

The Forest Vegetation Simulator (FVS) is a free software application developed by the US Forest Service. It is commonly used by foresters to perform growth and yield modeling, but can also be used to model wildfire fuel or carbon. The most recent releases of FVS use a web-based interface, rather than the older desktop Suppose application, and imports data via a SQLite database file.

Inventory Export supports export of data for FVS by writing out an FVS compatible SQLite database file. In order for to produce a valid FVS export, however, it is critical to use an export configuration file that maps between the Esri data model fields and the FVS expected fields. Successful creation of an export configuration file for FVS requires knowledge of FVS inputs and your Esri data model. To help support the creation of export configuration files, MB&G can provide example files that have been used by others for FVS data export.

Stands To Export

...

In addition to the original selection of stands described above, the stands to be exported can be further constrained using the Stands to Export setting on the Inventory Export tab.

Choose the category of stands to be exported from the drop-down menu.

• Selected stand(s) - will export all of the stands that are currently selected in the map.

• Cruised stands - will only select those stands where the status field has been set to cruised (requires that the system has been properly configured to identify the status attribute field and the values that qualify as cruised (e.g., ‘Cruised’ and ‘Checked’)

• All cruised (not checked) stands - similar to above, but will omit stands that have been checked

• All checked stands - similar to above but includes only those stands that have been checked

• Stands updated on/after… - will apply a starting date constraint on the last_modified_date field in order to only export the most recent data. An example of this would be if you need to export only those stands that were updated in the last 2 weeks. When using this option the date field below must be set to a valid date.

Export Codes Or Descriptions

For attribute fields that use coded value domains, it is possible to export either the codes or their descriptions. For example, if the species field uses 2-letter species codes, selecting Export codes would export the code ‘DF’ for Douglas fir, while selecting Export descriptions would export ‘Douglas fir’. This is a global setting and thus will use either codes or descriptions for all fields for all tables. It is typical to use descriptions when performing ad hoc review as they may be easier to interpret when scanning for data quality issues. When exporting data for other forest information systems, however, it is often necessary to export the codes for compatibility.

...

Calculate Check Cruise Score

Check cruise score calculation can be performed during the Inventory Export process. Check cruise score calculation requires that a Check_Rules table is present in the data model and is populated with one or more check cruise score rules. These rules define the quality control tests that should be applied and the point deductions that should be calculated. Below are some example check cruise score rules, written in a human readable format:

• If species is incorrect, deduct 5 points

• If the total height is off by more than 15%, deduct 3 points

• If plot was not properly flagged, deduct 2 points

When check cruise score calculation is applied, the general logic is as follows:

• Score calculations occur at the tree and plot levels

• Tree level calculations are performed first

• For each tree, the sum of its deductions is recorded, along with a comma separated list of tree rules that were violated

• Tree deductions for all trees on a plot are summed together as one component of the plot deductions

• Additional plot deductions are applied if plot level check score rules are violated

• The final set of plot deductions (plot level + sum of tree level) and subtracted from 100 to achieve a plot score

• For each plot, the plot score is recorded, along with a comma separated list of tree and plot rules that were violated

• The plot level score is written back to the Plots table to the fields ‘Check_Score’ and ‘Check_Details’ (these fields must be included in the Plots table for this functionality

To enable check cruise score calculating during export, check the Calculate check cruise score checkbox prior to clicking Export. When the export completes, if data were successfully written back to the Plots table a notification window will display the results of this process.

...

FVS Export

The Forest Vegetation Simulator (FVS) is a free software application developed by the US Forest Service. It is commonly used by foresters to perform growth and yield modeling, but can also be used to model wildfire fuel or carbon. The most recent releases of FVS use a web-based interface, rather than the older desktop Suppose application, and imports data via a SQLite database file.

Inventory Export supports export of data for FVS by writing out an FVS compatible SQLite database file. In order for to produce a valid FVS export, however, it is critical to use an export configuration file that maps between the Esri data model fields and the FVS expected fields. Successful creation of an export configuration file for FVS requires knowledge of FVS inputs and your Esri data model. To help support the creation of export configuration files, MB&G can provide example files that have been used by others for FVS data export.

When exporting data for FVS, use the appropriate export configuration file and check the box labeled Export for FVS (*.db).

This will produce a SQLite database suitable for use in the new version of FVS. The basic workflow for using this file within FVS is outlined below:

1. Open FVS (web-based version, not Suppose. Application will open in browser using 'loopback' URL 127.0.0.1)

2. Import Data Tab (upper left)

   1. Browse for file

   2. Install uploaded database

3. Runs Tab (upper left)

   1. Click ‘New’ button

   2. On ‘Groups’ tab, select ‘All_Stands’ item from list, then click ‘Add stands in selected groups’ button below lists

4. Time Tab (mid right)

   1. Select start, stop and interval

5. Select Outputs Tab

   1. Check boxes for ‘Tree Lists’ and ‘Inventory Statistics’ (and others for which you have input data, e.g., carbon, fuels, etc.)

6. *Run* Tab

   1. Click ‘Save and Run’

7. Review output chart

   1. Review units & values

   2. Modify data, settings, etc. as needed

...

Example results in FVS for 5 Southern Loblolly Pine stands exported from InventoryManager using the Export for FVS option.

TCruise Export

Similar to FVS Export, InventoryManager can export for use in TCruise Pro desktop compilation software. It is necessary for TCruise Export to be enabled in InventoryManager, and for a TCruise ‘Template’ (*.tct) file to be stored in InventoryManager. Once these have been implemented, an export configuration file can be used to provide the appropriate information for populating a TCruise-compatible SQLite database file which includes the following tables: Tract, Strata, Plots, Trees.

The image below shows an example TCruise-compatible export configuration file:

...

When exporting data for FVS, use the appropriate export configuration file and check the box labeled Export for FVS (*.db).

This will produce a SQLite database suitable for use in the new version of FVS. The basic workflow for using this file within FVS is outlined below:

1. Open FVS (web-based version, not Suppose. Application will open in browser using 'loopback' URL 127.0.0.1)

2. Import Data Tab (upper left)

   1. Browse for file

   2. Install uploaded database

3. Runs Tab (upper left)

   1. Click ‘New’ button

   2. On ‘Groups’ tab, select ‘All_Stands’ item from list, then click ‘Add stands in selected groups’ button below lists

4. Time Tab (mid right)

   1. Select start, stop and interval

5. Select Outputs Tab

   1. Check boxes for ‘Tree Lists’ and ‘Inventory Statistics’ (and others for which you have input data, e.g., carbon, fuels, etc.)

6. *Run* Tab

   1. Click ‘Save and Run’

7. Review output chart

   1. Review units & values

   2. Modify data, settings, etc. as needed

...

Example results in FVS for 5 Southern Loblolly Pine stands exported from InventoryManager using the Export for FVS option.

TCruise Export

Similar to FVS Export, InventoryManager can export for use in TCruise Pro desktop compilation software. It is necessary for TCruise Export to be enabled in InventoryManager, and for a TCruise ‘Template’ (*.tct) file to be stored in InventoryManager. Once these have been implemented, an export configuration file can be used to provide the appropriate information for populating a TCruise-compatible SQLite database file which includes the following tables: Tract, Strata, Plots, Trees.

The standard TCruise export uses the Stand_ID field as the STRATUMID that is stored in the Strata and Plots table of the export SQLite file. This results in 1 strata per Stand. To export a stratified cruise, in which stands are grouped into strata for analysis in TCruise, the ‘esriName’ for the output STRATUMID should be a fieldname that will have the same value for all Stands in a given strata. For example, if Stands have a Stand_ID and a Stratum_ID field and you want to perform a Stand-level analysis in TCruise, then the ‘esriName’ for the STRATUMID would be ‘Stand_ID’. For a stratified cruise, the ‘esriName’ for the Stand-level STRATUMID field would be ‘Stratum_ID' while the ‘esriName’ for the Plot-level STRATUMID field would be 'STANDS.Stratum_ID’ indicating that the plots STRATUMID should be populated by the Stratum_ID field found in the parent Stand.