On Mar 1, 2012, at 8:49 AM, John Caron wrote: > Hi all: > > If the checker can read from opendap, then putting the files on an opendap > server might be helpful, in > that only the metadata is read instead of the entire file. > > There are a few difference among servers (Hyrax, TDS, GDS, etc) but im pretty > sure this would work for > netcdf files well enough for the checker's needs. could be worth finding out.
Good idea! We have a server running on test.opendap.org that we would be willing to let others use. James > > john > > On 2/29/2012 7:55 AM, Bentley, Philip wrote: >> Hi Stephen, >> >> I may well be wrong, but I suspect that one of the reasons - perhaps the >> main reason - why folks would like access to a stand-alone cfchecker >> utility is the large size of their netcdf files. (It's certainly the >> reason we use a local version.) >> >> As you know only too well (from CMIP5), most of the netcdf files we're >> dealing with these days run into the high 100s of MB or low GBs. It's >> not really practical to upload such files in order to perform a CF >> compliance check. At least not on more than a few files. >> >> I wonder, therefore, if a possible solution is to develop an alternative >> checker utility that operates not on the netcdf file itself, but rather >> on the header info output by the ncdump -h command. Generating and >> uploading those would be trivial by comparison. >> >> Off the top of my head (and having given it almost zero thought!) the >> only test that I can think of which examines the actual data values is >> the check for coord vars being monotonic. But I suspect there are others >> I'm unaware of. >> >> If nothing else, such a utility might have some value as a 'first pass' >> checker. >> >> Any mileage in this? Apologies if it's already done the rounds! >> >> Regards, >> Phil >> >> >>> -----Original Message----- >>> From: cf-metadata-boun...@cgd.ucar.edu >>> [mailto:cf-metadata-boun...@cgd.ucar.edu] On Behalf Of >>> stephen.pas...@stfc.ac.uk >>> Sent: 29 February 2012 11:39 >>> To: christopher.s.lyn...@nasa.gov; cf-metadata@cgd.ucar.edu >>> Subject: Re: [CF-metadata] machine-accessible CF compliance checker? >>> >>> Hi Christopher, >>> >>> Are you looking for a way to run the cfchecker locally or >>> submit checking requests to one of the websites in a script? >>> >>> I think both would be possible with a little help. The >>> cfchecker is now available on the Python Package Index at >>> http://pypi.python.org/pypi/cfchecker. It needs a little >>> help to work out of the box -- you need to configure UDUNITS >>> and the location of several CF XML files. It's on my >>> long-term TODO list to make this configuration easier. >>> >>> Also the CF-checker at BADC and NCAS-CMS has a very simple >>> HTTP interface that could be scripted. >>> >>> Cheers, >>> Stephen. >>> >>> --- >>> Stephen Pascoe +44 (0)1235 445980 >>> Centre of Environmental Data Archival >>> STFC Rutherford Appleton Laboratory, Harwell Oxford, Didcot >>> OX11 0QX, UK >>> >>> >>> -----Original Message----- >>> From: cf-metadata-boun...@cgd.ucar.edu >>> [mailto:cf-metadata-boun...@cgd.ucar.edu] On Behalf Of >>> Lynnes, Christopher S. (GSFC-6102) >>> Sent: 28 February 2012 16:03 >>> To: cf-metadata@cgd.ucar.edu >>> Subject: [CF-metadata] machine-accessible CF compliance checker? >>> >>> I know about the web sites where you use a form to upload >>> files to check CF compliance, but is there a service >>> somewhere that can be accessed by a script? >>> -- >>> Dr. Christopher Lynnes NASA/GSFC, Code 610.2 phone: >>> 301-614-5185 >>> >>> >>> _______________________________________________ >>> CF-metadata mailing list >>> CF-metadata@cgd.ucar.edu >>> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata >>> -- >>> Scanned by iCritical. >>> _______________________________________________ >>> CF-metadata mailing list >>> CF-metadata@cgd.ucar.edu >>> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata >>> >> _______________________________________________ >> CF-metadata mailing list >> CF-metadata@cgd.ucar.edu >> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata > > _______________________________________________ > CF-metadata mailing list > CF-metadata@cgd.ucar.edu > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata -- James Gallagher jgallagher at opendap.org 406.723.8663
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ CF-metadata mailing list CF-metadata@cgd.ucar.edu http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata