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 John,These links are ncml for aggregations.Data files are inthe problem of aggregation with leap years isfor the same ncml file --- the older version of TDS ishttp://dataserver.nccs.nasa.gov/thredds/catalog/bypass/NEX-GDDP/bcsd/historical/r1i1p1/tasmin/catalog.html?dataset=bypass/NEX-GDDP/bcsd/historical/r1i1p1/tasmin/inmcm4.ncml (it has leap year date removed)On Thu, Jun 11, 2015 at 11:29 AM, John Caron <address@hidden> wrote:hi shen:cant get on to those computers - they want a name / passwordcan you send me a file that has the problem?On Thu, Jun 11, 2015 at 7:44 AM, Shen Yingshuo <address@hidden> wrote:Hi John,Recently there is a high publicity data release of NASA at White House Press ---Seethus we got a lot response from some very sophisticated users such as Don Murray -- who pointed out some error in date (causing by no leap year).365_day attribute works on THREDDS Version 4.3.16 on getting rid of 02-29 on leap year
http://dataserver.nccs.nasa.gov/thredds/wms/bypass/NEX-GDDP/bcsd/historical/r1i1p1/tasmin/inmcm4.ncml?service=WMS&version=1.3.0&request=GetCapabilitiesbut failswith new version (4.6.2)as you can see a lot 02-29 on leap yearsCan you help us out Or we have to go back early version ?Thanks