NOTE: The galeon mailing list is no longer active. The list archives are made available for historical reasons.
Hi, I think the idea that all CRS's can be well know is a stretch. One only need to change the origin or make a rotation to create a new CRS. I think this problem is solved by having the service advertise the CRS that it supports and use URN's to identify the CRS. A registry like (http://www.epsg-registry.org) can then be used to resolve the URNreference and get the CRS definition.
Ron From: galeon-bounces@xxxxxxxxxxxxxxxx [mailto:galeon-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Peter Baumann Sent: October 7, 2008 2:31 PM To: braeckel@xxxxxxxx Cc: Unidata GALEON Subject: 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
galeon archives: