Introduction to Open Geospatial Standards
Total Page：16
File Type：pdf, Size：1020Kb
Load more
Recommended publications
-
Understanding and Working with the OGC Geopackage Keith Ryden Lance Shipman Introduction
Understanding and Working with the OGC Geopackage Keith Ryden Lance Shipman Introduction - Introduction to Simple Features - What is the GeoPackage? - Esri Support - Looking ahead… Geographic Things 3 Why add spatial data to a database? • The premise: - People want to manage spatial data in association with their standard business data. - Spatial data is simply another “property” of a business object. • The approach: - Utilize the existing SQL data access model. - Define a simple geometry object. - Define well known representations for passing structured data between systems. - Define a simple metadata schema so applications can find the spatial data. - Integrate support for spatial data types with commercial RDBMS software. Simple Feature Model 10 area1 yellow Feature Table 11 area2 green 12 area3 Blue Feature 13 area4 red Geometry Feature Attribute • Feature Tables contain rows (features) sharing common properties (Feature Attributes). • Geometry is a Feature Attribute. Database Simple Feature access Query Connection model based on SQL Cursor Value Geometry Type 1 Type 2 Spatial Geometry (e.g. string) (e.g. number) Reference Data Access Point Line Area Simple Feature Geometry Geometry SpatialRefSys Point Curve Surface GeomCollection LineString Polygon MultiSurface MultiPoint MultiCurve Non-Instantiable Instantiable MultiPolygon MultiLineString Some of the Major Standards Involved • ISO 19125, Geographic Information - Simple feature access - Part 1: common architecture - Part 2: SQL Option • ISO 13249-3, Information technology — Database -
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 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. -
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. -
"The Global Spatial Data Infrastructure Association - Advancing a Location Enabled World"
GSDI and IGS Newsletter, Vol. 4, No. 2 News from the GSDI Association and the International Geospatial Society Vol. 4, No. 2, 2014 "The Global Spatial Data Infrastructure Association - Advancing a Location Enabled World" ASSOCIATION NEWS Association since 2010. Within local conservation circles he was primarily known for co-directing, with his partner GSDI Association Board Member Mark Becker Dies of 30 years Lori Charkey, the Bergen Save the Watershed in Tragic Accident Action Network (Bergen SWAN).” The GSDI Association learned of the tragic death of CIESIN Associate Director Mark Becker at the age of 53, on 26 February 2014 in a multi-vehicle accident on the New York State Thruway in Woodbury, NY. Mark was the GSDI Board member representing ‘GSDI Related Global Initiatives’ and was a valued member of the GSDI Outreach and Membership Committee, where his input and insight will be much missed by his colleagues at the Association. Below is an extract from the tribute to Mark from CIESIN. “In his 15 years at CIESIN Mark made contributions that will be felt for a long time. He began his CIESIN career in Mark Becker leading a teacher training workshop for the February 1999, and was soon appointed head of the CHANGE Viewer mapping tool. Pictured behind him is Geospatial Applications Division. … In many ways he Amy Work, IAGT, who helped develop the tool. Palisades, helped bring GIS to Columbia, as manager of the GIS New York, July 2013. Source: CEISIN Service Center and ESRI site license. He helped install many of the early GIS labs on campus and helped train See the full tribute to Mark on the CIESIN website at many of the people who operated them. -
OGC Web Coverage Processing Service (WCPS)
Open Geospatial Consortium Inc. Date: 2009-03-25 Reference number of this OGC® Project Document: OGC 08-068r2 Version: 1.0.0 Category: OpenGIS® Interface Standard Editor: Peter Baumann Web Coverage Processing Service (WCPS) Language Interface Standard Copyright © 2009 Open Geospatial Consortium, Inc. All Rights Reserved. To obtain additional rights of use, visit http://www.opengeospatial.org/legal/. Document type: OpenGIS® Interface Standard Document subtype: Extension Package Document stage: Approved Document language: English 1 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. If you modify the Intellectual Property, all copies of the modified Intellectual Property must include, in addition to the above copyright notice, a notice that the Intellectual Property includes modifications that have not been approved or adopted by LICENSOR. THIS LICENSE IS A COPYRIGHT LICENSE ONLY, AND DOES NOT CONVEY ANY RIGHTS UNDER ANY PATENTS THAT MAY BE IN FORCE ANYWHERE IN THE WORLD. THE INTELLECTUAL PROPERTY IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. -
Geospatial Artificial Intelligence
Geospatial Artificial Intelligence An introduction to pipelining for automated geospatial analysis, modelling and AI Simon D. Wenkel March 30, 2019 DRAFT 6 Selecting file formats Some of the biggest questions we have to ask ourselves when we start a geospatial project is what file formats do we want to use. There are many out there and some have their specific advantages for certain niches. GDAL/OGR [1] lists 96 vector formats and 155 raster formats. That is a lot to choose from. Comment 6.1 Utilizing normal files and databases for geospatial data In theory we could use any kind of file or database to store geospatial data as long as we know how we stored it and how the projection is linked to coordinates. Since the same coordinates will lead to different positions for different projections this can be dangerous and therefore is not recommended. However, we can see this often especially with text files and if they are not documented properly we end up with a big mess. 6.1 Databases vs. single files First, we have to decide on whether we want single files or a real database to store our data. The main challenge with geospatial data stored in single files is that we end up having multiple files that make a “single” file. If one of them is lost or not copied correctly we may are doomed if this is an essential one. The big advantage of using single files to store geospatial data is that if we manage to copy them correctly everyone can work with them without having deep knowledge on setting up databases. -
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 -
Linkage of OGC WPS 2.0 to the E-Government Standard Framework in Korea: an Implementation Case for Geo-Spatial Image Processing
International Journal of Geo-Information Article Linkage of OGC WPS 2.0 to the e-Government Standard Framework in Korea: An Implementation Case for Geo-Spatial Image Processing Gooseon Yoon 1, Kwangseob Kim 2 and Kiwon Lee 3,* 1 Department of Information Systems Engineering, Hansung University, Seoul 136-792, Korea; [email protected] 2 Department of Information and Computer Engineering, Hansung University, Seoul 136-792, Korea; [email protected] 3 Department of Electronics and Information Engineering, Hansung University, Seoul 136-792, Korea * Correspondence: [email protected]; Tel.: +82-2-760-4254 Academic Editors: Ozgun Akcay and Wolfgang Kainz Received: 15 October 2016; Accepted: 16 January 2017; Published: 20 January 2017 Abstract: There are many cases wherein services offered in geospatial sectors are integrated with other fields. In addition, services utilizing satellite data play important roles in daily life and in sectors such as environment and science. Therefore, a management structure appropriate to the scale of the system should be clearly defined. The motivation of this study is to resolve issues, apply standards related to a target system, and provide practical strategies with a technical basis. South Korea uses the e-Government Standard Framework, using the Java-based Spring framework, to provide guidelines and environments with common configurations and functions for developing web-based information systems for public services. This web framework offers common sources and resources for data processing and interface connection to help developers focus on business logic in designing a web system. In this study, a geospatial image processing system—linked with the Open Geospatial Consortium (OGC) Web Processing Service (WPS) 2.0 standard for real geospatial information processing, and based on this standard framework—was designed and built utilizing fully open sources. -
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 ............................................................................................................. -
Sensor Web and Geoprocessing Services for Pervasive Advertising
Sensor Web and Geoprocessing Services for Pervasive Advertising Theodor Foerster¹, Arne Bröring², Simon Jirka², Jörg Müller² ¹International Institute for Geoinformation Science and Earth Observation, ITC, Enschede, the Netherlands [email protected] ²Institute for Geoinformatics, University of Muenster, Muenster, Germany {arne.broering,simon.jirka,joerg.mueller}@uni-muenster.de Abstract: Pervasive advertising attracts attention in research and industry. Sensor information in this context is considered to improve the content communication of Pervasive Environments. This paper describes an architecture for integrating sensor information into Pervasive Environments. The sensor information is accessible through an abstraction layer, the Sensor Web, which is based on Web Service technology. The Sensor Web provides access to any deployed sensor for any compliant infrastructure, such as a Pervasive Environment. It thereby does not only access sensors that are deployed specifically for this system, but any sensor in the world that is available through the Sensor Web. In order to extract specific sensor information from the available sensor data, Geoprocessing Services are deployed as an intermediate component in the proposed architecture. 1 Introduction Advertising currently introduces novel pervasive technologies installed in urban spaces (e.g. digital signage, mobile phones). These new media enable a) to show live data about the environment collected by sensors (e.g. weather forecast) and b) to adapt information presentation to the context, as determined by sensors (e.g. ads for ice cream, when the sun is shining). Currently, local and individual sensors are deployed at the devices that show the adverts. For example, cameras are installed on digital signs and GPS devices are installed in cell phones. -
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.