DOCSLIB.ORG

Web Coverage Service (WCS) V1.0.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Web Coverage Service (WCS) V1.0.0 Open Geospatial Consortium Inc. Date: 2005-10-14 Reference number of this OGC® Project Document: OGC 05-076 Version: 1.0.0 (Corrigendum) Category: OGC® Implementation Specification Editor: John D. Evans Web Coverage Service (WCS), Version 1.0.0 (Corrigendum) Copyright © 2005 Open Geospatial Consortium. All Rights Reserved To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ Document type: OpenGIS® Implementation Specification Document subtype: Corrigendum Document stage: Approved Document language: English OGC 05-076 Contents Page 1 Scope........................................................................................................................1 2 Conformance............................................................................................................1 3 Normative references...............................................................................................1 4 Terms and definitions ..............................................................................................2 5 Conventions .............................................................................................................4 5.1 Symbols (and abbreviated terms) ............................................................................4 5.2 UML notation ..........................................................................................................4 5.3 XML schema notation..............................................................................................6 6 Basic service elements.............................................................................................6 6.1 Introduction..............................................................................................................6 6.2 Version numbering and negotiation.........................................................................7 6.2.1 Version number form...............................................................................................7 6.2.2 Version changes.......................................................................................................7 6.2.3 Appearance in requests and in service metadata .....................................................7 6.2.4 Version number negotiation.....................................................................................7 6.3 General HTTP request rules ....................................................................................8 6.3.1 Overview..................................................................................................................8 6.3.2 Key-value pair encoding (GET or POST) ...............................................................9 6.3.2.1 Overview..................................................................................................................9 6.3.2.2 Parameter ordering and case ....................................................................................9 6.3.2.3 Parameter lists..........................................................................................................9 6.3.3 XML encoding.......................................................................................................10 6.4 General HTTP response rules................................................................................10 6.5 Service exceptions .................................................................................................10 7 GetCapabilities operation ......................................................................................11 7.1 Introduction............................................................................................................11 7.2 GetCapabilities request..........................................................................................11 7.2.1 Key-value pair encoding........................................................................................11 7.2.2 XML encoding.......................................................................................................12 7.3 GetCapabilities response: Capabilities XML document........................................13 7.3.1 Overview................................................................................................................13 7.3.2 Service ...................................................................................................................13 7.3.3 Capability...............................................................................................................15 7.3.4 ContentMetadata and CoverageOfferingBrief.......................................................15 7.3.4.1 Overview................................................................................................................15 7.3.4.2 metadataLink..........................................................................................................17 7.3.4.3 description..............................................................................................................17 7.3.4.4 name 17 7.3.4.5 label 17 7.3.4.6 lonLatEnvelope......................................................................................................17 ii Copyright © Open Geospatial Consortium, Inc. (2005). All rights reserved. OGC 05-076 7.3.4.7 keywords................................................................................................................17 7.3.4.8 Additional coverage properties: DescribeCoverage ..............................................17 7.3.4.9 XLink pointer to external catalog ..........................................................................18 7.3.5 Exceptions..............................................................................................................18 8 DescribeCoverage operation..................................................................................18 8.1 Introduction............................................................................................................18 8.2 DescribeCoverage requests....................................................................................18 8.2.1 Overview................................................................................................................18 8.2.2 Key-value pair encoding........................................................................................18 8.2.3 XML encoding.......................................................................................................19 8.3 DescribeCoverage response: CoverageDescription and CoverageOffering..........20 8.3.1 Overview................................................................................................................20 8.3.2 domainSet ..............................................................................................................21 8.3.2.1 Overview................................................................................................................21 8.3.2.2 SpatialDomain........................................................................................................21 8.3.2.3 TemporalDomain ...................................................................................................22 8.3.3 rangeSet .................................................................................................................23 8.3.3.1 Overview................................................................................................................23 8.3.3.2 AxisDescription (for compound range sets) ..........................................................24 8.3.3.2.1 Introduction .......................................................................................................24 8.3.3.2.2 XML syntax.......................................................................................................25 8.3.3.2.3 Compound range sets ........................................................................................26 8.3.3.3 NullValues .............................................................................................................27 8.3.4 SupportedCRSs and coordinate reference systems (CRS) ....................................28 8.3.4.1 Overview................................................................................................................28 8.3.4.2 requestResponseCRSs ...........................................................................................29 8.3.4.3 requestCRSs...........................................................................................................29 8.3.4.4 responseCRSs ........................................................................................................29 8.3.4.4.1 nativeCRSs ........................................................................................................29 8.3.5 SupportedFormats..................................................................................................29 8.3.6 SupportedInterpolations.........................................................................................30 9 GetCoverage operation ..........................................................................................30 9.1 Introduction............................................................................................................30 9.2 GetCoverage requests ............................................................................................31 9.2.1 Overview................................................................................................................31
Load more

