The OGC seeks comment on GML Coverages GeoTIFF extension and WCS 2.0 GeoTIFF extension standard
The Open Geospatial Consortium (OGC®) seeks comment on a GeoTIFF extension to the OGC GML Coverages (GMLCOV) 1.0 Standard and on a GeoTIFF extension to the OGC Web Coverage Service (WCS) 2.0 Standard, based on the former.
The OGC Geography Markup Language (GML) Encoding Standard is a widely used XML encoding for geospatial data of all types. OGC "coverages", which can be encoded in GML, associate positions within a bounded space to feature attribute values. Examples of these geospatial coverages include Earth images, referenced and non-referenced rasters, curvilinear grids, and point clouds.
The OGC GML 3.2.1 Application Schema – Coverages (GMLCOV), based on OGC Abstract Topic 6 (which is identical to ISO 19123), provides a unified method for encoding OGC coverages in GML, the OGC Sensor Web Enablement (SWE) Common Standard, and the OGC Web Coverage Service (WCS) Interface Standard. As GMLCOV is independent of a particular service definition, it allows coverage data to be exchanged through different types of services that implement these OGC standards.
To provide maximum flexibility in sharing coverage data, the GML Coverages GeoTIFF extension provides a way to encode coverages that are represented in encoding formats other than GML, such as GeoTIFF. The WCS 2.0 GeoTIFF extension binds the former extension to WCS 2.0 to allow usage of GeoTIFF encoded coverages with WCS. The OGC seeks public comment on the OGC documents describing the candidate GMLCOV and WCS extension standards for encoding GeoTIFF data in GMLCOV and using them with WCS. These documents are free and can be downloaded below.
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: Click here to submit comments The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template