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 -The reason that happens is that the creation of the aggregation elements is part of an automated process. Often times there will be more than one file in the joinExisting aggregation and so the automated procedures were written to assume that was the case....
kev John Caron wrote:
Hi Kevin: why so you use an aggregation element here, when theres only one dataset?<dataset ID="hfls_monthly_1to2x-0_R1_00010101-02801231" name="hfls" urlPath="hfls_monthly_1to2x-0_R1_00010101-02801231"><serviceName>thisDODS</serviceName><netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"><aggregation dimName="time" type="joinExisting"><netcdf location="file:/data/gfdl_cm2_0/CM2Q-d2_1PctTo2x_i1/pp/atmos/ts/monthly/hfls_A1.000101-028012.nc" ncoords="3360" /></aggregation> </netcdf> </dataset>
-- Kevin O'Brien UW/JISAO Research Scientist NOAA/PMEL/TMAP 206-526-6751 http://tmap.pmel.noaa.gov"The contents of this message are mine personally and do not necessarily reflect any position of the Government or the National Oceanic and Atmospheric Administration."