Difference between revisions of "Sample Design"

From Heureka Wiki
Jump to navigation Jump to search
Line 10: Line 10:
 
*'''Create inventory (2)'''
 
*'''Create inventory (2)'''
 
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]].
 
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]].
 +
 +
*'''Import data from mobile database (3)'''
 +
 +
 +
*'''View imported data (4)'''
 +
 +
 +
*'''Summary (5)'''
 +
 +
 +
*'''Export data and Import to forest database (6)'''
 +
 +
  
  

Revision as of 17:29, 2 September 2009

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.

*) 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".

Buttons (1-6)
  • Import sample stands and sample plots (1)

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.

  • Create inventory (2)

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.

  • Import data from mobile database (3)


  • View imported data (4)


  • Summary (5)


  • Export data and Import to forest database (6)



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.