NOTE: The galeon mailing list is no longer active. The list archives are made available for historical reasons.
Hi All:I think Jon Blower may have mentioned this earlier, but there needs to be some differentiation in what is required of a server and a client. While servers may be able to vary (only 2-D or 3-D for example), there must be a larger minimum set that a client has to implement in order for there to be interoperability. In code my lab is developing, we are already running into this problem with WMS.
-Roy On Oct 6, 2008, at 8:37 AM, Wenli Yang wrote:
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
galeon archives: