...
The columns in the config CSV file are as follows:
table - the name of the table (spatial or attribute) in the Esri data model.
index - the order the field should be outputed in the exported file (1-n).
esriName - the name of the field in the Esri data model. Note that this should be the full Esri fieldname using correct case, underscores etc., not the field’s ‘alias’
exportName - the name of the field in the output Excel file.
defaultValue - a default value which will be written if the incoming field does not exist or there is no value on an incoming record.
dataType - one of TEXT,INT,DOUBLE indicating the data type. This field is optional, and is currently only used when exporting for TCruise. Use INT for integer or date fields, use double for decimal fields (floating point, double precision floating point) and TEXT for everything else.
The config file enables the following functionality:
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.
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;…).
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.
...