The dateFormatMark works on the name of the file, not including the
directories. You can use the ant-like "**" to indicate all directories
under a given directory. So, if you can rename your files to include the
date, you should be able to do something like
> ... />
I'm not sure how the dateFormatMark matches up with the regular
expression in ".*\.nc$". You may want to escape the "."s in your
dateFormatMark (or doing so may mess up the dateFormatMark handling).
I'll have to dig into that to be sure.
In case you haven't seen these docs, there's more detail at
Hope that helps,
On 4/19/2011 11:19 AM, Kyle Wilcox wrote:
> I've got a bunch of WRF forecasts in NetCDF format I want to collect into an
> Each run is split up into individual hour files (one time per file). All
> hour files for a run are organized by directory, with the directory name
> containing the information needed to parse out the RunTime for a FMRC.
> Sample directory structure:
> Here is how I am specifying the collection:
> name="WFlow_WRF_Large_Ensemble" recheckAfter="15 min" olderThan="5 min" />
> In catalogInit.log, I get a:
> **Error: DatasetFmrc =Weatherflow-WRF-Large/Agg-Collection.nc directory=
> </data/Weatherflow/ensemble/WRF_ensemble/#yyyy.MM.dd.HH#> does not exist
> ]$ ls -1t /data/Weatherflow/ensemble/WRF_ensemble
> Is it possible to specify the dateFormatMark on a directory name instead of a
> file? If not, I can rename files accordingly.
> Kyle Wilcox, Engineer
> Applied Science Associates
> 55 Village Square Drive
> South Kingstown, RI 02879
> p: (401) 789-6224
> e: kwilcox@xxxxxxxxxxxxxx
> thredds mailing list
> For list information or to unsubscribe, visit: