GeoAPI 2.0
Build 2005-06-08

Package org.opengis.coverage.grid

Grid coverages (coverages with gridded data).

See:
          Description

Interface Summary
Format A discovery mechanism to determine the formats supported by a GridCoverageExchange implementation.
GridCoverage Represent the basic implementation which provides access to grid coverage data.
GridCoverageExchange Support for creation of grid coverages from persistent formats as well as exporting a grid coverage to a persistent formats.
GridCoverageReader Support for reading grid coverages out of a persisten store.
GridCoverageWriter Support for writing grid coverages into a persistent store.
GridGeometry Describes the geometry and georeferencing information of the grid coverage.
GridPacking Describes the packing of data values within grid coverages.
GridRange Specifies the range of valid coordinates for each dimension of the coverage.
 

Class Summary
ByteInValuePacking Specifies the order of the bytes in multi-byte values.
ValueInBytePacking Order of values packed in a byte for sample dimensions with less than 8 bits.
 

Exception Summary
CannotCreateGridCoverageException Thrown when a grid coverage can't be created.
FileFormatNotCompatibleWithGridCoverageException Thrown when a grid coverage can't be exported in the specified format.
GridNotEditableException Thrown when an attempt is made to write in a non-editable grid.
InvalidRangeException Thrown when a grid range is out of grid coverage bounds.
 

Package org.opengis.coverage.grid Description

Grid coverages (coverages with gridded data). The following is adapted from OpenGIS® Grid Coverages Implementation Specification.

This Grid Coverage Implementation specification can accommodate grid coverages with the following characteristics:

 

Grid Coordinate System

A grid coverage has a grid coordinate reference system which allows for addressing individual cells in the grid. Individual cells are centered on the grid points. A grid has an ordering of cell values with the first cell in this ordering having a grid coordinate of 0,0. A two dimensional grid coverage with 512 rows and 512 columns would have grid coordinates with a range from 0 to 511 rows and 0 to 511 columns. The gridRange attribute GridGeometry structure defines the grid coordinate range. The number of cells in a dimension of the grid can be calculated as grid range maximumminimum.

 

Grid Coverage Tiling

This implementation specification has no explicit interfaces to retrieve data values from a grid coverage in tiles. It is expected that the implementation will efficiently retrieve data values when the client implementation retrieves data values on tile boundaries. The optimal size to access a dimension can be determined from the optimalDataBlockSizes attribute.

 

Interoperability

To help interoperability, many interfaces contained in this architecture have been made immutable. The assumption is that the objects supporting these interfaces should be immutable. This means that the objects should not change after a factory has created them. In particular, the following interfaces are assumed to be backed by immutable objects: SampleDimension, Format, GridCoverageExchange, Operation, GridAnalysis, GridCoverageProcessor.

In a GridCoverage, only the cell values may change. The size, geometry, interpolation, sequencing etc should never change. However, clients should be aware that the Grid Coverage object behind the GridCoverage interface may be adapted from other GridCoverage interfaces, so changing the grid point (pixel) values through one GridCoverage could change the grid point values in others. To allow client applications to anticipate adapted Grid Coverages being changed indirectly, the source Grid Geometry object(s) for adapted Grid Geometry objects can be traced.

 

WARNING: THIS PACKAGE WILL CHANGE. Current API is derived from OGC Grid Coverages Implementation specification 1.0. We plan to replace it by new interfaces derived from ISO 19123 (Schema for coverage geometry and functions). Current interfaces should be considered as legacy and are included in this distribution only because they were part of GeoAPI 1.0 release. We will try to preserve as much compatibility as possible, but no migration plan has been determined yet.


GeoAPI 2.0
Build 2005-06-08

Symbols, terms and definitions
Copyright OpenGIS® Consortium