George Percivall Chief Engineer and CTO

Similar presentations


Presentation on theme: "George Percivall Chief Engineer and CTO"— Presentation transcript:

1 George Percivall Chief Engineer and CTO gpercivall@myogc.org
Getting more from remote sensing data using OGC standards ASPRS GeoBytes George Percivall Chief Engineer and CTO © 2016 Open Geospatial Consortium

2 © 2016 Open Geospatial Consortium
My perspective Physics, remote sensing, systems engineering NASA weather satellite and information systems Standards for science and engineering OGC CTO © 2016 Open Geospatial Consortium

3 The OGC Mission Global forum for collaboration of developers and users of spatial data products and services Advance development of international standards for geospatial interoperability. For those of you that are new to OGC, the OGC is a global forum … We believe in A world in which everyone benefits from the use of geospatial information and supporting technologies. OGC members developments occur in several programs Source: Space Time Toolkit Source: One Geology Source: 3d Stadtmodell Berlin © 2016 Open Geospatial Consortium 3

4 © 2016 Open Geospatial Consortium
Outline of Talk Standards-Based Remote Sensing Geomatics Sensor Web Enablement (SWE) Coverages and Web Coverage Service (WCS) Geospatial Big Data Policies and Frameworks © 2016 Open Geospatial Consortium

5 © 2016 Open Geospatial Consortium
Question 1 Are you familiar with OGC and its standards? Very familiar Somewhat familiar Not familiar © 2016 Open Geospatial Consortium

6 Standards-Based Remote Sensing Geomatics
© 2016 Open Geospatial Consortium

7 Copyright © 2016 Open Geospatial Consortium
Geomatics Geomatics: Multi-disciplinary science and technology that integrates all means of spatiotemporal data acquisition, information production, and knowledge discovery - as well as location-based services - regarding the physical processes and human activities related to the Earth. Geomatics includes Remote Sensing and Photogrammetry Copyright © 2016 Open Geospatial Consortium

8 Geographic imagery scenario
ISO/TS :2008 Geographic information — Reference model — Part 2: Imagery Copyright © 2016 Open Geospatial Consortium

9 © 2016 Open Geospatial Consortium
What is a Standard? “An agreed way of doing something” EC: Practical standards guide for researchers - en © 2016 Open Geospatial Consortium 9

10 © 2016 Open Geospatial Consortium
What is a Standard? “An agreed way of doing something” Standards are distilled wisdom of people with expertise in their subject matter and who know the needs of the organizations they represent – people such as manufacturers, sellers, buyers, customers, trade associations, users or regulators. Standards are knowledge. They are powerful tools that can help drive innovation and increase productivity. They can make organizations more successful and people’s everyday lives easier, safer and healthier. EC: Practical standards guide for researchers - en © 2016 Open Geospatial Consortium 10

11 © 2016 Open Geospatial Consortium
What is an OGC Standard? Document; Established by consensus; Approved by OGC membership (balance of interest, all members have vote) Provides, rules, guidelines or characteristics Implementable in software Open Standards are not the same as Open Source software See: OGC/OSGeo Paper on Open Source and Open Standards: OGC standards are Open Standards Freely and publicly available No license fees Vendor neutral © 2016 Open Geospatial Consortium 11 11

12 OGC Services Architecture
Visualization / Decision Tools and Applications GeoAPI OpenLS SLD SE Data Models and Encodings WMC FE GML GeoXACML KML CityGML OpenGeoSMS IndoorGML GeoSparql WaterML GeoPackage NetCDF GMLJP2 Geospatially Enabled Metadata Discovery Services CSW OpenSearch Geo ebRIM Other Services Workflow, Alerts, Security Other Data Processing Services OpenMI WPS TJS WCPS WMS WMTS WFS Simple Features Access Access Services Geospatial Feature Data Geospatial Browse/Maps Geospatial Coverage Data WCS Sensors Puck SOS SPS O&M SensorML Sensor Web Enablement Discover Task Access Acronym List: Catalog Web Service (CSW) - Support the ability to publish and search collections of descriptive information (metadata) for data, services, and related information objects. Web Map Service (WMS) - XML encoding for the transport and storage of geographic information modeled according to the conceptual modeling framework including both the spatial and non-spatial properties of geographic features. Web Map Tile Service (WMTS) - Serves digital maps using predefined image tiles and complements the existing Web Map Service providing flexibility in the client request enabling clients to obtain the precise final image required. Web Coverage Service (WCS) – Provides access to detailed and rich sets of geospatial information in forms that are useful for client-side rendering, multi-valued coverages, and input into scientific models and other clients. Web Coverage Service Transactional (WCS-T) - Enables clients to add, modify, and delete grid coverages that are available from a WCS server. Web Feature Service (WFS) – Defines the interfaces for data access and manipulation operations on geographic features, feature information behind a map image. Web Feature Service Transactional (WFS-T) - Enables clients to add, modify, and delete feature data that are available from a WFS server. Sensor Planning Service (SPS) - Enables a client to determine collection feasibility for a desired set of collection requests for sensors and directly task those sensors. Sensor Observation Service (SOS) - Interface for requesting, filtering, and retrieving observations and sensor system information. Sensor Model Language (SML) - Enables users to access sensors; their location, their capabilities, and the data they acquire along with the ability to process the data through a standards-based, non-proprietary web interface. Observation & Measurements (O&M) - Specifies the core model, framework, and encoding for measurements and observations. Observation & Measurements XML (O&M XML) - XML schemas for observations, and for features involved in sampling when making observations. Geo eXtended Access Control Markup Language (GeoXACML) - An extension to the eXtensible Access Control Markup Language (XACML) Policy Language that supports the declaration and enforcement of access restrictions on geographic information. Styled Layer Descriptor (SLD) – Provides analysts control of the visual portrayal of the data with which they work. Symbology Encoding (SE) - an XML language to encode user-defined styling information that can be applied to digital Feature and Coverage data. Geography Markup Language (GML) - XML encoding for the transport and storage of geographic information modeled according to the conceptual modeling framework. KeyHole Markup Language (KML) - XML language focused on geographic visualization and used to encode and transport representations of geographic data for display in web browser, including annotation of maps and images. Filter Encoding (FE) - an XML encoding of the OGC Common Catalog Query Language (CQL) as a system neutral query representation. Web Map Context (WMC) - XML schemas for observations, and for features involved in sampling when making observations. Table Join Service (TJS) –Provides a mechanism to expose corporate tabular data, with geographic identifiers so that it can be discovered, accessed, and merged with spatial data to enable mapping or geospatial analysis. Table Join Service Transactional (TJS-T) - Enables clients to add, modify, and delete tabular data available from a TJS server. Web Processing Service (WPS) - WPS provides client access across a network to pre-programmed calculations and/or computation models that operate on spatially referenced data. Geo Short Message Service (GeoSMS) - Facilitate communication of location content between different LBS (Location-Based Service) devices or applications by extending Short Messaging Service (SMS). GeoSynchronization Service (GeoSynch) - Enables data collectors to submit new data or make modifications to existing data without directly affecting the data in the provider's data store(s) until validation has been applied. © 2016 Open Geospatial Consortium

13 Product Implementation and Compliance
Total = # of products declaring Implementation  Comp = # of products Certified as OGC Compliant As of 21 July 2016 Full list: © 2016 Open Geospatial Consortium

14 Sensor Web Enablement (SWE)
© 2016 Open Geospatial Consortium

15 OGC Sensor Web Enablement
Airborne Imaging Device Sensors connected to and discoverable on the Web Sensors have position & generate observations Sensor descriptions available Services to task and access sensors Local, regional, national scalability Enabling the Enterprise Satellite-borne Imaging Device Environmental Monitor Webcam Vehicles As Sensor Probe Health Monitor © 2016 Open Geospatial Consortium

16 Model of a Sensor System
Sensor Web Enablement Architecture, OGC document 06-021r4 © 2016 Open Geospatial Consortium

17 SWE Information Models and Schema
SWE Information Models and Encodings Sensor Model Language (SensorML) Observations and Measurements (O&M) SWE Common SWE Web Services Sensor Observation Service (SOS) Sensor Planning Service (SPS) Sensor Alert Service (SAS) PUCK DIB Applications - External Tasking, Mission Management, Distributed Sensor Planner Sensor Planning Service Provides a standard interface for planning and tasking sensors. SPS interface operations include: DescribeCollectionRequest() GetFeasibility() SubmitRequest() UpdateRequest() CancelRequest() GetStatus() ACTM – Airborne Common Tasking Message Created to reflect the tasking information used by all DoD and IC platforms. Provided as input to OWS-3 in support of the SPS maturation. Sensor Alert Service Under development in an OGC Interoperability Experiment SWE Standards are deployed in operational systems – TRL Level 9 © 2016 Open Geospatial Consortium

18 On-demand Geolocation using SensorML
AMSR-E SSM/I TMI & MODIS footprints MAS TMI Geolocation of satellite and airborne sensors using SensorML Cloudsat LIS

19 © 2016 Open Geospatial Consortium
UAV Geomatics UAVs bring new geographic information to many application domains UASs similar to other geographic imagery systems so existing frameworks are applicable But challenges unique to UASs exist in processing and creation of geospatial products Challenges motivate use of existing standards and extending standards COMMON APPROACH TO GEOPROCESSING OF UAV DATA ACROSS APPLICATION DOMAINS, ISPRS - International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences}, V. XL-1/W4, 2015,pp , ISPRS UAV-g2015 Conference © 2016 Open Geospatial Consortium

20 © 2016 Open Geospatial Consortium
Empire Challenge OV-1 © 2016 Open Geospatial Consortium

21 Tigershark UAV in Empire Challenge 2008
OpenGL SensorML-enabled Client SLD Tigershark SOS JP2 NAV Tigershark SOS offerings served in O&M: (1) time-tagged video frames (in JP2) (2) aircraft navigation (lat, lon, alt, pitch, roll, true heading) SensorML process chain (using CSM frame sensor model) geolocates streaming imagery on-the-fly Source: Mike Botts © 2016 Open Geospatial Consortium

22 Challenges with recent UAS popularity motivate the use of standards
Diversity of alternatives in UAVs show a lack of standardization at all levels: sensors, platforms, processing To advance, UASs need to increase use of existing standards and in some cases new standards will need to be developed. Standards for geographic observations are quite mature and UASs benefit from using them © 2016 Open Geospatial Consortium

23 Managing UAS complexity
Manage proliferation of sensors on UAV platforms Mission planning: after the most appropriate UAV is determined, it is time to choose which kind of sensor will be accompany to the UAV. Using SensorML to manage specifications Platforms: helicopter, quadcopter, blimp and airplane Sensors: micro analog, HD camera, lowlight and thermal camera In a database to support processing, e.g., MATLAB, BPEL Source: C. Avci,, Halmstad University © 2016 Open Geospatial Consortium

24 Framework to combine UAS with other sensors
Precision farming: variety of vendor-specific sensor systems, control units and processing software SWE-based infrastructure: control, access, transmission and storage of of sensor data for web services Field trial proved applicability of the infrastructure. SWE infrastructure for precision farming (Source: Geipel) © 2016 Open Geospatial Consortium

25 Geospatial Processing, Analysis, Workflow
Web Processing Service – WPS OGC Web Service workflow for algorithms Change detection, coordinate transformation, predictive models, simulation, geospatial analysis... Geoprocessing Workflow © 2016 Open Geospatial Consortium © 2015 Open Geospatial Consortium 25

26 OGC SWE vs WCS SWE: high flexibility to accommodate all sensor types → upstream integration Coverages/WCS one generic schema for all coverage types; scalable; versatile processing → downstream services Ingest/ Archive SWE Coverages Semantic Web

27 Coverages: WCS, WCPS, Encodings
© 2016 Open Geospatial Consortium

28 Big Data Variety: Coverages
n-D "space/time-varying phenomenon" [ISO 19123, OGC r2] «FeatureType» Abstract Coverage Grid Coverage MultiSolid Coverage Referenceable GridCoverage MultiCurve Coverage MultiSurface Coverage MultiPoint Coverage Rectified GridCoverage © 2016 Open Geospatial Consortium

29 Web Coverage Service (WCS)
WCS Core: Simple & efficient access to spatio-temporal coverages, in any suitable format subset = trim | slice WCS Extensions: additional, optional functionality facets WCS Application Profiles: domain-oriented bundling © 2016 Open Geospatial Consortium 29

30 Coverage Implementation
WCS 2: Big Picture Abstract Topic 6 SWE Common OWS Common Coverage Implementation Schema WCS Core Core Format Encoding Data Model Service Protocol Binding Usability GeoTIFF netCDF JPEG2000 etc. GRIB2 GMLJP2 WCS-T GET-KVP Processing POST-XML Extensions Range Subsetting SOAP JPIP Scaling REST CRS Interpolation Application Profiles data service EO-WCS MetOcean-WCS © 2016 Open Geospatial Consortium

31 OGC WCPS: Analyzing Datacubes
Web Coverage Processing Service (WCPS) = spatio-temporal datacube analytics language "From MODIS scenes M1, M2, M3: difference between red & nir, as TIFF" …but only those where nir exceeds 127 somewhere for $c in ( M1, M2, M3 ) where some( $c.nir > 127 ) return encode( $c.red - $c.nir, “image/tiff“ ) Enabling data/metadata integration © 2016 Open Geospatial Consortium

32 Moving to Global-scale Analysis
Traditional GIS and image analysis approaches assume flat earth geometries = simpler code… but data is warped to fit the “flattened” view of the Earth. OK for local scales (where approximate Earth surface is relatively flat) But Fails at larger scales (where curvature of the Earth becomes significant.) © 2016 Open Geospatial Consortium

33 Discrete Global Grid Systems
“…a spatial reference system that uses a hierarchical tessellation of cells to partition and address the globe. DGGS are characterized by the properties of their cell structure, geo-encoding, quantization strategy and associated mathematical functions.” OGC DGGS Candidate Standard © 2016 Open Geospatial Consortium

34 Standardising Discrete Global Grid Systems
Different Cell Shapes Square = Familiar Triangular = Fast Hexagonal = Fineness of Fit Unique Cell Indices Hierarchy-based, Space-filling Curve, Axes-based or Encoded Address nD Spatial Analyses 1D Array Processes 00 01 02 03 10 11 12 13 20 21 22 23 30 31 32 33 © 2016 Open Geospatial Consortium

35 © 2016 Open Geospatial Consortium
Point Clouds Many types of point clouds: LiDAR/laser, bathymetric, meteorologic, photogrammetric… OGC Point Cloud Working Group established in July 2015 © 2016 Open Geospatial Consortium

36 Point Cloud Survey Results
Questions range: storage, transfer, size, tools, etc. 188 responses from 175 different organizations Based on Survey, priorities for the OGC DWG are: Further collaborate with ASPRS on LAS Explore HDF5 as format for Point Cloud data Interoperable steaming Point Cloud webservices © 2016 Open Geospatial Consortium

37 © 2016 Open Geospatial Consortium
Question 2 Are you working with open standards for remote sensing geoinformatics? Actively involved in standards development Use standards regularly Familiar with standards Never use standards © 2016 Open Geospatial Consortium

38 © 2016 Open Geospatial Consortium
Geospatial Big Data © 2016 Open Geospatial Consortium

39 Big Geospatial Data 1PB in 1995 required a large building
1PB in 2015 requires a 1 car garage EROS Data Center, Sioux Falls, SD CyberGIS at NCSA Univ. of Illinois © 2016 Open Geospatial Consortium

40 Trends in Distributed Computing for Geospatial
Past Big data centers holding national archives It was new (~1994) to have a data center for multiple missions Catalogue discovery; Download by FTP Web mapping innovation – Landsat WMS Global Mosaic, Jan 2004 Emerging Commercial cloud hosting of large archives, local processing Currently not considering portability and open processing interfaces Catalogue/semantic discovery; Download by FTP/Linked Data WMS for many datasets – NASA GIBS Web Service access to data in archives Proliferation of APIs. Degradation of interoperability. © 2016 Open Geospatial Consortium

41 Use Cases for Big Geo Data
High Velocity Ingest Geospatial Databases GeoAnalytics, Machine Learning Spatial Modeling IoT Message Streaming Entity-oriented Spatial-temporal analytics Built environment models Array databases Grid-oriented Spatial-temporal analytics Social Media Message Processing Users and consuming apps Observation Sources NoSQL databases Integrated environmental models Feature Fusion ETL Stream processing using RDF Graph databases Modeling and simulation Remote sensed data processing Wide Area Motion Imagery SQL databases Machine Learning © 2016 Open Geospatial Consortium

42 Location Powers: Big Data
Tuesday 20th September Orlando, Florida #LPBigData © 2016 Open Geospatial Consortium

43 © 2016 Open Geospatial Consortium
Policy and Frameworks © 2016 Open Geospatial Consortium

44 Federated Remote Sensing Data Systems
GEOSS 10 Year Plan System of systems requires open, consensus standards. Multiple organizations began been preparing for this challenge before GEOSS was defined Standards and common practices have been developed by organizations like ISPRS, IEEE and OGC. (GEOSS-OGC, 2010.) Common Framework for Earth Observation Data US President’s Office of Science and Technology Policy (OSTP, 2016) – US GEO “By standardizing protocols for finding, accessing, and using Earth-observation data, the Common Framework will make it easier to obtain and assemble data from diverse sources for improved analysis, understanding, decision-making, community resilience, and commercial use.” © 2016 Open Geospatial Consortium

45 US OSTP - Common Framework for Earth Observation Data
© 2016 Open Geospatial Consortium

46 ESA Heterogeneous Mission Accessibility
Indispensable resource for organizations with EO assets that wish to connect to and build a local to global system of systems © 2016 Open Geospatial Consortium

47 ESA Heterogeneous Mission Accessibility
© 2016 Open Geospatial Consortium

48 © 2016 Open Geospatial Consortium
Outline of Talk Standards-Based Remote Sensing Geomatics Sensor Web Enablement (SWE) Coverages and Web Coverage Service (WCS) Geospatial Big Data Policies and Frameworks © 2016 Open Geospatial Consortium

49 For Details on OGC Standards…
Freely available George Percivall gpercivall at opengeospatial.org @percivall © 2016 Open Geospatial Consortium


Download ppt "George Percivall Chief Engineer and CTO"

Similar presentations


Ads by Google