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 core + extensions

Aaron-

Aaron Braeckel wrote:

For example, my WCS client knows how to
read data in a Lambert Conformal Conic projections, but not in EPSG
2017.  My understanding is that CRS's are required to be "well-known",
not that they be in a limited set that all client and server
implementations understand.  I see this as a similar case, because just
as a client can decide whether or not it knows how to deal with a
particular CRS, it can also decide whether it is capable of dealing with
any particular dimensionality of data.  Both seem like discoverable
aspects of the native dataset.


hm, this is an interesting idea. I am hesitant to say "yes, this will
fly" but I would like to carry this discussion into our WCS group to
hear opinions there. Stay tuned, we have our telecon tomorrow!

-Peter