®
®
Overview of OGC Web
Services
Luis Bermudez
Director of Interoperability Certification
lbermudez@opengeospatial.org
January 18th, 2011
Washington DC
1
OGC Mission
To serve as a global
forum for the
collaboration of
developers and users
of spatial data
products and services,
and to advance the
development of
international
standards for
geospatial
interoperability.
OGC
®
Copyright © 2011, Open Geospatial Consortium
OGC At A Glance
•A non-profit, international voluntary consensus standards
organization that is leading the development of standards for
geospatial and location based services.
•Founded in 1994.
•438 members and growing
University
24%
•35 implementation standards
•Hundreds of product implementations
in the market
Commercial
41%
Research
7%
•Broad user community
implementation worldwide
NGO
10%
•Alliances and collaborative activities
with ISO and many other SDO’s
OGC
Government
18%
®
© 2011, Open Geospatial Consortium
3
OGC At A Glance
•A non-profit, international voluntary consensus standards
organization that is leading the development of standards for
geospatial and location based services.
South America
2
Africa, 4
•Founded in 1994.
•438 members and growing
Asia Pacific,
59
•35 implementation standards
•Hundreds of product implementations
in the market
North America
163
•Broad user community
implementation worldwide
Europe
203
•Alliances and collaborative activities
with ISO and many other SDO’s
OGC
Middle East
7
®
© 2011, Open Geospatial Consortium
4
Standards Development is not easy!
→ Requires understanding of differences
→ Requires cooperation on a global basis
→ Requires consensus by many organizations
→ Requires give and take
→ Requires certified, repeatable process
OGC
®
And does not exist in isolation
Alliance Partners: Critical Resource for Advancing Standards
… and others
http://www.opengeospatial.org/ogc/alliancepartners
OGC
®
Making Location Count ...
De Facto
Where does OGC fit in the ‘standards’ world?
OGC
De Jure
ISO/CEN
Domains: Object /
Abstract Models,
Content,
Vocabulary
Domain
OGC
Software Interfaces
and encodings:
Instantiate Domain
and Dejure into
Infrastructure
OASIS/IETF /
W3C
Infrastructure:
TCP, HTTP, XML,
SAML
Infrastructure
®
7
What is an OGC Standard?
• A document, established by consensus, approved by
the OGC membership (balance of interest, all members have an
equal vote)
• Provides, rules, guidelines or characteristics.
• Implementable (testable) in software.
• Is not open source software
(http://wiki.osgeo.org/wiki/Open_Source_and_Open_Standards)
• OGC standards are Open Standards
– Freely and publicly available
– No license fees
– Vendor neutral
OGC
®
Why Open Standards?

Prevents a single, self-interested party from
controlling a standard
• Lower systems and life
cycle costs
• Encourage market competition
– Choose based on functionality
desired
– Avoid “lock in” to a proprietary
architecture
• Stimulates innovation beyond the standard by
companies that seek to differentiate themselves.
OGC
®
Source: Open Standards, Open Source, and Open Innovation: Harnessing the
Benefits of Openness, April 2006. Committee For Economic Development.
www.ced.org
Example worldwide standard: KML
Michael Weiss-Malik,
Google KML product manager
“What OGC brings to the table is…
everyone has confidence we won’t take
advantage of the format or change it in a
way that will harm anyone...
Governments like to say they can publish
to OGC KML instead of Google KML “
OGC
®
© 2011 Open Geospatial Consortium
OGC Specifications
http://www.opengeospatial.org/standards
• Implementation Specifications - Standards
– Basis for working software; detail the interface structure
between software components
• Abstract Specifications
– Conceptual foundation / reference model for spec development
• Best Practices
– Describe use of specifications
• Engineering Reports
– Results from OGC Interoperability Program
• Discussion Papers
– Forum for public review of concepts
OGC
®
Approved OGC® Standards
• Web Services
–
–
–
–
–
Web Map Service (WMS) {ISO}
Web Feature Service (WFS) {ISO}
Web Coverage Service (WCS)
Catalog Services for the Web (CS/W)
Coordinate Transformation
–
–
–
–
Geography Markup Language (GML) {ISO}
KML
Web Map Context
NetCDF
–
–
–
–
–
–
SensorML
TransducerML
Sensor Observation Service (SOS)
Sensor Planning Service (SPS)
Sensor Alert Service (SAS)
PUCK
Available free of charge at
http://opengeospatial.org/standards
• Encodings
• Sensor Web Enablement
• Open Location Services (OpenLS) {ISO}
• Tightly coupled
– Simple Feature Access – OLE, SQL, CORBA {ISO}
– Grid Coverages
• Others (33 total as of January 2011, plus profiles,
best practices, discussion papers, white papers,
etc.)
OGC
®
12
OGC Architecture
• OGC standards can be integrated into a
web services architecture / platform so that:
– Resource providers can advertise their resources
(publish)
– End users can discover resources that they need
at run-time (find)
– End users and their applications can
access and exercise resources
at run-time (bind)
OGC
®
© 2011 Open Geospatial Consortium
38
OGC Web Services (“W*S”) Pattern
What
can you
do?
GetCapabilities
Here…
read this.
<Service>
…
</Service>
<Capabilitiess>
…
</Capabilitie>
<Layer>
…
</Layer>
Capabilities Document
Great! Give
me data
Get Map, Feature, or Coverage
Data
OGC
®
Here you
are….
Making Location Count…
Copyright © 2011, Open Geospatial Consortium, Inc.
Catalog Services for
the Web
OGC
®
Copyright © 2010, Open Geospatial
Consortium, Inc.
Publishing and Discovery
• OGC Catalog Service
– Catalog Service for the Web (CSW)
– ISO 19119 Metadata Profile
– Z39.50 Profile
– OASIS ebRIM Profile
– OpenSearch
• Support publishing and
discovery of distributed
geospatial data and associated
services
OGC
®
Copyright © 2010, Open Geospatial Consortium, Inc.
16
OGC
®
17
GEOOS Registry – 396 entries
http://geossregistries.info/holdings.htm
OGC
®
Copyright © 2012, Open Geospatial Consortium
Web Map Service
OGC
®
Copyright © 2010, Open Geospatial
Consortium, Inc.
Web Map Service (WMS) can get multiple
maps
Cloud Cover
Elevation
Borders
Cities
Multiple
overlaid
maps
One GetMap
request:
OGC
®
20
OGC Web Mapping
Source A
Land
Source B
Water
Source C
OGC
®
Boundaries
Figure Source: Jeff de La Beaujardiere, NASA
Data about
Digital
Resources
OGC Web Map Service
• Spatial Context
– Spatial Reference System (EPSG)
– Corners of map (geographic extent)
– Image width & height
• List of “layers”
– Layer name
– Symbolization style
• Return Format
– GIF | JPEG | WebCGM | SVG, etc.
– Background info (color, transparency)
– Exception Type = InImage | Encoded/Parseable
OGC
®
Copyright © 2010, Open Geospatial Consortium, Inc.
Helping the World to Communicate
Geographically
WMS can query by pointing.
WMS GetFeatureInfo returns
attribute data for a feature or
coverage at a specified point.
Point
elev. = 237 m.
OGC
®
Copyright © 2010, Open Geospatial Consortium, Inc.
WMS-Tiling (WMTS) builds on WMS
• WMTS designed for high performance: anticipates
high volume of identical requests
– Pre-render data as tiles
– Supports caching
• WMS request by bbox & h/w
vs. WMTS request by Tiles
– TileMatrixSet (CRS)
– TileCol
– TileRow
• Bindings:
– KVP, SOAP/WSDL, RESTful
OGC
®
WMS Global Mosaic
• Mosaic of Landsat 7
– 8600 Georectified scenes
– 30 & 15 m resolution
• OpenGIS WMS Web Map Service
–
–
–
–
–
Onearth.jpl.nasa.gov
On-fly pan-sharpening
Client selected false-color rendering from 9 bands
Server development managed and funded by NASA GIO
Accessed by many different WMS Clients
• ~200,000 Landsat Images daily avg served as WMS layers
OGC
®
Web Feature Service
OGC
®
26
Web Feature Service (WFS) gets operable
feature data from multiple servers
Each layer is data, not
merely a view:
Elevation
Cities
Country is:
_ Name: Italy
_ Population: 57,500,000
_ Area: 301,325 sq km
...
Borders
Multiple
thematic
data layers
GetFeature
request:
OGC
®
© 2011 Open Geospatial Consortium
27
Web Feature Service (WFS)
GetCapabilities
Client
<Service>
<Name>CubeWerx WFS</Name>
<Title>CubeWerx Web Feature Service</Title>
<Abstract>Web Feature Server maintained by X.</Abstract>
<OnlineResource>http://www.server.com/wfs.cgi?</OnlineResource>
</Service>
<Capability>
<!-- defines which WFS operations the service supports, etc. -->
</Capability>
Capabilities
Response
GetCapabilities
Request
Web Feature Server
WFS
Opaque Feature Store
OGC
OGC
®
<!– Defines the list of feature types that this instance can operate upon and -->
<!-- which operations are supported on each feature type-->
<FeatureTypeList>
<Operations> <Query/> </Operations>
<FeatureType>
<Name>Roads</Name>
<SRS>EPSG:4326</SRS>
<LatLongBoundingBox minx="-179" miny="-85“ maxx="179“ maxy="83"/>
<Operations>
<Insert/>
<Update/>
<Delete/>
</Operations>
</FeatureType>
</FeatureTypeList>
<!– Defines the capabilities of the filter supported by this feature instance-->
<ogc:Filter_Capabilities>
<ogc:Spatial_Capabilities>
<ogc:Spatial_Operators> <ogc:BBOX/> </ogc:Spatial_Operators>
</ogc:Spatial_Capabilities>
</ogc:Filter_Capabilitites>
© 2011 Open Geospatial Consortium
17
Web Feature Service (WFS)
DescribeFeatureType
<?xml version="1.0" ?>
<DescribeFeatureType version="1.0.0“ service="WFS"
xmlns="http://www.opengis.net/wfs"
xmlns:ns01="http://www.server01.com/ns01"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<TypeName>ns01:Roads</TypeName>
Client
</DescribeFeatureType>
FeatureType
Description
Response
DescribeFeatureType
Request
Web Feature Server
WFS
<complexType name=“Roads">
<complexContent>
<extension base="gml:AbstractFeatureType">
<sequence>
<element name="WKB_GEOM“
type="gml:LineStringPropertyType">
<element name="SURFACE_TYPE" minOccurs="0">
</element>
<element name="NLANES" nillable="true" minOccurs="0">
<simpleType><restriction base="integer">
<totalDigits value="2"/> </restriction> </simpleType>
</element>
</sequence>
</complexContent>
</complexType>
Opaque Feature Store
OGC
OGC
®
© 2011 Open Geospatial Consortium
18
Web Feature Service (WFS)
GetFeature
Client
GetFeature
Request
Feature
Data
Response
Web Feature Server
WFS
Opaque Feature Store
OGC
OGC
®
<GetFeature version="1.0.0“ service="WFS“
xmlns:myns=http://www.someserver.com
<Query typeName="myns:ROADS“>
<ogc:PropertyName>myns:PATH</ogc:PropertyName>
<ogc:PropertyName>myns:LANES</ogc:PropertyName>
<ogc:Filter>
<ogc:Within>
<ogc:PropertyName>myns:PATH</ogc:PropertyName>
<gml:Box>
<gml:coordinates>50,40 100,60</gml:coordinates>
</gml:Box>
</ogc:Within>
</ogc:Filter>
</Query>
</GetFeature>
<wfs:FeatureCollection
<gml:featureMember>
<ROADS fid="ROADS.100">
<PATH>
<gml:LineString gid="1“ srsName="epsg.xml#4326">
<gml:coordinates>10,10 10,11 10,12 10,13</gml:coordinates> </gml:LineString>
</PATH>
<NLANES>4</NLANES>
</ROADS>
</gml:featureMember>
<gml:featureMember>
<ROADS fid="ROADS.105">
<PATH>
<gml:LineString gid="2“ srsName="epsg.xml#4326">
<gml:coordinates>10,10 10,11 10,12</gml:coordinates> </gml:LineString>
</PATH>
<NLANES>2</NLANES>
</ROADS>
</gml:featureMember>
</FeatureCollection>
19
© 2011 Open Geospatial Consortium
Geography Markup Language
(GML)
OGC
®
OGC Geography Markup Language (GML)
• GML an application of eXtensible Markup Language (XML)
– XML specified by World Wide Web Consortium (W3C)
– GML specifies XML Schemas that specify XML encoding of
geographic features, their geometry, and their attributes
• GML encodes digital feature data
– Encodes features, attributes, geometries, collections, etc.
– Basis for specifying Application Schemas
– GML v3, supports 2 1/2 and 3D geometry as well as complex
geometry and topology
• GML 3 is also ISO 19136
OGC
®
© 2011 Open Geospatial Consortium
Geography Markup Language: Representing Geographic
Features
Another Information
Community’s Schema
One Information
Community’s Schema
Road is:
_Width
_Lanes
_Pavement type
….
Cell tower is:
_Owner
_Height
_Licensees
….
Highway is:
_Pavement thickness
_Right of way
_Width
….
Cell transm. Platform is:
_Location
_No. of antennas
_Elevation
GML
Support for complex geometries, spatial and
temporal reference systems, topology, units of
measure, metadata, feature and coverage
visualization.
Backward compatible
….
Mayberry’s Cell Tower
(an instance of Cell Transm. Platform
in another IC’s schema)
Mayberry Road
(an instance of Road
in one IC’s schema)
GML defines a data encoding in XML that allows geographic data and its
attributes to be moved between disparate systems
OGC
OGC
®
Version 3.2 advances interoperability on all fronts!!
© 2011 Open Geospatial Consortium
14
GML Application Activities
Community Application Schemas
Profiles
–
–
–
–
–
GML Point Profile
GML Simple Features Profile
GML GeoShape for use in IETF
GML in JPEG2000
GeoRSS: GML Serialization
US NSDI GML Schemas for
Framework Datasets
European INSPIRE Data
Specifications
OGC
®
– Aeronautical Information Exchange Model
(AIXM)
– Climate Science Modeling Language
(CSML)
– CityGML
– CleanSeaNet
– NcML/GML (NetCDF and GML)
– TDWG Biodiversity GML
– GeoSciML - Geological Sciences ML
– MarineXML
– Ground Water Modeling Language
– WaterML
– Weather Information Exchange Model
(WXXM)
Further information on OGC Network
http://www.ogcnetwork.net/node/210
Helping the World to Communicate
Copyright (c) 2009 Opengeospatial Consortium
Geographically
33
3D Urban Models – OGC CityGML
Stuttgart, Germany
Atlanta, GA
Source: Thomas Kolbe. TU Berlin
OGC
®
Source: GTA Geoinformatik GmbH
Feature Portrayal
OGC
®
Copyright © 2010, Open Geospatial
Consortium, Inc.
Display Feature Data with different Symbols
User Community “A”
User Community “Y”
Emergency
Management
Maps
Map
Viewer
Client
Fire Incident
Violent Activities: Arson Fire
Emergency
Management
Symbol Sets
…
Commercial
Facility Fire
Forest
Fire
Grassland
Fire
Features (GML)
WFS
Maps (GIF,PNG,JPG)
Metadata (XML)
CSW
OGC
Hostile
Cadastral
CSW
Incidents
Population
Emergency Management Data Sources
®
Neutral
Styles (SLD), Symbols (CGM,SVG)
Cultural
Features
Critical
Infrastructure
Env.
Conditions
Friendly
Hotspot
Fire
WMS
Transportation
Unknown
Map
Viewer
Client
(Regional, International, National, State, Local)
© 2011 Open Geospatial Consortium
Intelligence
OpenGIS Styled Layer Descriptor
One data file…
…many different maps!
… and non-graphic
portrayals!
OGC
®
Copyright © 2010, Open Geospatial Consortium, Inc.
OGC KML
OGC
®
OGC KML
OGC
®
© 2011 Open Geospatial Consortium
OGC KML
• Annotate the Earth
• Specify icons and labels to identify locations on the surface of the
planet
• Create different camera positions to define unique views for KML
features
• Define image overlays to attach to the ground or screen
• Define styles to specify KML feature appearance
• Write HTML descriptions of KML features, including hyperlinks and
embedded images
• Organize KML features into hierarchies
• Locate and update retrieved KML documents from local or remote
network locations
• Define the location and orientation of textured 3D objects
OGC
®
© 2011 Open Geospatial Consortium
Web Coverage Service
OGC
®
Copyright © 2010, Open Geospatial
Consortium, Inc.
OGC Web Coverage Service (WCS)
• Service for access to Coverages
– Domain: grids; polygons, points, etc.
– Range components: vector- or scalar-valued
• Operations similar to WFS - tuned to Coverages
– GetCapabilities: Inquire about a WCS server
– DescribeCoverage: Fetch details about a coverage
– GetCoverage: Fetch data from a coverage
• Subsetting
OGC
®
© 2011 Open Geospatial Consortium
OGC Coverages
• Coverage = "space-time varying phenomenon“
– ISO 19123 (=OGC Abstract Topic 6)
– Today typically raster, but more defined
(curved grids, TINs, meshes, ...)
– historically constrained to x/y
...hm, x/y/t...hm, x/y/z/t...hm...pressure?
• Web Coverage Service (WCS)
= coverage access service
– Get original data (or subset thereof),
suitable for further processing
– www.ogcnetwork.net/wcs
• Coverage-related working groups within OGC:
– WCS.SWG
– Coverages.DWG
OGC
®
44
Coverages
“A coverage is a feature that associates positions within a bounded
space to feature attribute values”
• That is to say -- a collection of features that share a common regular
geometry
• Examples
– Raster image
– Digital elevation matrix
OGC
®
Latitude -->
– Polygon overlay
Longitude -->
Coverages represent space-varying phenomena
• Grid (e.g., visible brightness)
OGC
®
Copyright 2003 Global Science & Technology, Inc.
Coverages represent space-varying phenomena
• Grid (land use / land cover)
OGC
®
Copyright 2003 Global Science & Technology, Inc.
Graphic copyright © UCSC Remote Sensing Group. Used by
permission. http://www.es.ucsc.edu/~hyperwww/chevron
Coverages represent space-varying phenomena
• Grid (multi-spectral imagery)
OGC
®
Coverages represent space-varying phenomena
• Triangulated irregular network (TIN)
OGC
®
Copyright 2003 Global Science & Technology, Inc.
Coverage Encodings
OGC Specifications
• GeoJPG
• GML
• GML in JPEG2000
(GMLJP2)
• SWE Common
• Network Common Data
Format (NetCDF)
OGC
®
Other Specifications
• GeoTIFF
• National Imagery Transfer
Format / BIIF
• HDF and HDF-EOS
WCS Operations
• GetCapabilities
what service extensions? What coverages?
• DescribeCoverage
coverage metadata
• GetCoverage
coverage, or subset thereof
OGC
®
Operational OWS Implementations for Imagery
• ESA Heterogeneous Missions Accessibility (HMA)
– WCS Application Profile for Earth Observation
• Spot Image
– WMS, WCS
– WCS for the International Charter on Space and Major Disasters.
– Catalogue and multisatellite in data portal projects.
• Geoeye Geofuse
– KML, WMS, WFS and WCS
– Imagery holdings with less than 20% cloud cover
• Intermap NEXTMap
– WMS, WCS
– 1-meter vertically accurate digital elevation models and geometric
images
OGC
®
Copyright © 2010, Open Geospatial Consortium, Inc.
Web Processing Service
OGC
®
Geo-Processing
• Hundreds of types of algorithms for geodata
• How can we scale to interoperable geo-processing?
• OGC Web Processing Service (WPS)
– Interface that facilitates the publishing of geospatial processes, and
the discovery of and binding to those processes by clients
– Processes include any algorithm, calculation or model that operates
on spatially referenced data.
– WPS may offer calculations as simple as subtracting one set of
spatially referenced numbers from another) or as complicated as a
global climate change model.
OGC
®
Copyright © 2010, Open Geospatial Consortium, Inc.
OGC Web Processing Service (WPS)
WPS-client
Communication over the web using HTTP
GetCapabilities
WPS
DescribeProcess
Algorithms Repository
…
Execute
Data Handler Repository
…
…
…
Algorithm 1
Data Handler A
Web Processing Service
OGC
®
© 2011 Open Geospatial Consortium
“Chaining” Web Services for decision support
Assess Wildfire Activity
Geoprocessing worklow
developed in OGC testbeds
since 2004
Service chaining creates
value-added products
OGC
Interfaces
Internet
WCS
WPS - WCTS
Decision
Support Client
WPS –
Classification
WFS
…
OGC
®
Web servers
Sensor Web Enablement
OGC
®
OGC Sensor Web Enablement (SWE)
Discovery and tasking of sensors. Access, fusion and application
of sensor observations for enhanced situational awareness
•Sensor Model Language (SensorML)
•Observations & Measurements (O&M)
•Sensor Planning Service (SPS)
•Sensor Observation Service (SOS)
•Catalogue Service
•Sensor Alert Service (SAS)
•Web Notification Service (WNS)
OGC
®
© 2011 Open Geospatial Consortium
Basic Requirements for Sensor Web
• Quickly discover sensors and sensor data (secure or
public) that can meet my needs – location, observables,
quality, ability to task
• Obtain sensor information in a standard encoding that is
understandable by me and my software
• Readily access sensor observations in a common manner,
and in a form specific to my needs
• Task sensors, when possible, to meet my specific needs
• Subscribe to and receive alerts when a sensor measures a
particular phenomenon
OGC
®
© 2009 Open Geospatial Consortium, Inc.
Sensor Web Enablement Technologies
• Information Models and Schema
–Sensor Model Language (SensorML)
–Observations and Measurements (O&M)
–SweCommon
• Web Services
–Sensor Observation Service (SOS)
–Sensor Alert Service (SAS)
–Sensor Planning Service (SPS)
OGC
®
60
60
SWE Web Services
Access Sensor
Description and
Data
Command and
Task Sensor
Systems
SOS
Discover Services,
Sensors,
Providers, Data
SPS
SAS
Dispatch Sensor
Alerts to
registered Users
Catalog
Service
OGC
®
Clients
Copyright © 2009, Open Geospatial Consortium, Inc.
Accessible from
various types of
clients from PDAs
and Cell Phones to
high end
Workstations
61
IEEE 1451 – Smart Transducer Interface
Standard
OGC
®
PUCK – Plug and Work Standard for ocean
systems (Candidate OGC Standard)
NetCDF
• Network Common Data Form (NetCDF) Core Encoding
Standard defines an encoding for geospatial data,
specifically digital geospatial information representing
space and time-varying phenomena. NetCDF is a data
model for array-oriented scientific data. The CF-netCDF
Core and Extensions Primer provides an overview of the
OGC CF- netCDF standards suite by describing the CFnetCDF core and extensions.
OGC
®
Copyright © 2012, Open Geospatial Consortium
Current Status
http://www.ogcnetwork.net/standardtracker
• Status SWE Standards
– SensorML – 1.0.1 approved in 2007 (V2.0 anticipated by September
2011)
– SWE Common Data – V2.0 approved
– SWE Common Services – V2.0 approved
– Observations & Measurement – V2.0 approved
– SOS – V2.0 in final stages
– SPS – V2.0 approved
– SAS – being folded into Pub Sub (based on OASIS WS-N)
– PUCK – V1.0 approved
• Approved SWE standards can be downloaded:
– Specification Documents: http://www.opengeospatial.org/standards
– Specification
Schema: http://schemas.opengis.net/
®
OGC
Geosynchronization
OGC
®
GeoSynchronization Services
Publisher reads features
from a WFS managed by the
GSS and proposes changes
to those features. This may
include proposing creation
of new features.
2
1
GSS notifies Publisher
whether proposed
changes were Approved
or Rejected
Publisher Submits
Change Request
3
6
5
GSS notifies
Followers of
changes to
features (i.e.
Transactions)
GSS notifies
Reviewer
of pending
Change
proposals
Reviewer Approves
or Rejects the
proposed changes
GeoSynchronization Service (GSS)
Replication
Feed
Change
Feed
4
OGC WFS-T
OGC
Resolution
Feed
Approved changes are
applied to features via
OGC WFS-T
OGC WFS-T
®
Copyright © 2011, Open Geospatial Consortium, Inc.
OGC WFS-T
Geographic
features
accessible via
WFS
“Big” data requests vs. update requests
WFS request: give me all the parcels in town X
new
data
WFS
adapter
spatial
database
WFS
client
GeoSync request: give me all changes to the parcels in
town X since time T
GeoSync
adapter
GeoSync
client
change
log
OGC
OGC
spatial
database
®
© 2011 Open Geospatial Consortium
GeoSMS
OGC
®
Location Enabling SMS Messaging: GeoSMS
• Significant potential for many applications
• Characteristics
– Multilingual
– Multi-device
– Harmonized with many
existing applications
– Incorporates relevant
ISO standards
• OGC adoption expected in
2011
OGC
®
Copyright © 2010, Open Geospatial Consortium
OGC Open GeoSMS
Defines a short messaging service (SMS) encoding
to exchange lightweight location information
between different mobile devices or applications.
Open GeoSMS encoding for location is compatible
with other OGC standards, such as those for sensor
webs and earth imaging.
It is also compatible with standards such as the
OASIS Common Alerting Protocol (CAP) standard
and the IETF RFC Presence Information Data Format
Location Object (PIDF-LO).
OGC
®
© 2011 Open Geospatial Consortium
Venders/Services that have adapted Open GeoSMS
REAL PRACTICE IN TAIWAN
Open GeoSMS
Enabled Service
OGC
®
Free App: Open GeoSMSer
•
•
•
•
Free download from Android Marketplace
Get GPS data and send Open GeoSMS to your contact
Receive Open GeoSMS, bring up map and POI info
Developed with Open GeoSMS SDK from ITRI
OGC
®
Security
OGC
®
OGC and Security
• The OGC does not develop authentication, authorization
and security standards!!
• We define best practices and extensions to existing
standards from other standards organizations, such as
OASIS
– XACML (OASIS): access control policy language in XML
and a processing model to interpret the policies
– GeoXACML (OGC): geographic access control rules for
distributed geographic content.
OGC
®
Copyright © 2010, Open Geospatial
Consortium, Inc.
OWS-8 AIXM Auth Data Source
Architecture
WFS-T
Request
Subject
Access
Control
System
Response
Feature Store(s)
-
XACML based Access Control Systems support the enforcement of complex, fine grained rights
-
GeoXACML extension of XACML supports geometry and spatial functions
-
Examples
- deny if user interacts with a service on IP 123.123.123.123
- permit if Alice has activated role xyz and interacts with services of type WFS 2.0
- permit if GetFeature requests refer to features of type Runway within a certain area
- permit if the request is a valid (de-)commissioning for features of type RadarSystem
OGC
®
Geospatial Digital Rights Management
• OGC members are leveraging broader standards based Digital
Rights Management (DRM) approaches with OGC standards
Authentication
Pricing
Licensing
Copyright
GeoDRM Reference Model
http://portal.opengeospatial.org/files/?artifact_id=14085
OGC
®
Copyright © 2011, Open Geospatial Consortium, Inc.
How do you make sense
of all of this?
OGC
®
Understanding OGC standards – the ORM*
OGC Reference Model www.opengeospatial.org/standards/orm
• What is the purpose of the ORM?
– Overview of OGC Standards
Baseline
– Insight into the current state of
the work of the OGC
– Basis for coordination and
understanding of the OGC
documents
– Resource for defining
architectures for specific
applications
OGC
®
* Do not confuse with the ORM in Walter
Moers
“The City of Dreaming Books”.
Interoperability Program
Emphasis On Testing and Validation
• OGC Testbeds, Pilots,
Experiments and Plugfests
– Join technology providers and users
– Driven by user community scenarios
– Produce:
• Tested and validated draft standards
• Architectural recommendations
• Industry technology implementations
• Live demonstrations to validate utility
of standards in user context
Climate Challenge Integration Plugfest, 2009
CCIP experimented with ways to share the world’s meteorological and
weather forecast data through open standards for geospatial
information sharing
OGC
®
OGC Interoperability Program
Past Initiatives: http://www.opengeospatial.org/projects/initiatives/past
OGC
®
© 2011, Open Geospatial Consortium
OGC Compliance Program
• More than 10 years providing
certification
• Open Source Web Testing Engine
operational since 2007
• More than 650 implementing
products in the market
OGC
®
OGC Public Resources
• Adopted Standards:
– http://www.opengeospatial.org/standards
• OGC Reference Model:
– http://www.opengeospatial.org/standards/orm
• OGC Demonstrations
– http://www.opengeospatial.org/resource/demos
• Compliance Testing and Certification
– http://www.opengeospatial.org/compliance
• List of Registered Products using OGC Standards:
– http://www.opengeospatial.org/resource
• OGC Network – member-contributed OGC “encyclopedia”
– http://www.ogcnetwork.net
• OGC User – case studies of OGC implementations in the global
community
– http://www.opengeospatial.org, click on “Press Room”
OGC
®
82
The End
OGC standards are
there waiting for you
!!
OGC
®
Copyright © 2011, Open Geospatial Consortium