NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.

To learn about what's going on, see About the Archive Site.

Re: [galeon] WCS CF-netCDF profile document

NOTE: The galeon mailing list is no longer active. The list archives are made available for historical reasons.

George,

Core requires a "DomainSubset" element.  While the DomainObject can be n-D.  Core 
requires the DomainSubset with BoundingBox parameter but does not require TemporalSubset.  For the 
BoundingBox, it requires 2D, which I believe refer to "two near horizontal Ds".

If an implementation implements 3D (or >2D), it should have the capability of 2D as 
well, unless the 3- or n-D (n>2) does not include the "two near horizontal Ds).

I guess that the requirement in core on "two near horizontally Ds", which are 
traditionally geographic/cartographic Ds (i.e., geographic or projected CRSs), may cause 
problem for some of the metaocean data such as the vertical profile data I mentioned in 
one of my previous email.  A profile may have only one horizontal D and one or more other 
Ds such as time and pressure.


Wenli

----- Original Message -----
From: George Percivall <gpercivall@xxxxxxxxxxxxxxxxxx>
Date: Monday, October 6, 2008 8:03 am
Subject: Re: [galeon] WCS CF-netCDF profile document


Wenli,

Core is not to be a conformance class on its own.
Clients would need to be compliant to core plus one or more extensions. Core would specify the equivalent of CV_DomainObject with no detail on the geometric objects.
These would be two conformance classes with corresponding compliance tests: - Core + 2D extension would say CV_DomainObject only contains 2D geometric objects. - Core + 3D extension would say CV_DomainObject contains 3D geometric objects. 

George
  • 2008 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the galeon archives: