You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recommended dataset naming is to end it with "DATASET/filelist", e.g., "MyDataset/filelist" (not "filelist/MyDataset"), and also add "x_parameterSchema="filelist" in the info response.
We start with a base class which is just a "Listing of Times":
time isotime
"Availability" required elements:
startDate - start date/time of coverage (isotime, required)
stopDate - (isotime) stop date/time of coverage; exclusive (like HAPI request end times)
Optional and recommended elements:
numberValidRecords (int) count of the records in the interval where there is at least one non-FILL value in the record; this is easy an unambiguous to compute on the server side; the interpretation by clients is harder, esp. for non-uniform cadence (clients want to know - is this interval good or not)
For future discussion
numberOfRecords (int) - the number of records (valid data or FILL values) that are present within the startDate and stopDate
estimatedFractionOfIntervalFilledWithValidRecords - easy to use for clients, but hard to know how to uniformly implement on servers