Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
I noticed in this that the THREDDS WCS doesn't look at the "calendar" attribute and therefore doesn't calculate dates for 365-day calendars correctly. This is just to note that we have code in the WMS that interprets most (if not all) of the CF calendars correctly - I can provide details if necessary, but feel free to steal the code if you like! (I *think* that this code is in THREDDS-WMS; it's possible that it's still only in ncWMS, to be folded into TDS later.) Cheers, Jon ---------------------------------------------------------------------- Message: 1 Date: Wed, 6 Oct 2010 10:35:43 -0600 From: Ben Domenico <Ben@xxxxxxxxxxxxxxxx> To: THREDDS community <thredds@xxxxxxxxxxxxxxxx> Cc: Kevin Sampson <ksampson@xxxxxxxx> Subject: [thredds] Issues with THREDDS and WCS Message-ID: <AANLkTimq5wmsfvHq1NHPXPFpVzCjkJnskvG+FwAtarda@xxxxxxxxxxxxxx> Content-Type: text/plain; charset="iso-8859-1" Hi, Kevin Sampson of the NCAR GIS Program has summarized some issues we've encountered in a collaborative effort to make weather and climate data available via the THREDDS Data Server and the associated WCS (and WMS in some cases) interfaces. Kevin has posted a document describing those issues at: https://sites.google.com/site/geointeropdemos/home/issues-with-thredds-w cs and would welcome any suggestions or further discussion with others who have worked in this area. -- Ben -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.unidata.ucar.edu/mailing_lists/archives/thredds/attachme nts/20101006/7056c0da/attachment.html> End of thredds Digest, Vol 21, Issue 2 **************************************
thredds
archives: