© 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach [email protected].

31
© 2003, OGC © 2003, OGC Specification Update Specification Update June 2003, FGDC By Sam Bacharach [email protected]

Transcript of © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach [email protected].

Page 1: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC© 2003, OGC

Specification UpdateSpecification Update

June 2003, FGDC

By

Sam Bacharach

[email protected]

Page 2: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 2

Helping the World to Communicate Geographically

Where to Find OGC SpecificationsWhere to Find OGC Specifications- - www.opengis.orgwww.opengis.org - -

Page 3: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 3

Helping the World to Communicate Geographically

Software Implementing / Conforming to OGC Software Implementing / Conforming to OGC SpecificationsSpecifications

Click on “Implementing Products” at

www.opengis.org

Page 4: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 4

Helping the World to Communicate Geographically

Quick Update on OGC GrowthQuick Update on OGC Growth

• Over 250 members worldwide – 30 countries & 5 continents– 91 European members - 19 countries– 35 Asia-Pacific members - Japan, Republic of Korea, Australia, China, and

Thailand

• Eleven approved, publicly available Implementation Specifications

• Broad OGC participation with other industry and international standards organizations (OASIS, W3C, OMG, ISO, OMA, IETF…)

• 30+ candidate Implementation Specifications in work

• OGC Reference Model defines interoperable geo architecture

• Rapidly growing list of vendor implementations

Page 5: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 5

Helping the World to Communicate Geographically

OGC’s Program ApproachOGC’s Program Approach

• Interoperability Program (IP) - a global, innovative, hands-on engineering and testing program designed to accelerate interface development and bring interoperability to the market.

• Specification Development Program –Consensus processes similar to other Industry consortia (W3C, OMG, etc.).

• Outreach and Community Adoption Program – education and training, encourage take up of OGC specifications, business development, communications programs

Rapid InterfaceDevelopment

StandardsSetting

CommunityTake Up Demand

Creation

Page 6: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 7

Helping the World to Communicate Geographically

A Sample of Interoperability InitiativesA Sample of Interoperability Initiatives

• OGC Web Services 1.2 (2002)• Critical Infrastructure Protection Initiatives 1 and 2 (2003)• Conformance Interoperability Test Environment (2002 –2003)• OGC Web Services 2.0 (2003)• Geospatial One Stop Transportation Pilot (2003)• Geospatial One Stop Portal (2003)• Property and Land Initiative (2003)• Geographic Objects (2003)

Page 7: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 8

Helping the World to Communicate Geographically

OGC Web Services (OWS) IOGC Web Services (OWS) Initiativenitiative

• Develops common interfaces and schemas that support the “Spatial Web,” a world-wide network of geographic data and geoprocessing services

• Allows future applications to be assembled from multiple, network-enabled geoprocessing services implementing OpenGIS Specifications

• Integrates mainstream Web Services Integrates mainstream Web Services standards into the geospatial marketstandards into the geospatial market

• Generates next-generation Web Mapping, Generates next-generation Web Mapping, multi-source Feature and Imagery multi-source Feature and Imagery production, Information Interoperability, production, Information Interoperability, distributed Sensor Webs, GeoCommerce distributed Sensor Webs, GeoCommerce specificationsspecifications

Information Interoperability

Page 8: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC© 2003, OGC

OGC Web Services 1.2 OGC Web Services 1.2 Initiative SummaryInitiative Summary

Page 9: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 10

Helping the World to Communicate Geographically

And Others

Page 10: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 11

Helping the World to Communicate Geographically

Page 11: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 12

Helping the World to Communicate Geographically

EOC Must EOC Must Respond to Respond to

Dynamic Events Dynamic Events Happening Happening

SimultaneouslySimultaneously……

conduct multi-conduct multi-source analysissource analysis

Page 12: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 13

Helping the World to Communicate Geographically

Scenario 1:Scenario 1:Searching for Searching for mobile target mobile target

in Urban in Urban EnvironmentsEnvironments

Emergency Operations CenterEmergency Operations Center

Scenario 2:Scenario 2:La Plata La Plata TornadoTornado

Scenario 3:Scenario 3:Wilson Wilson Bridge Bridge

IncidentIncident

Scenario 1B:Scenario 1B:Searching for Searching for mobile target mobile target

in Urban in Urban EnvironmentsEnvironments

Detection, Planning, Response, RecoveryDetection, Planning, Response, Recovery

TaskingTasking CollectionCollection Processing Dissemination AnalysisProcessing Dissemination Analysis

Potential for Tasking, Potential for Tasking, Collection, Collection,

Processing, Processing, Dissemination, and Dissemination, and

Analysis across open, Analysis across open, industry interfacesindustry interfaces

Target

Page 13: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 14

Helping the World to Communicate Geographically

Access to diverse, Access to diverse, multi-source, real-time multi-source, real-time

information across information across open, industry open, industry

interfacesinterfaces

Page 14: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 15

Helping the World to Communicate Geographically

OGC WFS, OGC WFS, WCS, and WCS, and

GML support GML support multi-source multi-source

analysisanalysis

Page 15: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 16

Helping the World to Communicate Geographically

Situational Situational awareness awareness

generated rapidly generated rapidly in response to in response to

unexpected unexpected eventsevents

Massive amounts Massive amounts of data integrated of data integrated

in minutesin minutes

Integrated live sensorsIntegrated live sensors

Page 16: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 17

Helping the World to Communicate Geographically

Rapid, flexible symbolizationRapid, flexible symbolization

Page 17: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 18

Helping the World to Communicate Geographically

OWS 1.2 Candidate SpecificationsOWS 1.2 Candidate Specifications

• Common ArchitectureCommon Architecture– Service Architecture IPRService Architecture IPR

– Service Information Model IPRService Information Model IPR

– Messaging Framework IPRMessaging Framework IPR

– Registry Service IPRRegistry Service IPR

– UDDI Experiment IPRUDDI Experiment IPR

– SOAP Experiment IPRSOAP Experiment IPR

– Integrated Client IPRIntegrated Client IPR

– Context IPRContext IPR

• Image HandlingImage Handling– Image Handling Architecture IPRImage Handling Architecture IPR

– Image Handling Design IPRImage Handling Design IPR

– Image Handling Metadata IPRImage Handling Metadata IPR

– Web Coverage Service IPRWeb Coverage Service IPR

• Feature HandlingFeature Handling– Style Management Service IPRStyle Management Service IPR– Style Layer Descriptor IPRStyle Layer Descriptor IPR– Web Feature Service IPRWeb Feature Service IPR– Web Map Service IPRWeb Map Service IPR– Coverage Portrayal Service IPRCoverage Portrayal Service IPR– GML3.0 Schema Evaluation IPR GML3.0 Schema Evaluation IPR

• Sensor Web EnablementSensor Web Enablement– Observations and Measurement Observations and Measurement

IPRIPR– Sensor Model Language IPRSensor Model Language IPR– Sensor Collection Service IPRSensor Collection Service IPR– Sensor Planning Service IPRSensor Planning Service IPR– Web Notification Service IPR Web Notification Service IPR

Page 18: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 19

Helping the World to Communicate Geographically

OWS 1.2 Service FrameworkOWS 1.2 Service Framework

= OGC/IP Interface

Map Viewer Client

WFST WCS

ImageryExploitation

Client

Discovery Client

SWE Client

Coord.Transf.Service

CPS

SensorInstanceRegistry

Service Type

Registry

Service InstanceRegistry

Data Services

PortrayalServices

Registry/Catalog Services

Processing Services

Multi-source, Integrated Application Client

Bind

Find

SCSGeocoderWMS

SMS Gazetteer

Encodings

GML (2.1 and 3.0)

SLD

ServiceMetadata SensorML Obs

& Meas

XIMA

LOF

Other TypeRegistry

IAS

ImageMetadata

Publish

Value-Add Client

SymbolManagement

Client

SPS

OtherInstanceRegistry

SensorType

Registry

WOSFilter

Encoding

CatalogServices

GridCov.

SimpleFeatures

Page 19: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 20

Helping the World to Communicate Geographically

Anticipated OGC Web Services-2 ThemesAnticipated OGC Web Services-2 Themes

Sensor Web Enablement

Open Location Based Services

Modeling & Simulation (Toxic Dispersion)

Image Handling

Common Architecture

G-Commerce

Decision Support

Multi-Source Info Ops (“Portal-In-A-Box”)

Advancingthe

SpatialWeb

Applications That Broadly

Span The Market

Page 20: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 21

Helping the World to Communicate Geographically

OGC Conformance and OGC Conformance and Interoperability Test and Evaluation Interoperability Test and Evaluation (CITE) Initiative (CITE) Initiative

Geospatial Community

s

www.ogcnetwork.org

Reference Implementations

WMS

WFSWMS

WFS

WMS

Lab accessible on OGC Network

Company A WMS v1.1.1Company B WFS v1Company C WMS v1.0.0

CITE Portal Reference Implementation

s

Conformance Testing

Resources

WMS TesterWFS TesterGML TesterTest Resources

• Develops Develops Consortium-Consortium-approved approved process by process by which software which software vendors can vendors can prove their prove their products’ products’ conformance to conformance to OGC’s OpenGIS OGC’s OpenGIS SpecificationsSpecifications

• CITE Initiative CITE Initiative provides a provides a methodology and methodology and tools which meet tools which meet vendors’ need to vendors’ need to distinguish their distinguish their products from non-products from non-conformant products conformant products and the buyers’ need and the buyers’ need for guarantees of for guarantees of interoperabilityinteroperability

Page 21: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 22

Helping the World to Communicate Geographically

OGC Critical Infrastructure Protection Initiative OGC Critical Infrastructure Protection Initiative (CIPI)(CIPI)

• Develops, tests, and validates interoperable architectures for infrastructure information sharing challenges

• Conducts Pilots coordinated with National, State, Local Government, and Commercial Organizations under defined activity framework

• Implements interoperable nodes at USGS, NIMA, GeoConnections Canada, and Census data centers

• Enables growth of a collaborative, distributed network of critical infrastructure information services based OGC Web Services, supports policy and legislative activity

Detection

Planning

Prevention

Recovery

Response

ApplicationClients

BrokerServices

Users

(Local, State, National)

CIPFunctions

Policy Infrastructure - Security

Assesses policy and security structuresto support infrastructure information sharing

Conducts multiple Pilot Projects(CIPI-1, 2, 3…)

Page 22: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 23

Helping the World to Communicate Geographically

CIPI-1 OverviewCIPI-1 Overview

• CIPI-1.1 Kickoff occurred October 16-17

• Two Builds in CIPI-1– Phase 1 – Complete

• GeoConnections• USGS• Security• Contributory Node• Alert messaging

– Phase 2 – now underway• Schema Translation• NIMA Node• Security• Contributory Node• WFS Extension• Integrated Experiments

Contributory Contributory NodesNodes

Page 23: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 24

Helping the World to Communicate Geographically

CIPI-2 (CIPI-2 (Census Bureau Pilot)Census Bureau Pilot)

• RFQ released 27 Sep

• RFQ responses due 17 Oct

• Response Evaluation 18 Oct – 1 Nov– Sponsor meeting and final review 1 Nov

• Participant Negotiations 1 Nov - 8 Nov

• Initiative Kick-off 12 Nov

• Demonstration / Pilot Development 12 Nov – May ‘03

• Demonstration 15 Apr ‘03

Collaborating Communities

Users GIS Functions

Geospatial One-Stop

Local Mapping Services

State Mapping Services

Federal Mapping Services

eGov Mapping Services

CIPI POLICY & TECHNOLOGY INFRASTRUCTURE

STIA

Update Boundary Info

LEGEND

Certification Authority

Security Infrastructure

Distributed Geoprocessing Resource

Application Service

OGC

WebBAS

CIPI 2

WebTIGERUpdate TIGER Data

Census Node

CIPI-1 Node

CIPI-1 Node

CIPI-1 Node

Page 24: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 25

Helping the World to Communicate Geographically

Geospatial One-Stop – Transportation Geospatial One-Stop – Transportation Pilot(GOS-TP)Pilot(GOS-TP)

• Supports National Spatial Data Infrastructure (NSDI) and Geospatial One Stop objectives

• GOS-TP is an OGC effort focused on assessing data content standards and application schema models, implemented as part of Geospatial One Stop

• Promotes migration to an environment that enables spatial data maintained by various collaborating communities to be readily accessed, integrated, fused and applied to support critical decision-making

• Implements WFS’s in California and Oregon that serve data that conforms to the emerging Road Transportation Data Content Standard

EnablesInformation

Interoperability

Oregon Node

WFS-T+ WMS

Road Data

Data & ServiceCatalog

Oregon Node

WFS-T+ WMS

Road Data

Data & ServiceCatalog

WFS-T+ WMS

Road Data

Data & ServiceCatalog

California Node

WFS-T+ WMS

Road Data

Data & ServiceCatalog

California Node

WFS-T+ WMS

Road Data

Data & ServiceCatalog

WFS-T+ WMS

Road Data

Data & ServiceCatalog

Jackson Co. Node

WFS-T+ WMS

Road Data

Data & ServiceCatalog

Jackson Co. Node

WFS-T+ WMS

Road Data

Data & ServiceCatalog

WFS-T+ WMS

Road Data

Data & ServiceCatalog

Siskiyou Co. Node

WFS-T+ WMS

Road Data

Data & ServiceCatalog

Siskiyou Co. Node

WFS-T+ WMS

Road Data

Data & ServiceCatalog

WFS-T+ WMS

Road Data

Data & ServiceCatalog

Page 25: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 26

Helping the World to Communicate Geographically

Geospatial One-Stop Portal Initiative (GOS-PI)Geospatial One-Stop Portal Initiative (GOS-PI)

• Geospatial One-Stop is one of 24 federal E-Government initiatives to improve effectiveness, efficiency, and customer service throughout all layers of government.

• Geospatial One-Stop builds upon National Spatial Data Infrastructure (NSDI) objectives to enhance interoperability among geographic components of government activities and to maintain a common inventory of geospatial content and services.

InternetInternet

@portalhost site@portalhost site

InternetInternet

Geospatial One-Stop Portal

Web Browser (Thin Client)Web Browser (Thin Client) Applications (Thick Client)Applications (Thick Client)

GNIS

Services

Provider Organizations

Data

GNIS

Services

Provider Organizations

Data

GNIS

Services

Provider Organizations

Data

Services

Provider Organizations

ServicesServices

Provider Organizations

Data

ClientsWFS WMS WCS CatWFS ClientsWFS WMS WCS CatWFS

(gazetteer)

• ScheduleSchedule

Nov 2002: Nov 2002: Release Release CFARCFARDec 2002: Dec 2002: Release Release RFQRFQJan 2003Jan 2003 RFQ responsesRFQ responses

Feb 2003:  Feb 2003:  Kickoff Kickoff Project Project

May 2003May 2003 Initial DemoInitial Demo

June 2003:June 2003: CompleteComplete

Page 26: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 27

Helping the World to Communicate Geographically

Geospatial1-StopPortal

Segments:

County Provider Node

State Provider Node

Federal Provider Node

County Provider Node

Internet(Data Sources)

Internet(Data Sources)

Application Services

Portrayal Services

Processing Services

Catalog Services

Application Integration Framework

DistributedUsers

DistributedUsers

Auth. Services

GOS Portal Segments and Reference ArchitectureGOS Portal Segments and Reference Architecture

• 22 Responses Rcvd22 Responses Rcvd

