Initial Knowledge of OGC Specifications

OpenGISWhat is

OGC provides a comprehensive set of specifications for access to geographic data and geographic information resources in a distributed environment. It includes abstract and implementation specifications. Various vendors develop GIS software in accordance with the specifications set by OpenGIS, and some software can achieve interoperability.

OGIS (Open Geodata Interoperability Specification )-Open Geospatial data interoperability specifications

This specification consists of three parts:

1. Open Geodata Model)
2. OGIS Service Model)
3. Information Comunities Model)

OpenGISService Architecture

This specification classifies Geographic Information Services as follows

1. User interaction service: includes user interface graphics and multimedia management services and service document performance services
2. Model/Information Management Service: mainly includes metadata concept model and data set development operations and storage management services
3. Workflow/Task Service: Mainly used to support certain tasks or work-related activities.
4. Processing Service: mainly refers to services that perform massive computing on geographic data, including space processing service special processing service time-phase processing service and metadata processing service.
5. Communication Service: mainly includes data encoding and data transmission services
6. System Management Service: It mainly refers to the management services of system component applications and networks, as well as management services for user accounts and access permissions.

OWS (OGC Web Service)-OWSAbstract Model

The OWS abstract model includes two types of components: operational and data components.

Operational components include

1. Customer Service, 2. Directory and Registration Service, 3. Application Service, 4. Data Service

Data components include

1. Data, 2. Original data, 3. Name, 4. Association, 5. Container

OWSOperating System Structure
Describes the system concepts involved in applying OWS to the Web environment, including

1. Common Architecture refers to the Common elements in the OGC technical Architecture, including service model encoding mechanism, Web registration service, and other public services.
2. Customer Service is an application client component that can interact with users. It can interact with server-side client application servers and data servers.
3. The client program on the server is the main component of the server. It can interact with the customer service and call application services and data services on the server, including Web drawing and decision support.
4. The basic application service building module that can operate data and provide value-added services includes supporting components for decision-making support for Web drawing.
5. Data Service provides data in OWS, especially basic service component modules of spatial data, including WMS Web Map Server Web element Server WFS Web Feature Server and Web Coverage Server.

OWSTechnical Architecture
Based on the abstract model and operating system structure, the OWS technical architecture is proposed.

1. The public architecture part focuses on the common basic elements in the OGC technical architecture, including service model encoding mechanism Web registration service and other public services.
2. The Web plotting part focuses on the research of Web drawing Customer Service Server Client application data service and supporting Application Service Based on WMTI Web Mapping Test beds I and WMTII WebMapping Test beds II. and so on
3. Image exploitation part focuses on the customer service developed based on Web images, server-side customer application data services, and supporting application services.
4. Sensor Web focuses on the customer service of Sensor networks, server-side customer applications, Data Service-supported application services, as well as Sensor Markup Language and Sensor registration services.
5. The decision support part focuses on the customer service, server-side customer applications, and data service-backed application services supported by decision-making, modeling Markup Language and event and Event Service encoding mechanism

OpenGISService Framework
The OpenGIS service framework establishes public interface exchange protocols and services that can be used by any application, including

1. application customer, 2. Registration Service, 3. Encoding Processing Service, 4. descriptive Service, 5. Data Service

 

OGCInteroperability program service model-(IPSM Interoperability Program Service Model)

A computing model for OpenGIS is described. The OGC interoperability program service model is built on the OGC service architecture, however, it emphasizes how to use existing technical platforms and mechanisms to implement services that are interoperable. A basic idea of this model is that an application can dynamically combine runtime discovery and collection services for e-commerce, information exchange centers, and enterprise applications. since there are many specific methods to implement a service, this model focuses on describing the principles and basic models for creating a dynamic loosely coupled system.

 

Ogc sfs (Simple Element Specification)

Application programming interfaces (Simple Element specification for OGC) specifies the release, storage, reading, and simple operation of simple elements such as points, lines, surfaces, and multiple points. These Specifications aim to enable GIS software designers to use these interfaces to operate elements composed of simple geometric elements under different technologies (OLE/COM, SQL, and CORBA.

 

CompletedWMSMap Service System

Harvard University WMS (Distributed) Servers [14. The engine used by the system to connect to the backend database is ArcIMS 3.1 spatial engine. The GetMap and GetCapabilities operations are completed. GetMap does not support user-defined styles. Support map image output in various bitmap formats

Intergraph GeoMedia WebMap WMS Adapter Kit [15]: GeoMedia WMS AdapterKit uses GeoMedia WebMap to develop a map server that complies with WMS1.1.0 specifications. It supports the GetCapabilities, GetMap, and GetFeatureInfo interfaces. It can display images according to custom rules. The results returned by the GetMap operation can be JPG or PNG images.

 

This article from the CSDN blog, source: http://blog.csdn.net/angeltimes/archive/2007/03/05/1521554.aspx