Process and Technology of the Open Geospatial Consortium
Total Page:16
File Type:pdf, Size:1020Kb
Geospatial Interoperability Standards Biology and Environment Phillip C. Dibner Ecosystem Associates SEE Grid II Canberra, Australia March 16, 2005 Motivation • Tens (100s?) of billions of dollars worth of spatial data already archived at diverse sites, using a variety of data formats and supporting software suites • Too large and expensive to move and convert • Prohibitively inconvenient to store and manage centrally • Operationally constraining and administratively challenging to mandate a single-technology supplier The Solution: Interoperate • Data remain in place • No constraints on maintenance operations or policy • Existing in-house tools and applications remain viable • Only the interfaces need be well-defined among interoperating clients and servers Open Geospatial Consortium (Until Recently “Open GIS Consortium”) • The Open Geospatial Consortium (OGC) grew out of the need among federal agencies to share data. • Currently a collaboration of more than 250 vendors, integrators, academic institutions, government and private agencies, and other end users. • Published specifications – Abstract Spec in 16 volumes – 14 Implementation Specs published – Recommendations and Discussion Papers – More in various stages of creation or refinement • Technology baseline is maturing. Increasing emphasis on application to specific domains. Structural View of OGC • Planning Committee – Steering, policy, general management and oversight • Strategic Member Advisory Committee • Technical Committee (TC) – Meets 4 times per year. Next: United Nations, NYC, January 17 - 20, 2005. C’mon down! – Develops specifications, discussion papers, recommendations – Working Groups (WGs) • Technology • Domain Current (+/-) Working Groups • Architecture (Arch WG) • Coordinate Reference Systems (CRS WG) • Decision Support WG (DS WG) • Earth Observation (EO WG) • Geo Digital Rights Management (GeoDRM WG) • GeoAPI (GeoAPI WG) • Geography Markup Language (GML WG) • Image Exploitation Services (IES WG) • Information Communities and Semantics (ICS WG) • Location Services (LS WG) • Metadata (Metadat WG) • Natural Resources and Environment (NRE WG) • Query Language (Query WG) • Sensor Web (SWE WG) • University (Univ WG) • Web Feature Service (WFS WG) • Joint Advisory Group (JAG) Revision Working Groups • Focus on (revisions to !) an existing specification • Formed and dissolved according to status of that spec • Current (+/-): – Catalog RWG –GML RWG – GO-1 RWG – OpenLS RWG – Styled Layer Descriptor RWG – RWGs for WCS, WFS, WMS Process View of OGC • Interoperability Program(IP) – Interoperability Initiatives, Interoperability Experiments, Pilots, etc. – Experimental testbeds for proposed technologies, test existing specs and implementations, discover needs and generate requirements and proposals for new specs. • Standards Program – Requirements come from WGs, IP, and other sources – Produces draft standards (or accepts them from IP) – WG votes bring candidate documents to the TC at large Philosophy of Standards Development • Minimal impact on existing implementations • Base content and communications standards on implementation-independent abstractions • Use the expertise of other information communities (“buy don’t build”) • Interaction with and participation in other standards bodies – ISO TC 211: • ISO 19107, Feature Geometry; ISO 19128, Web Map Server spec; 19136, GML, are ISO standards or standards in process • Use ISO 19115, 19119, 19139, others –W3C, OMG, … • SOAP, WSDL, UDDI (testbeds), ebRIM -> OGC RIM, BPEL for service chaining (recent testbed), serious examination of XQuery –TDWG?? Abstract Specification • Conceptual foundation / reference model for spec development • http://www.opengeospatial.org/specs/?page=abstract • 17 “books” or “Topics” (including overview) • Each topic described in 6 sections, including: – Essential Model: real-world items relevant to or that define the universe of discourse – Abstract Model: defines classes and their relationships, typically using a graphical or lexical language – Well known structures, described in UML • Two central themes: sharing geospatial information, and providing services Abstract Spec: Sharing Geospatial Information • Fundamental Data Types – Topic 5: The OpenGIS Feature. (Misleading, useful hint: think “vector data - point, line, polygon.”) • An abstraction of a real-world phenomenon • Geographic if associated with a location on the Earth • Geometric and non-spatial attributes – Topic 6: The Coverage Type. (Misleading hint: think “raster.”) • A specialization of feature • A two- (sometimes higher) dimensional metaphor for phenomena on the surface of the earth • Essentially a function over a contiguous area • Also requires a mapping from earth coordinates to the coverage extent, to provide geolocation – Topic 7: Earth Imagery. A special case of Coverage Abstract Spec: Sharing Geospatial Information • Prerequisites for sharing geospatial data – Topic 1: Feature Geometry • Geometric and topological primitives and operators – Topic 2: Spatial Reference Systems – Topic 3: Locational Geometry Structures • Within images, rasters, and similar entities – Topic 4: Stored Functions and Interpolation • Essential for the support of Coverages – Topic 8: Relationships Between Features – Topic 11: Metadata • Modeling and query Abstract Spec: Providing Geospatial Services • Topic 12: Service Architecture – comprehensive suite of services – relationships to each other – CORBA / OMG compliance and relationships • Topic 13: Catalogs • Topic 15: Image Exploitation Services • Topic 16: Image Coordinate Transformation Services Abstract Spec: Miscellaneous Topics • Topic 9: Quality • Topic 10: Feature Collections – Transient or persistent – Dependent on world view or “Project Structure” – Abstract model not yet defined • Topic 14: Semantics & Information Communities Implementation Specifications • Provide basis for working software; detail the interface structure between software components • http://www.opengeospatial.org/specs/?page= specs • Tested and refined in Testbeds and Pilot programs; recommended changes are brought back to the Technical Committee for vote • Many implementations in commercial and open-source software Recommendations and Discussion Papers • Recommendations: – http://www.opengeospatial.org/specs/?page=recommendation – Revisions of other specs (e.g., GML and WMS) – Units of Measure, Observation: particularly interesting to TDWG • Discussion Papers – http://www.opengeospatial.org/specs/?page=discussion – Forum for public review of results and proposed but unvoted standards – Geoparser, Geocoder, Gazetteer – Other results from IP initiatives OGC Data Services (“W*S”) Pattern What can you Here… do? GetCapabilities read this. <Service> … </Service> <Capabilitiess> … </Capabilitie> <Layer> … </Layer> Capabilities Document Great! Give Get Map, Feature, or Coverage me data Here you Data are…. Capabilities Document • An XML document that describes the service. • Specified by XML Schema in most recent version. • <Service> element that provides general metadata for the service as a whole – E.g., name, human-readable title, online resource • <Capability> metadata – Operations such as <GetMap> and <GetCapabilities> – Output formats for these operations (e.g., PNG or JPG for GetMap requests – URL prefix for each operation • Hierarchically nested <Layer> elements – Name, title – Spatial Reference System (SRS) - supports EPSG codes – Enclosing <LatLonBoundingBox> of layer NOAA Hurricane Image of the Gulf of Mexico Source: Web Map Service Implementation Specification OGCProject Document 01-047r2 Political, Coastline, and Populated Areas, Southeastern United States Source: Web Map Service Implementation Specification OGCProject Document 01-047r2 Combined Hurricane Image and Population Map Source: Web Map Service Implementation Specification OGCProject Document 01-047r2 Cascading Map Server Map GIF Server WGS 84 Different viewer client in browser! Web Browser Cascading Map Server Map PNG Server AL St Pln Capabilities Integrator Map internet internet GIF Map Server NAD 83 Integrator Map JPEG Server WGS 84 Adapted from Web Map Server Demonstration presentation © 2000 OGC Web Feature Server • Passes GML-encoded data (not pictures) between server and client. • Basic WFS: – GetCapabilities – DescribeFeatureType – GetFeature • Transactional WFS provides for remote update of datastore: – Transaction –LockFeature OGC Data Services Web GetCoverage Coverage WCS Client Service Coverage Data Coverage Data Coverage Portrayal Service Web GetFeature WFS Feature Client Service Feature Data (as GML) Vector Data SLD Service GetMap Map Layers Web Map WMS Service Client Rendered Map Image Sensor GetObservation SOS Observation Client Constellation of Sensors Service Measurement Collection Planning Studies Diverse jurisdictions Different data sets Hazards Database Transportation Network Design Server Background 1 Background 2 Natural Resources Canada Protected Areas Management of protected areas: Whose responsibility? Whose jurisdiction? Data Service Application Protected areas from all provinces, multiple services Jurisdictional boundaries overlay Sources: OGC User (http://www.opengeospatial.org/press/?page=ogcuser). Data view: Canadian National Forest Information System. Analysis of an Invasion by Exotic Beetles Green dots: collections of native beetles Yellow: exotics Red: exotics not yet established. Guides and optimizes management practices Sources: OGC User (http://www.opengeospatial.org/press/?page=ogcuser). Data view: Canadian National