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).
AutoNDA by SimpleDocs
Field Data i. Data collected as points and break lines to define a proper DTM if requested outside of aerial mapping.
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.
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.

Related to Field Data

  • Product Data Illustrations, standard schedules, performance charts, instructions, brochures, diagrams, and other information furnished by Developer to illustrate a material, product, or system for some portion of the Work.

  • Background Data The Disclosing Party's Background Data, if any, will be identified in a separate technical document.

  • Licensed Materials The materials that are the subject of this Agreement are set forth in Appendix A ("Licensed Materials").

  • Customer Materials 12.1 The Supplier including any of its employees, agents, consultants, contractors and any third party shall:

  • Licensee Data Licensee acknowledges and agrees that Licensee will be solely responsible for backing-up, and taking all appropriate measures to protect and secure, Licensee Data. Licensee acknowledges that Nuix may make, store and maintain back up copies of Licensee Data, but is not obliged to do so. Nuix will not be liable for any loss or corruption of Licensee Data.

  • Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.

  • Third Party Materials The Application may display, include, or make available third-party content (including data, information, applications, and other products, services, and/or materials) or provide links to third-party websites or services, including through third- party advertising ("Third-Party Materials"). You acknowledge and agree that Company is not responsible for Third-Party Materials, including their accuracy, completeness, timeliness, validity, copyright compliance, legality, decency, quality, or any other aspect thereof. Company does not assume and will not have any liability or responsibility to you or any other person or entity for any Third-Party Materials. Third-Party Materials and links thereto are provided solely as a convenience to you, and you access and use them entirely at your own risk and subject to such third parties' terms and conditions.

  • API If the Software offers integration capabilities via an API, your use of the API may be subject to additional costs or Sage specific policies and terms and conditions (which shall prevail in relation to your use of the API). You may not access or use the API in any way that could cause damage to us or the Software, or in contravention of any applicable laws. We reserve the right in our sole discretion, to: (i) update any API from time to time; (ii) place limitations around your use of any API; and (iii) deny you access to any API in the event of misuse by you or to otherwise protect our legitimate interests.

  • Technical Information The Employer agrees to provide to the Union such information that is available relating to employees in the bargaining unit, as may be required by the Union for collective bargaining purposes.

  • Recipient Products Updated Project Schedule (if applicable) • Updated List of Match Funds (if applicable) • Updated List of Permits (if applicable) CAM Product: • Kick-off Meeting Agenda

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!