NOTE: The galeon mailing list is no longer active. The list archives are made available for historical reasons.
Hi Ben, I agree with this - definitely the community should agree on CF conventions for all the new and awkward data types. Sorry if I implied otherwise - I just meant to express worries about the difficulty of then moving all this into the OGC/ISO world. But it's valuable to the CF process to know how the OGC/ISO world deals with stuff, particularly nasty things like vertical CRSs. So I completely agree that the cross-talk between the communities is vital.
"Simple Ain't Easy."
Too right! Jon On Thu, Oct 9, 2008 at 4:38 PM, Ben Domenico <Ben@xxxxxxxxxxxxxxxx> wrote:
Jon, I completely agree that the remaining steps are many and they will not be easy. And Roy is correct that getting as far as we have was more difficult than it looks in hindsight. But it's important to keep in mind that all the hard work is not thrown away if we don't accomplish the ultimate goals completely and quickly. For instance, I think it will be extremely valuable for our community to agree on CF conventions for some of the non-gridded data types we have identified. This will facilitate the exchange of other types of data within our own community with added semantics that we agree on. This can provide a building block for future OGC/ISO extension standards, but it will be valuable and useful in a very practical way strictly on its own merit. Another important class of benefits I refer to as "collateral successes." These are valuable outcomes that were not among the initial explicit goals. A great example of this is going on in another GALEON discussion thread on parametrized projections and EPSG codes. This will help us be more explicit about the coordinate reference systems we use. On the other side of the coin, it is clear that many members of the traditional GIS community are developing a much better understanding of 3D time varying data. And some have implemented code for reading and writing CF-netCDF directly. These are very valuable steps forward even though they don't completely solve the interoperability problem in themselves and there is still a huge amount of challenging work to be done. I'll close with the quote from Thelonius Monk that I have at the top of the whiteboard in my office: "Simple Ain't Easy." -- Ben
galeon archives: