Import of stand register - Revision history

Osskyn at 10:21, 26 November 2024

2024-11-26T10:21:05Z

Osskyn at 10:19, 26 November 2024

2024-11-26T10:19:53Z

Jonare at 07:22, 4 December 2023

2023-12-04T07:22:09Z

Peder at 14:54, 5 November 2019

2019-11-05T14:54:16Z

Peder at 13:39, 7 November 2014

2014-11-07T13:39:04Z

Hah: /* Import templates */

2014-08-22T06:42:13Z

Import templates

Peder: /* Import templates */

2014-08-21T14:56:20Z

Import templates

Peder: /* File specification */

2014-08-21T14:47:18Z

File specification

Show changes

Peder: /* File specification */

2014-08-21T14:34:01Z

File specification

Peder: /* File specification */

2014-08-21T14:31:02Z

File specification

Show changes

@@ Line 6: / Line 6: @@
 ===Instructions===
 See {{HeurekaHelpLinkEng}}importera_bestandsregister.htm.
 ===File specification===

@@ Line 1: / Line 1: @@
-{{Languages|Import of stand register}}
+{{Languages|Import_of_stand_register}}
 [[Category:Database]]
 [[Category:Reference Manual]]

@@ Line 1: / Line 1: @@
-{{Languages}}
+{{Languages|Import of stand register}}
 [[Category:Database]]
 [[Category:Reference Manual]]

← Older revision		Revision as of 14:54, 5 November 2019
Line 5:		Line 5:

	===Instructions===		===Instructions===
−	See ~~http://heurekaslu.org/help/en/index.html?~~importera_bestandsregister.htm.	+	See {{HeurekaHelpLinkEng}}importera_bestandsregister.htm.

@@ Line 3: / Line 3: @@
 [[Category:Reference Manual]]
 [[Category:User's Guides]]
-''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.).''
+===Instructions===
 ===File specification===
 {{:StandRegisterFileSpecification}}
-==Link to existing area==
+<!--
 ==Simulating single tree-data==
 A stand register usually includes, in each stand, average values and totals for several variables. However, models applied in the simulations of growth, treatments, etc. need initial forest state descriptions at the single tree-level. If not obtained in a forest inventory, e.g. according to [[Ivent]], such data can be simulated. Other inventory methods, and other simulation techniques (e.g. sample plot imputation), are available. Remote sensing like airborne laser sensors may soon return (a sample of) single-tree data for large areas without great costs, but of great interest.
@@ Line 44: / Line 18: @@
 The shape parameter is of importance, including both the actual shape of the distribution and its scale. A scale parameter is known for "stretching/shrinking the width of the distribution". A stand register, unfortunately, seldom includes any information about the distribution of tree sizes. Any notes like "homogeneous" or "heterogeneous" should be taken into consideration. For the moment, this is done using the mandatory field "EvenAgedCode" in the stand register import. With a heterogeneous stand the user should here select "UnevenAged" to obtain a relatively wide diameter distribution, and vice versa. As you notice, this is not fully consistent - a stand with trees of same age might very well include both large and small trees (both dominating and supressed trees).

@@ Line 20: / Line 20: @@
 ===Import templates===
-Use the supplied template to create a correct import file for stand register import. The template is en Excel-file with a built-in macro that can be used to export the require file in csv-format. The template ("ImportTemlate_verX.xlsx) is available here:
+Use the supplied template to create a correct import file for stand register import. The template is an Excel-file with a built-in macro that can be used to export the required file(s) in .csv-format. The template ("ImportTemplate_verX.xlsx) is available here:
 [ftp://salix.slu.se/download/Heureka/ImportTemplates Import templates at SLU:s ftp-server]

@@ Line 29: / Line 29: @@
 ===File specification===
 '''Notes:'''
 *'''Column order is irrelevant''', the import function uses column names for matching. Optional columns can be be dropped, or left blank. '''It is important that the column names are correct.'''
@@ Line 38: / Line 39: @@
 *Columns denoted as "Required..." in the table below are required if single tree-data should be simulated (with a Weibull-distribution, see below).
-*Do not enter zeroes in cells unless the values should actually be zero. Leave the cells empty or remove columns for whicH you have no data.
+*Do not enter zeroes in cells unless the values should actually be zero. Leave the cells empty or remove columns for which you have no data.
 *If "Maturity Class" is used, make sure it is correctly depicted, e.g. no overstorey data are allowed to describe a stand classified as K. The class R2 should be used with precaution (if treatment programs including cleaning should be generated, use class R1).''