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.
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.
Patrick, from the aggregation documentation : http://www.unidata.ucar.edu/software/netcdf/ncml/v2.2/Aggregation.html when the units of the aggregation coordinate change on the existing coordinate variables, you must add timeUnitsChange="true" on the aggregation element: Regards Antonio El 15/02/2012, a las 17:22, "Patrick Brockmann" <P.Brockmann@xxxxxxx> escribió: > Hi, > > I have discovered that when an aggregation has been made over time > with files that contains different time references then the result time axis > is not correct (not monotically increasing). > > Precisely, I have files with > time:units = "days since 1850-01-01 00:00:00" ; > others with > time:units = "days since 1870-01-01 00:00:00" ; > or > time:units = "days since 1880-01-01 00:00:00" ; > or > time:units = "days since 1970-01-01 00:00:00" ; > > When I access to this aggregation (16 files aggregated) > with ferret, the time axis is detected as not correct > and the following warning is displayed > > *** NOTE: Coordinates out of order or missing on axis time at subscript 241 > *** NOTE: A dummy axis of subscripts will be used > > Is there a way to take into account that time references may vary > from the different files aggregated ? > > Thanks > Patrick > > -- > LSCE/IPSL, Laboratoire CEA-CNRS-UVSQ > Data Analysis and Visualization Engineer > ICMC - IPSL Climate Modelling Centre > -- > > > _______________________________________________ > thredds mailing list > thredds@xxxxxxxxxxxxxxxx > For list information or to unsubscribe, visit: > http://www.unidata.ucar.edu/mailing_lists/
thredds archives: