DOCSLIB.ORG

Open Geospatial Consortium Inc

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

OGC 07-041r1 Open Geospatial Consortium Inc. Date: 2007-05-8 Reference number of this OGC® project document: OGC 07-041r1 Version: 0.3.0 Category: OGC® Discussion Paper Editors: Ilya Zaslavsky, David Valentine, Tim Whiteaker CUAHSI WaterML Copyright notice Copyright © 2007 Open Geospatial Consortium. All rights reserved. Copyright © 2007 Open Geospatial Consortium. All rights reserved. To obtain additional rights of use, visit http://www.opengeospatial.org/legal/. Warning This document is not an OGC Standard. This document is an OGC Discussion Paper and is therefore not an official position of the OGC membership. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an OGC Standard. Further, an OGC Discussion Paper should not be referenced as required or mandatory technology in or mandatory technology in procurements Document type: OGC® Publicly Available Draft Document subtype: Candidate Discussion Paper Document stage: Draft Document language: English OGC 07-041r1 . ii Copyright © 2007 Open Geospatial Consortium. All rights reserved. OGC 07-041r1 Contents i. Preface.................................................................................................................. vii ii. Submitting organizations ................................................................................... vii iii. Submission contact points ................................................................................. viii iv. Revision history.................................................................................................. viii v. Changes to the OGC® Abstract Specification ................................................. viii vi. Future work.......................................................................................................... ix Foreword.............................................................................................................................x Introduction...................................................................................................................... xi 1 Scope........................................................................................................................1 2 Conformance ..........................................................................................................1 3 Normative references.............................................................................................1 4 Terms and definitions............................................................................................2 5 Conventions ............................................................................................................5 5.1 Symbols (and abbreviated terms).........................................................................5 5.2 XML conventions...................................................................................................6 6 WaterML Core Concepts and Implementation Context....................................7 6.1 Introduction............................................................................................................7 6.2 Core concepts .........................................................................................................8 6.2.1 Space, Time, Variable............................................................................................8 6.2.2 Observation network, observation series...........................................................11 6.2.3 Types in WaterML...............................................................................................12 6.2.4 The basic content, and extensibility ...................................................................13 6.3 Implementation context.......................................................................................13 6.4 General issues of bridging with OGC specifications and best practices.........14 7 WaterML element descriptions ..........................................................................15 7.1 Element naming conventions in WaterML........................................................15 7.2 Namespace ............................................................................................................16 7.3 Elements dealing with space ...............................................................................16 7.3.1 General description..............................................................................................16 7.3.2 The SiteInfoType type .........................................................................................18 7.3.3 The DataSetInfoType type ..................................................................................19 7.3.4 The site element....................................................................................................20 7.3.5 The LatLonPointType type.................................................................................21 7.3.6 The LatLonBoxType type ...................................................................................22 Copyright © OGC 2007 – All rights reserved iii OGC 07-041r1 7.3.7 Notes on compatibility with OGC specifications...............................................23 7.4 Elements dealing with variables .........................................................................24 7.4.1 General description..............................................................................................24 7.4.2 The variable element............................................................................................25 7.4.3 Units element ........................................................................................................26 7.4.4 Notes on compatibility with OGC specifications...............................................27 7.5 Elements dealing with time and measured values ............................................27 7.5.1 General description..............................................................................................27 7.5.2 Values 28 7.5.3 Elements of TimePeriodType..............................................................................32 7.5.4 Notes on compatibility with OGC specifications...............................................35 7.6 Series and series catalogs.....................................................................................35 7.6.1 General description..............................................................................................35 7.6.2 Series 35 7.6.3 SeriesCatalog........................................................................................................38 7.6.4 Notes on compatibility with OGC specifications...............................................40 7.7 Elements dealing with web method queries.......................................................42 7.7.1 General description..............................................................................................42 7.7.2 SiteInfoResponse Type ........................................................................................43 7.7.3 VariablesResponse Type .....................................................................................46 7.7.4 TimeSeriesResponse Type...................................................................................47 7.7.5 QueryInfo Element ..............................................................................................50 8 Limitations, and future work..............................................................................51 8.1 Multiple siteCodes and variableCodes...............................................................51 8.2 Categorical Values ...............................................................................................51 8.3 Adding support for groups..................................................................................52 8.4 Terminology..........................................................................................................52 8.5 Metadata ...............................................................................................................52 ANNEX A (normative) Controlled Vocabularies (XML Enumerations) .............54 A1 Introduction..........................................................................................................54 A2 Censor Code CV: <CensorCodeCVEnumeration> ..........................................54 A3 DataType CV: <DataTypeCVEnumeration>....................................................54 A4 General Category CV: <GeneralCategoryCVEnumeration> .........................55 A5 Quality Control Levels CV: <QualityControlLevelEnumeration>.................55 A6 Sample Medium CV: <SampleMediumCVEnumeration> ..............................56 A7 Sample Type CV: <SampleTypeCVEnumeration>..........................................57 A8 Topic Category CV: <TopicCategoryCVEnumeration> .................................58 A9 Units CV: <UnitsCVEnumeration> ...................................................................58 A10 Value Type CV: <ValueTypeCVEnumeration> ...............................................64 A11 Variable Name CV: <VariableNameCVEnumeration>...................................64 A12 Vertical Datum CV: <VerticalDatumCVEnumeration> .................................67 A13 Spatial Reference Systems...................................................................................68 Annex B (informative) The Context of WaterML: CUAHSI HIS Services Oriented Architecture, Web Services, and Related
Recommended publications
  • FGDC Standards Program

    FGDC Standards Program

    FGDC Standards Program Presented by Julie Binder Maitra To ISO Standards in Action Workshop November 16, 2013 1 Topics Policies guiding FGDC standards program FGDC Participation in Non-Federal Standards Bodies Recent FGDC standards activities Update of Chapter 10 of SDI Cookbook Policies guiding FGDC standards program OMB Circular A-16 and supplemental guidance call for development of standards for NSDI data themes OMB Circular A-119 Directs Federal agencies to use “voluntary consensus standards” in lieu of government-unique standards whenever possible Directs Federal agencies to participate in voluntary consensus standards bodies Policies guiding FGDC Standards Program FGDC Policy on Recognition of Non-Federally Authored Geographic Information Standards and Specifications Although Circulars A-16 and A-119 direct the use of non-Federally developed standards, they do not define a mechanism for the identification, selection, and coordinated implementation of non- Federally developed standards. The FGDC Policy enables a fast track to FGDC endorsement of external standards, as standards have already been vetted through a rigorous standards development process. FGDC Participation in Non-Federal Standards Bodies International International Organization for Standardization (ISO) ISO Technical Committee 211 National ISO member body InterNational Committee for American National Standards Information Technology Institute (ANSI) Standards (INCITS) /JAG INCITS Technical Committee L1 MoU Are members of Federal Defense and Intelligence Communities Federal Geographic Data Geospatial Intelligence Committee (FGDC) member Working Group (GWG) agencies Are members of Open Geospatial Consortium (OGC) Recent FGDC standards activities In 2010, the FGDC endorsed 64 Non-Federally Authored Geospatial Standards, in support of the Geospatial Platform. Standards included: De facto standards Standards developed through voluntary consensus standards bodies such as ANSI, ISO, and OGC.
  • Survey of Microbial Composition And

    Survey of Microbial Composition And

    The Proceedings of the International Conference on Creationism Volume 7 Article 11 2013 Survey of Microbial Composition and Mechanisms of Living Stromatolites of the Bahamas and Australia: Developing Criteria to Determine the Biogenicity of Fossil Stromatolites Georgia Purdom Answers in Genesis Andrew A. Snelling Answers in Genesis Follow this and additional works at: https://digitalcommons.cedarville.edu/icc_proceedings DigitalCommons@Cedarville provides a publication platform for fully open access journals, which means that all articles are available on the Internet to all users immediately upon publication. However, the opinions and sentiments expressed by the authors of articles published in our journals do not necessarily indicate the endorsement or reflect the views of DigitalCommons@Cedarville, the Centennial Library, or Cedarville University and its employees. The authors are solely responsible for the content of their work. Please address questions to [email protected]. Browse the contents of this volume of The Proceedings of the International Conference on Creationism. Recommended Citation Purdom, Georgia and Snelling, Andrew A. (2013) "Survey of Microbial Composition and Mechanisms of Living Stromatolites of the Bahamas and Australia: Developing Criteria to Determine the Biogenicity of Fossil Stromatolites," The Proceedings of the International Conference on Creationism: Vol. 7 , Article 11. Available at: https://digitalcommons.cedarville.edu/icc_proceedings/vol7/iss1/11 Proceedings of the Seventh International Conference on Creationism. Pittsburgh, PA: Creation Science Fellowship SURVEY OF MICROBIAL COMPOSITION AND MECHANISMS OF LIVING STROMATOLITES OF THE BAHAMAS AND AUSTRALIA: DEVELOPING CRITERIA TO DETERMINE THE BIOGENICITY OF FOSSIL STROMATOLITES Georgia Purdom, PhD, Answers in Genesis, P.O. Box 510, Hebron, KY, 41048 Andrew A.
  • The Milesian Calendar in Short

    The Milesian Calendar in Short

    The Milesian calendar in short Quick description The Milesian calendar is a solar calendar, with weighted months, in phase with seasons. It enables you to understand and take control of the Earth’s time. The next picture represents the Milesian calendar with the mean solstices and equinoxes. Leap days The leap day is the last day of the year, it is 31 12m or 12m 31 (whether you use British or American English). This day comes just before a leap year. Years The Milesian years are numbered as the Gregorian ones. However, they begin 10 or 11 days earlier. 1 Firstem Y (1 1m Y) corresponds to 21 December Y-1 when Y is a common year, like 2019. But it falls on 22 December Y-1 when Y is a leap year like 2020. The mapping between Milesian and Gregorian dates is shifted by one for 71 days during “leap winters”, i.e. from 31 Twelfthem to 9 Thirdem. 10 Thirdem always falls on 1 March, and each following Milesian date always falls on a same Gregorian date. Miletus S.A.R.L. – 32 avenue Théophile Gautier – 75016 Paris RCS Paris 750 073 041 – Siret 750 073 041 00014 – APE 7022Z Date conversion with the Gregorian calendar The first day of a Milesian month generally falls on 22 of the preceding Gregorian month, e.g.: 1 Fourthem (1 4m) falls on 22 March, 1 Fifthem (1 5m) on 22 April etc. However: • 1 Tenthem (1 10m) falls on 21 September; • 1 12m falls on 21 November; • 1 1m of year Y falls on 21 December Y-1 if Y is a common year, but on 22 December if Y is a leap year; • 1 2m and 1 3m falls on 21 January and 21 February in leap years, 20 January and 20 February in common years.
  • Part 1- Timeseries

    Part 1- Timeseries

    OGC WaterML 2.0 OGC 10-126r4 Open Geospatial Consortium Approval Date: 2012-06-23 Publication Date: 2014-02-24 Reference number of this OGC® project document: OGC 10-126r4 OGC name of this OGC® project document: http://www.opengis.net/doc/IS/waterml/2.0.1 Version: 2.0.1 Category: OGC® Implementation Standard - Corrigendum Editor: Peter Taylor OGC® WaterML 2.0: Part 1- Timeseries Copyright notice Copyright © 2012-2014 Open Geospatial Consortium To obtain additional rights of use, visit http://www.opengeospatial.org/legal/. Notice This document is an OGC Member approved international standard. This document is available on a royalty free, non-discriminatory basis. Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation. Document type: OGC® Implementation Standard - Corrigendum Document subtype: Encoding Document stage: Approved for Public Release Document language: English OGC 10-126r4 WaterML 2.0 License Agreement Permission is hereby granted by the Open Geospatial Consortium, ("Licensor"), free of charge and subject to the terms set forth below, to any person obtaining a copy of this Intellectual Property and any associated documentation, to deal in the Intellectual Property without restriction (except as set forth below), including without limitation the rights to implement, use, copy, modify, merge, publish, distribute, and/or sublicense copies of the Intellectual Property, and to permit persons to whom the Intellectual Property is furnished to do so, provided that all copyright notices on the intellectual property are retained intact and that each person to whom the Intellectual Property is furnished agrees to the terms of this Agreement.
  • The Common Year

    The Common Year

    THE COMMON YEAR #beautyinthecommon I am typing this in a hospital lobby just outside Detroit at and designed by veritable gobs and gobs of wonderful 3am as I sleepily but eagerly await the birth of my dear friends from all sorts of backgrounds and perspectives. brother’s first child. The smell of the pizza, Starbucks, and lo mein reminds me fondly of the last 13 hours Each written piece will be broken into what may seem we’ve spent gathered together in this “very hospitally” like peculiar categories: waiting room. Word | Meal | Music | Prayer | Time And while everyone is currently dozing on plastic chairs as the infomercials on the lobby television rage on – the Our hope is that these narratives will be more than room is still electric somehow. There is wonder and inspiring thoughts and truisms and instead will beauty in the air. Even here – even in the stillness of challenge each of us to more fully engage all of life as sweet anticipation not yet realized. deeply sacred. There will be invitations to listen to new songs, share in new meals, and see in new ways. I I want to live my life like this. challenge you to carve out time to really soak in each of these pieces and see just what it is that God might To both await with eagerness the mountaintop awaken in your own heart as you do. moments and to also see more fully and experience more deeply the beauty in the mundane, the “in- So print this framework out. Put it in a binder.
  • NGDA Baseline Standards Inventory Companion Guide

    NGDA Baseline Standards Inventory Companion Guide

    The Companion Guide: Achieving an NGDA Baseline Standards Inventory A Baseline Assessment to Meet Geospatial Data Act, Federal Data Strategy, and Other Requirements Federal Geographic Data Committee August 31, 2020 Contents Introduction .................................................................................................................................................. 1 Approach ....................................................................................................................................................... 2 Outcomes ...................................................................................................................................................... 2 How to Use this Document ........................................................................................................................... 2 Geospatial Data and Metadata Standards .................................................................................................... 3 Data Standards Categories ............................................................................................................................ 5 Data Content Standards Category Definitions .......................................................................................... 5 Data Exchange Standards Definitions ....................................................................................................... 8 Metadata Standards Categories ..................................................................................................................
  • A Pilot for Testing the OGC Web Services Integration of Water-Related Information and Models

    A Pilot for Testing the OGC Web Services Integration of Water-Related Information and Models

    RiBaSE: A Pilot for Testing the OGC Web Services Integration of Water-related Information and Models Lluís Pesquer Mayos, Simon Jirka, Grumets Research Group CREAF 52°North Initiative for Geospatial Open Source Software Edicifi C, Universitat Autònoma de Barcelona GmbH 08193 Bellaterra, Spain 48155 Münster, Germany [email protected] [email protected] Christoph Stasch, Joan Masó Pau, Grumets Research Group CREAF 52°North Initiative for Geospatial Open Source Software Edicifi C, Universitat Autònoma de Barcelona GmbH Bellaterra, Spain 48155 Münster, Germany [email protected] [email protected] David Arctur, Center for Research in Water Resources, University of Texas at Austin 10100 Burnet Rd Bldg 119, Austin, TX USA [email protected] Abstract—The design of an interoperability experiment to The OGC is an international industry consortium of demonstrate how current ICT-based tools and water data can companies, government agencies and universities participating work in combination with geospatial web services is presented. in a consensus process to develop publicly available interface This solution is being tested in three transboundary river basins: standards. Some successful examples of OGC standards for Scheldt, Maritsa and Severn. The purpose of this experiment is to general spatial purposes are, for example, the Web Map assess the effectiveness of OGC standards for describing status Service (WMS) for providing interoperable pictorial maps and dynamics of surface water in river basins, to demonstrate over the web and the Keyhole Markup Language (KML) as a their applicability and finally to increase awareness of emerging data format for virtual globes. On the other hand, hydrological standards as WaterML 2.0.
  • Metadata and Data Standards. Sharing Data in Hydrology: Best Prac�Ces

    Metadata and Data Standards. Sharing Data in Hydrology: Best PracCes

    Metadata and Data Standards. Sharing Data in Hydrology: Best Prac8ces Ilya Zaslavsky San Diego Supercomputer Center LMI Workshop, Hanoi, August 18-22 / With several slides from last week’s HDWG workshop, presented By HDWG memBers Irina Dornblut, Paul Sheahan, and others/ Outline • Why use standards? • Open Geospaal ConsorFum, and spaal data standards • Standards for water data, and the OGC/WMO Hydrology Domain Working Group – history, acFviFes, WMO connecFon, workshop last week – Suite of water data standards • WaterML 2.0 in detail (opFonal) • Assessing compliance, and the CINERGI project (opFonal) Why sharing data in LMI? • Several countries rely on the Mekong But data sharing is complicated Challenges: Habitat alteraon PolluFon Extreme weather events Over-exploitaon of resources Diseases and invasive species Poverty and social instability . Water - our most valuable asset But ... • In many places we can’t assess – How much we have – Where it is – Who owns it – What it is fit for – How much we will have – Where it will Be • We certainly can’t yet share informaon in a useful Fmeframe – In parFcular given the complexity of water cycle Why is it important to coordinate? • The orBiter was taken within 57 km of the surface where it likely disintegrated Why? • The flight system so[ware used metric units (Newtons); so[ware on the ground used the Imperial system (pound-force, or lbf) A common situaon in hydrology… Hydro Jack Need flow data! Don Hmm mayBe Don can help… *RING RING* To: Jack Hmm, I’ve got one site. I’ll 01/02/09, 3.2, 3, 1 Hi Don, I need some send it through… 01/02/09, 3.1, 3, 1 *RING RING* upper Derwent flow 10 minutes… readings for my 10 minutes… Ok.
  • The Calendars of India

    The Calendars of India

    The Calendars of India By Vinod K. Mishra, Ph.D. 1 Preface. 4 1. Introduction 5 2. Basic Astronomy behind the Calendars 8 2.1 Different Kinds of Days 8 2.2 Different Kinds of Months 9 2.2.1 Synodic Month 9 2.2.2 Sidereal Month 11 2.2.3 Anomalistic Month 12 2.2.4 Draconic Month 13 2.2.5 Tropical Month 15 2.2.6 Other Lunar Periodicities 15 2.3 Different Kinds of Years 16 2.3.1 Lunar Year 17 2.3.2 Tropical Year 18 2.3.3 Siderial Year 19 2.3.4 Anomalistic Year 19 2.4 Precession of Equinoxes 19 2.5 Nutation 21 2.6 Planetary Motions 22 3. Types of Calendars 22 3.1 Lunar Calendar: Structure 23 3.2 Lunar Calendar: Example 24 3.3 Solar Calendar: Structure 26 3.4 Solar Calendar: Examples 27 3.4.1 Julian Calendar 27 3.4.2 Gregorian Calendar 28 3.4.3 Pre-Islamic Egyptian Calendar 30 3.4.4 Iranian Calendar 31 3.5 Lunisolar calendars: Structure 32 3.5.1 Method of Cycles 32 3.5.2 Improvements over Metonic Cycle 34 3.5.3 A Mathematical Model for Intercalation 34 3.5.3 Intercalation in India 35 3.6 Lunisolar Calendars: Examples 36 3.6.1 Chinese Lunisolar Year 36 3.6.2 Pre-Christian Greek Lunisolar Year 37 3.6.3 Jewish Lunisolar Year 38 3.7 Non-Astronomical Calendars 38 4. Indian Calendars 42 4.1 Traditional (Siderial Solar) 42 4.2 National Reformed (Tropical Solar) 49 4.3 The Nānakshāhī Calendar (Tropical Solar) 51 4.5 Traditional Lunisolar Year 52 4.5 Traditional Lunisolar Year (vaisnava) 58 5.
  • Augmenting Hydrologic Information Systems with Streaming Water Resource Data

    Augmenting Hydrologic Information Systems with Streaming Water Resource Data

    AUGMENTING HYDROLOGIC INFORMATION SYSTEMS WITH STREAMING WATER RESOURCE DATA S. Esswein1, J. Hallstrom2, C. J. Post1, D. White3, G. Eidson4 AUTHORS: Forestry and Natural Resources1; School of Computing2; Computing and Information Technology3; Restoration Institute4, Clemson University, Clemson, SC USA 29634 REFERENCE: Proceedings of the 2010 South Carolina Water Resources Conference, held October 13-14, 2010, at the Columbia Metropolitan Convention Center. examined with an emphasis on design decisions regarding Abstract. Access to timely and accurate hydrological leveraging available standards and software. Insight and environmental observation data is a crucial aspect of garnered from several years of data acquisition experience an integrated approach to water resources management. is provided, along with a recent case study involving a This presentation describes an end-to-end system designed monitoring deployment supporting the Sand River to support realtime monitoring and management of water Headwaters Green Infrastructure project located in the resources. The main components of the hardware/software City of Aiken, South Carolina. infrastructure of this system are broken into four There are four components or tiers of a realtime- categories and briefly described. This organization monitoring infrastructure: (i) sensing platforms collect in provides the basis for a synthesis of several prominent situ observation data, (ii) communication and uplink standards and software solutions relevant to the technologies transmit realtime observation data, (iii) data hydrologic and environmental observing communities. streaming middleware provides highly distributed These standards are described in the context of their role publication and subscription of observation data, and (iv) in our end-to-end system. The presentation concludes with back-end repository and presentation services provide a a case study describing a green infrastructure monitoring means of viewing and utilizing data products.
  • Charles Ballinger Executive Director Emeritus

    Charles Ballinger Executive Director Emeritus

    NAYRE Charles Ballinger Executive Director Emeritus National Association for Year-Round Education Eight Reasons Given to Avoid Calendar Modification 1. Children might be on differing schedules. 2. Child care might not be available. 3. Students might not find and hold jobs after calendar modification. 4. Students might not be able to be involved in out-of-school activities, extracurricular activities, and sports. 5. There is no air-conditioning during warm weather. 6. Facility cleaning and maintenance will be disrupted. 7. Teachers will have difficulty with in-service and graduate work. 8. Family vacations will be difficult to schedule. Six Generalized Reasons for Calendar Modification 1. Modified, balanced calendars can effectively maintain student interest in learning. 2. Students, learning differently, require different time configurations. 3. Intersession classes provide faster remediation and advanced enrichment. 4. Students learning a second language can benefit from the balanced calendar. 5. Co-curricular and extracurricular activities can take place throughout the year and can reinforce previous learning. 6. Teachers can take advantage of year-long opportunities for staff development. School Year Flexibility 365 Days per calendar year -180 Days of legislatively-mandated instruction annually -104 Weekend days (Saturday and Sunday) - 10 Winter Holidays (Christmas and New Year’s) - 11 Other Legal Holidays 60 Remaining optional/flexible days 45-15 Single Track Model 15 15 15 15 45 Classroom School 45 Classroom School 45 Classroom School
  • Waterml 1.1 Part 1

    Waterml 1.1 Part 1

    CUAHSI WATERML 1.1 Specification Part 1: Introduction to WaterML Schema June 11, 2009 by: David Valentine Ilya Zaslavsky San Diego Supercomputer Center University of California at San Diego San Diego, California, USA Distribution Copyright © 2009, Consortium of Universities for the Advancement of Hydrologic Science, Inc. All rights reserved. Funding and acknowledgements Funding for this document was provided by the Consortium of Universities for the Advancement of Hydrologic Science, Inc. (CUAHSI) under NSF Grant No. EAR-0413265. In addition, much input and feedback has been received from the CUAHSI Hydrologic Information System development team. Their contribution is acknowledged here. We would also like to thank partner agency personnel from USGS (Water Resource Division), EPA (the STORET team), and NCDC, as well as data managers and personnel of hydrologic observatory testbeds for cooperation, discussions and insightful feedback. We are especially grateful to the USGS and NCDC teams, and other partners who implemented WaterML-compliant web services over their repositories. Scope Water Markup Language (WaterML) specification defines an information exchange schema, which has been used in water data services within the Hydrologic Information System (HIS) project supported by the U.S. National Science Foundation, and has been adopted by several federal agencies as a format for serving hydrologic data. The goal of the first version of WaterML was to encode the semantics of hydrologic observation discovery and retrieval and implement water data services in a way that is both generic and unambiguous across different data providers, thus creating the least barriers for adoption by the hydrologic research community. This documents WaterML version 1.0 as implemented and utilized in the CUAHSI HIS system.