Weather Station Metadata Clause Samples

Weather Station Metadata. ‌ For weather stations and in-situ measurements, different information will be used in the metadata so that the instruments that measure the variables are described. As well as the entries from the Spatial metadata (excluding spatial-specific entries 5 and 7), these are: Sensor information • Sensor type • Manufacturer • Sensor model • Serial number • Firmware version • Measured variable identifier(s) • Measurement unit of each variable • Accuracy of each variable • Raw sampling rate • Transmission rate Installation information • Connection type / Transmission technology • Position (X, Y information in WGS84) • Height of the instrument above ground (m) • Estimated height of surrounding buildings (m) • Vertical and horizontal orientation of instrument (degrees) • Instrument mounting description • Data format • Photograph(s) of the station and immediate surroundings after installation The above information will be stored in a designed form in Excel, named with the station’s name and the instrument serial number. A consistent set of variable names and measurement units for the weather stations should be agreed upon by the URBANFLUXES Partners before the metadata are populated. It is noted that equipment may need replacing at a particular station and it will be clear when this happens in the framework of the project. To access to the data description with simple tools, contextual information about the data (one per product) will be added in a text based document. This will contain less information than the XML suggested by the INSPIRE Directive or the form containing the weather station metadata. However, this information will be enough to describe the data. Information on the creation date, data source, scale, creator, life span in cases of temporal update will be included in the text file. Information on the source of dataset, time window, expiration date scale of the dataset, owner should be included in both the XML and the TXT files. The final products will be made available through the URBANFLUXES Data Repository hosted in the project’s web server. These products will be accompanied by their metadata, based on the INSPIRE Directive. The non-spatial data will have their own metadata. For multimedia files (photography and video - documentary), keywords based on IPTC protocol for metadata will be used. The list of keywords will be defined by the Consortium. For the documents, keywords from a predefined list can be used either within the text or at the attribu...
View Source
Weather Station Metadata. For the in-situ measurements, different information is used in the metadata in order to ensure that the instruments of the measurements are described. As well as the entries from the Spatial metadata (excluding spatial-specific entries 5 and 7), these are: Sensor information • Sensor type • Manufacturer • Sensor model • Serial number • Firmware version • Measured variable identifier(s) • Measurement unit of each variable • Accuracy of each variable • Raw sampling rate • Transmission rate Installation information • Connection type / Transmission technology • Position (X, Y information in WGS84) • Height of the instrument above ground (m) • Estimated height of surrounding buildings (m) • Vertical and horizontal orientation of instrument (degrees) • Instrument mounting description • Data format • Photograph(s) of the station and immediate surroundings after installation The above data are stored in a designed form, named with the station’s name and code (if available). A consistent set of variable names and measurement units for the weather stations have been agreed upon by the URBANFLUXES Partners before the metadata are populated. It is noted that equipment may need replacing at a particular station and it will be clear when this happens in the framework of the project.
View Source

Related to Weather Station Metadata

  • Metadata Where the Contractor has or generates metadata as a result of services provided to the Province, where that metadata is personal information, the Contractor will: not use it or disclose it to any other party except where the Agreement otherwise specifies; and remove or destroy individual identifiers, if practicable.

  • Contract Database Metadata Elements Title: Sayville Union Free School District and Sayville Union Free School Custodial and Maintenance Employees Unit, United Public Service Employees Union (UPSEU), Local 424 (2011) Employer Name: Sayville Union Free School District Union: Sayville Union Free School Custodial and Maintenance Employees Unit, United Public Service Employees Union (UPSEU) Local: 424 Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 6131 Unit Size: 55 Number of Pages: 24 For additional research information and assistance, please visit the Research page of the Catherwood website - ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇▇▇.▇▇▇/library/research/ For additional information on the ILR School - ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇▇▇.▇▇▇/ 55 People TABLE OF CONTENTS ARTICLE Page XXII ANNUAL LEAVE DAYS 14 XXV BREAKS 18 XXVI CIVIL SERVICE LAW ARTICLE SECTION 75 18 XXVIII DURATION 19 XIV EMERGENCY WORK 11 XXI FOUL WEATHER CLOTHING 14 XI GRIEVANCE PROCEDURE 9 XVI HIGHER JOB CLASSIFICATION 12 XVIII HOLIDAYS 13 XV HOLIDAY AND WEEKEND BUILDING CHECKS 12 V INSURANCE 4 X LAYOFF, DISPLACEMENT AND RECALL ORDER 8 VII MANAGEMENT RIGHTS 7 XXVII MISCELLANEOUS 19 XVII NOTICES OF PROMOTIONS 13 XIII OVERTIME 10 II PAYROLL DEDUCTIONS 1 III PERSONNEL FILES 2 XXIV PHYSICAL EXAMINATIONS 18 XXIII RETIREMENT 16 IX STRIKES AND LOCKOUTS 7 XIX VACATIONS 13 XX VISITATION 14 IV WAGES 3 VI WORKERS' COMPENSATION 6 XII WORKWEEK 10 VIII WRITTEN BOARD POLICY 8 APPENDIX A 20 4/20/2016 AGREEMENT made and entered into this day of November 2013 between the SAYVILLE UNION FREE SCHOOL DISTRICT (hereinafter referred to as the “District”) and United Public Service Employees Union, ▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇, ▇▇▇▇▇▇▇▇▇▇, N.Y. 11779 (hereinafter referred to as the “Union”).

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Network Interconnection Methods 3.1 The Interconnection provided herein may not be used solely for the purpose of originating a Party’s own interexchange traffic.

  • Catalog Information about Hawthorn University is published in a school catalog that contains a description of certain policies, procedures, and other information about the school. Hawthorn University reserves the right to change any provision of the catalog at any time. Notice of changes will be communicated in a revised catalog, an addendum or supplement to the catalog, or other written format. Students are expected to read and be familiar with the information contained in the school catalog, in any revisions, supplements and addenda to the catalog, and with all school policies. By enrolling in Hawthorn University, the student agrees to abide by the terms stated in the catalog and all school policies.