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.
I just fixed a bug like that in FmrcSingle, but i havent seen it for joinExisting. Are you sure its happening for joinExisting? > Hello again! > > Thanks for your help with the IOSP issue - the more I dig into Unidata's > NetCDF Java API, the more I like it. > > I am using an NCML file to aggregate NetCDF files into a single > GridDataset, and I see the following odd behavior: a call to > aggregatedGridDataset.getGrids() sometimes returns all the grids in the > aggregate, and sometimes returns only some of these grids - apprarently, > the grids in only one of the aggregate members. This occurs when I use > the <netcdf> element and when I use the <scan> element: > > <aggregation dimName="time" type="joinExisting"> > <netcdf location="/path/to/member_1.nc"/> > <netcdf location="/path/to/member_2.nc"/> > <netcdf location="/path/to/member_3.nc"/> > <netcdf location="/path/to/member_4.nc"/> > </aggregation> > > <aggregation dimName="time" type="joinExisting"> > <scan location="/path/to/members/directory" suffix=".nc"/> > </aggregation> > > Any ideas why I am getting inconsistent results? > > Thanks, > Tom > > Ticket Details =================== Ticket ID: VSP-832015 Department: Support netCDF Java Priority: Critical Status: Open