Recommended publications
  • Opengis Web Feature Services for Editing Cadastral Data
    OpenGIS Web Feature Services for editing cadastral data Analysis and practical experiences Master of Science thesis T.J. Brentjens Section GIS Technology Geodetic Engineering Faculty of Civil Engineering and Geosciences Delft University of Technology OpenGIS Web Feature Services for editing cadastral data Analysis and practical experiences Master of Science thesis Thijs Brentjens Professor: prof. dr. ir. P.J.M. van Oosterom (Delft University of Technology) Supervisors: drs. M.E. de Vries (Delft University of Technology) drs. C.W. Quak (Delft University of Technology) drs. C. Vijlbrief (Kadaster) Delft, April 2004 Section GIS Technology Geodetic Engineering Faculty of Civil Engineering and Geosciences Delft University of Technology The Netherlands Het Kadaster Apeldoorn The Netherlands i ii Preface Preface This thesis is the result of the efforts I have put in my graduation research project between March 2003 and April 2004. I have performed this research part-time at the section GIS Technology of TU Delft in cooperation with the Kadaster (the Dutch Cadastre), in order to get the Master of Science degree in Geodetic Engineering. Typing the last words for this thesis, I have been realizing more than ever that this thesis marks the end of my time as a student at the TU Delft. However, I also realize that I have been working to this point with joy. Many people are “responsible” for this, but I’d like to mention the people who have contributed most. First of all, there are of course people who were directly involved in the research project. Peter van Oosterom had many critical notes and - maybe even more important - the ideas born out of his enthusiasm improved the entire research.
    [Show full text]
  • Array Databases: Concepts, Standards, Implementations
    Baumann et al. J Big Data (2021) 8:28 https://doi.org/10.1186/s40537-020-00399-2 SURVEY PAPER Open Access Array databases: concepts, standards, implementations Peter Baumann , Dimitar Misev, Vlad Merticariu and Bang Pham Huu* *Correspondence: b. Abstract phamhuu@jacobs-university. Multi-dimensional arrays (also known as raster data or gridded data) play a key role in de Large-Scale Scientifc many, if not all science and engineering domains where they typically represent spatio- Information Systems temporal sensor, image, simulation output, or statistics “datacubes”. As classic database Research Group, Jacobs technology does not support arrays adequately, such data today are maintained University, Bremen, Germany mostly in silo solutions, with architectures that tend to erode and not keep up with the increasing requirements on performance and service quality. Array Database systems attempt to close this gap by providing declarative query support for fexible ad-hoc analytics on large n-D arrays, similar to what SQL ofers on set-oriented data, XQuery on hierarchical data, and SPARQL and CIPHER on graph data. Today, Petascale Array Database installations exist, employing massive parallelism and distributed processing. Hence, questions arise about technology and standards available, usability, and overall maturity. Several papers have compared models and formalisms, and benchmarks have been undertaken as well, typically comparing two systems against each other. While each of these represent valuable research to the best of our knowledge there is no comprehensive survey combining model, query language, architecture, and practical usability, and performance aspects. The size of this comparison diferentiates our study as well with 19 systems compared, four benchmarked to an extent and depth clearly exceeding previous papers in the feld; for example, subsetting tests were designed in a way that systems cannot be tuned to specifcally these queries.
    [Show full text]
  • 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.
    [Show full text]
  • OWS-4 Geodds Mass Market (Formerly Georss) Interoperability Program Report
    OGC 07-004 Open Geospatial Consortium Inc. Date: 2007-05-02 Reference number of this OGC® document: OGC 07-004 Version: 0.0.1 Category: OpenGIS® Discussion Paper Editor: Panagiotis (Peter) A. Vretanos OWS-4 GeoDDS Mass Market (formerly GeoRSS) Interoperability Program Report Copyright notice 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 procurements. Document type: OpenGIS® Discussion Paper Document subtype: Engineering Specification Document stage: Draft Document language: English File name: 07-004.doc OGC 07-004 Contents 1 SCOPE..........................................................................................................................................................1 2 CONFORMANCE........................................................................................................................................1 3 NORMATIVE REFERENCES....................................................................................................................1 4 TERMS AND DEFINITIONS.....................................................................................................................3
    [Show full text]
  • Wcs-Overview.Pdf
    OGC Coverages: Data & Services Peter Baumann Jacobs University | rasdaman GmbH [gamingfeeds.com] Coverages Tutorial :: © 2013 Peter Baumann Overview . Motivation: What is a “coverage”? . Coverage data: the OGC Coverage Model . Coverage services: the WCS Suite . Conformance Testing . Implementations . Summary Coverages Tutorial :: © 2013 Peter Baumann2 Facing the Coverage Tsunami sensor feeds [OGC SWE] coverage server Coverages Tutorial :: © 2013 Peter Baumann3 Taming the Coverage Tsunami sensor feeds [OGC SWE] coverage server Coverages Tutorial :: © 2013 Peter Baumann4 Serving Coverages . WCS: one generic schema for all coverage types; n-D; scalable; versatile processing → access & processing services SOS WCS coverage . SOS: server high flexibility to accommodate all sensor types → data capturing Coverages Tutorial :: © 2013 Peter Baumann (Part of) The OGC Standards Quilt data images data data feature coverage meta FE WCPS CQL WFS-T WCS-T CS-T WFS WMS WCS CS-W • WMS "portrays spatial data pictures" • WCS: "provides data + descriptions; data with original semantics, may be interpreted, extrapolated, etc.“ [09-110r3] Coverages Tutorial :: © 2013 Peter Baumann6 Overview . Motivation: What is a “coverage”? . Coverage data: the OGC Coverage Model . Coverage services: the WCS Suite . Conformance Testing . Implementations . Summary Coverages Tutorial :: © 2013 Peter Baumann7 OGC Coverages . Coverage = "space-time varying phenomenon“ - ISO 19123 (=OGC Abstract Topic 6) - Today typically raster, but more defined (curved grids, TINs, meshes, ...)
    [Show full text]
  • Open Geospatial Consortium: 2D Or Not 2D?
    ® Open Geospatial Consortium: 2D or Not 2D? Chris Little, Co-Chair Met Ocean DWG Marie-Françoise Voidrot-Martinez, Météo-France, Co-Chair EGOWS at FMI, Helsinki, Finland 2016-09-20/22 © 2010 Open Geospatial Consortium, Inc. 0. Introduction 1. What is OGC? 2. Who is OGC? 3. How does OGC work? 4. What is OGC doing? 5. Current issues, futures & possibilities? 6. Questions & (maybe) Answers? ® OGC © 2010 Open Geospatial Consortium, Inc. 1. What is OGC? • See also http://www.opengeospatial.org ® OGC © 2010 Open Geospatial Consortium, Inc. 3 What is OGC? • International, non-profit, consortium • Develops standards for geospatial OGC Membership Distribution data & services, >25 years 9 % Commercial • Funded by ~500 members 6 % Government • 38 adopted standards 43 % Academic • Consensus process 24 % • Docs freely available Research • 100s of implementations Not For Profit • Alliance partnerships with 30+ 18 % standards & professional organizations • Broad user community worldwide • Several standards fast tracked in ISO (and WMO!) OGC® What is OGC’s Vision? Vision: A world in which everyone benefits from the use of geospatial information and supporting technologies. Mission: Global forum for collaboration of developers and users of spatial data products and services and to advance the development of international standards for geospatial interoperability Strategic Goals: Goal 1 - Provide free and openly available standards to the market that are of tangible value to Members and have measurable benefits for users. Goal 2 - Lead worldwide in the creation and establishment of standards that enable global infrastructures for delivery and integration of geospatial content and services into business and civic processes. Goal 3 - Facilitate the adoption of open, spatially enabled reference architectures in enterprise environments worldwide.
    [Show full text]
  • Wcs-Core-2.0.1
    Open Geospatial Consortium Approval Date: 2012-07-10 Publication Date: 2012-07-12 External identifier of this OGC® document: http://www.opengis.net/doc/IS/wcs-core-2.0.1 Reference number of this Document: OGC 09-110r4 Version: 2.0.1 Category: OGC® Interface Standard Editor: Peter Baumann OGC® WCS 2.0 Interface Standard- Core: Corrigendum Copyright © 2012 Open Geospatial Consortium. To obtain additional rights of use, visit http://www.opengeospatial.org/legal/. Warning This document is an OGC Member approved corrigendum to existing OGC 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® Interface Standard Document subtype: Corrigendum Document stage: Approved for public release Document language: English OGC 09-110r4 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.
    [Show full text]
  • RMDCN Developments
    OGC Standards EGOWS 2010 ECWMF, Reading, 2010/06/1-4 Chris Little [email protected] +44 1392 886278 OGC Co-Chair Meteorology & Oceanography Domain Working Group © Crown copyright 2007 Apologies & Disclaimers I speak too fast No pictures I was involved in international standards • ISO • WMO View of the OGC ‘landscape’ • ‘Valleys & hills’ • NOT ‘Turn 3rd left after pub’ © Crown copyright 2007 Structure of Talk • Some Background • Why OGC? • Standards • Issues for Meteorology © Crown copyright 2007 OGC Standards Some Background © Crown copyright 2007 OGC Met Ocean DWG 2007: ECMWF 11th Workshop on Meteorological Operational Systems - recommended: 2008: ECMWF-OGC Workshop on Use of GIS/OGC Standards in Meteorology - recommended: - Establish OGC Met Domain WG - Establish WMO-OGC Memorandum of Understanding - Develop WMS meteorological profile - Develop core models and registries - Interoperability test beds for met. data & visualization OGC web services © Crown copyright 2007 OGC Who? • Open Geospatial Consortium http://opengeospatial.org • Non-profit making • Standards setting http://opengeospatial.org/standards • Global • >400 members http://opengeospatial.org/members • Industry • Government bodies • Academia • Individuals © Crown copyright 2007 OGC How? TC - Technical Conference, 4 days every 3 months - Darmstadt Sept 2009 EUMETSAT - Mountainview Dec 2009 Google - Frascati Mar 2010 ESA SWG - Standards Working Groups, ~24, - Fast track to ISO, short lived, ‘vertical’ DWG - Domain Working Groups, ~27 - Cross-cutting, longer lived,
    [Show full text]
  • Web Coverage Service Developer Guide Cloud Services | August 2013
    Web Coverage Service Developer Guide Cloud Services | August 2013 Web Coverage Service Developer Guide | 2 Table of Contents List of Figures .................................................................................................................................. 3 List of Tables ................................................................................................................................... 4 1 Introduction ................................................................................................................................ 5 1.1 About This Document ............................................................................................................ 5 1.2 Targeted Audience ................................................................................................................ 5 1.3 What is WCS? ....................................................................................................................... 5 1.4 References ............................................................................................................................ 5 2 Open Geospatial Consortium (OGC) ......................................................................................... 6 2.1 About OGC ............................................................................................................................ 6 2.2 The OGC Process ................................................................................................................. 6 2.3 OGC Standards and Specification
    [Show full text]
  • International Standards for Spatial Data Infrastructures
    ® International Standards for Spatial Data Infrastructures Sam A. Bacharach [email protected] +1 703-352-3938 Copyright 2006, Open Geospatial Consortium, Inc. (OGC) WhatWhat isis thethe OGC?OGC? • Open Geospatial Consortium (OGC) – Global, not-for-profit, international voluntary consensus standards organization – More than 335 industry, government, research and university member organizations – Founded in 1994, Incorporated in US, UK, Australia OGCOGC Vision:Vision: AA worldworld inin whichwhich allall peoplepeople andand institutionsinstitutions benefitbenefit fromfrom spatialspatial informationinformation resourcesresources andand supportingsupporting technologytechnology services.services. ® Helping the World to Communicate Geographically 2 Copyright 2006, Open Geospatial Consortium, Inc. (OGC) TheThe NutsNuts andand BoltsBolts ofof thatthat VisionVision Data Civil Analysis & Emergency First Providers Authorities Support Mgmt Personnel Responders Common User Defined Interoperable Operating Pictures Private Data and Services Local Data and Services State Data and Services Federal Data and Services Tribal Data and Services Information Architecture: Service Architecture: Models, Transforms, Application Standards, Certified Services for Accessing, Schemas and Dictionaries Processing, Presenting Information ® Geospatial Interoperability Framework development is a key focus of ongoing OGC Helping the World to Communicate Geographically 3 TestbedsCopyright 2006, to Open meet Geospatial cross-organizational Consortium, Inc. (OGC)
    [Show full text]
  • GIS Glossary (PDF)
    GIS Glossary A AAT Arc attribute table. A table containing attributes for arc coverage features. In addition to user-defined attributes, the AAT contains the from and to nodes, the left and right polygons, the length, an internal sequence number and a feature identifier. See also feature attribute table. ACCESS directory The system directory that LIBRARIAN uses to store the files that manage access to the library. Each library has an ACCESS directory located in the library's DATABASE directory. accessibility An aggregate measure of how reachable locations are from a given location. The ACCESSIBILITY command computes values for accessibility as a function of the distance between locations and an empirically derived distance decay parameter. access rights The privileges accorded a user for reading, writing, deleting, updating and executing files on a disk. Access rights are stated as `no access', `read only' and `read/write'. ACODE file An INFO data file storing arc attributes for coverages created from TIGER, DIME, IGDS and Etak files. ACODE stands for `Arc CODE'. The ACODE file is related by Cover-ID to the Arc Attribute Table (AAT) of the coverage. address matching A mechanism for relating two files using address as the relate item. Geographic coordinates and attributes can be transferred from one address to the other. For example, a data file containing student addresses can be matched to a street coverage that contains addresses creating a point coverage of where the students live. ADS 1. Arc Digitizing System. A simple digitizing and editing system used to add arcs and label points to a coverage.
    [Show full text]
  • Web Coverage Service (WCS) V0.8.4
    Open Geospatial Consortium Inc. Date: 2003-08-27 Reference number of this OGC™ Project Document: OGC 03-065r6 Version: 1.0.0 Category: OpenGIS® Implementation Specification Editor: John D. Evans Web Coverage Service (WCS), Version 1.0.0 © OGC 2003 – All rights reserved i OGC 03-065r6 Copyright notice Copyright 2002, 2003, BAE SYSTEMS Mission Solutions Copyright 2002, 2003, CubeWerx Inc. Copyright 2002, 2003, George Mason University Copyright 2002, 2003, German Aerospace Center – DLR Copyright 2002, 2003, Intergraph Mapping and Geospatial Solutions Copyright 2002, 2003, IONIC SOFTWARE s.a. Copyright 2002, 2003, National Aeronautics and Space Administration (U.S.) Copyright 2002, 2003, Natural Resources Canada Copyright 2002, 2003, PCI Geomatics Copyright 2002, 2003, Polexis, Inc. The companies listed above have granted the Open Geospatial Consortium, Inc. (OGC) a nonexclusive, royalty-free, paid up, world- wide license to copy and distribute this document and to modify this document and distribute copies of the modified version. This document does not represent a commitment to implement any portion of this specification in any company’s products. OGC’s Legal, IPR and Copyright Statements are found at http://www.opengeospatial.org/about/?page=ipr&view=ipr_policy NOTICE Permission to use, copy, and distribute this document in any medium for any purpose and without fee or royalty is hereby granted, provided that you include the above list of copyright holders and the entire text of this NOTICE. We request that authorship attribution be provided in any software, documents, or other items or products that you create pursuant to the implementation of the contents of this document, or any portion thereof.
    [Show full text]