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.
Rob Weingruber wrote:
Hi ;-) Dont forget that we oughtta get together ;-)) Here's the quick question...What is returned from the Thredds Data Server (eg: when I geoGrid.subset(...))? If I were to NOT use a Netcdf API, how would I parse/interpret the data that is streamed back from any Thredds request? Is there a document/specificationthat describes the data stream? Ditto for the inbound request protocol. The reason I ask is because we need to document our inbound protocols andoutbound data formats, so that 3rd party clients can request/read our data using their own code. And I am thinking that using Thredds out of the box is the best architectural solution (rather than growing our own in/out protocol ordittoing existing ones). ;-) You da man....
Hi Rob, im outta town for the week, not sure when we can meet for now...geoGrid.subset(...) returns a GridDatatype object, useable only within Java. whats on the network wire depends on the data access protocol, eg. opendap or WCS.
netcdf-java archives: