Field Data Sample Clauses

Field Data. A primary goal of the field data collection, was to locate the 130 field plots across the full range of riparian forest types in the Mashel watershed. These plots were then measured for the various riparian forest metrics under investigation and either used to build the models, assess the accuracy of the models or both. The watershed was pre-stratified into bins, and eight to 14 plot locations were randomly chosen for each bin from potential areas of the watershed in that bin, this binning process is described more in-depth in Appendix B. Certain bins made up a higher proportion of the watershed, so these bins were assigned more plots. Thus, very large trees, which are rare on the landscape, had fewer bins and thus fewer plots. There are also fewer of these trees in our models and the residuals associated with these heights of these trees are larger, thus the errors in height estimates for these taller trees will also be slightly greater. This is a common issue with LiDAR data, especially since we don’t expect the LIDAR pulse to hit the or even register a return off the most top leader of the tree. For more detailed information, see Appendix B - Plot Location Selection. The field data collection is described briefly in Appendix C and a full field data collection Protocol is provided as a separate publication (Xxxxxx X. X., 2016). 1. Xxxxxx, X. X., X. Xxxxx and T. Axe, 2016.

Field Data i. Data collected as points and break lines to define a proper DTM if requested outside of aerial mapping. ii. Includes utilities collected on surface as required. iii. Includes Horizontal control points from ROS 14492 used to define the Basis of Bearings and Vertical control Benchmark(s) to establish elevation. iv. Includes record monument points. v. Data collector project files. vi. Raw (unedited) data file.

Field Data. ‌ The field data were supplied by HS-ORKA and ISOR in frequent email exchange. They concentrated on technical and material characteristics of the well, logged temperature data and petrophysical data. The relevant borehole and petrophysical data are shown below, the used temperature logs are presented later in Section 3.4. The definition of the borehole and petrophysical parameters is of key importance when running WellboreKIT simulations. These data have been closely integrated into the WellboreKIT model.

Field Data. Field data forms and sheets will be placed in the project file and copies provided to the Project Manager. These results will be scanned and transferred directly from the various forms and sheets into the Consultant’s database and incorporated into the Final Report. The summary tables will be checked by the Consultant’s staff to ensure that all data have been accurately presented before final storage of the data. These worksheets will be saved electronically as described in SOP SAS-01-02. This will allow these data to be retrieved and used for whatever reporting purposes may be required.

Field Data. Field data will be recorded in project logbooks and/or on standardized forms, and is entered into project electronic files on a routine basis. Each data record will include, as a minimum, the name of the individual collecting the data, the date and time of collection, the applicable instrument number and calibration information, the intended purpose of the data, and the type of data collected, along with applicable sample numbers, if appropriate.