Hi Katherine, > I'd like to be able to have one catalog.xml file with multiple > datasetscans each with a different filter to create a hierarchical > look for a bunch of datasets that are all under one directory Yes, that can be done. Your attempt is failing due to a small problem with your datasetScan elements. The path attribute values must be unique. (This is true across a TDS. Meaning that each path attribute for all datasetScan and datasetRoot elements in all config catalogs for a TDS must be unique.) The reason is that the path value is how the TDS matches an incoming request URL to a particular datasetScan. I'm including my changes to your example below. Notice also that I'm changing the ID value as well (dataset IDs have to be unique in a catalog but it is convenient to have the ID match the path in datasetScans). > <datasetScan name="My Pressure Level Data" > ID="ecmwf19972001" > path="ecmwf19972001" ID="pLevel-ecmwf19972001" path="pLevel-ecmwf19972001" > location="/data/ecmwf19972001/" harvest="true"> > <filter> > <include wildcard="ggap*.nc" /> > </filter> > </datasetScan> > <datasetScan name="My Surface Data" > ID="ecmwf19972001" > path="ecmwf19972001" ID="surf-ecmwf19972001" path="surf-ecmwf19972001" > location="/data/ecmwf19972001/" harvest="true"> > <filter> > <include wildcard="ggas*.nc" /> > </filter> > </datasetScan> Hope that makes sense. Let me know if you have any other questions or run into other problems. Ethan Ticket Details =================== Ticket ID: CUU-719322 Department: Support THREDDS Priority: Normal 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.