Difference between revisions of "Import of stand register"
Jump to navigation
Jump to search
| Line 443: | Line 443: | ||
An existing analysis area can be regarded as a forest holding, consisting of several forest estates. Each forest estate could have its own stand register, to be imported separately. Similar situations can occur, e.g., when a forest owner acquire additional forest land. Use the "Link to existing area..."-function, either at the same time as the stand register import or afterwards. Currently, there are two sub-levels available in an analysis area, fields called "AreaLevel2" and "AreaLevel3" in the stand register template. These can be regarded as ''Part of my forest holding located in the forested mountain areas'' and ''Part of my forest holding located elsewhere'', respectively. | An existing analysis area can be regarded as a forest holding, consisting of several forest estates. Each forest estate could have its own stand register, to be imported separately. Similar situations can occur, e.g., when a forest owner acquire additional forest land. Use the "Link to existing area..."-function, either at the same time as the stand register import or afterwards. Currently, there are two sub-levels available in an analysis area, fields called "AreaLevel2" and "AreaLevel3" in the stand register template. These can be regarded as ''Part of my forest holding located in the forested mountain areas'' and ''Part of my forest holding located elsewhere'', respectively. | ||
| − | Another situation is when supplementary information becomes available. Lets say that more stands should be added to already imported stands (belonging to the same area, e.g. due to an ongoing forest inventory). By linking, such completing of the stand register is no problem. Neither is there a problem if some stands have updated stand data (e.g., ) .. | + | Another situation is when supplementary information becomes available. Lets say that more stands should be added to already imported stands (belonging to the same area, e.g. due to an ongoing forest inventory). By linking, such completing of the stand register is no problem. Neither is there a problem if some stands have updated stand data (e.g., updated management classification). Linking and importing stands with identical identification (usually by the fields "MapId", "StandId", and "SubStandId") will replace these stands and leave all other stands of the area unaffected. |
| − | When linking new data to existing you need to specify a link, a valid "Attribute Key", found in the | + | When linking new data to existing you need to specify a link, a valid "Attribute Key", found in the combo box. Use fields from the stand register or user defined-constants. |
==Simulate single tree-data== | ==Simulate single tree-data== | ||