OGC Orientation and Introduction Adopted OGC Standards November
OGC Orientation and Introduction: Adopted OGC Standards November 2009 Carl Reed CTO, OGC creed@opengeospatial. org Copyright (c) 2009, Open Geospatial Consortium, Inc.
Overview • This set of slides provides introductory information on the approved (adopted) OCG Abstract Specification Topic volumes and Adopted OGC Interface and Encoding Standards • To aid in navigation, several slides provide a list of OGC standards. Each standard name is also a hyperlink that will let you “jump” to the slides for that particular standard. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 2
OGC Abstract Specification Copyright (c) 2009, Open Geospatial Consortium, Inc.
Abstract Specifications: reference models for the development of OGC Implementation Specifications 1. Feature Geometry 2. Spatial Referencing by Coordinates 3. Locational Geometry Structures 4. Stored Functions and Interpolation 5. Features 6. Coverage Type 7. Earth Imagery 8. Relationships between Features 9. Feature Collections 10. Metadata 11. Open. GIS Service Architecture 12. Catalog Services 13. Semantics and Information Communities 14. Image Exploitation Services 15. Image Coordinate Transformation Services 16. Location-based Mobile Services 17. Geospatial Digital Rights Management Reference Model (Geo. DRM RM) 18. Topic Domain Models 1 Telecommunications Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 4
Key Abstract Spec Topic Volumes • • Topic 0: Overview Topic 1: Feature Geometry (same as ISO 19107) Topic 2: Spatial Referencing by Coordinates (same as ISO 19111) Topic 6: Schema for Coverage Geometry and Functions Topic 7: Earth Imagery (same as ISO 19101) Topic 11: Metadata (same as ISO 19115) Topic 12: Services (same as ISO 19119) Topic 18 - Geospatial Digital Rights Management Reference Model (Geo. DRM RM) Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 5
Topic 1: Feature Geometry • Specifies conceptual schemas for describing the spatial characteristics of geographic features, and a set of spatial operations consistent with these schemas. It treats vector geometry and topology up to 3 dimensions. It defines standard spatial operations for use in access, query, management, processing, and data exchange of geographic information for spatial (geometric and topological) objects of up to 3 topological dimensions embedded in coordinate spaces of up to 3 axes. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 6
Topic 2: Spatial Referencing by Coordinates • Defines the conceptual schema for the description of spatial referencing by coordinates, optionally extended to spatiotemporal referencing. It describes the minimum data required to define 1 -, 2 - and 3 -dimensional spatial coordinate reference systems with an extension to merged spatial-temporal reference systems. It allows additional descriptive information to be provided. It also describes the information required to change coordinate values from one coordinate reference system to another. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 7
Topic 6: Schema for Coverage Geometry and Functions • Defines a conceptual schema for the spatial characteristics of coverages. Coverages support mapping from a spatial, temporal or spatiotemporal domain to feature attribute values where feature attribute types are common to all geographic positions within the domain. A coverage domain consists of a collection of direct positions in a coordinate space that may be defined in terms of up to three spatial dimensions as well as a temporal dimension. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 8
Topic 7: Earth Imagery • Defines a reference model for standardization in the field of geographic imagery. This reference model identifies the scope of the standardization activity being undertaken and the context in which it takes place. The scope will include gridded data with an emphasis on imagery. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 9
Topic 11: Metadata • Defines the schema required for describing geographic information and services. It provides information about the identification, the extent, the quality, the spatial and temporal schema, spatial reference, and distribution of digital geographic data. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 10
Topic 12: Services • This abstract spec provides – Identification and definition of the architecture patterns for service interfaces used for geographic information and definition of the relationships to the Open Systems Environment model. – presents a geographic services taxonomy and a list of example geographic services placed in the services taxonomy. – Prescribes how to create a platform-neutral service specification, and how to derive platform-specific service specifications that are conformant with this. – guidelines for the selection and specification of geographic services from both platform-neutral and platform-specific perspectives. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 11
Topic 18 – Geo. DRM Reference Model • The Geo. DRM RM defines the framework for software mechanisms and rights expression languages to articulate and protect the rights of all participants in the geographic information marketplace, including the owners of intellectual property and the users who wish to use it. • A key aspect of the Geo. DRM RM is that it is independent of the type of agreement between the participants which might range from an open-content sharing model, to a costrecovery program of a public or government organization and to a full commercial vendor license model. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 12
Approved Standards Copyright (c) 2009, Open Geospatial Consortium, Inc.
Approved OGC Standards • Catalogue Services • Encodings – Geography Markup Language (GML) – CS Core – CS-W eb. RIM – CS-W 19115/19119 • City. GML • Processing Services – Open. LS Core Services – Sensor Planning Service – Web Processing Service – WCS Web Coverage Processing Servic – WCS Transaction Processing service – Filter Encoding – GML in JPEG 2000 – KML – Observations & Measurements (O&M) – Sensor Model Language (Sensor. ML) – Symbology Encoding – Styled Layer Descriptor (SLD) – Web Map Context (WMC) – Transducer Markup Language (TML) Copyright (c) 2009, Open Geospatial Consortium, Inc. Copyright © 2009 Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 14
Approved OGC Standards (Continued) • Data Services • Portrayal Service – Grid Coverages – Simple Features – Web Coverage Service (WCS) – Web Feature Service (WFS) – Sensor Observation Service (SOS) – Web Map Service (WMS) • Others – Geo. XACML – Geospatial Objects – OWS Common Copyright (c) 2009, Open Geospatial Consortium, Inc. Copyright © 2009 Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 15
Classes of OGC Standards • Interface Standards – Application Profiles (extensions) to an interface standard • Encoding Standards – Profiles – Application Schemas Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 16
Two Major Classes of OGC Interface Standards • Tightly Coupled – Tightly coupled components require detailed knowledge of the technology, such as a data structure, of the called component, and precise definition of the call structure and the arguments in it. • Loosely Coupled – In the OGC, typically a http based Web Service that supports asynchronous message queuing. Detailed knowledge other than of the interface structure and operations is not required. Source: Application Connections for E-Business, June 2000. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 17
Tightly Coupled Interface Standards • Simple Feature Access – – SF Common 1. 2 SF SQL 1. 2 SF OLE/COM 1. 1 SF CORBA 1. 1 • Gridded Coverages 1. 0 • Coordinate Transformation (CT 1. 1) • Geo. Spatial Objects 1. 0 Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 18
Web Services (loosely coupled) Interface Standards. • OWS Common Specification 1. 1 • Catalog (CAT 2. 0. 2) – In revision – CSW ISO 19115/19119 Application Profile 1. 0 • • Web Map Service (WMS 1. 3) (WMS 1. 1. 1 widely implemented) Web Feature Service (WFS 1. 1) (WFS 1. 2 Joint Work item with ISO) Filter 1. 1 (1. 2 Joint Work item with ISO) Web Coverage Service (WCS 1. 1) Web Map Context 1. 1 Location Service Core Interface Standards (OLS 1. 2) Sensor Web Enablement Standards – Sensor Planning Service (SPS 1. 0) – In revision. – Sensor Observation Service (SOS 1. 0) – In revision Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 19
Encoding Standards • Geography Markup Language (GML 3. 1. 1 and 3. 2. 1) – GML in JPEG 2000 for Geographic Imagery Encoding Specification 1. 0 (In revision) – GML Simple Features Profile 1. 0 • Style Layer Descriptors (SLD 1. 1) • Symbology Encoding (SE 1. 1) • Sensor Web Encoding Standards – Sensor. ML 1. 0 – In revision – Transducer. ML (TML 1. 0) Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 20
“Tightly Coupled” OGC Simple Feature (1. 2) Copyright (c) 2009, Open Geospatial Consortium, Inc.
OGC Simple Feature (SF)1. 2 • Interface for Open. GIS Simple Features. – Designed for tightly coupled applications – Spatial and non-spatial properties – Two dimensional – The supported geometry types include points, linestrings, curves, and polygons. – Application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features. – Three profiles • CORBA • OLE/COM • SQL – ONly one with broad implementation. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 22
“Tightly Coupled” OGC Grid Coverages (1. 0) Copyright (c) 2009, Open Geospatial Consortium, Inc.
Open. GIS Grid Coverages (1. 0) • Designed to promote interoperability between software implementations that provide grid analysis and processing capabilities. – Designed for tightly coupled applications – Coverage is a function or any set of entities that exhaustively cover a plane, such as satellite imagery and Digital Elevation Models (DEMs) – Provides for basic image access for purposes of requesting and viewing a grid coverage and performing certain kinds of analysis Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 24
“Tightly Coupled” OGC Geospatial Objects (1. 0) Copyright (c) 2009, Open Geospatial Consortium, Inc.
Geo. Spatial Objects (GO) 1. 0 • Describes the specification for Application Objects. These are the Java and other implementations of objects and interfaces that can be used to implement geospatial applications. • Application Objects are oriented on the application domain (e. g. user-facing, localized processes and operations), and less so on the service domain (e. g. centralized processes and operations that are not necessarily exposed to the user). • While this specification outlines certain service interfaces, it does not require the use of any particular service implementation. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 26
Geo. Spatial Objects • The basis of the interface definition are the object models defined in The Open. GIS Abstract Specification Topic 1: Feature Geometry (ISO-19107 Spatial Schema) Version 5 (OGC 01 -101 r 5) and The Open. GIS Abstract Specification Topic 2: Spatial Referencing By Coordinates (Open Geospatial Consortium Inc). These models provide the architectural bridge between the OGC GO-1 applicationdomain specification and other OGC service-domain specifications. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 27
Loosely Coupled (Also known as web services) Copyright (c) 2009, Open Geospatial Consortium, Inc.
OWS Common Standard 1. 1 • The Open. GIS® Web Services Common (WS-Common) Interface Standard specifies parameters and data structures that are common to all OGC Web Service (OWS) Standards. • Those standards currently include the Web Map Service (WMS), Web Feature Service (WFS), and Web Coverage Service (WCS). • Common aspects include: operation request and response contents; parameters included in operation requests and responses; and encoding of operation requests and responses. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 29
Open. GIS® Coordinate Reference System (CRS) • Used in all OGC interface specifications • A common and consistent way to define interfaces and interface content (parameters, KVPs, etc) for general positioning, coordinate systems, and coordinate transformations. – Grounded in ISO TC 211 work as the abstract model. • Currently using EPSG as the authority for CRS parameters. – Defines thousands of reference systems – normative reference for the EPSG database is www. ihsenergy. com/Epsg_v 61. zip. • An OGC CRS Registry: http: //crs. opengis. org/crsportal/index. html – GML 3 encoding of the entire EPSG v 6. 1 CRS database Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 30
OGC Web Service Interface Standards Catalog Interface Standard sub-chapter Copyright (c) 2009, Open Geospatial Consortium, Inc.
What is a Catalog? • A catalog is a database of information about geospatial resources (data and services) available to a group or community of users. A catalog typically stores descriptive information about the resource being described, and does not store the information resource itself. Such descriptions are known as metadata. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 32
What is an OGC Catalog Service? • The interfaces on catalogs enable services that are collectively referred to as Catalog Services in OGC. We use the term “catalog” or “catalog services” to describe the set of service interfaces that support organization, discovery, and access of geospatial information and services. Catalog services help users or application software to find information and services that exists anywhere in a distributed computing environment. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 33
Spatial data servers with metadata and Open. GIS Catalog Server interfaces Data Catalog Registered geodata metadata Metadata Metadata Metadata Metadata …. . a URL Copyright (c) 2009, Open Geospatial Consortium, Inc. for for for for a a a a feature feature feature feature collection, collection, collection, collection, and and and and a a a a URL URL URL URL Where? When? How? What? Who? Why? Helping the World to Communicate Geographically 34
The OGC Catalog 2. 0. 2 Standard • This Open. GIS® document specifies the interfaces, bindings, and a framework for defining application profiles required to publish and access digital catalogues of metadata for geospatial data, services, and related resource information. • Metadata act as generalised properties that can be queried and returned through catalogue services for resource evaluation and, in many cases, invocation or retrieval of the referenced resource. • This Open. GIS® document is applicable to the implementation of interfaces on catalogues of a variety of information resources. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 35
The Catalog 2. 0. 2 Reference Model • The Catalog 2. 0. 2 Standrd is technology and implementation neutral. • It defines an abstract model for defining Profiles using a Reference Model. • The Reference Model for the OGC Catalogue Interface is composed of two parts: a Reference Architecture and a Decomposition of Catalogue Services. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 36
The Reference Architecture • The figure below is the Reference Architecture assumed for development of the OGC Catalogue Interface. The architecture is a multi-tier arrangement of clients and servers. To provide a context, the architecture shows more than just catalogue interfaces. The bold lines illustrate the scope of OGC Catalogue and Features interfaces. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 37
Decomposition of Catalog Services • The diagram in the next slide shows the decomposition of the OGC catalogue service functions. The OGC_Service interface provides access to a service description. The Discovery component allows a client to search for and retrieve resources of interest. The Brokered. Access component provides operations to order data products that will be delivered by some means outside of the Catalogue Interface. Session-related operations are provided by the Session component. The Manager component allows a client to publish and modify the metadata held by a catalogue. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 38
Decomposition Figure Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 39
What Use Cases for Discovery Does the Catalog Specification Address Extracted from a presentation by Doug Nebert, FGDC Copyright (c) 2009, Open Geospatial Consortium, Inc.
Option 1: Data then Services • User types in search terms against a catalog of data specifying the information content, characteristics, limitations, suitable scale range, and service/operation type s/he is interested in. • Data metadata is returned with ISO 19115 qualified Online_Resource leads that point to a service instance 'handle' stored in an instance registry. • The handle is used to fetch the valid parameters for the invocation of the map service instance, coupled with the data name stored in the data metadata as a qualifier. • The client assembles a valid OWS service request on the specific data. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 41
Metadata Scenarios User Catalog Service Catalog metadata references data metadata service Copyright (c) 2009, Open Geospatial Consortium, Inc. operation Helping the World to Communicate Geographically 42
Option 2: Service then Data • User types in search terms against a service catalog specifying rough content, geographic area of interest, and the general service/operation type s/he is interested in. • Service/operation metadata is returned with either 1) a specific data instance linkage or 2) a data type description (for services not bound to specific data). There is sufficient information to allow the user to select and evaluate the service instance, or for a more advanced client to build service associations (chains). • The client assembles a valid OWS service request Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 43
Metadata Scenarios User Catalog Service Catalog metadata references data metadata service Copyright (c) 2009, Open Geospatial Consortium, Inc. operation Helping the World to Communicate Geographically 44
Option 3: Data Catalog Only • User types in search terms against a gateway or catalog of data specifying the information content, characteristics, limitations, suitable scale range, and service/operation type s/he is interested in. • Data metadata is returned with ISO 19115 qualified Online_Resource leads that points to the capabilities request URL for the specified service. • The capabilities are fetched directly from the OWS service provider for the invocation of the service instance, coupled with additional qualifiers, as necessary, stored in the data metadata such that a service instance registry is not required in this case. • The client assembles a properly-formed OWS service request on the specific data. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 45
Metadata Scenarios User Catalog Service Catalog metadata references data metadata service Copyright (c) 2009, Open Geospatial Consortium, Inc. operation Helping the World to Communicate Geographically 46
Option 4: Brokered Catalog • User submits search terms to a software agent or broker specifying the information content, characteristics, limitations, suitable scale range, and service/operation type s/he is interested in. The broker may be accessed via a catalog service interface. • The broker consults registered collections of data and service instances and returns a mixture of metadata representing the related data and services that meet the search criteria. Elements of 19115 and 19119 would be returned for evaluation and use. • The client assembles a valid OWS service request on the specific data. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 47
Metadata Scenarios User Broker Catalog Service Catalog metadata references data metadata service Copyright (c) 2009, Open Geospatial Consortium, Inc. operation Helping the World to Communicate Geographically 48
OGC Web Services – OWS Web Map Service Interface Standard 1. 3 Copyright (c) 2009, Open Geospatial Consortium, Inc.
OGC Web Map Service (WMS) Standard • The Open. GIS® Web Map Service Interface Standard (WMS) provides a simple HTTP interface for requesting geo-registered map images from one or more distributed geospatial databases. A WMS request defines the geographic layer(s) and area of interest to be processed. The response to the request is one or more geo-registered map images (returned as JPEG, PNG, etc) that can be displayed in a browser application. • Easy to implement – http: //clearinghouse 1. fgdc. gov/scripts/ogc/ms. pl? version=1. 1. 1& request=map&srs=EPSG: 4326&b. Box=-180, -90, 180, 90& width=400&height=200&format=JPEG&styles=BLACK& layers=boundary, coastline, elevation, lakes, rivers& • An ISO Standard Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 50
WMS request flow Web Server Request (HTTP CGI form) Response (JPEG file) Web Browser “get. Map” WMS Request WMS services Native services Geo. Media Auto. CAD Map. Extreme Oracle Minnesota mapserver Arc. IMS Arc. View Arc. GIS Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 51
Web Map Service (WMS) can get multiple maps Elevation cloud cover Borders Cities Multiple overlaid maps One Get. Map request: Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 52
WMS can’t “give data away. ” Roma WMS Get. Map returns a server’s “dumb” JPEG, GIF or PNG representation of the data on the server. It does NOT return the actual data, only a bitmap of the data. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 53
WMS can query by pointing. WMS Get. Feature. Info returns attribute data for a feature or coverage at a specified point. Lat/Long elev. = 237 m. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 54
Numerous Implementations of WMS Interface • Many vendors have implemented and now part of announced products • Many Government Organizations have implemented around the world as part of portals and other applications • Open Source reference implementations • At last count. Over 1, 000 implementations and ½ million layers available via WMS. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 55
OGC Web Services – OWS Web Feature Service Interface Standard 1. 1 Copyright (c) 2009, Open Geospatial Consortium, Inc.
Web Feature Service 1. 1 Interface Standard • The Web Feature Service Interface Standard (WFS) defines an interface for specifying requests for retrieving geographic features across the Web using platformindependent calls. • When coupled with Filter, can specify integrated attribute and spatial queries. • Defines interfaces for data access and manipulation operations on geographic features, using HTTP as the distributed computing platform. Via these interfaces, a Web user or service can combine, use and manage geodata -the feature information behind a map image -- from different sources. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 57
WFS Capabilities • The WFS operations support INSERT, UPDATE, DELETE, QUERY and DISCOVERY operations on vector geographic features using HTTP as the distributed computing platform. • QUERY and DISCOVERY are mandatory. • Basic interface, as does WMS, allows user/client to specify Bounding Box (AOI) and Coordinate Reference System • The WFS FILTER specification defines how to use OGC Query Language to perform query operations (same as Catalog) • Returns features as GML 3. 1. 1 encoding (default). Other encodings, such as KML or Geo. RSS, may be returned Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 58
Web Feature Service (WFS) returns data. Web Feature Server Get. Feature request: I-295 I 8 7 I 95 Feature & attribute data Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 59
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 Get. Feature request: Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 60
Web Feature Server enables distributed, vendor-neutral data maintenance. X Turn left ahead! Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 61
Many WFS Implementations • Operational WFS implementations are working at ESA, Hutchinson 3 G, US Census Bureau, Norwegian Mapping, Ordnance Survey, Nature GIS, Geo. Connections, CANRI, Western Australia others. • Geo. Tools/Geo. Server, an Open Source OGC implementation has over 650 people on the mail list and is implementing WFS. • Over 50 commercial implementations are listed on the OGC web site and there many more out there Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 62
OGC Web Services – OWS Web Coverage Service Interface Standard 1. 1 Copyright (c) 2009, Open Geospatial Consortium, Inc.
OGC® Web Coverage Interface Standard • The Web Coverage Service Interface Standard (WCS) defines a standard interface and operations that enables interoperable access to geospatial "coverages". The term "grid coverages" typically refers to content such as satellite images, digital aerial photos, digital elevation data, and other phenomena represented by values at each measurement point. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 64
Web Coverage Service (WCS) • Can be used to query against multiple coverage repositories, such as imagery archives and having the selected coverage data available for use in one of several formats, such as Geo. Tiff. – Scope: Retrieval of gridded, swath, TIN or other "coverage" data in binary or other formats (HDF, Geo. TIFF, NITF, Net. CDF, etc. ) – Operations: • Get. Capabilities • Get. Coverage Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 65
Web Coverage Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 66
Using OGC Data Access Interface Standards Together Web Feature Server Web Coverage Server Web Map Server Web Terrain Server Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 67
Use of OGC Specifications enables information fusion Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 68
Processing Standard Web Processing Service and Extensions Copyright (c) 2009, Open Geospatial Consortium, Inc.
Web Processing Service 1. 0 • Designed to standardize the way that geospatial calculations, such as polygon overlay, are made available to the Internet. WPS can describe any calculation (i. e. process) including all of its inputs and outputs, and trigger its execution as a Web Service. • Supports simultaneous exposure of processes via GET, POST, and SOAP Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 70
WPS Operations • WPS defines three operations: – Get. Capabilities returns service-level metadata – Describe. Process returns a description of a process including its inputs and outputs – Execute returns the output(s) of a process Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 71
Location Services Interface Standard Copyright (c) 2009, Open Geospatial Consortium, Inc.
Location Services (Open. LS): Core Services 1. 2 • This Open. GIS Implementation Standard describes Open. GIS Location Services (Open. LS): Core Services, Parts 1 -5, an open platform for location-based application services. It also outlines the scope and relationship of Open. LS with respect to other standards and standardization activities. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 73
OGC Location Services Standard – 6 Interfaces • Gateway Service – A network-accessible service that fetches the position of a known mobile terminal from the network. This interface is modeled after the Mobile Location Protocol (MLP), Standard Location Immediate Service, specified in OMA 3. 2 (see Open Mobile Alliance). • Location Utility Service (Geocode/Reverse Geocode) – Geocoding: A network-accessible service that transforms a description of a location, such as a place name, street address or postal code, into a normalized description of the location with a Point geometry (see GML Specification for OGC geometry). – Reverse Geocoder: A network-accessible service that transforms a given position into a normalized description of a feature location (Address with Point), where the address may be defined as a street address, intersection address, place name or postal code. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 74
OGC Location Services Standard - Continued • Directory Service – A network-accessible service that provides access to an online directory (e. g. Yellow Pages) to find the location of a specific or nearest place, product or service. • Presentation Service – A network-accessible service that portrays a map made up of a base map derived from any geospatial data and a set of ADT’s as overlays. • Route Determination Service – A network-accessible service that determines travel routes and navigation information between two or more points. • Navigation Service – An enhanced version of the Route Service, which is a networkaccessible service that determines travel routes and navigation information between two or more points. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 75
Open. LS Core Services Service Provider Geo. Mobility Server Open. LS Position Determination Equipment (GMLC/MPC) LIF Personal Navigator, Concierge, Tracker Open. LS Core Services • Route Determination • Map Display • Presentation Service • Directory Service • Traffic • Geocode / Reverse Geocode • Gateway Service (LIF Gateway) • Navigation Service Core Network Location Function Location Content • Road Networks • Navigation Info • Maps • Directories • Addresses • Traffic Info Copyright (c) 2009, Open Geospatial Consortium, Inc. Open. LS Portal w/ Service Infrastructure (e. g. Provisioning, Billing, etc) Open. LS-based Applications Residing on Mobile Terminals & Desktops Helping the World to Communicate Geographically 76
OGC Encoding Standards Filter Encoding 1. 1 Copyright (c) 2009, Open Geospatial Consortium, Inc.
OGC® Filter Encoding (FE) Standard • FES Defines an XML encoding for filter expressions. A filter expression logically combines constraints on the properties of a feature in order to identify a particular subset of features to be operated upon. For example, a subset of features might be identified to render them in a particular color or convert them into a user-specified format. Constraints can be specified on values of spatial, temporal and scalar properties. An example of a filter is: Find all the properties in Omstead County owned by Peter Vretanos. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 78
Filter Encoding • Any service that requires the ability to query objects from a Web-accessible repository can make use of the XML filter encoding described in this document • The predicate language defined in this document is based on the productions for the Common Query Language (CQL) found in the Catalog Interface Implementation Specification V 1. 0. The spatial operators included in this specification are derived from Catalogue and from the Simple Features Specification For SQL, Revision 1. 2. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 79
Filter Example In this case we are finding all features that have a geometry that spatially interacts with the specified bounding box. The expression NOT DISJOINT is used to exclude all features that do not interact with the bounding box; in other words identify all the features that interact with the bounding box in some way. <Filter> <Not> <Disjoint> <Property. Name>Geometry</Property. Name> <gml: Envelope srs. Name="http: //www. opengis. net/gml/srs/epsg. xml#63266405"> <gml: lower. Corner>13. 0983 31. 5899</gml: lower. Corner> <gml: upper. Corner>35. 5472 42. 8143</gml: upper. Corner> </gml: Envelope> </Disjoint> </Not> <Filter> Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 80
OGC Encoding Standards Geography Markup Language 3. 2. 1 Copyright (c) 2009, Open Geospatial Consortium, Inc.
Open. GIS® Geography Markup Language (GML) • The Geography Markup Language (GML) XML-based language for encoding geographic information in order to be stored and transported over the Internet • GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. • GML defines both the geometry and properties of objects that comprise geographic information. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 82
Geography Markup Language: Representing Geographic Features Another Information Community’s Schema Highway is: _Pavement thickness _Right of way _Width …. One Information Community’s Schema Road is: _Width _Lanes _Pavement type …. Cell tower is: _Owner _Height _Licensees …. Cell transm. Platform is: _Location _No. of antennas _Elevation GML 3. 1. 1 ready for prime time! 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 with ease Version 3. 0 advances interoperability on all fronts!! Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 83
An example of Semantic Interoperability: Database Independent Schema Modeling – GOS-TP Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 84
More about GML • GML encodes basic data structures for digital feature data – Encodes features, attributes, geometries, collections, etc. – Applications require specifying more specific Application XML Schemas • GML supports encoding of “simple” feature geometries without topology or • With GML v 3, supports encoding of feature geometries with topology (and many more capabilities) Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 85
More on GML • Based on the OGC abstract model for features and geometry. – This describes the world in terms of geographic entities called features. – A feature is a list of properties and geometries. – Properties have the usual name, type, value description. – Geometries are composed of basic geometry building blocks such as points, lines, curves, surfaces and polygons. • Extensions have been added that will handle 2 1/2 and 3 D geometry as well as complex geometry and topology (version 3) Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 86
GML Application Example Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 87
OGC Encoding Standards City. GML 1. 0 Copyright (c) 2009, Open Geospatial Consortium, Inc.
OGC City. GML 1. 0 • A common information model for the representation of 3 D urban objects. It defines the classes and relations for the most relevant topographic objects in cities and regional models with respect to their geometrical, topological, semantical and appearance properties. • Encoded as a GML Application Schema Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 89
City. GML 1. 0 • Included are generalization hierarchies between thematic classes, aggregations, relations between objects, and spatial properties. These thematic information go beyond graphic exchange formats and allow to employ virtual 3 D city models for sophisticated analysis tasks in different application domains like simulations, urban data mining, facility management, and thematic inquiries. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 90
Examples of the LODs supported Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 91
OGC Encoding Standards GML Simple Features Profile 1. 0 (based on 3. 1. 1 of GML) Copyright (c) 2009, Open Geospatial Consortium, Inc.
GML Simple Features Profile • GML for Simple Features is a restricted subset of GML (Geography Markup Language) and XML-Schema that supports the XML encoding of geographic features with simple geometric property types (Points, Line and Polygons). • The profile defines three conformance classes that restrict how spatial and non-spatial properties are declared in a GML application schema. Level-0 supports spatial and simple non-spatial property types whose value cardinality can be 0 or 1. Level-1 supports the same set of spatial property types as Level-0 but allows non-spatial properties to have unconstrained value cardinalities and be of complex or aggregate types. Level-2 supports the same set of spatial property types as Level -0 and Level-1 and places no restrictions on how non-spatial properties are declared in an application schema. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 93
OGC Encoding Standards GML in JPEG 2000 (based on 3. 1. 1 of GML) Copyright (c) 2009, Open Geospatial Consortium, Inc.
GML in JPEG 2000 Implementation Standard • Defines the means by which GML is used within JPEG 2000 images for geographic imagery. • This includes the following: – Specification of the uses of GML within JPEG 2000 data files. – Packaging mechanisms for including GML within JPEG 2000 data files. – Specific GML application schemas to support the encoding of OGC coverages within JPEG 2000 data files. • GML used for: – Coverage description (generally Grid, Rectified. Grid) – Feature and/or styled data – Annotations between geometric “regions” (0 d, 1 d, 2 d etc. ) in an image and annotation text, imagery, video and feature references. – Metadata – CRS and UOM identification and dictionary Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 95
OGC Encoding Standards: Geospatial e. Xtensible Access Control Markup Language Ge 0 XACML 1. 0 Copyright (c) 2009, Open Geospatial Consortium, Inc.
Geo. XACML 1. 0 Encoding Standard • Defines Geo extensions/policies for XACML • XACML = e. Xtensible Access Control Markup Language – An OASIS standard (version 2. 0) – A common language for expressing security policy Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 97
Geo-extensions to XACML – Use cases • Many policies depend on geometric and other geographic constraints. – Only authorized officials can delete bridges. – A police officer can see property owners but only within their jurisdiction (e. g. state, prov). – An oil lease cannot intersect a national park. – An oil lease can intersect a national park if you hold an exemption certificate. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 98
Geo. XACML • Geo. XACML defines: – the geometry model on which the geometric data types in access rules have to be based on, – the different encoding languages for geometric data types (which are provided in the extensions to this core standard), – the testing functions for topological relationships between geometries, and – the geometric functions. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 99
OGC Encoding Standards KML 2. 2 Copyright (c) 2009, Open Geospatial Consortium, Inc.
KML Encoding Standard • XML-based language schema for expressing geographic annotation and visualization on existing or future Webbased, two-dimensional maps and three-dimensional Earth browsers. • The KML file specifies a set of features (placemarks, images, polygons, 3 D models, textual descriptions, etc. ) for display • KML IS NOT a content modeling language. If you wish to encode geospatial content for sharing, consider using GML! Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 101
OGC Encoding Standards Style Layer Descriptor Copyright (c) 2009, Open Geospatial Consortium, Inc.
Style Layer Descriptor Version 1. 1 • Controls the presentation (style) of a map portrayal • Allows fine grained control for symbolization on a layer by layer basis • Rule-based • Uses XML • Allows rules for portrayal of – Points, line strings, polygons, text, and other commonly used geometries. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 103
SLD Detailed Description • The Open. GIS® Styled Layer Descriptor (SLD) profile of the Web Map Service Implementation Specification defines an encoding that extends the Web Map Service specification to allow user-defined symbolization of geographic feature and coverage data. It allows users to determine which features or layers are rendered with which colors or symbols. • SLD addresses the important need for users (and software) to be able to control the visual portrayal of the geospatial data. The ability to define styling rules requires a styling language that the client and server can both understand. Symbology Encoding provides this language, while the SLD profile of WMS enables application of Symbology Encoding to WMS layers using extensions of WMS operations. Additionally, SLD defines an operation for standardized access to legend symbols. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 104
One GML data file… …many different maps! Open. GIS Styled Layer Descriptor Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 105
Architecture using WMS, WFS, and SLD WMS Client Web Browser Get. Map Web Map Server Get. Features Map Fetch Reference Web Feature Server XML SLD Doc Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 106
Symbology Encoding 1. 0 • The Open. GIS Symbology Encoding standard defines an XML language for styling information that can be applied to digital geographic Feature and Coverage data. – SE along with the OGC Styled Layer Descriptor Profile for the Web Map Service Implementation Specification are the direct evolution of the OGC Styled Layer Descriptor Standard 1. 0. The old document was split up into two documents to allow the parts that are not specific to WMS to be reused by other service specifications. Symbolgy Encoding is independent of any Services descriptions and could therefore even be used to describe styling information of systems not connected to any kind of service (e. g. desktop GI systems). Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 107
OGC Encoding Standards Web Map Context 1. 1 Copyright (c) 2009, Open Geospatial Consortium, Inc.
Open. GIS Web Map Context 1. 1 • Describes a standardized approach to enable the capture and maintenance of the context - or state information - of a Web Map Server (WMS) request so that this information can be reused easily in the future user session. – Information typically includes: window size and placement, bounding box (in a common Earth coordinate reference system), URLs and other details that could be used by another client to access the same servers and recreate the same representation of overlaid map layers, or to support generation of a similar map representation based on modified parameters from the original request. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 109
OGC and Sensor Webs – Sensor Web Enablement (SWE) Copyright (c) 2009, Open Geospatial Consortium, Inc.
Sensor Web Enablement Activity • A Sensor Web refers to web accessible sensor networks and archived sensor data that can be discovered and accessed using standard protocols and application program interfaces (APIs). Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 111
General SWE Architecture Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 112
SWE Standards Baseline • Observations & Measurements (O&M) - Models and XML Schema for encoding observations and measurements from a sensor, both archived and real-time. • Sensor Model Language (Sensor. ML) - Models and XML Schema for describing sensors systems and processes associated with sensor observations • Transducer Model Language (Transducer. ML or TML) The conceptual model and XML Schema for describing transducers and supporting real-time streaming of data to and from sensor systems. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 113
SWE Standards Baseline • Sensor Observations Service (SOS) - Interface for requesting, filtering, and retrieving observations and sensor system information in a standard way. • Sensor Planning Service (SPS) - Interface for tasking a sensor in a standard way. • Sensor Alert Service (SAS) – Interface for publishing and subscribing to alerts from sensors. • Web Notification Service –Manage message dialogue between client and Web service(s) for long duration (asynchronous) processes Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 114
Transducer. ML • Transducer Markup Language (TML) is a method and message format for describing information about transducers and transducer systems and capturing, exchanging, and archiving live, historical and future data received and produced by them. • A transducer is a superset of sensors and actuators. TML provides a mechanism to efficiently and effectively capture, transport and archive transducer data, in a common form, regardless of the original source. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 115
What is Sensor. ML • Sensor. ML provides standard models and an XML encoding for describing any process related to the description and use of a sensor system, including the process of measurement by sensors and instructions for deriving higher-level information from observations. • Sensor. ML descriptions of sensor systems or simulations can be mined in support of establishing OGC Sensor Observation Services (SOS), Sensor Planning Services (SPS), and Sensor Alert Services (SAS). Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 116
Scope of Sensor. ML Support • Designed to support a wide range of sensors – Including both dynamic and stationary platforms – Including both in-situ and remote sensors • Examples: – Stationary, in-situ – chemical “sniffer”, thermometer, strain gauge – Stationary, remote – stream velocity profiler, tripodmounted camera, Doppler radar – Dynamic, in-situ – aircraft mounted ozone “sniffer”, GPS unit, dropsonde – Dynamic, remote – satellite radiometer, airborne lidar, soldier-mounted video Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 117
Information Provided by Sensor. ML • Observation characteristics – Physical properties measured (e. g. radiometry, temperature, concentration, etc. ) – Quality characteristics (e. g. accuracy, precision) – Response characteristics (e. g. spectral curve, temporal response, etc. ) • Geometry Characteristics – Size, shape, spatial weight function (e. g. point spread function) of individual samples – Geometric and temporal characteristics of sample collections (e. g. scans or arrays) • Description and Documentation – Overall information about the sensor – History and reference information supporting the Sensor. ML document Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 118
Real-Time Management of Sensor Web Assets Sensor. ML is the means by which sensors make themselves known Sensor. ML Sensor. ML Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 119
Why is Sensor. ML Important ? • Supports discovery of sensors and sensor services • Allows for geolocation and processing without a priori knowledge of sensor (and without need for sensor-specific software) • Provides the means by which sensors make themselves known on web and establish communication • Provides qualification of observations (e. g. sensitivity, resolution, accuracy, etc. ) • Enables “plug-n-play” of sensors • Enables intelligent, autonomous sensor web and real-time streaming of observations direct from sensors to client • Supports definition of processing chains that can act or have acted on sensor products Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 120
Sensor Observation Service (SOS) • Provides access to observations from sensors and sensor systems in a standard way that is consistent for all sensor systems including remote, in-situ, fixed and mobile sensors. The OGC Sensor Observation Service specification defines an API for managing deployed sensors and retrieving sensor data and specifically “observation” data. • The SOS is the intermediary between a client and an observation repository or near real-time sensor channel. Clients implementing SOS can also obtain information that describes the associated sensors and platforms. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 121
SOS - Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 122
Observations and Measurements • Provides an abstract model and XML encodings for sensor observations and measurements. • O&M describe a framework and encoding for measurements and observations. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 123
Sensor Planning Service • Enable an interoperable service by which a client can determine collection feasibility for a desired set of collection requests for one or more sensors/platforms, or a client may submit collection requests directly to these sensors/platforms. • Specifically, specifies interfaces for requesting information describing the capabilities of a SPS for determining the feasibility of an intended sensor planning request, for submitting such a request, for inquiring about the status of such a request, for updating or canceling such a request, and for requesting information about further OGC Web services that provide access to the data collected by the requested task. Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 124
Typical in-situ Sensor Planning Service Copyright (c) 2009, Open Geospatial Consortium, Inc. Helping the World to Communicate Geographically 125
- Slides: 125