Update on New OGC 
Standards 
GeoPackage and OWS Context 
Luis Bermudez 
Director Compliance Program 
OGC 
FOSS4G, Portland, Sept 10, 2014 
© 2014 Open Geospatial Consortium
Part I
How do you share Geospatial data?
ShapeFiles? 
MyShapeFile.shp 
MyShapeFile.shx 
MyShapeFile.dbf 
Simple! Since 1990 
But … 
! 
size max 2 GB 
! 
multiple files 
! 
no topological information 
! 
field names max 10 character limit 
! 
one kind of geometry per layer
FileGDB? 
• Specific proprietary technology 
• Reverse Engineer efforts 
https://github.com/rouault/dump_gdbtable/wiki/FGDB-Spec
<KML> ? 
Is a visualization encoding 
! 
For viewing purposes 
! 
A file with more than 15 mb can cause 
problems 
…
Maybe others… 
CSV 
Empire State Building NY NY,3,Long lines! 
Washington Square Park NY NY,4,Beautiful fountains! 
127 W. 28th Street NY NY,2,Nice brownstone! 
75 Washington Place NY NY,2,Short walk from park! 
Statue of Liberty NY NY,1,Inspirational 
Spreadsheets
What do we want? 
http://www.spatiallyadjusted.com/2012/12/20/ogc-draft-geopackage-specification/
SQLite: Small, Fast, Reliable
SQLite: Small, Fast, Reliable 
http://www.sqlite.org
Max Size of 
Geopackage File 
http://www.sqlite.org/limits.html
Vectors as 
Simple Features SQL 
http://www.opengeospatial.org/resource/products/stats
Vectors as 
Simple Features SQL 
http://www.opengeospatial.org/resource/products/stats
Vectors as 
Simple Features SQL 
http://www.opengeospatial.org/resource/products/stats 
Widely 
implemented!
Vectors as 
Simple Features SQL 
ISO 19125-2:2004 
Geographic information -- Simple feature access -- 
Part 2: SQL option 
ISO 19125-1:2004 
Geographic information -- Simple feature 
access -- Part 1: Common architecture
Vectors as 
Simple Features SQL 
ISO 19125-2:2004 
Geographic information -- Simple feature access -- 
Part 2: SQL option 
ISO 19125-1:2004 
Geographic information -- Simple feature 
access -- Part 1: Common architecture 
Widely 
recognized!
Vectors as Simple Features 
From Simple Feature Access - SQL (SFS)
Vectors as Simple Features 
From Simple Feature Access - SQL (SFS)
Vectors as Simple Features 
Well Known Binary (WKB) Geometries encoded in ! 
Binary Large Objects (BLOBs)!
Vectors as Simple Features 
Linear 2D 
Geometries 
with optional 
elevation and 
measure values 
! 
XY 
XYZ 
XYM 
XYZM
Simple Features in Tables 
1 geometry column per table 
R*Tree indexes
Support for Rasters/Tiles 
• Data model was implemented based on MBTiles 
Specification. 
• One file can store multiple raster and tile pyramid 
data sets in different tables or views.
zoom level 
zoom level 
Coarser 
resolution 
Array of tiles ! 
for second level 
More detailed resolution
Tile Matrix
Tile Data
Raster
Raster Metadata
The OGC Process 
Where is the 
living place 
of the 
document?
Nop
https://github.com/ 
opengeospatial/ 
geopackage
The OGC Process 
Abstract Tests
The OGC Process 
Abstract Tests 
Executable Test
http://cite.opengeospatial.org/teamengine/
Free Self Testing Facility 
http://cite.opengeospatial.org/teamengine/
The OGC Process 
Where is the 
executable 
test suite?
https://github.com/ 
opengeospatial/ets-geopackage10
More on Directions 
Magazine Webinar 
http://vimeo.com/88285579
Document Link 
Version Document Title Number Type 
1.0 OGC® GeoPackage 
Encoding Standard 
12-128r10 IS
Part II
How do you easily share what you are viewing in your 
client, your annotations, cool layers you have put together?
Multiple Layers from different WMSs
Map with GML Annotations
Map with SVG annotation
OWS Context
WMTS 
Service 
WCS 
Service 
WPS 
Service 
GML 
Geospatial 
file
WMTS 
Service 
WCS 
Service 
WPS 
Service 
GML 
Geospatial 
file
WMTS 
Service 
WCS 
Service 
WPS 
Service 
GML 
Geospatial 
file
WMTS 
Service 
“hey, I have all the 
WCS 
Service 
WPS 
Service 
GML 
Geospatial 
file 
data 
and have annotated 
the hurricane track. 
I will send you a … 
of the operational 
picture”
OWS Context Document 
WMTS 
Service 
WCS 
Service 
WPS 
Service 
GML 
Geospatial 
file 
<href> 
<href> <href>
OWS Context Document 
WMTS 
Service 
WCS 
Service 
WPS 
Service 
GML 
Geospatial 
file 
<href> 
<href> <href>
OWS Context in an atom feed 
… 
… 
… 
http://www.creaf.uab.es/hurricane-tomas.xml 
…
Works With Google Maps 
https://maps.google.es/maps?q=http:%2F%2Fwww.creaf.uab.es%2Fhurricane-tomas.xml
WFS Offering Example
Anatomy of a context 
document 
• Extends the Atom XML format! 
• Contains Atom <entries> which have OGC 
<offering>s. 
• Offerings are data sources: 
• Services (e.g. WMS, WFS, WMTS and WCS) 
• File-based data sets (e.g like GML, KML 
and PDF). 
• File-based data sets may be specified by 
reference with a URL, or included inline.
Anatomy of a context 
document 
• 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, so 
clients implementing Context should handle 
non-spatial offerings in a way other than 
mapping them.
https://github.com/ 
opengeospatial/ 
owscontext/
https://github.com/ 
opengeospatial/ets-owc10 
Executable ! 
Test suite
Document Links 
Ver Document Title # Type 
1.0 OGC OWS Context 
Conceptual Model 
! 
12-080r2 
IS 
1.0 OGC OWS Context Atom 
Encoding Standard 
12-084r2 
IS 
OGC® OWS-10 Rules for 
JSON and GeoJSON Adoption: 
Focus on OWS-Context 
14-009r1 
PER
Final Thoughts 
• Let me know if you are interested in: 
• advancing tests 
• implementing reference implementations 
• contributing to the specs! 
• any other idea 
Luis Bermudez! 
lbermudez@opengeospatial.org 
Twitter @berdez

Geo Package and OWS Context at FOSS4G PDX

  • 1.
    Update on NewOGC Standards GeoPackage and OWS Context Luis Bermudez Director Compliance Program OGC FOSS4G, Portland, Sept 10, 2014 © 2014 Open Geospatial Consortium
  • 2.
  • 3.
    How do youshare Geospatial data?
  • 4.
    ShapeFiles? MyShapeFile.shp MyShapeFile.shx MyShapeFile.dbf Simple! Since 1990 But … ! size max 2 GB ! multiple files ! no topological information ! field names max 10 character limit ! one kind of geometry per layer
  • 5.
    FileGDB? • Specificproprietary technology • Reverse Engineer efforts https://github.com/rouault/dump_gdbtable/wiki/FGDB-Spec
  • 6.
    <KML> ? Isa visualization encoding ! For viewing purposes ! A file with more than 15 mb can cause problems …
  • 7.
    Maybe others… CSV Empire State Building NY NY,3,Long lines! Washington Square Park NY NY,4,Beautiful fountains! 127 W. 28th Street NY NY,2,Nice brownstone! 75 Washington Place NY NY,2,Short walk from park! Statue of Liberty NY NY,1,Inspirational Spreadsheets
  • 8.
    What do wewant? http://www.spatiallyadjusted.com/2012/12/20/ogc-draft-geopackage-specification/
  • 10.
  • 11.
    SQLite: Small, Fast,Reliable http://www.sqlite.org
  • 12.
    Max Size of Geopackage File http://www.sqlite.org/limits.html
  • 13.
    Vectors as SimpleFeatures SQL http://www.opengeospatial.org/resource/products/stats
  • 14.
    Vectors as SimpleFeatures SQL http://www.opengeospatial.org/resource/products/stats
  • 15.
    Vectors as SimpleFeatures SQL http://www.opengeospatial.org/resource/products/stats Widely implemented!
  • 16.
    Vectors as SimpleFeatures SQL ISO 19125-2:2004 Geographic information -- Simple feature access -- Part 2: SQL option ISO 19125-1:2004 Geographic information -- Simple feature access -- Part 1: Common architecture
  • 17.
    Vectors as SimpleFeatures SQL ISO 19125-2:2004 Geographic information -- Simple feature access -- Part 2: SQL option ISO 19125-1:2004 Geographic information -- Simple feature access -- Part 1: Common architecture Widely recognized!
  • 18.
    Vectors as SimpleFeatures From Simple Feature Access - SQL (SFS)
  • 19.
    Vectors as SimpleFeatures From Simple Feature Access - SQL (SFS)
  • 20.
    Vectors as SimpleFeatures Well Known Binary (WKB) Geometries encoded in ! Binary Large Objects (BLOBs)!
  • 21.
    Vectors as SimpleFeatures Linear 2D Geometries with optional elevation and measure values ! XY XYZ XYM XYZM
  • 22.
    Simple Features inTables 1 geometry column per table R*Tree indexes
  • 23.
    Support for Rasters/Tiles • Data model was implemented based on MBTiles Specification. • One file can store multiple raster and tile pyramid data sets in different tables or views.
  • 24.
    zoom level zoomlevel Coarser resolution Array of tiles ! for second level More detailed resolution
  • 25.
  • 26.
  • 27.
  • 28.
  • 29.
    The OGC Process Where is the living place of the document?
  • 31.
  • 32.
  • 34.
    The OGC Process Abstract Tests
  • 35.
    The OGC Process Abstract Tests Executable Test
  • 36.
  • 37.
    Free Self TestingFacility http://cite.opengeospatial.org/teamengine/
  • 38.
    The OGC Process Where is the executable test suite?
  • 39.
  • 41.
    More on Directions Magazine Webinar http://vimeo.com/88285579
  • 42.
    Document Link VersionDocument Title Number Type 1.0 OGC® GeoPackage Encoding Standard 12-128r10 IS
  • 43.
  • 44.
    How do youeasily share what you are viewing in your client, your annotations, cool layers you have put together?
  • 45.
    Multiple Layers fromdifferent WMSs
  • 46.
    Map with GMLAnnotations
  • 47.
    Map with SVGannotation
  • 48.
  • 50.
    WMTS Service WCS Service WPS Service GML Geospatial file
  • 51.
    WMTS Service WCS Service WPS Service GML Geospatial file
  • 52.
    WMTS Service WCS Service WPS Service GML Geospatial file
  • 53.
    WMTS Service “hey,I have all the WCS Service WPS Service GML Geospatial file data and have annotated the hurricane track. I will send you a … of the operational picture”
  • 54.
    OWS Context Document WMTS Service WCS Service WPS Service GML Geospatial file <href> <href> <href>
  • 55.
    OWS Context Document WMTS Service WCS Service WPS Service GML Geospatial file <href> <href> <href>
  • 56.
    OWS Context inan atom feed … … … http://www.creaf.uab.es/hurricane-tomas.xml …
  • 57.
    Works With GoogleMaps https://maps.google.es/maps?q=http:%2F%2Fwww.creaf.uab.es%2Fhurricane-tomas.xml
  • 58.
  • 59.
    Anatomy of acontext document • Extends the Atom XML format! • Contains Atom <entries> which have OGC <offering>s. • Offerings are data sources: • Services (e.g. WMS, WFS, WMTS and WCS) • File-based data sets (e.g like GML, KML and PDF). • File-based data sets may be specified by reference with a URL, or included inline.
  • 60.
    Anatomy of acontext document • 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, so clients implementing Context should handle non-spatial offerings in a way other than mapping them.
  • 61.
  • 62.
  • 63.
    Document Links VerDocument Title # Type 1.0 OGC OWS Context Conceptual Model ! 12-080r2 IS 1.0 OGC OWS Context Atom Encoding Standard 12-084r2 IS OGC® OWS-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context 14-009r1 PER
  • 64.
    Final Thoughts •Let me know if you are interested in: • advancing tests • implementing reference implementations • contributing to the specs! • any other idea Luis Bermudez! lbermudez@opengeospatial.org Twitter @berdez