Exported Content

REST SC

Chair(s):

Lieberman, Joshua (Harvard University)

Group Description:

The work of the REST Sub Committee of the OGC Standards Program is to define a set of best practices and potentially rules for use in creating REST serializations/instances of existing or furture OGC web services standards.

Chair: Josh Lieberman

GeoAPI Implementation Specification

The GeoAPI Implementation Standard defines, through the GeoAPI library, a Java language application programming interface (API) including a set of types and methods which can be used for the manipulation of geographic information structured following the specifications adopted by the Technical Committee 211 of the International Organization for Standardization (ISO) and by the Open Geospatial Consortium (OGC). This standard standardizes the informatics contract between the client code which manipulates normalized data structures of geographic information based on the published API and the libr...

OGC network Common Data Form (netCDF) standards suite

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...

SWE Service Model Implementation Standard

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...

Pages