EnterpriseEnterprise viewpoint: articulates a viewpoint: articulates a“business modelbusiness model”” that should be that should beunderstandable by all stakeholders;understandable by all stakeholders;focuses on purpose, operationalfocuses on purpose, operationalobjectives, policies, enterpriseobjectives, policies, enterpriseobjects, etcobjects, etcInformation Information viewpoint: focuses onviewpoint: focuses oninformation content and systeminformation content and systembehavior (i.e. data models,behavior (i.e. data models,semantics, schemas).semantics, schemas).Computational Computational viewpoint:viewpoint:captures component and interfacecaptures component and interfacedetails without regard todetails without regard todistribution.distribution.Engineering Engineering viewpoint: exposesviewpoint: exposesthe distributed nature of the systemthe distributed nature of the systemand provides standard definitions toand provides standard definitions todescribe engineering constraints.describe engineering constraints.

Page 27: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 28

Helping the World to Communicate Geographically

Property and Land Information Initiative Property and Land Information Initiative Planning Activity - Call for SponsorsPlanning Activity - Call for Sponsors

• Call for Sponsors that may support an OGC Property and Land Information (PLI) Initiative.

• This planning activity will seek interested Sponsors to provide input on – technology requirements

and concepts

– capabilities to enable broader sharing and application of property data and land information between collaborating organizations.

Insert new graphics

Page 28: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 29

Helping the World to Communicate Geographically

Emergency Mapping Symbology (EMSym)Emergency Mapping Symbology (EMSym)

• Emergency Mapping Symbology (EMSym) Interoperability Initiative

– A planned collaborative effort to support development and testing of an Interoperability Capability that applies emerging Emergency Mapping Symbology for Homeland Security within an interoperable specification framework for geographic symbolization.

• Opportunities to leverage common interest and requirements

– Coordinating with SSMC– Initial coordination with DGIWG

Insert new graphics

Page 29: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 30

Helping the World to Communicate Geographically

OGC Geographic Objects Initiative OverviewOGC Geographic Objects Initiative Overview

• Extends OGC beyond the WWW

• Provides for future interoperability on multiple computing platforms

• Uses Unified Modeling Language™ (UML™) to capture and express the essence of information and services

• Allows developers to take advantage of the valuable components on any development platform required.

Abstract Model (UML)

Profile for DCP

Implementation

The GO-1 Initiative is developing an open set of consistent, language-independent interface models for describing, managing, rendering, and manipulating map displays,

features, coordinate spaces and other topics that can support development of applications on multiple distributed

computing platforms (DCP). These Geographic Objects will be defined at an abstract level using UML models and at a DCP

specific level for Java and Web implementations.

Page 30: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 31

Helping the World to Communicate Geographically

Geographic Objects-1 Technology View Geographic Objects-1 Technology View

Produce an Abstract Service Interface Specification for all GO-1 Objects (Application Objects, Information Objects and Service Objects) from which multiple implementation profiles could be derived for specific target platforms. Specify, build and test a Java Implementation Profile as derived from the GO-1 Abstract Service Interface Specification.

ImplementationSpecifications

For Web

OtherSources

OGCAbstract Service Interface Specifications

1 1

APPLICATION OBJECTS

INFORMATION OBJECTS

SERVICE OBJECTS

UML

Generate Generate

2Generate

ImplementationSpecifications for

Java Profile

Other(ex. .Net)

Other(XML Schema)

Page 31: © 2003, OGC Specification Update June 2003, FGDC By Sam Bacharach sbacharach@opengis.org.

© 2003, OGC 32

Helping the World to Communicate Geographically

OGC on Review PolicyOGC on Review Policy

• OGC concurs with the Review Policy as written, given the following:• Full implementation of the process will not be truly rational until:

– An USG Architecture (Framework) is defined to describe how the Endorsed “Mandatory” or “Recommended” Standards ‘fit’ together to meet government needs

• Somebody may have developed slickest steering wheel in existence, but it is not of much value in an fighter jet airplane

• The GIRM was intended to serve this purpose, and to compliment data content standards development by FGDC

• We do not believe you can properly evaluate any standards for adoption without this level of organization

• The FGDC determination of status organizations as Voluntary Consensus should be performed once– By assuring that organization policies and procedures meet the criteria.

Repetitave determination is not warranted. – Rather, require that all changes in Policies and Procedures that might affect

this status be identified when they occur