Keiser, Ken wrote:
The dataType enumerations have been completely neglected, and practically undefined. I have never quite understood the difference between HDF-EOS "grid" vs "swath" : is the grid type regularly spaced, and the swath not? I am not even sure of the practical distinction bewteen "Image" and "Grid". So the first step is to start defining what these data types are. Any help from this group would be appreciated. My inclination would be not to try to do much in this 1.0 version, but to try to do something significant for the 1.1 version.John,
Some nice new features in this spec, especially in the services area. A couple of observations based on our use.
(1) There is still not a "swath" dataType - as opposed to "grid" or "image". Maybe we're the only ones using swath so its not a community issue, but thought I would mention it.
(2) Obviously we are always looking at ways to facilitate the use of ESML definitions. I looked through the spec trying to figure out where it might fit best. I guess one place might be as a serviceType for the service element if there could then be an associated URL for the description file. Another thought was in the metadata element, or maybe a combination of the two - in other words a serviceType of ESML which could then trigger an application to look at an associated metadata element for the necessary links. It might be appropriate as a type in dataFormat where there is a list of known formats and the use of ESML there could essentially make that list extensible to less known formats that could be defined by an ESML description.
Those are suggestions, but I'm sure you guys can better see where it would fit best based on your conceptual view of the catalog if there is any interest.
Thats a really interesting question and all the above seem possible.
So sounds like adding ESML as a dataFormatType is useful in either case.
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.