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.

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.

• 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.  For example, 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;…).

• Subtract one valu

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.

...

• Score calculations occur at the tree and plot levels

• Tree level calculations are performed first

• For each tree, the sum of its deductions isrecordedis 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

...

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 knowlege 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).

...

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:

For a stratified cruise