Hi Massimiliano, There isn't currently a way to configure the TDS aggregation dataset access patterns. However, we would like to keep the data access limited to the datasets required to satisfy the query. So, we will look into this and see what we can do. Could you send us three days worth of the datasets behind your nested aggregation that we can use to debug this? Or you could add a dataset to your configuration that serves the individual files using an HTTPServer service element: <service name="fileServer" serviceType="HTTPServer" base="/thredds/fileServer/" /> and we can grab a few days worth of sample files. Thanks, Ethan Massimiliano Drudi wrote: > Dear Ethan > we are testing Thredds 4.2.20100825.2246 . > > Our link is > http://gnoodap.bo.ingv.it:8080/thredds/catalog.html > > The attached file is the xml used in our test. That xml is on internet > at this link: > http://gnoodap.bo.ingv.it:8080/thredds/MYOv01-MFS-AN.html > > I experienced what you wrote in the case of the joinExisting aggregation. > > But in the case of the nested aggregation joinExisting+union , in > order to handle each request, it opens (=unzip) all the files > corresponding to the day. Is it possible configure the system in order > to unzip the only one file corresponding to the day and containing the > requested variable? > > Regards, > Massimiliano Ticket Details =================== Ticket ID: FAQ-337688 Department: Support THREDDS Priority: Emergency Status: Closed
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.