{
  "id": "open-geospatial-consortium",
  "title": "Open Geospatial Consortium",
  "lang": "en",
  "source_lang": "en",
  "summary": "The Open Geospatial Consortium is an international nonprofit organization that develops open standards for sharing, accessing, and processing geographic information across software systems.",
  "category": "geography",
  "subcategory": "",
  "type": "organization",
  "aliases": [
    "OGC",
    "Open GIS Consortium",
    "OpenGIS Consortium"
  ],
  "generated_at": "2026-11-04",
  "model": "pro/gpt-6.1-sol",
  "url": "https://aiwiki.page/en/open-geospatial-consortium/",
  "translations": {
    "zh-Hans": {
      "url": "https://aiwiki.page/zh/open-geospatial-consortium/",
      "json": "https://aiwiki.page/zh/open-geospatial-consortium.json"
    }
  },
  "sections": [
    {
      "heading": "",
      "text": "The Open Geospatial Consortium (OGC) is an international nonprofit standards-development organization concerned with geographic information and location-based technologies. Its members include businesses, government agencies, universities, research institutions, and other organizations. It develops publicly available standards that enable different software systems to exchange, interpret, display, and process geospatial information. These standards support geographic information systems (GIS), web mapping, environmental monitoring, three-dimensional city models, and other applications that depend on location.\n\nOGC is a standards organization rather than a software vendor or a central repository of geographic data. Its specifications describe interfaces, data encodings, conceptual models, and implementation requirements that software developers and data providers can adopt."
    },
    {
      "heading": "Origins and development",
      "text": "OGC was established in 1994 as the Open GIS Consortium. Its formation addressed a persistent difficulty in geographic computing: data and software from different suppliers often used incompatible formats, interfaces, and spatial models. Moving information between systems could require custom conversion software and could lose important information about geometry, attributes, or spatial reference.\n\nThe organization adopted the name Open Geospatial Consortium in 2004, reflecting a scope extending beyond conventional desktop GIS to distributed services, mobile applications, sensors, and other location-enabled technologies.\n\nIts standards work developed alongside changes in computing. Early specifications emphasized shared geometry models and database access. As the Internet became a major platform for geographic information, OGC standardized web services for maps, geographic features, and gridded data. More recent work includes web-oriented application programming interfaces, cloud-based access, streaming observations, and three-dimensional geospatial information.\n\nThese generations coexist. Established web-service standards remain widely deployed, while newer interfaces offer alternatives suited to contemporary web development."
    },
    {
      "heading": "Purpose and approach",
      "text": "The central objective of OGC standards is interoperability: allowing independently developed systems to work together without requiring a separate custom integration for every pair of products.\n\nInteroperability involves several distinct problems:\n\n- Data structure: how geometry, attributes, observations, and multidimensional values are represented.\n- Service behavior: how a client discovers available data, submits a request, and interprets a response.\n- Spatial referencing: how coordinates are associated with a coordinate reference system, including relevant units and axis conventions.\n- Meaning: how different communities describe comparable objects, properties, and observations.\n- Conformance: how an implementation demonstrates that it satisfies specified requirements.\n\nA standard need not prescribe a complete software architecture. It may define a narrow interface, a file format, a conceptual model, or a set of requirements that can be combined with other standards.\n\n“Open” in this context does not mean that every implementation must be open-source software or that all data accessed through an OGC interface must be freely available. Proprietary and open-source products can implement the same standards, and services may impose authentication, licensing conditions, or charges."
    },
    {
      "heading": "Major standards and specifications",
      "text": "Geometry and geographic data encoding\n\nSimple Features establishes a common model for basic geographic geometries, including points, lines, and polygons, together with associated spatial operations. It provides an important foundation for storing and querying vector geographic data in spatial databases.\n\nGeography Markup Language (GML) is an XML-based language for representing geographic information. It supports geometries, features, coordinate reference systems, and application-specific data models. Its flexibility supports detailed information exchange, although complex application schemas can require substantial implementation effort.\n\nGeoPackage defines a portable container based on SQLite for geospatial information, including vector features and tiled imagery. It is useful where data must be transferred as a single file or used without a continuous network connection.\n\nGeoTIFF specifies how georeferencing information is encoded in TIFF imagery. It allows software to locate image pixels in geographic space, making it important for aerial imagery, satellite products, and other raster datasets.\n\nWeb mapping and data access\n\nWeb Map Service (WMS) defines an interface for requesting map images from a server. A client specifies information such as the geographic extent, layers, image dimensions, and output format. The response is generally a rendered image rather than the underlying geographic objects.\n\nWeb Map Tile Service (WMTS) supports access to map tiles organized into predefined tile matrices. This approach is suited to efficient display and caching at established scales.\n\nWeb Feature Service (WFS) provides access to geographic features and their properties rather than only their rendered appearance. Depending on the version and supported capabilities, implementations may also allow changes to feature data.\n\nWeb Coverage Service (WCS) supports access to coverages: spatially or temporally varying phenomena represented through values associated with a domain. Examples include elevation surfaces and multidimensional environmental datasets. Unlike a map image intended primarily for viewing, a coverage can preserve values needed for analysis.\n\nOGC APIs\n\nThe OGC API family develops modular standards around contemporary web practices and application programming interfaces. Different members address features, maps, tiles, coverages, processes, records, and other geospatial resources.\n\nFor example, OGC API – Features defines standardized access to collections of geographic features. The family emphasizes discoverable resources and reusable components rather than requiring every capability to be delivered through one large interface.\n\nOGC API standards are not simply new version numbers for all earlier OGC web services. They form a related but distinct approach, and migration depends on application requirements and available implementations.\n\nSensors and three-dimensional environments\n\nSensorThings API provides a standardized web interface and data model for observations and related information from sensor systems. It helps applications connect measurements with the sensors, observed properties, and features to which those measurements refer.\n\nCityGML defines a conceptual model and exchange framework for semantically structured three-dimensional urban information. It distinguishes objects such as buildings and transportation infrastructure rather than treating a city solely as an undifferentiated visual mesh. Such models can support urban planning, environmental analysis, and infrastructure information management."
    },
    {
      "heading": "Standards development and testing",
      "text": "OGC develops standards through member participation, technical discussion, working groups, review, and formal approval procedures. Domain-oriented groups identify shared requirements, while standards working groups develop or revise particular specifications.\n\nAlongside formal standards development, OGC runs collaborative experimentation and testing activities. Testbeds and pilot projects allow participants to investigate whether proposed interfaces and data models work across independently developed systems. Their results can identify gaps and inform later standards work; an experimental report is not itself necessarily an adopted standard.\n\nFor standards covered by its compliance program, OGC provides testing and certification mechanisms. Conformance testing checks specified requirements and can reduce ambiguity in implementation. Certification applies to the tested implementation and relevant standard, however, rather than guaranteeing that a product will interoperate perfectly with every other system in every deployment.\n\nOGC also cooperates with other standards bodies, notably the International Organization for Standardization’s technical committee for geographic information, ISO/TC 211. Some OGC specifications have corresponding ISO standards. The organizations have overlapping interests but are institutionally distinct."
    },
    {
      "heading": "Applications and limitations",
      "text": "OGC standards are used in spatial data infrastructures, public mapping portals, environmental information services, and cross-organizational data exchange. They can allow one application to combine a background map from one provider, administrative boundaries from another, and observations from a third. They also help separate data publication from the choice of client software.\n\nTheir effectiveness depends on more than adopting a standard’s name. Implementations may support different versions, optional capabilities, encodings, or application profiles. Two conforming systems can therefore require additional configuration to work together.\n\nSyntactic compatibility also does not ensure semantic agreement. Organizations may classify land use differently, use different identifiers for the same object, or collect observations at incompatible spatial and temporal resolutions. Coordinate transformations, data quality, and measurement uncertainty remain important even when transmission follows a common standard.\n\nSecurity and access control require separate attention. A standardized geospatial endpoint does not by itself establish adequate cybersecurity, determine permissible data use, or protect sensitive location information. Providers must address these matters through deployment architecture, access policies, and applicable legal requirements.\n\nLong-lived deployments must also balance compatibility with technical change. Established interfaces may offer mature tooling and a large installed base, while newer APIs may fit modern development practices more closely. Supporting both can improve accessibility but increases maintenance and testing obligations."
    }
  ],
  "links": [
    "geographic-information-system",
    "internet",
    "coordinate-reference-system",
    "vector-geographic-data",
    "geopackage",
    "geotiff",
    "raster-data",
    "web-map-service",
    "application-programming-interface",
    "urban-planning",
    "measurement-uncertainty",
    "cybersecurity"
  ],
  "sources": [],
  "license": "https://creativecommons.org/licenses/by/4.0/"
}