1. OGC Reference Model Open Standards for Geospatial Interoperability
Adapted from a Presentation by:
George Percivall
OGC Chief Architect
Executive Director, Interoperability Program

2. Copyright © 2009, Open Geospatial Consortium, Inc.
OGC Reference Model (ORM) Click on “Standards” at
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
Why Read This Document?
Better understand the OGC Standards Baseline
Better understand the ongoing work of the OGC
Gain an understanding necessary to contribute to OGC process
Aid in implementing one or more of the OpenGIS Standards
Copyright © 2009, Open Geospatial Consortium, Inc.

3. OGC Reference Model (ORM)
Organized in the following sections:
The Enterprise View of OGC
Geospatial Information
Geospatial Services
Reusable Patterns for Deployment
Implementations of OGC Standards
Structured along the lines of the ISO Reference Model for Open Distributed Processing

4. Architecture Viewpoints for Distributed Information Systems
Information technology — Open distributed processing — Use of UML for ODP system specifications
ITU-T Recommendation X.906 | ISO/IEC 19793

5. ORM Viewpoint 2: The Enterprise View of OGC
1.1 Interoperability Is Essential
1.2 An Example: Web Map Service (WMS)
1.3 Business Processes Benefit from Geospatial Standards
1.4 The OGC Members and Programs
1.5 The OGC Standards and Specifications

6. What do we mean by interoperability?
"capability to communicate, execute programs, or transfer data among various functional units in a manner that requires the user to have little or no knowledge of the unique characteristics of those units“
Source: OGC Abstract Specification Topic 12: Services. Derived from ISO
Organizational
Cultural
Legal
Technical
The OGC staff and our members are committed to the concept of geospatial data, services, and application interoperability. Together with terms like "metadata" and "joined-up thinking", this word is increasingly being used in information management discourse across all of our information gathering institutions. So what do we mean by interoperability? From the OGC technology perspective and as documented in the OGC Abstract Specification (derived from ISO and 19112) interoperability is the “capability to communicate, execute programs, or transfer data among various functional units in a manner that requires the user to have little or no knowledge of the unique characteristics of those units”. Excellent examples of interoperability at its best are the Internet and the World Wide Web. “Plug and Play” is another term we often see in use. An excellent example of the implementation of plug and play concept is the stereo component market: you can plug and play receivers, DVD players, and dozens of other components from many providers – and it will work! We and our members have the same interoperability vision.
However, interoperability at the technology level is only one aspect of what the term encompasses. At a higher (more general) level, To be interoperable, one should be actively engaged in the ongoing process of ensuring that the systems, procedures and culture of an organization are managed in such a way as to maximize opportunities for exchange and re-use of information, whether internally or externally.
Based upon this definition, it should be clear that there is far more to ensuring interoperability than using compatible software and hardware, although that is of course important. Rather, assurance of effective interoperability will require often radical changes to the ways in which organizations work and, especially, in their attitudes to information.
Copyright © 2009, Open Geospatial Consortium, Inc.

7. Interoperability allows a Common Reality
“What we are doing is facilitating a common picture of reality for different organizations which have different views of the reality, the disaster, the catastrophe, that they all have to deal with collectively”
David Schell
CEO and Chairman
OGC
Copyright © 2009, Open Geospatial Consortium, Inc.

8. Interoperability – You know when you don’t have it…
Custom Integration
High system lifecycle costs
Difficult to rapidly mobilize new capabilities
Duplication of effort, missed opportunities to collaborate
Copyright © 2008, Open Geospatial Consortium, Inc., All Rights Reserved.

9. Web Map Service (WMS) can get multiple maps
cloud cover
Elevation
Borders
Cities
Multiple
overlaid maps
One GetMap
request:

10. Copyright © 2009, Open Geospatial Consortium, Inc.
Why Open Standards?
Rapidly mobilize new capabilities – plug and play
Lower systems costs
Encourage market competition
Choose based on functionality desired
Avoid “lock in” to a proprietary architecture
The decision to share information and services enabled by policy
Copyright © 2009, Open Geospatial Consortium, Inc.

