Difference between revisions of "Import of stand register"
Jump to navigation
Jump to search
| Line 445: | Line 445: | ||
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. | 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 combo box. Use fields from the stand register or user defined | + | 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 and/or user defined constants. |
==Simulate single tree-data== | ==Simulate single tree-data== | ||