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.
Hi Pauline: I think Andrew's the expert on this, sounds like WCS 1.1 does not yet support irregular x,y coordinates. WCS 1.1.0 (http://www.opengeospatial.org/standards/wcs) is final, but there are ongoing efforts to improve the next version (1.2 i suppose). The GALEON document was written before the spec was final, so it is not authoritative. Pauline Mak wrote:
Hi John & Andrew :) Thanks for the insight into WCS - I must confess I'm not very geographically-minded and find the standard document somewhat daunting! I'm still a little confused though... So is WCS 1.1 still in development? And that, once it's publish, it will include irregular grid? I've also found an interesting document here: http://www.unidata.ucar.edu/projects/THREDDS/GALEON/WCSnetCDFencoding.htm and it seems to imply that WCS can support irregular grid. I could have misunderstood what it meant about row 6... Some clarification would be much appreciated :) Cheers, -Pauline. On Tue, 2007-04-24 at 18:10 +0100, Woolf, A (Andrew) wrote:WCS 1.1 does not yet support other than regular grids, though note there is now a change proposal in (OGC document 06-160) to get irregular grids (ISO 19123 CV_ReferenceableGrid in ISO-speak) into GML which should help. In my view it is crucial that conceptual models for grids remain unified between GML, WCS, and ISO 19123.-----Original Message-----From: address@hidden [mailto:address@hidden] On Behalf Of John CaronSent: 24 April 2007 16:45 To: Pauline Mak Cc: address@hidden Subject: Re: Question about CDM Pauline Mak wrote:I've foundHi all,Thanks for the help - through the second validator, I thinkout what's wrong with the dataset. Some of the axisdoesn't have anyvalues under the regular column. I've written a littleJava app thatgoes through a directory and find all nc files and checksthat a) itopens up as a GriddedDataset and then 2) theGridCoordSystem from theGriddedDataset isRegularSpatial(). Is this what it meansby the WCSyes. I think WCS 1.1 relaxes the regular spacing need, which will implement later this year (probably).standard that it has to be gridded and regularly spaced?Thanks, -Pauline.On 4/21/07, *Ethan Davis* <address@hidden <mailto:address@hidden>> wrote:Hi Pauline,Another resource for validating datasets against the CDM is available athttp://motherlode.ucar.edu:8080/thredds/cdmValidate.html <http://motherlode.ucar.edu:8080/thredds/cdmValidate.html>And I believe it is distributed with all TDSinstallations, so you couldtry it locally athttp://yourserver:port/thredds/cdmValidate.htmlWhich datasets can be served by the TDS depends on theservice overwhich you want to make them available. The HTTP bulkfile downloadservice (/thredds/fileServer/) can serve any file. TheOPeNDAP service(/thredds/dodsC/) can serve any dataset that thenetCDF-java librarycanread (the file types that can be read are listed on thehome page,http://www.unidata.ucar.edu/software/netcdf-java/). TheWCS servicecurrently only handles gridded data. The key here isthat they have tobe recognized as gridded datasets by the netCDF-javalibrary. Thelibrary can recognize gridded data and the coordinatesin the data usinga few different conventions. As Tom and/or Roymentioned, CF is theconvention we recommend. The CDM validator above shouldgive you moreclues on how well you dataset validates. Hope that helps. Ethan Pauline Mak wrote: > Hi all, > > I'm currently setting up a THREDDS server to server our datasets. The> setup was fairly easy! However, I'm running intoproblems withNetCDF> files which doesn't conform to the "Common Data(Access) Model" - we> want to serve all of our data through WCS (whichcomes for free with> THREDDS data server!). I've searched high and lowfor documentation> on how to 'correct' incompatible files. but failedto come up with> anything. Am I missing something? Should all NetCDFfiles "justwork"> with the NetCDF-Java 2.2 library? I'm aware thatfiles should be> gridded and regular. Am I understanding correctlythat gridded means> the files should have an x and y axis with optionalz and t? Is> there a nice method to find out if a file iscompatible 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 <mailto:address@hidden> <mailto:address@hidden <mailto:address@hidden>> --Ethan R. DavisTelephone: (303) 497-8155Software Engineer Fax:(303) 497-8690UCAR Unidata Program Center E-mail: address@hidden <mailto:address@hidden>P.O. Box 3000Boulder, CO 80307-3000 http://www.unidata.ucar.edu/--------------------------------------------------------------------------- -- -- 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 <mailto:address@hidden>============================================================== ================= To unsubscribe thredds, visit: http://www.unidata.ucar.edu/mailing-list-delete-form.html ============================================================== ================================================================================================ To unsubscribe thredds, visit: http://www.unidata.ucar.edu/mailing-list-delete-form.html ===============================================================================
=============================================================================== To unsubscribe thredds, visit: http://www.unidata.ucar.edu/mailing-list-delete-form.html ===============================================================================