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.

4 matching datasets. This web page was generated at 2025-01-23T18:49:56Z .

outOfDate	testOutOfDate	maxTime	datasetID	title
███ 50.11831	now-1day	2024-12-04T16:00:00Z	totals_yucatan_oi_qc_nrt_flagged	Yucatan 6km Sea Surface Currents
███ 7.1597223	now-7days	2024-12-04T16:00:00Z	radials_iscy_ideal	UGOS-3 - HFR: Isla Contoy, Mexico (ISCY), Ideal, Long Range Radial Currents - Real-time
███ 6.1864185	now-122days	2022-12-31T01:00:00Z	gom_ssh_2022	Gulf of Mexico SSH Anomaly Grid - 2022
███ 0.24301636	now-1day	2025-01-23T13:00:00Z	radials_uasa_ideal	UGOS-3 - HFR: Puerto Morelos, Mexico (UASA), Ideal, Long Range Radial Currents - Real-time

This web page was generated at 2025-01-23T18:49:56Z .
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://gcoos5.geos.tamu.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.