ERDDAP > Out-Of-Date Datasets
The outOfDate index is a simplistic measure of how out-of-date a dataset is: <0: unexpectedly from the future(!), <1: up-to-date, >=1: out-of-date, >=2: very out-of-date. For out-of-date datasets, there is presumably a problem with the data source, so ERDDAP is unable to access data from more recent time points.
1 matching datasets. This web page was generated at 2024-11-24T00:13:48Z .
outOfDate
| testOutOfDate
| maxTime
| datasetID
| title
|
███ 86.46851
| now-18days
| 2020-08-20T13:51:15Z
| oleanderTsg
| Oleander TSG data
|
This web page was generated at 2024-11-24T00:13:48Z .
This web page will refresh itself automatically every 15 minutes.
Options
You can add tabledap-like constraints to requests to this web page,
for example,
http://erddap.oleander.bios.edu:8080/erddap/outOfDateDatasets.html?&outOfDate>=0.5 .
Usually, the parameter values in the URL (the parts after '=' signs) must be properly
percent encoded:
all characters other than A-Za-z0-9_-!.~'()* must be encoded as %HH,
where HH is the 2 digit hexadecimal value of the character, for example, a space becomes
%20. Characters above #127 must be converted to UTF-8 bytes, then each UTF-8 byte must
be percent encoded (ask a programmer for help). There are
web sites that percent encode and decode for you.
The information in the table above is also available in other file formats
(.csv, .htmlTable, .itx, .json, .jsonlCSV, .jsonlKVP, .mat, .nc, .nccsv, .tsv, .xhtml) via a RESTful web service.