In "Image I/O metadata for multidimensional coverage" document

> 5. ImageIO MetaData for Multidimensional Coverages overview
> -----------------------------------------------------------
> In order to be able to describe a Multidimensional Coverage (or
> ND-Coverage), we need to introduce the concept of coverage metadata,
> which sits right in between the stream metadata concept and the image
> metadata concept.

I was expecting a 1-to-1 relationship between an Image and a Coverage
(or at least a GridCoverage2D). The need for a Coverage intermediate
level suggests that there is no such 1-to-1 relationship. What is the
relationship then? Do we expect Coverage metadata to be returned by
"smart" readers only, and not the "flat" ones? Do we expect a one-to-one
or one-to-many relationship between "Coverage metadata" and "Image
metadata"?


"overview" in Figure 8
----------------------
"Overviews" seems to be used there in a sense similar to "Thumbnails" in
J2SE ImageReader. Is "Overviews" the term used in OGC specification? If
not, should we consider using the same term than J2SE ImageReader?


"bandKeys" in Figure 8
----------------------
See my comment for stream metadata. I believe that "bandKeys" and
"nullValues" should not be part of CRS axis, but rather part of
SampleDimensions. Or maybe the whole "axis" node is about
SampleDimensions, in which case I would suggest to rename it?



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to