I assume you've seen these docs:
Anyway, you dont need scan, you can just list all the datasets
(1)<dimension name="time" length="0"/> <variable name="time" type="int" shape="time"> <attribute name="units" value="months since 2000-6-16 6:00"/> <attribute name="_CoordinateAxisType" value="Time" /> </variable>
(2)<aggregation dimName="time" type="joinNew"> (3) <variableAgg name="T"/> (4) <netcdf location="file:test/data/ncml/nc/time0.nc" coordValue="0"/> <netcdf location="file:test/data/ncml/nc/time1.nc" coordValue="1"/> <netcdf location="file:test/data/ncml/nc/time2.nc" coordValue="2"/> </aggregation>
lemme know if that helps...
I'm setting up a TDS to replace our older Aggregation Server. I've reviewed the documentation you have, at least all the links that I could find/follow. My question is does the new aggregation configuration require the use of 'scan', or can I setup the configuration file similarly to the old way? If so, would you have any examples I could look at for type 'join-new', that is where I'm creating a new dimension. The typical new 'time' dimension, hopefully expressible using the old 'coord=' attribute.
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.