11. What do we mean by “Open” Standard?
Freely and publicly available
Non discriminatory
No license fees
Vendor neutral
Data neutral
Agreed to by a formal consensus process
What do we mean by “open” and an “open system”? First, consider the term “open”. This adjective is used extensively in the IT industry – including the GIS industry. But very seldom do we see this term actually defined. At the OGC, we use the term Open in very much the same way as the Open Source organization does (
So, from the OGC perspective, we and our members firmly believe that all of the standards and specifications created by the OGC member consensus process must be:
Freely and publicly available: All of the OGC specifications must be available free of charge (no royalties) and unencumbered by patents and other intellectual property.
Non discriminatory: Available to any one, any organization, any time, any where with no restrictions.
No license fees: There are no charges any time for the use of OpenGIS specifications.
Vendor neutral: The OpenGIS specifications do not favor any vendor over another. They are vendor neutral in terms of their content and implementation concept.
Data neutral: OpenGIS Specifications are independent of any data storage model or format.
Agreed to by a formal, member based consensus process: All OpenGIS specifications are defined, documented, and approved by a formal, member driven consensus process. The OGC Technical Committee Polices and Procedures document all aspects of the formal consensus process.
Definitions from the International Telecommunications Union (ITU) Open System: A system with characteristics that comply with specified, publicly maintained, readily available standards and that therefore can be connected to other systems that comply with these same standards. A system is a combination of two or more interrelated services arranged in a functional package to perform an operational function or to satisfy a requirement. Within the OGC, many of the terms and concepts related to open systems and interoperability can be traced to the OSI-RM, or OSI Reference Model. Essentially, this is a model of network architecture and a suite of protocols (a protocol stack) to implement it, developed by ISO in 1978 as a framework for international standards in heterogeneous computer network architecture.
Copyright © 2009, Open Geospatial Consortium, Inc.

12. Copyright © 2009, Open Geospatial Consortium, Inc.
Return on Investment
Multiple studies confirm the value and advantage of open standards based solutions:
NASA Geospatial Interoperability: Return on Investment Study:
Value of Standards, Delphi Report:
Economic Benefits of Standardization, DIN German Institute for Standardization:
Copyright © 2009, Open Geospatial Consortium, Inc.

13. Copyright © 2009, Open Geospatial Consortium, Inc.
What is the OGC?
Open Geospatial Consortium, Inc. (OGC)
Not-for-profit, international voluntary consensus standards organization
Founded in 1994, Incorporated in US, UK, Australia
385 industry, government, research and university members
OGC Mission
To lead in the development, promotion and harmonization of open geospatial standards …
Copyright © 2009, Open Geospatial Consortium, Inc.

14. OGC’s Approach for Advancing Interoperability
Interoperability Program (IP) - a global, innovative, hands-on prototyping and testing program designed to accelerate interface development and validation, and bring interoperability to the market
Rapid Interface
Development
Specification Development Program –Consensus processes similar to other Industry consortia (World Wide Web Consortium, OMA, OMG, etc.).
Standards
Setting
As a response, the OpenGIS concept and dream began due to:
1. The user’s need to integrate geographic information contained in heterogeneous data stores whose incompatible formats and data structures have prevented interoperability. This incompatibility has limited use of the technology in enterprise and Internet computing environments, and the time, cost, and expertise required for data conversion have slowed adoption of geoprocessing across all market segments.
2. The larger community’s need for improved access to public and private geodata sources, with preservation of the data’s semantics.
3. Agency and vendor needs to develop standardized approaches for specification of geoprocessing requirements for information system procurements.
4. The industry’s need to incorporate geodata and geoprocessing resources into national and enterprise information infrastructures, in order that these resources may be found and used as easily as any other network-resident data and processing resources.
5. Users’ need to preserve the value of their legacy geoprocessing systems and legacy geodata while incorporating new geoprocessing capabilities and geodata sources.
Outreach and Community Adoption Program – education and training, encourage take up of OGC specifications, business development, communications programs
Market
Adoption
Copyright © 2009, Open Geospatial Consortium, Inc.

15. Where does OGC fit in the ‘standards’ world?
OASIS/IETF / W3C
Infrastructure: WSDL, UDDI, SOAP, XML
De Facto
ISO
Domains: Object / Abstract Models, Content, Vocabulary
OGC
Software Interfaces: Instantiate Domain and Dejure into Infrastructure
De Jure
Domain
Infrastructure
Copyright © 2009, Open Geospatial Consortium, Inc.

16. Alliance Partnerships
International Organization for Standards (ISO)
World Wide Web Consortium (W3C)
Digital Geospatial Information Working Group (DGIWG)
OASIS
Open Mobile Alliance (OMA)
Internet Engineering Task Force (IETF)
buildingSMART International / Alliance (bSi / bSa)
IEEE Technical Committee 9 (Sensor Web)
Web3D Consortium
Many others

17. OGC Implementation in the Marketplace
We know of several hundred products implementing OpenGIS Specifications
See OGC “Registered Products” List under “Resources” at
Formal Compliance certification is increasing in importance

18. ORM Viewpoint 2: Geospatial Information
2.1 Geospatial Information Is Fundamental or “Everything is somewhere”
2.2 Information Specifications Architecture
2.3 Spatial Referencing
2.4 Maps and KML
2.5 Geographic Features
2.6 Geometry and Topology
2.7 Geography Markup Language
2.8 Sensor Web Enablement Information Standards
2.9 GeoDRM and GeoXACML
2.10 Metadata
2.11 OGC Schema Repositories

19. Every human activity happens somewhere – and “somewhen”!
Source:
Can anyone in the audience think of any human activity that is not impacted by location or impacts a location?
Geospatial Information Is Fundamental
Copyright © 2008, Open Geospatial Consortium, Inc., All Rights Reserved.

20. ORM Information Viewpoint
Concerned with the semantics of information and information processing
Geospatial Information Is Fundamental
Spatial Referencing
Maps and Features
Geometry and Topology
Geography Markup Language
Sensor Web Enablement Information
Policy and Rights Management
Metadata
Information Viewpoint

21. Spatial Referencing Terminology with spatial reference, two cases:
Civic locations using geographic terms
Examples: postal code, place name
Can be ambiguous / amorphous, e.g. Springfield, Danube River
ISO Spatial Referencing By Geographic Identifiers; and OGC Gazetteer, Geocoder, Geoparser
Coordinate Reference Systems
Consists of a coordinate system and a datum
OGC Abstract Specification Topic 2: Spatial Referencing By Coordinates (basis for revision of ISO 19111:2003)
Coordinate Transformations
Conversion: operation on coordinates that does not change datum,
Transformation: operation on coordinates that changes datum
OGC Abstract Specification Topic 2
Information Viewpoint

22. Maps are display of spatial information
Image
Features
Data Source
Display Elements
Display
Render
Display Element Generator
Filter
Device Characteristics
Image Constraints
Style
Query Constraints

23. Geographic features feature: an abstraction of a real world phenomenon
geographic feature is a feature associated with a location relative to the Earth
Information Viewpoint

24. Geometry and topology conceptual schemas
Geometry objects
Combination of a coordinate geometry and a coordinate reference system
OGC AS Topic 1 - Feature Geometry, identical with ISO 19107
Topology
Query Operators
Characterizing topological relations between different features.
Temporal
References to ISO — Temporal, ISO 8601
Spatiotemporal Schema
Spatiotemporal conceptual schema under development in ISO TC211
Information Viewpoint

25. Geometry
Information Viewpoint

26. Spatial query operator examples
Standardized definition for query operations applied in multiple OGC standards

27. 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
Polygon overlay
Digital elevation matrix
Longitude -->
Value = 80
Value = 95
Value = 85
Latitude -->
Value = 100
Value = 90
Value = 50
Value = 55
Value = 85
Value = 30

28. OpenGIS Geography Markup Language (GML)
GML is application of the eXtensible Markup Language (XML)
Based on XML specified by World Wide Web Consortium (W3C)
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.
Applications require specifying more specific Application XML Schemas
GML v3, supports 2 1/2 and 3D geometry as well as complex geometry and topology
GML 3 is also ISO 19136
Historically, the task of moving geographic data from one format to another has been difficult. As a result, many users with large data stores have been locked into a single vendor’s format and have been restricted to using one vendor’s analysis and decision support tools. The Geography Markup Language (GML) attempts to alleviate these difficulties by increasing organizations’ ability to share geographic information. GML, which is based on the eXtensible Markup Language (XML), is an open and non-proprietary specification used for the transport and storage of geographic information.
As with the OpenGIS Simple Feature Specification, GML utilizes the OpenGIS Abstract Specification geometry model. However, unlike the Simple Features Specification, the GML Specification includes the ability to handle complex properties.

29. GML: Representing Geographic Features
Another Information
Community’s Schema
Highway is:
_Pavement thickness
_Right of way
_Width ….
Cell transm. Platform is:
_Location
_No. of antennas
_Elevation
Support for complex geometries, spatial and temporal reference systems, topology, units of measure, metadata, feature and coverage visualization.
One Information
Community’s Schema
Road is:
_Width
_Lanes
_Pavement type ….
Cell tower is:
_Owner
_Height
_Licensees
Mayberry’s Cell Tower
(an instance of Cell Transm. Platform
in another IC’s schema)
GML is more than just a mechanism for encoding spatial data. It also provides the ability to define application schemas that are specific to a given domain, such as transportation or cadastral, and capture both the geometry and topology relationships but also the semantics of the specific domain being modeled.
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 with ease

30. GML Application Activities
Community Application Schemas
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
Further information on OGC Network
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
Base Transportation
Roads
Governmental Units
Linear Reference Systems
Dictionaries
Hydrology

31. OGC Sensor Web Enablement
Industrial
Process
Monitor
Sensors connected to and discoverable on the Web
Sensors have position & generate observations
Sensor descriptions available
Services to task and access sensors
Local, regional, national scalability
Enabling the Enterprise
Automobile
As Sensor Probe
Environmental
Monitor
Traffic
Monitoring
Temp
Sensor
Stored
Sensor
Data
Airborne
Imaging
Device
Webcam
Strain
Gauge
Health
Monitor
Satellite-borne
Imaging Device

32. Observations
An observation feature binds a result to a feature of interest, upon which the observation was made
Observation - act of observing a property or phenomenon, with the goal of producing an estimate of the value of the property.
Observations are modeled as Features within the context of the General Feature Model [ISO 19101, ISO 19109].
Copyright © 2007, Open Geospatial Consortium, Inc., All Rights Reserved.

33. SWE Languages and Encodings
Information Model for Observations and Sensing
Sensor and Processing Description Language
Observations & Measurements (O&M)
SensorML
TransducerML
GML Observations Application Schema
SWE languages:
SensorML – XML language for describing Sensor Hardware as well as data processing chain (geo-location, color processing, etc…)
O&M – XML language for describing Sensor Observations (includes metadata about the observation + observation result data encoded using SWE common)
SWE Common encodings – Common XML description of data structures and encodings (binary base64, ASCII blocks, out of band, encapsulate MPEG4, etc…)
Multiplexed RT Streams – Used for alerts and real time data (data is pushed by the server)
SWE Common Data Structure And Encodings
Multiplexed, Real Time Streaming Protocol
Copyright 2006, OGC

34. Metadata Metadata is data about data Dataset metadata Service Metadata
characterize geographic data; enables in most efficient manner; facilitates data discovery, retrieval and reuse; fitness for of use
datasets, aggregations of datasets, individual geographic features,
core metadata - subset of the full set of elements
OGC adopted ISO 19115, additional material in
Service Metadata
"Get Capabilities" operation common to all OWS1 services, returns a "capabilities document" describing the service.
OGC AS Topic 12 (identical with ISO 19119)
Registry Information Model (RIM)
all metadata and data types are registry objects.
RIM under development in OWS
Information Viewpoint

35. Geospatial Rights Management
Digital rights management for geospatial (GeoDRM) builds on larger market by with geospatial resources specifics

36. ORM Viewpoint 3: Geospatial Services
3.1 Services Architecture
3.2 OGC Web Services
3.3 Sensor Web Enablement (SWE) Services
3.4 Processing Services and Service Chaining
3.5 Mass Market Services
3.6 Open Location Services
3.7 Fine-Grained Services

37. Services, Interfaces and Operations
Service - distinct part of the functionality that is provided by an entity through interfaces,
Interface - named set of operations that characterize the behavior of an entity
Operation - transformation or query that an object may be called to execute. Each operation has a name and a list of parameters.
Variations:
Granularity: coarse-grained vs. fine-grained
Data/service coupling: tight vs. loose
See OGC Abstract Specification Topic 12 - OpenGIS Service Architecture (ISO 19119)
Computational Viewpoint

38. OGC Web Services (OWS) Common
Defines the aspects of OGC standards that are common to all OGC Web Services Interface Implementation Standards such as Web Map Service (WMS), Web Feature Service (WFS), Web Coverage Service (WCS)
Operation request and response contents
Parameters and data structures included in requests/responses
Encoding of operational requests / responses

39. Copyright © 2009, Open Geospatial Consortium, Inc.
OGC Web Services (OWS)
Just as is the dial tone of the World Wide Web, and html / xml are the standard encodings, the geospatial web is enabled by OGC standards:
Web Map
Server
Web Coverage
Web Feature
Web Map Service (WMS)
Web Feature Service (WFS)
Web Coverage Service (WCS)
Catalogue (CSW)
Geography Markup Language (GML)
OGC KML
Others…
Relevant to geospatial information applications: Critical Infrastructure, Emergency Management, Weather, Climate, Homeland Security, Defense & Intelligence, Oceans Science, others
Copyright © 2009, Open Geospatial Consortium, Inc.

40. Web Feature Service (WFS) gets operable
feature data from multiple servers
Each layer is data, not merely a view:
Country is:
_ Name: Italy
_ Population: 57,500,000
_ Area: 301,325 sq km
. . .
Borders
Elevation
Cities
Multiple
thematic
data layers
GetFeature
request:
Copyright (c) 2009, Open Geospatial Consortium, Inc.

41. Architecture using WMS, WFS, and SLD
Web Browser
WMS Client
Web Feature Server
SLD Doc
Web Map Server
GetMap
Map
Features
GetFeature
Fetch
Reference
XML

42. Emergency Management Symbology-1
User Community “A”
User Community “Y”
Emergency Management Maps
Map Viewer Client
Map Viewer Client
Fire Incident
Emergency Management Symbol Sets
Violent Activities: Arson Fire
Unknown
Friendly
Neutral
Hostile …
Commercial
Facility Fire
Forest
Fire
Grassland
Fire
Hotspot
Fire
Features (GML)
Maps (GIF,PNG,JPG)
Metadata (XML)
Styles (SLD), Symbols (CGM,SVG)
WFS
WMS
CSW
CSW
Transportation
Critical
Infrastructure
Cultural
Features
Incidents
Env.
Conditions
Cadastral
Population
Intelligence
Emergency Management Data Sources
(Regional, International, National, State, Local)

43. Web Coverage Service (WCS)
Scope: Retrieval of gridded, swath, TIN or other "coverage" data in binary or other formats (HDF, GeoTIFF, NITF, NetCDF, etc.)
Elevation, Orthoimagery
Operations:
GetCapabilities
GetCoverage
The Web Coverage Service (WCS) supports the networked interchange of geospatial data as "coverages" containing values or properties of geographic locations The specification details interfaces that allow client applications to seamlessly query and access raw or processed satellite imagery, digital elevation models, raster data, and other types of coverage data stored on one or more distributed servers.
Unlike the Web Map Service (WMS) which filters and portrays spatial data as static geo-registered "pictures", the Web Coverage Service provides allows a client application to query and access geospatial information that represents a fully tessellated surface (satellite data, digital orthophotos, and so forth). The returned data can be used for client-side rendering, multi-valued coverage analysis, and input into scientific models and other clients applications beyond simple viewers.

44. Section 3.3: Sensor Web Enablement (SWE) Services
Enables discovery, access and application of real time sensor observations for enhanced situational awareness
Sensor Model Language (SensorML)
Transducer Markup Language (TML)
Observations & Measurements (O&M)
Sensor Planning Service (SPS)
Sensor Observation Service (SOS)
Sensor Alert Service (SAS)
Web Notification Service (WNS)
IEEE (sensor) and OASIS (alert) stds
Quickly discover sensors (secure or public) that can meet my needs – and learn about what they can do (location, observables, quality, ability to task)
Obtain sensor information in a standard encoding that is understandable by the user and by 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
Request and receive alerts / notification when a sensor measures a particular phenomenon, or completes a requested task
Information Models and Schema
Sensor Model Language (SensorML) for In-situ and Remote Sensors - Core models and schema for observation processes: support for sensor components, georegistration, response models, post measurement processing
Observations and Measurements (O&M) – Core models and schema for observations
TransducerML – adds system integration and real-time streaming clusters of observations
Web Services
Sensor Observation Service - Access Observations for a sensor or sensor constellation, and optionally, the associated sensor and platform data
Sensor Alert Service – Subscribe to alerts based upon sensor observations
Sensor Planning Service – Request collection feasibility and task sensor system for desired observations
Web Notification Service –Manage message dialogue between client and Web service(s) for long duration (asynchronous) processes
Sensor Registries – Discover sensors and sensor observations
Copyright © 2009, Open Geospatial Consortium, Inc.

45. SWE Components – Web Services
Access Sensor Description and Data
Command and Task Sensor Systems
SOS
SPS
Discover Services, Sensors, Providers, Data
Accessible from various types of clients from PDAs and Cell Phones to high end Workstations
SAS
Catalog Service
Dispatch Sensor Alerts to registered Users
Clients
SWE web services:
Sensor Observation Service – Access to sensor or simulated data
Sensor Planning Service – Sensor System or Simulator Control Interface
Sensor Alert Service – Subscribe to specific alerts usually derived from sensor/simulator data
Catalog Service – Discover other services, sensors, providers and data sets
SWE Steps:
Services are first registered in one or several catalogs also accessible through a standard interface.
Client can discover services, provider, sensors and datasets by using the catalog
Client can then access data from SOS, control sensors and simulators using SPS and receive alerts from SAS
Mike Botts, Alexandre Robin, Tony Cook
Copyright 2006, OGC

46. Processing Services, Workflow and Service Chaining

47. OGC Web Processing Service (WPS)
WPS-client
Communication over the web using HTTP
WPS
GetCapabilities
DescribeProcess
Execute
Algorithms Repository
Data Handler Repository … … … …
Algorithm 1
Data Handler A
Web Processing Service
© 2009 Open Geospatial Consortium, Inc.

48. “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
Decision Support Client
Internet
WCS
(NASA Data Pool)
WPS - WCTS
(Producer-B, Vendor-2)
WPS - Classification
(Producer-C,Vendor-3)
WFS
(Producer-n, Vendor-x)
Web-based geospatial service chaining and decision support. How do we reliably and repeatedly combine results from several distributed services on the web to produce a result for a user? Service chaining is the term commonly used for the process of organizing disparate web based services into an orderly process. For instance, a raw image is sent to a service that performs a coordinate transformation. This services sends the transformed image to a classifier service that processes the image to highlight areas of active fire. The result of this service is sent to a user’s client along with other geospatial data such as vegetation overlays, transportation. Service chaining will play an important role in future capabilities. …
Web Servers

49. Mass Market Geo OGC Vision is being realized in ‘mass market geo’
Google Earth & Maps
Windows Virtual Earth
Yahoo Maps
Mobile phone location based services (e.g. Nokia Ovi)
Real time ‘sensor connection’ to the world coming soon
Standards for Mass Market Geo need to match weight of uses
Lightweight application schemas of encodings
GeoRSS
GeoJSON
Open Location Services

50. Fine-Grained Services
OGC Simple Feature Specification
application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features.
Three profiles: CORBA, OLE/COM, SQL
OpenGIS Grid Coverages Specification 1.0
interoperability for grid analysis and processing capabilities.
Provides for basic image access for purposes of requesting and viewing a grid coverage and performing certain kinds of analysis
Coordinate Transformation Service (CT)
specify and access coordinate transformation services for use on specified spatial data.

51. Open Location Services (OpenLS)
An open (middleware) platform for location-based application services for mobile assets and terminals.
The primary goal of the OpenLS initiative series is to define the specifications for the “Core Services and Abstract Data Types (ADT)” that comprise this platform.
XML for Location Services - Core Spec Package, V 1.0
Interfaces for core LS functions: geocode, reverse geocode, directory, gateway, etc.
OpenLS Pending Documents
OpenLS Presentation Experiment
OpenLS Location Refinement Service
OpenLS Positioning Service
OpenLS Navigation Service

52. ORM Viewpoint 4: Reusable Patterns for Deployment

53. ORM Viewpoint 4: Reusable Patterns for Deployment
OGC technology applied in several environments
Reusable patterns use OGC standards to accomplish typical tasks.
Engineering patterns
Publish, Find and Bind Pattern
Geospatial Portal and Clients
Multi-Tier Architectures
Spatial Data Infrastructures
Sensor Webs
Workflow and Service Chaining

54. Publish-Find-and-Bind Pattern
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)

55. Service tiers in OWS architecture

56. Reference Architecture Service Distribution
Geospatial Portal
Viewer Clients
Discovery Clients
Management Clients
Access Control
Exposed Services
Portal
Services
Data
Services
Portrayal
Services
Internet
Portrayal
Services
Portrayal
Services
Data
Services
Data
Services
Features
Gazetteer
Coverages
Symbology Mgmt
Maps
Styling
Coverages
Map Context
Catalog
Services
Catalog
Services
Catalog
Services
Data Discovery
Service Discovery
Catalog Update
Query Languages

57. GEOSS Engineering Viewpoint
Clearinghouses
GEO
Web Portals
GEOSS Common
Infrastructure
Components
& Services
Standards and
Interoperability
Best Practices
Wiki
User Requirements
Registries
Main GEO
Web Site
Registered Community Resources
Community
Portals
Client
Applications
Client Tier
Business Process Tier
Catalogues
Alert
Servers
Workflow
Management
Processing
Access Tier
GEONETCast
Product Access
Sensor Web
Model Access
Test Facility
Mediation
CSW
WMS
W*S
WFS
SOS
SAS
SPS
WPS
CSW
WMS
CSW
So from a client tier perspective, augment the GCI via the contribution of community portals supporting specific communities of practice and stand-alone applications that can leverage the GCI. On the business Process level, we’ve focused on community catalogs (including WAFs) and workflow and processing services. And test facility which was used to test the services by the partipants. Finally various access tier components at the bottom.

58. Integrated Client for Decision Support using multiple OGC Services

59. Conflation Workflow Architecture
The Conflation Process has not yet been configured to load rules from an external rules service.

60. SWE and Geoprocessing Workflow
Access & Processing Node
CSW
WFS
CSW
WCS
WPS
Register
Measurement
Types
SPS
SOS
SAS
CSW
SOS
SAS
SOS !
Sensor Net
Mission Control Center

61. ORM Viewpoint 5: Implementations of OGC Standards
5.1 OGC Compliance Test Program
5.2 Registered Implementations
5.3 Operational Networks using OGC Standards

62. ORM Viewpoint 5: Implementations of OGC Standards
OGC Compliance Test Program
Registered Implementations
Operational Networks using OGC Standards

63. Copyright © 2009, Open Geospatial Consortium, Inc.
Market Availability see
Free availability of standards stimulates market
Hundreds of Products Implementing OGC Standards
Compliance Test & Certification Program
Copyright © 2009, Open Geospatial Consortium, Inc.

64. Compliance Test Development Process
SWG submits Candidate Standard
and ATS
OAB Standard & ATS
review
CITE SC reviews Abstract Test Suite
Implement
draft ETS and
test datasets
TC & Public Review –
3 supporting organizations
required to proceed
Develop Reference
Implementations
SC, TC & PC vote –
This versioned baseline
forms the basis for change
control of the compliance package
Release final ETS,
test datasets, RI’s
Compliance Testing Begins
The CITE team in OWS6 followed the previously established process for developing new compliance tests. This process begins with a detailed review of a specification for which a compliance test will be developed. From that review, an Abstract Test Suite is defined. This ATS is documented and sent out to the OGC community for review and feedback. Once the ATS is in a final state, development begins on the Executable Test Suite. Development of a Reference Implementation happens in parallel with the development of an ETS to ensure that the Reference Implementation is 100% compliant with the newly emerging ETS. The ETS and Reference Implementation are then made available for an open review period where feedback is welcomed. After the community has reviewed the ETS and RI, and when 3 implementations “support” or pass the new compliance tests, the ATS, ETS and RI are submitted to the OGC for a vote. Official testing with this new package of tools can begin once the OGC community votes to accept the new tests.
Maintenance phase, with possible
(separately versioned) changes to:
Standard
ATS
ETS
Test datasets
© 2006 Open Geospatial Consortium, Inc.

65. GEOSS AIP-2 Flood Prediction and Response Led by NASA, Spot Image, Northrop Grumman, ERDAS
From portal select desired theme(s) and area of interest
Selected workflow automatically activates needed assets and models
Disaster Management Information System (DMIS)
Mozambique
Workflows
Wizard
Wizard picks appropriate workflow for desired result
Estimated rainfall accumulation and flood prediction model
Baseline water level, flood waters and predicted flooding
Flood Model

66. GEOSS AIP-2 Biodiversity & Climate Change Led by CNR, Univ of Colorado, GBIF
GEOSS Portal
OGC WPS Access to Model
req
resp
Research Scientist
IP3 Client & Workflow engine
CSW
IP3 Distributed Community Catalog/Mediator
req
req
req
req
req
req
req
req
Broker
resp
resp
resp
resp
resp
resp
resp
resp
Other Non-OGC Services
GBIF
WCS - T
WCS
WFS
Non-OGC Services

67. GSDI - A Global Capability Based on Commonly Accepted Best Practices
Easier access to multiple online info sources and services
Minimize duplication through reuse of geospatial information and technology solutions within an across organizations
Clearinghouse
Geoparser
Vendor
Data
Local
Government
National
Other
Collections
Whoville
Cedar Lake
Buildings
Roads
Images
Targets
Boundaries
...
Catalog View
Common interfaces enable interoperability
Queries
extract info from diverse sources
Integrated View
Gazetteer
Coordinate
Transform
Web Mapping Server, Web Feature Server, Web Coverage Server
Catalog Services
Services
Metadata
Internet
Geocoder
Reduced deployment and operational costs
Support public and private decision making requirements
Establish partnerships to share successes, capture and share best practices
The geospatial community has made substantial progress in advancing a set of best practices necessary to make a shared Spatial Data Infrastructure (SDI) a reality from the local to global levels. The SDI movement that started back in the mid 1990’s has yielded world wide agreement on a core set of principles that has improved our ability to share geospatial information in support of a variety of mission needs.
Geoparser

68. Parting Thoughts…
OGC Reference Model is moving into an annual revision cycle.
Let’s consider including some real world practical examples of Semantics and Ontology work as direct reference in OGC Reference Model:
One Geology
Marine Semantic Mediation Web Services (MMI)
Semantic Sensor Web
Semantic Sensor Network
Hydrologic Sensor Web
OGC deeply engaged implementation level standards development
Identify and socialize S/O topics in the OGC process to spur development, prototyping and testing

69. Interoperability is about Organizations
“Interoperability seems to be about the integration of information. What it’s really about is the coordination of organizational behavior.”
David Schell
CEO and Chairman
OGC
Copyright © 2009, Open Geospatial Consortium, Inc.

70. Thank you for your attention!
Mark Reichardt
President & CEO
Copyright © 2009, Open Geospatial Consortium All Rights Reserved. 70 70