...
The table below shows an example of a simple import configuration file for importing Tree-level (no Logs) data produced from a TCruise SQLite Export file using the processed described in the next section:
table | index | esriName | exportName |
Stands | 1 | Stand_ID | Stand_ID |
Stands | 2 | Status | Status |
Plots | 1 | Stand_ID | Stand_ID |
Plots | 2 | Plot_ID | Plot_ID |
Plots | 3 | Status | Status |
Trees | 1 | Stand_ID | Stand_ID |
Trees | 2 | Plot_ID | Plot_ID |
Trees | 3 | Tree_ID | Tree_ID |
Trees | 4 | Species | Species |
Trees | 5 | Tally | Tally |
Trees | 6 | DBH | DBH |
Trees | 7 | Height_to_Record_Top_Diameter | Height_to_Record_Top_Diameter |
Trees | 8 | Product_Number | Product_Number |
Trees | 9 | Reproduction | Reproduction |
Trees | 10 | Saw_Stopper | Saw_Stopper |
Trees | 11 | Pulp_Stopper | Pulp_Stopper |
Data Files - General
Data files for the 'Import CSV' tool are single tables that contain all of the attribute information that will be imported for the Stands, Plots, Trees and Logs. They are non-normalized data, meaning that there will be redundant data at the higher levels (e.g., Stands and Plots). If logs are included in the import, the data file will have 1 row for each log, and thus each tree will be repeated multiple times - once for each log in that tree. If logs are not included, the data file will have 1 row for each tree, and thus each plot will be repeated multiple times, once for each tree in that plot.
...
Note that the Process button will be disabled after it is clicked to prevent the accidental re-run of that step. This is especially important with the Trees and Logs levels as it could result in the creation of duplicate data.
There is an alternate option to import only trees. This requires the following:
A stand or plot(s) must be selected
All incoming tree data must have plot IDs to associate trees to their parent plots.
To only import trees:
Select ‘Import CSV’ tab
Select import configuration CSV file
Use dot notation in the Plots configuration rows and Tree configuration rows to build relationships from Tree data to its parent plot and stand. The following is a simple example of the first 5 rows of a configuration file which will do this successfully:
Stands,1,Stand_ID,Stand_ID,,Plots,1,Stands.Stand_ID,Stand_ID,,Plots,1,Plot_ID,Plot_ID,,Trees,1,Stands.Stand_ID,Stand_ID,,Trees,2,Plots.Plot_ID,Plot_ID,,
Select the data file with tree CSV data formatted as described in the above sections.
In the Trees row: select Import into map selection
Ignore Stands and Plots rows
...
Import Scenarios
The process described above assumes that the user intends to recreate the Stand, Plot, Tree and optionally Log data exactly as they exist in another system. There are other scenarios were this is not needed. When historical or simulated data are being loaded for verification and testing, it may not always be necessary to recreate the exact geometry of Stands or Plots. Consider the following 2 scenarios:
...