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.
On 04/29/2011 11:42 AM, John Caron wrote:
On 4/29/2011 10:20 AM, Ethan Davis wrote:Hi Roland, The fileTypeId wasn't really designed with virtual datasets in mind or with any particular semantics in mind. They are similar to using software version numbers to indicate capabilities, you just have to know what they mean. Since virtual datasets may change the characteristics expected from a dataset with a given fileTypeId, perhaps we should extend fileTypeIds toallow for multi-layer names. Maybe something like "ncAggregation - GRIB2".for your case, maybe the best that can be done is "F-TDS" or similar ??
Yes, that seems like the simplest and most direct answer. Put ID: F-TDS Description: Ferret I/O Service Provider and Server-side AnalysisReference URL: http://ferret.pmel.noaa.gov/LAS/documentation/the-ferret-thredds-data-server-f-tds
in the official list and I'll start using these values. Roland
_______________________________________________ thredds mailing list thredds@xxxxxxxxxxxxxxxxFor list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
thredds
archives: