Import > Batch import Turboveg2 databases

In case multiple Turboveg2 databases need to be imported a batch procedure can be used to ease the process. The required information for the import of each databases need to be stored in an Excel file. The first row should have the headings as indicated below. The order of headers is not important, the names however, should exactly match as indicated. From row two on all the information of the databases to be imported is included.

The name of the sheet should be identical to the name of the Turboveg3 database in which the Turboveg2 databases need to be imported.

In the folder <Installation folder>\AutoImport and example file can be found.

Headings

•Import: Indicated with 'x' if the Turboveg2 databases concerned should be imported. The database will be ignored if the cell is empty.

•DataPath: The base folder to the Turboveg2 'Data', 'Species' and 'Popup' folder.

•DbGroup: The name of dataset group in the Turboveg3 database to which the dataset needs to be assigned.

•DbName: The name of the Turboveg2 database.

•SpeciesList: The name of the species list connected to the Turboveg2 database.

•PopupList: The name of the dictionary (set of lookup tables) connected to the Turboveg2 database. Leave empty if the default dictionary is used.

•Georef: Indicated how the vegetation plots are georeferenced. Enter 'DecimalDegrees' if longitude and latitude are stored in decimal degrees in the Turboveg2 database. [For other formats information will follow].

•CustodianID: Enter the numerical ID of the custodian provided that the name is already stored in the custodian list in the Turboveg3 database. The list should be updated in the Turboveg3 database prior to the import. See Manage custodians.

•DeputyCustodianID: Enter the numerical id if the deputy custodian. This requires that the name is already stored in the custodian list in the Turboveg3 database. The list should be updated in the Turboveg3 database prior to the import. See Manage custodians.

•GIVD-Code: Enter the GIVD-code here if the Turboveg2 database concerned is registered in the Global Index of Vegetation-Plot Databases.

•CodePage: Do not enter a code page number here if the Turboveg databases are managed on your own computers.

•MissingValue: Enter a number here, if a certain value is used to indicated missing values in the header data table of a Turboveg2 database. E.g. -9 or -9999.

•OemTranslate: Leave empty if an OEM to ANSI conversion of strings is not required, otherwise put 'x' in the cell. This option needs trial and error in case special characters like 'š' do not appear properly in the Turboveg database.