�ݺ�ߣ

Editor's Notes

• #7: As a response, the OpenGIS concept and dream began due to: 1. The user’s need to integrate geographic information contained in heterogeneous data stores whose incompatible formats and data structures have prevented interoperability. This incompatibility has limited use of the technology in enterprise and Internet computing environments, and the time, cost, and expertise required for data conversion have slowed adoption of geoprocessing across all market segments. 2. The larger community’s need for improved access to public and private geodata sources, with preservation of the data’s semantics. 3. Agency and vendor needs to develop standardized approaches for specification of geoprocessing requirements for information system procurements. 4. The industry’s need to incorporate geodata and geoprocessing resources into national and enterprise information infrastructures, in order that these resources may be found and used as easily as any other network-resident data and processing resources. 5. Users’ need to preserve the value of their legacy geoprocessing systems and legacy geodata while incorporating new geoprocessing capabilities and geodata sources. From the Technology Perspective, OGC envisions the full integration of geospatial data and geoprocessing resources into mainstream computing and the widespread use of interoperable, commercial geoprocessing software throughout the information infrastructure.
• #22: Implementation of OGC's OpenGIS Specifications open interfaces – vendor-neutral and technology neutral – enables a "Spatial Web" in which diverse spatial data and spatial processing resources are available and can be used together. The different interfaces for "features" (vector data) and "coverages" (imagery and sensors) are based on the same geometry model and services architecture. Use of these standards enables applications to easily access and integrate multi source data, enabling better and more effective information fusion and exploitation.