Importing existing trees from a survey file

Survey file tree data can be imported into Vectorworks Landmark, and then used to automatically create existing trees with the proper attached information, including location. By mapping the attached data to the existing tree parameters and to record fields, valid existing tree objects are created in the file with all the survey data incorporated. After modification, data from an existing tree schedule can then be exported as a tree survey text file.

If desired, loci with attached record data can be created instead. The loci with the tree information can then be exported in shapefile format.

The Import Tree Survey dialog box opens. Specify how to import the tree survey data and how to map the data to the existing tree parameters in the Vectorworks file. The settings can be saved for future use.

Parameter	Description
Saved Settings Options	See Using saved sets to save and apply saved settings
Survey File Format	Specifies the File Type of the import file: ● Excel: .xls or .xlsx file; if the spreadsheet contains multiple sheets, the first sheet will be imported ● Tab delimited: File with tab delimiters between fields ● Other: File in any other format; also enter the Delimiter Character that separates the fields
Survey Data
Data Starts at Row Number	Indicates the row where the survey data starts listing the existing tree information (this allows extraneous information such as author, title, and so on to be ignored)
Data Has Column Headers	If the survey data contains a header row, select this option, and then do not count the header row when entering the row number where data starts. The header rows, if they exist, are listed for each row of the Survey Column in the Survey Mapping data; if they do not exist, the Survey Column rows are numbered sequentially.
Create Custom Record with Name	In addition to mapping the data to existing tree parameters, a record format can be created and attached to the existing tree or the 2D or 3D loci that are created. When creating existing trees, this is useful for retaining all survey data with the objects. When creating loci, this allows all data to be retained for each locus.
Survey Mapping table	Each row in the table corresponds to a column in the tree survey file
Survey Column	If the data has a column header row, the headers are listed in the Survey Column rows; otherwise, the rows are numbered sequentially
Parameter	For each row, indicates the existing tree parameter that the Survey Column item is mapped to
Unit	For each row, indicates the unit that will be used at import. ● If the imported row contains text or entries which do not need a unit, leave the default selection of None/Automatic. ● If data can be imported with the specified document units, this will occur automatically with the selection of None/Automatic. ● If the imported data requires units that are different from the document defaults, select the unit to use for importing the data.
Add to Record	If creating a custom record to be attached at import, a check mark in a row indicates that the data for that row should be included in the custom record
Selected Existing Tree Parameter	Indicates how the selected row data should be mapped to its equivalent parameter at import
Selected Unit	Indicates the units for the selected row at import
Import Options
Create Existing Tree Objects	Creates existing tree objects from the imported survey data
Create 2D Locus Objects	Creates 2D loci from the imported survey data (if the file is later exported as a shapefile, the loci within the shapefile are 2D loci). Only X/Y coordinates and any custom record information are imported when 2D loci are created. The remaining existing tree parameters are not included, even if they are mapped.
Create 3D Locus Objects	Creates 3D loci from the imported survey data (if the file is later exported as a shapefile, the loci within the shapefile are 3D loci). Only X/Y/Z coordinates and any custom record information are imported when 3D loci are created. The remaining existing tree parameters are not included even if they are mapped.

3.Select each row of the survey mapping table, and then specify how it should be mapped to the equivalent existing tree parameter by selecting it from the Selected Existing Tree Parameter. If necessary, select the specific units that should be used if they’re different from the document defaults. If the row data should be added to a custom record, place a check mark in the row.

When mapping to existing tree parameters, the associated data values are mapped directly when the type is compatible. For example, when the height parameters are mapped, the height value from the survey file becomes the Height value for the existing tree; a mapped Condition parameter is set as expected if the entry matches one of the default options (Excellent, Good, Average, Poor), or to Custom if the entry doesn’t match the defaults.

If no data are provided for mapped parameters, the default values of the Existing Tree tool are used.

There are some existing tree parameters for which there is no survey data equivalent; these parameters are also set to their defaults upon creation of the existing tree object.