Serving Large-Scale Coverages - How to Tame an Elephant

Transcription

1 Serving Large-Scale s - How to Tame an Elephant OGC Workshop 2 INSPIRE Conference Edinburgh, 29-jun-2011 Peter Baumann Jacobs University rasdaman GmbH OGC WCS.SWG chair OGC spec editor

2 Sensor & Image Data Collection sensor data via SOS, WCS-T,... coverage server [OGC-SWE]

3 Sensor & Image Data Access Services sensor data via SOS, WCS-T,... coverage server [OGC-SWE] Semantic Web

4 (Part of) The OGC Quilt data images data data feature coverage FE WCPS WFS-T WCS-T WFS WMS WCS meta CS-W CQL CS-T = n-d "space-time-varying phenomenon" [ISO 19123]

5 Types, as per GML Discrete «FeatureType» Abstract Continuous MultiSolid MultiSurface MultiCurve MultiPoint Grid Rectified Grid Referenceable Grid

6 WCS Core [OGC r3] GetCapabilities WCS offering can be seen as a single virtual document Describe Notwithstanding other actual encodings Get Hook for future service-related coverage metadata 6

7 WCS Suite: The Big Picture Core 0..* 1..* 0..* Data Encoding Model Format Service 1..* Protocol Binding 0..* Usabil ity Geo- TIFF Range Subsetting Uncertainty GET- KVP Multi linguality Non-Refer enced netcdf WCS-T POST- XML JPEG 2000 WCPS SOAP etc. Scaling & Interpolation CRS

8 Advanced Service/1: WCPS XQuery for s : navigation, extraction, aggregation, analysis Time series Image processing Summary data Sensor fusion & pattern mining

9 Advanced Service/2: EO-WCS OGC WCS Earth Observation Application Profile Candidate standard, in adoption process EO-specific add-on structures & functionality Metadata and provenance, hierachical coverage groupings Overlaying, uniform spatio-temporal retrieval EO Metadata Record 1 EO Metadata Record 2 [EOX] t lat long [Jacobs/EOX] 9

10 INSPIRE INSPIRE Annex II & III heavily rely on coverages Ortho images, elevation data, classifications, metocean data, TWGs need to harmonize 2 xtwgs: metadata, coverages common approach: overall coverage model + theme-specific application schemas common understanding between OGC and INSPIRE: ISO provides high-level basic model does not ensure interoperability Mapping to encoding (e.g., OGC encoding definitions) still needs to be established OGC sees a few issues, have been expressed to INSPIRE ex: Global modeling, interleaved representation, in places underspecification ( xs:any ) Well-established communication & collaboration between OGC & INSPIRE

11 Next Steps in World Version roll-out planning: WCS 2.0.1: Corrigendum (transitional) -- September ex: SWE Common 2.0 has changed after WCS adoption WCS 2.1: Enhancements (stable) -- December ex: dynamic CRS handling OGC OWS-8: High activity on extending coverage data & service model EO-WCS, Format encodings, dynamic CRSs,... Specifications & demonstrations available by September 2011 Continue liaison between OGC and INSPIRE

12 Summary OGC has a stable suite of coverage standards Single, coherent model cross-domain integration Based on ISO 19123, but technically concise interoperable Concise semantics, down to pixel level semantic conformance testing The Data Model: GML s All GML coverage types: nd rasters, curvilinear grids, point clouds, meshes, surfaces,... Service-independent coverages interchangeable between OGC services Various representation schemes efficient encoding & interchange The Service Suite: WCS Modular : Core, encodings, CRS, WCS-T, WCPS, EO-WCS,... [seriouseats.com] Concrete service can range from simple access to advanced processing Concisely defined interop mechanisms Proven to allow efficient implementation (rasdaman: n-d, MapServer: 2-D)