NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Mark, OK. I got something that should work for you. Grab this jar file ftp://ftp.unidata.ucar.edu/pub/thredds/cataloggen/cataloggen-0.7a4.jar and try it with the "dir namer" after the "netCDF namer", both inside the datasetSource element. The order matters because the "dir namer" pattern will match all the datasets and "directory" datasets but the code goes through them in order and doesn't rename already named datasets. This is a bit of a hack. I really need to rethink how all of this is working but that's not going to happen yet. Let me know how that goes. Ethan Mark A Ohrenschall wrote: > > Hi Ethan, > > When I do that (and the "dir namer" datasetNamer is at the same level as the > "netCDF namer" datasetNamer) then the bottom-level dataset elements > (corresponding to the data files, i.e., the netCDF files) either get > named using the "dir namer" datasetNamer (if it comes before the "netCDF > namer") or they get named after the "netCDF namer" and the "dir namer" is > ignored (if it comes after the "netCDF namer"). Either way, the > middle-level dataset elements (corresponding to the directories) retain their > directory names. > > Thanks, > > Mark > > Ethan Davis wrote: > > > Try moving the "dir namer" datasetNamer element inside the datasetSource > > element. I think that will work. Let me know. If not, I have a few other > > ideas > > that I'm hoping aren't the case. -- Ethan R. Davis Telephone: (303) 497-8155 Software Engineer Fax: (303) 497-8690 UCAR Unidata Program Center E-mail: edavis@xxxxxxxx P.O. Box 3000 Boulder, CO 80307-3000 http://www.unidata.ucar.edu/
thredds archives: