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.

3 matching datasets. This web page was generated at 2025-11-07T13:36:18Z .

outOfDate	testOutOfDate	maxTime	datasetID	title
███ 7.0223083	now-3days	2025-10-17T12:00:00Z	nesdisL3Collatedn20C	Sea-Surface Temperature, NOAA ACSPO NOAA-20 VIIRS CoastWatch Co-gridded 4km Daily (degrees C)
███ 2.0334466	now-2days	2025-11-03T12:00:00Z	noaacwN20VIIRSchlaDaily	Chlorophyll, NOAA NOAA-20 VIIRS, Near Real-Time, Global 4km, Level 3, 2017-present, Daily
███ 1.0074319	now-9days	2025-10-29T12:00:00Z	noaacwNPPVIIRSchlaWeekly	Chlorophyll, NOAA S-NPP VIIRS, Near Real-Time, Global 4km, Level 3, 2017-present, Weekly

This web page was generated at 2025-11-07T13:36:18Z .
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,
https://coriolix.savannah.skio.uga.edu/erddap/outOfDateDatasets.html?&outOfDate>=0.5 . Usually, the parameter values in the URL (the parts after '=' signs) must be properly percent encoded (external link)

: 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 websites that percent encode and decode for you (external link)

The information in the table above is also available in other file formats (.csv, .htmlTable, .itx, .json, .jsonlCSV1, .jsonlCSV, .jsonlKVP, .mat, .nc, .nccsv, .tsv, .xhtml) via a RESTful web service.