GeoPackage, OWS Context and the OGC Interoperability Program

OGC Interoperability Program Update to SMAC

New Standards for Sharing Location and the OGC Development Processpresented by: Raj SinghOpen Geospatial ConsortiumJune, 2014 2014 Open Geospatial Consortium

OGCRaj will talk about the recently approved GeoPackage and OWS Context standards and how they take data and map sharing to a new level. He will also describe the Interoperability Program, OGC's multi-firm, collaborative, rapid prototyping process that ensures standards are developed based on ideas backed by running code.1

OWS Context

OGCSharing a map

Multipleoverlaid maps

BordersElevationCloud Cover

Cities

2014 Open Geospatial Consortium

OGC3

OGC web services standards do a great job of facilitating spatial data visualization. You can bring in different data layers and pan and zoom, using standardized interfaces implemented by hundreds of software packages. Some of the key OGC standards include:Web Map Service (OGC & ISO) Style Layer Descriptor (OGC)Feature Model & GML (OGC & ISO) Web Feature Service (OGC)Web Coverage Service (OGC)Web Map Context (OGC)Catalogue (OGC )KMLMetadata (ISO 19115 & OGC)Others see www.opengeospatial.org (Standards)

Many of these standards have been submitted to the ISO for standardization as ISO International Standards.

What has been missing is the ability to SHARE this spatial contextualization with colleagues or the public. While there is a well-specified machine language for requesting data from a service, when you want to have someone else pull up the same map on their system, your only option was to explain what layers to access, how to symbolize them, and where to focus the map.

An OGC Web Context document, alleviates this problem by specifying a vendor-neutral map description language that supports a wide range of data sources, from OGC web services like WMS, WFS, WCS and WMTS, to file formats like GML and KML, to vendor-specific formats like Shapefiles and PDFs.

Here, our GIS professional puts together a contextualized map from multiple data sources. He wants a colleague to see the same view of the world, but that colleague uses different software. So he saves the map configuration, or context, to an OWS Context document and emails it.

Sharing a map

BordersElevationCloud Cover

Cities


OGC4

The colleague receives the email and opens it in his software, which automatically pulls in the referenced data services and displays the same map.

Anatomy of a Context document

A context document extends the Atom XML format (or in the future JSON).It contains Atom which have OGC s. Offerings are data sources. They may be either services (and particularly OGC services like WMS, WFS, WMTS and WCS) or file-based data sets, like GML, KML and GeoPackage.File-based data sets may be specified by reference with a URL, or included inline.OGC service offerings contain a GetCapabilites request and a request to get data, such as GetMap, GetTiles, GetFeature, etc.Offerings do not have to be spatial (e.g. PDFs, videos, Dropbox links), so implementing software should handle non-spatial offerings in an elegant way other than mapping them.


OGC

5

Example Offering - WMS


OGCExample Offering - WFS

Sample Map Showing WMS and WFS http://www.example.com/ogcservices/map#dasfe3dsf Bob Smith 2013-12-03T12:00:30Z

http://www.opengis.net/owc/1.0/examples/AGU/wcs Context Example for AGU :: Web Coverage Service Raj Singh 2013-12-06T00:00:00Z http://eos.ga.gov.au/thredds/wcs/LANDSAT/2008/10/LS7_ETM_NBAR_P54_GANBAR01-002_115_079_20081021_BX.nc Australian Reflectance Grid 25 (ARG25) 2012-08-06T00:00:00Z Geoscience Australia John Doe Raj Singh with OxygenXML http://eos.ga.gov.au/thredds/wcs/ Australian Reflectance Grid 25 111.842625 -28.410875 114.357125 -26.434375000000003


OGCGeoPackage

OGCWhy GeoPackage?

Shapefiles, as a format, are dinosaursweb services dont work without internet accessinternet sucks power from a mobile device


OGC

11

OverviewA GeoPackage is a platform-independent SQLite database fileA GeoPackage may containData in any geographic or projected CRS using any DatumVector Feature User Data TablesGP BLOB Geometry Binary Format containing WKB GeometriesLinear 2D Geometries with optional elevation and measure valuesTile Matrix Pyramid User Data TablesPNG and JPEG TilesZoom times two (adjacent zoom level pixel sizes)First open source implementationhttps://bitbucket.org/luciad/libgpkgA SQLite 3 extension that provides a minimal implementationdistributed under the Apache Software License version 2.0 2014 Open Geospatial Consortium

OGCRegistered Extensions NonLinear 2D GeometriesGP BLOB Extension for User-Defined Geometry TypesSpatial IndexesSQL Triggers using Geomety SQL API functions, Other TriggersWebP TilesZoom any intervals

12

GeoPackage Tables for Features 2014 Open Geospatial Consortium

OGCSQLite tables in a sample fileusing SQLite Manager Firefox extension


OGCGeoPackage Tables for Tiles 2014 Open Geospatial Consortium

OGCSQLite command line examplerajsingh$ gpkg World.gpkg SQLite version 3.8.1 2013-10-17 12:57:35libgpkg version 0.9.7Enter ".help" for instructionsEnter SQL statements terminated with a ";"

GeoPackage> .tablesgpkg_contents gpkg_tile_matrix_metadatagpkg_data_columns rtree_world_shape gpkg_extensions rtree_world_shape_node gpkg_geometry_columns rtree_world_shape_parent gpkg_metadata rtree_world_shape_rowid gpkg_metadata_reference world gpkg_spatial_ref_sys

GeoPackage> .schema worldCREATE TABLE "world" ( "COUNTRY" TEXT, "CAPITAL" TEXT, "POP_1994" INT, "POP_GRW_RT" DOUBLE, "POP_MALE" INT, "POP_FEM" INT, "POP_0_14" INT, "POP_15_64" INT, "POP_65PLUS" INT, "MALE_0_14" INT, "MALE_15_64" INT, "65PLUS" INT, "FEM_0_14" INT, "FEM_15_64" INT, "FEM_65PLUS" INT, "POP_URBAN" INT, "POP_RURAL" INT, "URB_MALE" INT, "URB_FEM" INT, "RUR_MALE" INT, "RUR_FEM" INT, "ARABLE_PCT" DOUBLE, "LITERACY" DOUBLE, "RATE" DOUBLE, "RATE0" DOUBLE, "GROWTH" DOUBLE, "CONTINENT" TEXT, "_id" INTEGER PRIMARY KEY AUTOINCREMENT , "shape" GeometryCollection);

GeoPackage> select country,capital from world limit 3;Afghanistan|KabulAlbania|TiraneAlgeria|Algiers


OGC

Luciad & GeoPackage use cases

OGC OWS-9 AviationSpot reporting with location and camera picture info

Access elevation data to enable visibility calculations

Create and edit annotations in the field

OGC

17

the specificationshttp://geopackage.org

http://www.owscontext.org 2014 Open Geospatial Consortium

OGCOGC Interoperability Program

OGCPrototyping Versus SpecifyingPrototyping Versus Specifying: A Multiproject ExperimentPrototyping yielded products with roughly equivalent performance, but with about 40 percent less code and 45 percent less effort. The prototyped products rated some what lower on functionality and robustness, but higher on ease of use and ease of learning. Specifying produced more coherent designs and software that was easier to integrate.

BARRY W. BOEHM, TERENCE E. GRAY, AND THOMAS SEEWALDT, IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. SE-10,NO. 3,MAY 1984See also Michael Schrage, e.g., Serious Play and Cultures of Prototyping in Bringing Design to Software 2014 Open Geospatial Consortium

OGCAnatomy of a Testbed

Stated in RFPAnswered in proposalsExample: define a SQLite-based format for storing vector and raster data (GeoPackage)RequirementsDevelop solutions in-houseMeet weekly for an hour or two to refineExecutionChosen participants meet for a few days to share successful proposals and rough-out collaborative approachesKickoffWork with other developers to test interoperabilityTestingUse the tech to tell a compelling storyShow what could be with interopVideos, presentations, screencastsDemonstration 2014 Open Geospatial Consortium2-3d2-3d1-2d/wk1-2d/wk2d6-9 mocompliance testsprototypesreportsdraft specs

OGCIncreasing the Technology Readiness Level 2014 Open Geospatial ConsortiumTechnology Maturation And ComplianceInteroperability ExperimentPlugfestOGC NetworkPilotTestbedOGC Standards ProgramStandards, BPs, ERs, DPs, WPs

OGCA Word from our Sponsors: OGC Testbed 9 2014 Open Geospatial Consortium

OGC

23