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.
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.
NOTE: The galeon mailing list is no longer active. The list archives are made available for historical reasons.
Ron, looks like we "wildly agree" (nice term I learnt recently): in a GetCoverage response there is the coverage payload + metadata. I do like the idea of having a canonical + complete metadata set in XML (ok, GML) I also have advocated that, in case the server erroneously puts divergent metadata into format header and XML, the XML data prevail. Quite some folks alternatively want to have a "stripped" response without XML and MIME encapsulation (or whatever), though. That's where we have to live with incomplete metadata then - but IMHO this is a user's informed decision then. Va bene. Ron Lake wrote:
Peter:There is no conflict between TIFF and GML -- just some of the TIFF (if you used GeoTiff) would be redundantly encoded in GML. Very few GML coverages would use XML To carry the "pixel" values -- so there is no problem with Tiff, JPG, JP2, etc. Ron
galeon archives: