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.
Greetings Ghansham, Essentially, yes: https://www.unidata.ucar.edu/software/thredds/current/tds/reference/collections/FmrcCollection.html Cheers! Sean > Will the ncml aggregation given be used for serving in tds as well? > > address@hidden> wrote: > > > It looks like the best option would be to use an FMRC, using NcML: > > > > https://www.unidata.ucar.edu/software/thredds/current/netcdf-java/ncml/ > > FmrcAggregation.html > > > > This will aggregate the variables such they they have two times - the > > model run time and the valid forecast time. > > > > Cheers, > > > > Sean > > > > > I hv a grads ctl and dat file. > > > > > > address@hidden> wrote: > > > > > > > GrADS ctl file? If so, what is the underlying format they reference? > > > > > > > > > Its ctl file > > > > > > > > > > address@hidden> wrote: > > > > > > > > > > > Greetings Ghansham, > > > > > > > > > > > > What is the data format of your files? > > > > > > > > > > > > Cheers, > > > > > > > > > > > > Sean > > > > > > > > > > > > > Dear sir > > > > > > > > > > > > > > I hv some daily forecast files which have forecast of next 72 > > hours > > > > at 3 > > > > > > > hours interval. How to go about aggregating they may have same > > time > > > > > > values > > > > > > > like we the forecast for 30 hour from day1 may match the 6 hour > > from > > > > day > > > > > > 2. > > > > > > > I hope you understand what I mean. What could be possible > > solution > > > > while > > > > > > > aggregating it using ncml? > > > > > > > > > > > > > > Regards > > > > > > > Ghansham > > > > > > > > > > > > > > > > > > > > > > > > > > Ticket Details > > > > > > =================== > > > > > > Ticket ID: TAB-488483 > > > > > > Department: Support netCDF Java > > > > > > Priority: Normal > > > > > > Status: Open > > > > > > =================== > > > > > > 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. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Ticket Details > > > > =================== > > > > Ticket ID: TAB-488483 > > > > Department: Support netCDF Java > > > > Priority: Normal > > > > Status: Open > > > > =================== > > > > 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. > > > > > > > > > > > > > > > > > > > > > > Ticket Details > > =================== > > Ticket ID: TAB-488483 > > Department: Support netCDF Java > > Priority: Normal > > Status: Open > > =================== > > 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. > > > > > > > > Ticket Details =================== Ticket ID: TAB-488483 Department: Support netCDF Java Priority: Normal Status: Open =================== 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.