This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a "native" storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and per...
This standard describes the use cases, requirements and conceptual model for the OWS Context encoding standard. The goal of this standard is to provide a core model, which is extended and encoded as defined in extensions to this standard. A ‘context document’ specifies a fully configured service set which can be exchanged (with a consistent interpretation) among clients supporting the standard.
The OGC Web Services Context Document (OWS Context) was created to allow a set of configured information resources (service set) to be passed between applications primarily as a collection of serv...
3) Official Schemas
4) Related News
WaterML 2.0 is a standard information model for the representation of water observations data, with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of exchange requirements, some of which are described later in this document.
The OGC GeoSPARQL standard supports representing and querying geospatial data on
the Semantic Web. GeoSPARQL defines a vocabulary for representing geospatial data in
RDF, and it defines an extension to the SPARQL query language for processing
geospatial data. In addition, GeoSPARQL is designed to accommodate systems based on qualitative
spatial reasoning and systems based on quantitative spatial computations.
This standard defines a protocol for RS232 and Ethernet connected instruments. PUCK addresses installation and configuration challenges for sensors by defining a standard instrument protocol to store and automatically retrieve metadata and other information from the instrument device itself.
Most sensor networks require careful manual installation and configuration by technicians to assure that software components are properly associated with the physical instruments that they represent. Instrument driver software, configuration files, and metadata describing the instrument and its ...
The OGC Open GeoSMS Standard provides developers with an extended Short Message Service (SMS) encoding and interface to facilitate communication of location content between different LBS (Location-Based Service) devices or applications. SMS is the open text communication service standard most commonly used in phone, web and mobile communication systems for the exchange of short text messages between fixed line or mobile phone devices. The lightweight and easy to implement Open GeoSMS Standard facilitates interoperability between mobile applications and the rapidly expanding world of geospatia...
This OGC® standard specifies the interfaces, bindings, requirements, conformance classes, and a framework for implementing extensions that enable complete workflows for ordering of Earth Observation (EO) data products.
netCDF is a set of software libraries and self-describing, machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data. The conventions for climate and forecast (CF) metadata are designed to promote the processing and sharing of netCDF files. The conventions define metadata that provide a definitive description of what the data represents, and the spatial and temporal properties of the data.
The OGC CF-netCDF standard consists of a suite of standards that support encoding of digital geospatial information representing space/ti...
This standard currently defines eight packages with data types for common use across OGC Sensor Web Enablement (SWE) services. Five of these packages define operation request and response types. The packages are: 1.) Contents – Defines data types that can be used in specific services that provide (access to) sensors; 2.) Notification – Defines the data types that support provision of metadata about the notification capabilities of a service as well as the definition and encoding of SWES events; 3.) Common - Defines data types common to other packages; 4.) Common Codes –Defines commonly used li...