Hi Hoop,
Try adding the following to your featureCollection element
<metadata inherited="true">
<serviceName>all</serviceName>
</metadata>
Also, since your most recent dataset is the one that is changing, you
might want to change protoDataset@choice from "Latest" to "Penultimate"
(which is the default, so you could just drop protoDataset all
together). Also, since data files in your dataset don't age off, it
probably isn't too important which dataset is used but probably better
to not use the one that gets updated. The protoDataset is used to
populate the metadata in the feature dataset.
Since your datasets are a simple timeseries rather than a full-blown
FMRC, you will probably want to add
<fmrcConfig datasetTypes="Best"/>
The fmrcConfig@datasetTypes value tells the featureCollection which
types of FMRC datasets to create. With the value "Best", the forecast
types are left off and only the "Best Time Series" dataset is created.
Not the best dataset name for a simple time series grid (its not just
the best time series, its the only one!) but that's what we have for the
moment. If you want to let people see the underlying files, you could
add "Files" to the fmrcConfig@datasetTypes value.
I'm including the link to the FeatureCollection tutorial [1] which I
forgot to point out in an earlier email when I gave you the link to the
reference docs [2].
Hope that helps,
Ethan
[1]
http://www.unidata.ucar.edu/projects/THREDDS/tech/tds4.2/tutorial/FeatureCollectionsTutorial.html
[2]
http://www.unidata.ucar.edu/projects/THREDDS/tech/tds4.2/reference/collections/FeatureCollections.html
On 3/26/2012 11:13 AM, Hoop wrote:
> Ethan,
>
> The catalog is attached. The filter element is in a datasetScan
> element that we use to generically wrap our NetCDF files, and
> not included within the featureCollection element or any other
> aggregation element. It is meant to generally apply throughout our
> installation.
>
> Sample files may be obtained from:
>
> ftp://ftp.cdc.noaa.gov/Datasets/noaa.oisst.v2.highres/
> The files for this year are updated on a daily basis, barring
> problems.
>
> Let me know what else I can do to help.
>
> -Hoop
>
>> Date: Sat, 24 Mar 2012 23:02:53 -0600
>> From: Ethan Davis <edavis@xxxxxxxxxxxxxxxx>
>> To: thredds@xxxxxxxxxxxxxxxx
>> Subject: Re: [thredds] Pb between OpenDap and THREDDS when netcdf file
>> are modifed
>> Message-ID: <4F6EA6FD.8080906@xxxxxxxxxxxxxxxx>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> Hi Hoop,
>>
>> Can you send us (or point us to) a few sample files and send us your
>> full catalog?
>>
>> Is the filter you mention below part of your featureCollection element?
>>
>> Ethan
>>
>> On 3/9/2012 1:59 PM, Hoop wrote:
>>> Ethan,
>>>
>>> I don't believe John ever responded as you had requested.
>>> I did my best to try "featureCollection", but I got nowhere.
>>> It doesn't help that the XSDs specify required elements
>>> (for "update" and "filter") that are not mentioned in the
>>> online documentation; the validation process that TDS runs
>>> at start-up informed me of those errors. I have no clue how
>>> to correct them. Here is the attempt I made:
>>>
>>> <featureCollection name="SST_NOAA_OISST_V2_HighResFC" featureType="FMRC"
>>> harvest="true" path="Datasets/aggro/OISSThires.nc">
>>> <collection
>>> spec="/Datasets/noaa.oisst.v2.highres/sst.day.mean.#yyyy#.v2.nc$"
>>> name="SST_OISST_V2_HighResFC" olderThan="15 min" />
>>> <protoDataset choice="Latest" change="0 0 7 * * ? *" />
>>> <update startup="true" rescan="0 0 * * * ? *" />
>>> </featureCollection>
>>>
>>> My use of "filter" is as follows:
>>>
>>> <filter>
>>> <include wildcard="*.nc"/>
>>> <exclude wildcard="*.data"/>
>>> <exclude wildcard="*.f"/>
>>> <exclude wildcard="*.gbx"/>
>>> <exclude wildcard="*.txt"/>
>>> <exclude wildcard="README"/>
>>> </filter>
>>>
>>> Someone want to tell me what I did wrong in each case?
>>>
>>> Thanks,
>>> -Hoop
