Inventory design - Revision history

Peder at 12:20, 12 February 2010

2010-02-12T12:20:47Z

Peder at 15:42, 29 December 2009

2009-12-29T15:42:36Z

Hah at 12:33, 11 November 2009

2009-11-11T12:33:25Z

Peder: Inventory design moved to Sample Design: Nytt namn i systemet

2009-10-28T13:10:22Z

Inventory design moved to Sample Design: Nytt namn i systemet

New page

#REDIRECT [[Sample Design]]

@@ Line 2: / Line 2: @@
 [[Category:PlanStart]]
 [[Category:Database]]
 After a sample has been designed, also an inventory (database) needs to be designed before the actual field inventory. Both the export of a database to the data collector and the import of in-field collected data is handled from here. The inventory is always linked to an analysis area*, and usually to a sample of the stands in this area (possibly in different domains). This if the "stratification" of the imported stand register was successful.

← Older revision		Revision as of 15:42, 29 December 2009
Line 1:		Line 1:
		+	[[Category:User's Guides\|PlanStart\|PlanStart]]
		+	[[Category:PlanStart]]
		+	[[Category:Database]]
		+
	After a sample has been designed, also an inventory (database) needs to be designed before the actual field inventory. Both the export of a database to the data collector and the import of in-field collected data is handled from here. The inventory is always linked to an analysis area*, and usually to a sample of the stands in this area (possibly in different domains). This if the "stratification" of the imported stand register was successful.		After a sample has been designed, also an inventory (database) needs to be designed before the actual field inventory. Both the export of a database to the data collector and the import of in-field collected data is handled from here. The inventory is always linked to an analysis area*, and usually to a sample of the stands in this area (possibly in different domains). This if the "stratification" of the imported stand register was successful.

← Older revision		Revision as of 12:33, 11 November 2009
Line 1:		Line 1:
−	~~#REDIRECT~~ [[~~Sample Design~~]]	+	After a sample has been designed, also an inventory (database) needs to be designed before the actual field inventory. Both the export of a database to the data collector and the import of in-field collected data is handled from here. The inventory is always linked to an analysis area*, and usually to a sample of the stands in this area (possibly in different domains). This if the "stratification" of the imported stand register was successful.
		+
		+	''<sup>*)</sup> Not necessarily linked to a geo-referenced area (i.e. a forest map), though such is usually available and already imported. Theoretical sample plot-centre coordinates (x- and y-values) are expected to be derived externally, more about this below and in "Sample design".''
		+
		+	*'''Inventory Design'''
		+	:'''New Inventory...'''
		+
		+	:'''Export For Plot Positioning...'''
		+
		+	:'''Setup...'''
		+
		+	:'''Edit...'''
		+
		+	:'''Delete''' will delete the selected inventory.
		+
		+	Data from the predeeding sample design is here selected, including the sample stands (a.k.a. the Treatment Units) and the corresponding sample plots (a.k.a. the Reference Units). In the "Auto"-tab, select the sample design of interest and press the "Generate plots..."-button. The two other tabs are used in exporting the sample stands and importing the sample plots respectively, in formatted text files. This to enable external derivations of theoretical coordinates in any GIS.
		+
		+	Actually, the inventory is predefined in a number of tables (found in the "Table"-droplist). Most of the variables to be estimated/measured in field are mandatory, shown as shaded rows, only a few are voluntary and hence possible to exclude. However, it is possible to define new variables (by the "Add item"-button), just make sure they are added to correct tables (following the logical order to be estimated in field). Finish this part by "Create inventory database". A mobile, compact SQL database (.sdf-file) is either saved to the computer or directly to a connected data collector. The field data collectors are assumed to be equipped with Windows Mobile as OS and SQL Server Compact Edition. The field inventory is described in [[User's guide to Ivent]].
		+
		+	*'''Mobile Device Synchronization'''
		+	:'''Export...'''
		+
		+	:'''Import...'''
		+
		+	Collected data can continuously be imported as the inventory proceeds. This meaning the system recognize new, in-field collected data and add this to the temporary inventory database (and not the forest database). Only data with a matching sample design available can be imported.
		+
		+	*'''Inventory Results'''
		+	:'''View Inventory Summary...'''
		+
		+	:'''Edit Field Data...'''
		+
		+	:'''Export Tree Data...'''
		+
		+	Measurements and estimates made in the field can be pre-viewed, selecting a sample stand and corresponding sample plot. Depending on the setup (variables selected in "Create inventory") different data and values are shown. One can always, at the sample plot-level, regard site data, dead tree data, plant data (i.e. main- and bi-seedlings or saplings), and tree data (calliper- and sample-trees, respectively). If trees have been positioned it is possible to view a plot (in 2D) of these.
		+
		+	Once all sample plot data of a certain sample stand have been imported it can be summarized and viewed. In the first tab, "Average values", the stand is shown and described by both totals and average values. Following tabs show the calibration of tree heights and volumes made at the stand-, the stratum-, and the analysis area-level (or the domain-level).
		+
		+	*'''Analysis Area'''
		+	:'''Save As Analysis Area...'''
		+
		+	Data is checked for errors, corrected if neccessary, and when the inventory of plots and stands is completed, set as "Checked". Data is finally transferred from the inventory database to the forest database, ready to be analyzed with [[PlanWise]].