Difference between revisions of "Import of stand register"
Jump to navigation
Jump to search
(→test) |
|||
| Line 6: | Line 6: | ||
''NB: If other information, not covered by the specified variables, is available and of interest in the analyses (or in the inventory setup) such should be imported here, using the fields "UserDefinedVariable1-10". For example, interesting information could have been derived in preceding GIS-analyses (of stands coinciding with high nature value-areas, etc.).'' | ''NB: If other information, not covered by the specified variables, is available and of interest in the analyses (or in the inventory setup) such should be imported here, using the fields "UserDefinedVariable1-10". For example, interesting information could have been derived in preceding GIS-analyses (of stands coinciding with high nature value-areas, etc.).'' | ||
| − | = | + | ===Instruction=== |
| + | #Open an exisiting project or [[Create_a_new_Project | create a new one]] | ||
| + | #From the top menu, select "External Data" > "Stand Register" > "Import Stand Register" | ||
| + | #Click the "Browse"-button and locate and select the csv-file to be imported (see below) | ||
| + | #In the Description-field, name the stand register. If you will simulate tree data based on the stand register, the description field will be used as the name of the analysis area (the root node) | ||
| + | #In some cases the stand register import may be done after you have imported forest data, for example if you have [[Import_of_FMPP_data | imported FMPP-data]]. You may want to this to supply complimentary data, for example to use when setting up Forest Domains. You can link the stand register to an existing analysis area by checking "Link to existing area". You can construct a matching attribut key by combining several columns in the stand register. The values in the textbox "Preview Attribute Key" should match those in the textbox "Preview Treatment Unit Descriptions". | ||
===Encoding=== | ===Encoding=== | ||