This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
G'day Pauline.... You might strong consider using the "CF Conventions" for your NetCDF files. These were set up for model data and are widely accepted and understood. You may find out details here: <http://www.cgd.ucar.edu/cms/eaton/cf-metadata/CF-current.html> and <http://www.cgd.ucar.edu/cms/eaton/cf-metadata/conformance-req.html> There is an on-line compliance checker at: <http://titania.badc.rl.ac.uk/cgi-bin/cf-checker.pl> Further, if you cannot change the files,you might be able to use the NCML to effectively 'rework' the structure into CF compliance -- I do this occasionally when I get a netCDF file that is not compliant or imcompatible with the application I'm using. The "toolsUI" suite is good at showing the structure and has facilities for creating and editing NCML if you need to. There is a download for this off the Unidata NetCDF-Java page: <http://www.unidata.ucar.edu/software/netcdf-java/> Hope that helps....I'm sure others will chime in as well... Best wishes, tom On 4/19/07, Pauline Mak <address@hidden> wrote:
Hi all, I'm currently setting up a THREDDS server to server our datasets. The setup was fairly easy! However, I'm running into problems with NetCDF files which doesn't conform to the "Common Data (Access) Model" - we want to serve all of our data through WCS (which comes for free with THREDDS data server!). I've searched high and low for documentation on how to 'correct' incompatible files. but failed to come up with anything. Am I missing something? Should all NetCDF files "just work" with the NetCDF-Java 2.2 library? I'm aware that files should be gridded and regular. Am I understanding correctly that gridded means the files should have an x and y axis with optional z and t? Is there a nice method to find out if a file is compatible and if it's not compatible, why it is so? My understanding of NetCDF file is rather shallow... so please bear with me if I'm asking a simple question... Thanks & cheers, -Pauline. -- Pauline Mak Software Developer, Insight4 Suite 2 / Level 1, 114 Murray St. Hobart, Australia 7000 p: (03) 6234 5203 f: (03) 6234 5603 address@hidden
-- Tom Whittaker University of Wisconsin-Madison Space Science & Engineering Center (SSEC) Cooperative Institute for Meteorological Satellite Studies (CIMSS) 1225 W. Dayton Street Madison, WI 53706 USA ph: +1 608 262 2759 =============================================================================== To unsubscribe thredds, visit: http://www.unidata.ucar.edu/mailing-list-delete-form.html ===============================================================================