Sample Design

From Heureka Wiki
Revision as of 14:06, 13 May 2009 by Hah (talk | contribs)
Jump to navigation Jump to search

The inventory is always linked to an analysis area*, and usually to a sample of the stands in this area. This if the stratification of the imported stand register was successful. Data from the stratification is here selected, first the sample stands (a.k.a. the Treatment Units), then the corresponding sample plots (a.k.a. the Reference Units).

*) Not necessarily linked to a geo-referenced area (i.e. a forest map), though such is usually available (already imported). Theoretical plot-centre coordinates (x- and y-values) are expected to be derived externally, see "Stratification".

  • Create the actual inventory

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, only a few are voluntary and hence possible to exclude. However, it is possible to define "new" variables, 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".

  • Create the mobile database

The mobile database, created from the inventory database, is exported to and imported in the field data collectors, assumed to be equipped with Windows Mobile as OS and SQL Server Compact Edition. The field inventory is described in IVent. Collected data can continuously be imported as the inventory proceeds.

  • Export - import in the forest database

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.