geo package and ows context at foss4g pdx
Post on 21-Nov-2014
481 Views
Preview:
DESCRIPTION
TRANSCRIPT
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…
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
CSV
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/statsWidely 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 FeaturesLinear 2D Geometries with optional elevation and measure values !XY XYZ XYM XYZM
Simple Features in Tables1 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
More detailed resolution
Array of tiles !for second level
Tile Matrix
Tile Data
Raster
Raster Metadata
The OGC Process
Where is the living place of the document?
Nop
The OGC ProcessAbstract Tests
The OGC ProcessAbstract Tests
Executable Test
http://cite.opengeospatial.org/teamengine/
http://cite.opengeospatial.org/teamengine/
Free Self Testing Facility
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
Geospatial file
GML
WMTS Service
WCS Service
WPS Service
Geospatial file
GML
WMTS Service
WCS Service
WPS Service
Geospatial file
GML
WMTS Service
WCS Service
WPS Service
Geospatial file
GML
“hey, I have all the data
and have annotated the hurricane track. I will send you a … of the operational
picture”
WMTS Service
WCS Service
WPS Service
Geospatial file
GML
<href>
<href> <href>
OWS Context Document
WMTS Service
WCS Service
WPS Service
Geospatial file
GML
<href>
<href> <href>
OWS Context Document
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/ets-
owc10
Executable !Test suite
Document LinksVer 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
top related