Grid Coverage Exchange as specified by the OGC.

• http://www.opengis.org/docs/01-004.pdf

Once again the GeoAPI package description is a great introduction:

• http://www.opengis.org/docs/01-004.pdf

The Java community had a bit of a rethink on this spec covering THREE points of contention:

1. PARAMETERS - a common parameter class was used. Based on the CRS parameter definition, this was not the best trade (due to complexity). The issue is important - each OGC spec makes its own Parameter model wasting our time.
2. NAME - GridCoverageExchange was thought out with respect to a magic String "name" with no method of data discovery. It is assumed the initial implmentation was based on files, this is a poor assumption - Geotools has managed to make both a file and a wms based GridCoverageExchange.
3. STREAMING - related to the use of Name, the major bit of value in this API is the Format construct (Format turns URL+params into a GridCoverage), changes were made to allow the use of Format with a streaming content such as a GridCoverage retrieved from a URL.

The spec has not moved for 4 years, perhaps interested has shifted to Web Coverage Service.

The ground covered here is worthwhile, in retrospect we should of taken the GridCoverage and Format classes and run with it, it is all client code is using anyways. The higher level Grid Coverage Exchange construct can be built out of the parts, or indeed a Open Web Service Web Coverage Service. Indeed there is a move in GeoAPI to exactly do this breakdown.

The notes taken during API review may be helpful:

• Grid Coverage Exchange Design

Tutorial is also available:

• Using Grid Coverage Exchange