Open Geospatial Consortium Inc

Total Page:16

File Type:pdf, Size:1020Kb

Open Geospatial Consortium Inc Open Geospatial Consortium Inc. Date: 2006-03-04 Reference number of this document: OGC 06-021r1 Version: 1.0 Category: OpenGIS® Discussion Paper Editors: Mike Botts Alex Robin John Davidson Ingo Simonis OpenGIS® Sensor Web Enablement Architecture Document Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved. To obtain additional rights of use, visit http://www.opengeospatial.org/legal/. Warning This document is not an OGC Standard. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an OGC Standard. 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 do Document type: OpenGIS® Interoperability Program Report Document subtype: Discussion Paper Document stage: Approved Document language: English OGC 06-021r1 Contents Page i. Preface.................................................................................................................... iv ii. Submitting organizations ....................................................................................... iv iii. Document contributor contact points..................................................................... iv iv. Revision history.......................................................................................................v v. Changes to the OGC Abstract Specification............................................................v vi. Future work..............................................................................................................v Foreword............................................................................................................................ vi Introduction....................................................................................................................... vii 1 Scope........................................................................................................................1 2 Normative references...............................................................................................1 3 Terms and definitions ..............................................................................................2 4 Conventions .............................................................................................................7 4.1 Abbreviated terms ...............................................................................................7 4.2 UML notation......................................................................................................7 5 Sensor Web Enablement Architecture Overview ....................................................8 5.1 Motivation ...........................................................................................................8 5.2 Approach ...........................................................................................................10 5.3 High level concepts...........................................................................................10 5.4 Example Scenarios ............................................................................................13 6 SWE Architecture Components.............................................................................15 6.1 Information Model............................................................................................15 6.1.1 Observations and Measurements (O&M) [OGC 05-087r2] ..................................17 6.1.2 Sensor Model Language (SensorML) [OGC 05-086r2] ........................................19 6.1.3 Transducer Model Language (TML) [OGC 06-010]............................................22 6.1.4 SWE Common [OGC 05-086r2; OGC 05-087r2]..........................................................24 6.2 Service Model....................................................................................................29 6.2.1 Sensor Observation Service (SOS) [OGC 06-009] ..............................................29 6.2.2 Sensor Alert Service (SAS) [OGC 05-098]..........................................................31 6.2.3 Sensor Planning Service (SPS) [OGC 05-089r2] .................................................33 6.2.4 Web Notification Service (WNS) [OGC 05-114] ...............................................34 6.2.5 Sensor Web Registry.....................................................................................35 7 Interrelationships....................................................................................................38 7.1 Dependencies on and references to SWE Common..........................................38 7.2 Dependencies on and references to SensorML .................................................39 7.3 Dependencies on and references to Observations .............................................39 7.4 Dependencies on and references to TML..........................................................39 ii Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved. OGC 06-021r1 7.5 Dependencies on and references to Geography Markup Language (GML) .....39 8 Typical Work Flows ..............................................................................................41 8.1 Discovery of SWE Services using a Registry ...................................................41 8.2 Registration of a new SWE Service in a Registry.............................................42 8.3 Request of discrete observation data.................................................................43 8.4 Request of streaming (out of band) observation data........................................44 8.5 Access to Sensor Descriptions ..........................................................................45 8.6 Data Processing using SensorML......................................................................46 8.7 Subscribing and Receiving Sensor Alerts .........................................................47 8.8 Tasking Sensor Systems....................................................................................49 9 Implementation examples ......................................................................................51 9.1 Using SWE services in a “star” network configuration ....................................51 10 Future Directions...................................................................................................59 10.1 OWS4 Potential SWE Directions......................................................................60 Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved. iii OGC 06-021r1 i. Preface Suggested additions, changes, and comments on this Discussion Paper are welcome and encouraged. Such suggestions may be submitted by email message or by making suggested changes in an edited copy of this document. The changes made in this document version, relative to the previous version, are tracked by Microsoft Word, and can be viewed if desired. If you choose to submit suggested changes by editing this document, please first accept all the current changes, and then make your suggested changes with change tracking on. ii. Submitting organizations The following organizations submitted this document to the Open Geospatial Consortium Inc. Image Matters, Inc. University of Alabama in Huntsville University of Muenster iii. Document contributor contact points All questions regarding this document should be directed to the editor or the contributors: CONTACT COMPANY ADDRESS Mike Botts University of ESSC/NSSTC Alabama in Huntsville, AL 35899 Huntsville Alex Robin University of ESSC/NSSTC Alabama in Huntsville, AL 35899 Huntsville John Davidson Image Matters 201 Loudoun St, SW Leesburg, VA 20175 Ingo Simonis University of Robert-Koch-Str. 26-28 Muenster 48149 Muenster Germany Simon Cox CSIRO ARRC Exploration PO Box 1130 and Mining Bentley WA 6102 Australia iv Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved. OGC 06-021r1 iv. Revision history Date Release Editor Primary clauses Description modified 2006-01-20 R1 meb throughout Initial draft 2006-02-13 R1 meb, ar throughout completed draft v. Changes to the OGC Abstract Specification The OpenGIS® Abstract Specification does not require changes to accommodate the technical contents of this document. vi. Future work Improvements in this document are desirable to account for status changes in the individual specifications and to outline further use cases within Appendix A. Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved. v OGC 06-021r1 Foreword There are no annexes to this document. This is an Informative document that describes the framework surrounding sensor web/network specification described in other OGC documents. Therefore, no Sections nor Annexes in this document are normative. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The OGC shall not be held responsible for identifying any or all such patent rights. vi Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved. OGC 06-021r1 Introduction In much the same way that HTML and HTTP standards enabled the exchange of any type of information on the Web, the Open Geospatial Consortium’s (OGC) Sensor Web Enablement (SWE) initiative is focused on developing standards to enable the discovery, exchange, and processing of sensor observations, as well as the tasking of sensor systems. The functionality that OCG has targeted within a sensor web includes: • Discovery of
Recommended publications
  • OGC Sensor Web Enablement
    Botts et al. OGC Sensor Web Enablement OGC® Sensor Web Enablement: Overview And High Level Architecture Mike Botts George Percivall Univ. of Alabama in Huntsville Open Geospatial Consortium, Inc. [email protected] [email protected] Carl Reed John Davidson Open Geospatial Consortium, Inc. Image Matters LLC [email protected] [email protected] ABSTRACT A precursor paper (also available as an OGC White Paper) provides a high-level overview of and architecture for the Open Geospatial Consortium (OGC) standards activities that focus on sensors, sensor networks, and a concept called the “Sensor Web”. This OGC focus area is known as Sensor Web Enablement (SWE). For readers interested in greater technical and architecture details, please download and read the OGC SWE Architecture Discussion Paper titled “The OGC Sensor Web Enablement Architecture” (OGC document 06-021r1). Keywords Sensor, OGC, “Sensor Web Enablement”, “sensor web”, transducer, geospatial, “web service”, SOA, “service oriented architecture”, imaging. INTRODUCTION A sensor network is a computer accessible network of many, spatially distributed devices using sensors to monitor conditions at different locations, such as temperature, sound, vibration, pressure, motion or pollutants1. A Sensor Web refers to web accessible sensor networks and archived sensor data that can be discovered and accessed using standard protocols and application program interfaces (APIs). Figure 1: Sensor Web Concept 1 Wikipedia - http://en.wikipedia.org/wiki/Wireless_sensor_network (Last viewed 18 March 2008) Proceedings of the 5th International ISCRAM Conference – Washington, DC, USA, May 2008 F. Fiedrich and B. Van de Walle, eds. 713 Botts et al. OGC Sensor Web Enablement In an Open Geospatial Consortium, Inc.
    [Show full text]
  • 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.
    [Show full text]
  • An Interoperable Multi-Sensor System for Healthcare
    2013 IEEE GCC Conference and exhibition, November 17-20, Doha, Qatar An Interoperable Multi-Sensor System For Healthcare Bassant Selim Youssef Iraqi Ho-Jin Choi Khalifa University Khalifa University KAIST Sharjah, United Arab Emirates Sharjah, United Arab Emirates Daejeon, South Korea Email: [email protected] Email: [email protected] Email: [email protected] Abstract—Pervasive healthcare systems, enabled by informa- an introduction to the sensor standards considered, section tion and communication technology (ICT), can allow the elderly IV presents the requirements and solutions that insure the and chronically ill to stay at home while being constantly adequate performance of our system, section V provides an monitored. Patient monitoring can be achieved by sensors and example of sensor Modeling Language description of a body sensor systems that are both worn by the patient and installed temperature sensor, section VI presents related works in the in his home environment. There is a large variety of sensors area of applying standards to healthcare monitoring systems available on the market that can all serve to this purpose. In order to have a system that is independent of the sensors that and finally section VII concludes this work. are used, standardization is the key requirement. This work aims to present a framework for healthcare monitoring systems based II. SYSTEM ARCHITECTURE on heterogeneous sensors. In order to achieve interoperability, standards are considered in the system design. The proposed system is composed of multiple hierarchical layers that are each responsible of monitoring different pa- Keywords—Heterogeneous Sensor Networks, SensorML, IEEE rameters of the patient’s health.
    [Show full text]
  • Semantic Sensor Observation Service
    Wright State University CORE Scholar The Ohio Center of Excellence in Knowledge- Kno.e.sis Publications Enabled Computing (Kno.e.sis) 5-2009 SemSOS: Semantic Sensor Observation Service Cory Andrew Henson Wright State University - Main Campus Josh Pschorr Wright State University - Main Campus Amit P. Sheth Wright State University - Main Campus, [email protected] Krishnaprasad Thirunarayan Wright State University - Main Campus, [email protected] Follow this and additional works at: https://corescholar.libraries.wright.edu/knoesis Part of the Bioinformatics Commons, Communication Technology and New Media Commons, Databases and Information Systems Commons, OS and Networks Commons, and the Science and Technology Studies Commons Repository Citation Henson, C. A., Pschorr, J., Sheth, A. P., & Thirunarayan, K. (2009). SemSOS: Semantic Sensor Observation Service. 2009 International Symposium on Collaborative Technologies and Systems: May 18-22, 2009, Baltimore, Maryland, USA, 44-53. https://corescholar.libraries.wright.edu/knoesis/333 This Article is brought to you for free and open access by the The Ohio Center of Excellence in Knowledge-Enabled Computing (Kno.e.sis) at CORE Scholar. It has been accepted for inclusion in Kno.e.sis Publications by an authorized administrator of CORE Scholar. For more information, please contact [email protected]. 1 SemSOS: Semantic Sensor Observation Service Cory A. Henson, Josh K. Pschorr, Amit P. Sheth, and Krishnaprasad Thirunarayan Kno.e.sis Center, Department of Computer Science and Engineering Wright State University, Dayton, OH 45435 [email protected], [email protected], [email protected], [email protected] enabled by semantic modeling and what advantages this Abstract provides to standard SOS.
    [Show full text]
  • OGC Sensorthings API FROST Server
    OGC SensorThings API and FROST Server® Michael Jacoby Open Geospatial Consortium http://www.opengeospatial.org ▪ International consortium ▪ over 522 companies, government agencies and universities ▪ “Geo-enable” mainstream IT ▪ Develop publicly available standards ▪ Web Map Service ▪ CityGML ▪ WaterML ▪ Earth Observations 2019-10-29 2 / 38 © Fraunhofer IOSB OGC & IoT? ▪ IoT deals with Sensors and Actuators ▪ Sensors and Actuators have Location ▪ OGC Sensor Web Enablement (SWE) ▪ Enable developers to make all types of sensors and sensor data repositories discoverable, accessible and useable via the Web ▪ Since 1990 by NASA ▪ Since 2001 in OGC ▪ SensorML Sensor Observation Service (SOS) Sensor Planning Service (SPS) Observations & Measurements (O&M) ▪ Sensor Data & Metadata ©OGC: http://www.opengeospatial.org/ogc/markets-technologies/swe 2019-10-29 3 / 38 © Fraunhofer IOSB From SWE to SensorThings ▪ “Old” SWE Standards ▪ XML Encoded ▪ SOAP bindings ▪ Complex in use ▪ No easy browsing ▪ No pagination ▪ No pub/sub Time for an update → SensorThings API 2019-10-29 4 / 38 © Fraunhofer IOSB OGC SensorThings API https://www.opengeospatial.org/standards/sensorthings https://github.com/opengeospatial/sensorthings ▪ A standard for exchanging sensor data and metadata ▪ Historic data & current data ▪ JSON Encoded ▪ RESTful ▪ Adapting OASIS OData URL patterns and query options ▪ Supporting MQTT pub/sub ▪ Easy to use & understand ▪ Discoverable with only a web browser 2019-10-29 5 / 38 © Fraunhofer IOSB OGC SensorThings API ▪ Divided into multiple Parts
    [Show full text]
  • DGIWG Service Architecture
    DGIWG – 306 DGIWG Service Architecture Document Identifier: TCR-DP-07-041-ed2.0.1-DGIWG_Service_Architecture Publication Date: 05 November 2008 Edition: 2.0.1 Edition Date: 05 November 2008 Responsible Party: DGIWG Audience: Approved for public release Abstract: This document provides architecture guidance to DGIWG. Copyright: (C) Copyright DGIWG, some rights reserved - (CC) (By:) Attribution You are free: - to copy, distribute, display, and perform/execute the work - to make derivative works - to make commercial use of the work Under the following conditions: - (By:) Attribution. You must give the original author (DGIWG) credit. - For any reuse or distribution, you must make clear to others the license terms of this work. Any of these conditions can be waived if you get permission from the copyright holder DGIWG. Your fair use and other rights are in no way affected by the above. This is a human-readable summary of the Legal Code (the full license is available from Creative Commons <http://creativecommons.org/licenses/by/2.0/ >). DN:07-041 05 November 2008 Contents Executive summary ..................................................................................................... 1 Acknowledgement ....................................................................................................... 1 1 Introduction .......................................................................................................... 2 1.1 Scope .............................................................................................................
    [Show full text]
  • Current Status of Standards for Augmented Reality
    Current Status of Standards for Augmented Reality Christine Perey1, Timo Engelke2, Carl Reed3 Abstract This chapter discusses the current state, issues, and direction of the development and use of international standards for use in Augmented Reality (AR) applications and services. More specifically, the paper focuses on AR and mobile devices. Enterprise AR applications are not discussed in this chapter. There are many existing international standards that can be used in AR applications but there may not be defined best practices or profiles of those standards that effectively meet AR development requirements. This chapter provides information on a number of standards that can be used for AR applications but may need further international agreements on best practice use. Introduction Standards frequently provide a platform for development; they ease smooth opera- tion of an ecosystem in which different segments contribute to and benefit from the success of the whole, and hopefully provide for a robust, economically-viable, value chain. One of the consequences of widespread adoption of standards is a baseline of interoperability between manufacturers and content publishers. Anoth- er is the ease of development of client applications. In most markets, standards emerge during or following the establishment of an ecosystem, once a sufficient number of organizations see market and business value in interoperating with the solutions or services of others. Augmented Reality (AR) has arisen as a result of two driving forces: a push force brought about by convergence of improvements in technology (networking, com- putational, devices, display technology, sensors, etc) and a pull force arising from a critical mass of users who—once enabled with lighter, more powerful and less 1 Christine Perey, Spime Wrangler, PEREY Research & Consulting 2 Timo Engelke, Fraunhofer IGD 3 Carl Reed, PhD, CTO, Open Geospatial Consortium expensive technologies—seek knowledge and information in context with their surroundings.
    [Show full text]
  • Integrating the Ogc Sensor Web Enablement Framework Into the Ogc Catalogue
    INTEGRATING THE OGC SENSOR WEB ENABLEMENT FRAMEWORK INTO THE OGC CATALOGUE S.Jirka a, *, D. Nüst a, J. Schulte a, F. Houbie b a Westfälische Wilhelms-Universität Münster, Institut für Geoinformatik, Weseler Straße 253, 48151 Münster, Germany - (jirka, daniel.nuest, janschulte)@uni-muenster.de b ERDAS SA, Quai Timmermans 14/01, 4000 Liège, Belgium - [email protected] KEY WORDS: Internet/Web, Interoperability, Metadata, Sensor, Software, Standards ABSTRACT: The Sensor Web Enablement (SWE) architecture of the Open Geospatial Consortium (OGC) has reached a broad acceptance. However, although the core specifications reached a mature state, the integration of a cataloguing service for sensors has not yet been achieved. Previous work focused on registries that address the specifics of dynamic sensor networks, on mechanisms for handling the semantics of phenomena and on metadata models based on the Sensor Model Language (SensorML). This work describes how existing elements supporting sensor discovery can be coupled with the already well established OGC Catalogue Service (CSW). The approach presented in this work relies on a SensorML profile specifying metadata necessary and sufficient for sensor discovery. SensorML documents that conform to the profile are automatically harvested from SWE services by a lower level registry and are subsequently transformed into an information model supported by the CSW. Finally the metadata is pushed into CSW instances and becomes available through the CSW interface. In summary, this work presents for the first time a working example how resources provided through SWE services can automatically be published through common OGC Catalogue Service instances. We expect that the presented approach is an important step in order to achieve a full integration of SWE components into spatial data infrastructures and to offer SWE services to a broader audience.
    [Show full text]
  • Workshop Proceedings ENABLING SENSOR
    Ref. No. [UMCES]CBL 07-079 Alliance for Coastal Technologies Indexing No. ACT-06-07 Workshop Proceedings ENABLING SENSOR* INTEROPERABILITY Portland, Maine October 16-18, 2006 Funded by NOAA’s Coastal Services Center through the Alliance for Coastal Technologies (ACT) * For the purpose of the workshop, participants spoke in terms of “instruments” rather than “sensors,” defining an instrument as a device that contains one or more sensors or actuators and can convert signals from analog to digital. An ACT Workshop Report Enabling Sensor Interoperability Portland, Maine October 16-18, 2006 Sponsored by the Alliance for Coastal Technologies (ACT) and NOAA’s Center for Coastal Ocean Research in the National Ocean Service. Hosted by ACT Partner, Gulf of Maine Ocean Observing System. ACT is committed to develop an active partnership of technology developers, deliverers, and users within regional, state, and federal environmental management communities to establish a testbed for demonstrating, evaluating, and verifying innovative technologies in monitoring sensors, platforms, and software for use in coastal habitats. Enabling Sensor Interoperability ..................................................................................................... i TABLE OF CON T EN T S Executive Summary .........................................................................................................................1 Alliance for Coastal Technologies ...................................................................................................2
    [Show full text]
  • Exploring the Use of the Semantic Web for Discovering, Retrieving and Processing Data from Sensor Observation Services Ivo De Liefde June 2016
    MSc thesis in Geomatics Exploring the use of the semantic web for discovering, retrieving and processing data from Sensor Observation Services Ivo de Liefde June 2016 EXPLORINGTHEUSEOFTHESEMANTICWEBFOR DISCOVERING,RETRIEVINGANDPROCESSINGDATAFROM SENSOROBSERVATIONSERVICES A thesis submitted to the Delft University of Technology in partial fulfillment of the requirements for the degree of Master of Science in Geomatics by Ivo de Liefde June 2016 Ivo de Liefde: Exploring the use of the semantic web for discovering, retrieving and processing data from Sensor Observation Services (2016) cb This work is licensed under a Creative Commons Attribution 4.0 Inter- national License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/. The work in this thesis was made in the: Department of GIS Technology OTB Research Institute for the Built Environment Faculty of Architecture & the Built Environment Delft University of Technology Supervisors: Drs. M.E. de Vries Dr.ir. B.M. Meijers Co-reader: Dr. Dipl.-Ing. S. Zlatanova ABSTRACTDevelopments such as smart cities, the Internet of Things (IoT) and the Infras- tructure for Spatial Information in Europe (INSPIRE) are causing a growing amount of observation data to be produced. The Open Geospatial Con- sortium (OGC) has developed Sensor Web Enablement (SWE) standards for modelling and publishing this data online. However, their use is currently limited to geo information specialists, who have knowledge about which data services are available and how to access them. With the use of the semantic web, online processes can automatically find and understand ob- servation metadata. This opens up the SWE services to a large user audience.
    [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]
  • Open Geospatial Consortium Activities – Reichardt
    ® ® Driving geospatial interoperability - communities of interest Mark E. Reichardt President & CEO [email protected] +1 301 840-1361 © 2012 Open Geospatial Consortium www.opengeospatial.org Cross-Boundary / Limited or No Connectivity Information Sharing Continues to be one of our biggest challenges! Source: www.fao.org/docrep/008/ae929e/ae929e03.htm Source: David Rydevik, Thailand Tsunami, 2004 OGC® Aeronautical Information Management (AIM) (OGC Web Services Phase 6 & 7 Testbeds) • Develop and test standards‐based service‐ oriented architecture to support the provision of aeronautical information directly to flight decks and Electronic Flight Bags (EFB) • Support vision for Aeronautical Information Management – Interconnected systems with many actors and many users – Need for real-time information used in flight planning, navigation, rerouting, etc. – Right information at the right time at the right place to the right user – End-to-end management of information © 2012, Open Geospatial Consortium Aeronautical Information Management Architecture (OGC Web Services Phase 6 Testbed) NNEW – NextGEN Network Enabled Weather TAF – Terminal Aerodrome Forecast WXXM – Weather Info. Exchange Model WFS – OGC Web Feature Service © 2011, Open Geospatial Consortium Community and Use Case Driven Meteorology and Oceanography Domain Working Group Source: http://external.opengeospatial.org/twiki_public/MetOceanDWG/MetOceanUseCases ® OGC © 2012 Open Geospatial Consortium. 9 OneGeology • Distributed, interoperable geologic information • Leverages open standards: • OGC Web Map Service • OGC Web Feature Service • Geography Markup Language • OGC Observations & Measurements • GeoSCIML (GML Schema) • Broad agreement between geologic surveys, organizational bodies • http://onegeology.org ® OGC © 2012, Open Geospatial Consortium OneGeology Addressing Semantic Differences GeoSciML – an OGC Geography Markup Language application schema for the sharing of Geologic information Canada USA France United Kingdom Sweden Australia ….
    [Show full text]