ERDDAP
Easier access to scientific data
?
log in

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  Argo Reference Measurements Subscribe RSS
Institution:  Argo   (Dataset ID: ArgoFloats-ref)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
   or a List of Values ?
   Maximum ?
 
 pres ?          -0.20000000298023224    2650.0
 temp ?          -1.8880000114440918    33.38999938964844
 ptmp ?          -1.8880352559081022    33.38918683999088
 psal (PSU) ?          0.0    39.54999923706055
 pi_name ?      
   - +  ?
 platform_number ?      
   - +  ?
 cycle_number ?          "000"    "665"
 latitude (degrees_north) ?          -75.201    78.198
  < slider >
 longitude (degrees_east) ?          -179.99900000000002    179.99900000000002
  < slider >
 time (UTC) ?          2000-06-09T00:08:14Z    2018-09-24T11:52:30Z
  < slider >
 
Server-side Functions ?
 distinct() ?
? ("Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.")

File type: (more information)

(Documentation / Bypass this form ? )
 
(Please be patient. It may take a while to get the data.)


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  pres {
    Float64 _FillValue NaN;
    Float64 actual_range -0.20000000298023224, 2650.0;
    Float64 colorBarMaximum 5000.0;
    Float64 colorBarMinimum 0.0;
    Float64 missing_value 99999.0;
  }
  temp {
    Float64 _FillValue NaN;
    Float64 actual_range -1.8880000114440918, 33.38999938964844;
    Float64 colorBarMaximum 32.0;
    Float64 colorBarMinimum 0.0;
    Float64 missing_value 99999.0;
  }
  ptmp {
    Float64 _FillValue NaN;
    Float64 actual_range -1.8880352559081022, 33.38918683999088;
    String long_name "PTMP";
    Float64 missing_value NaN;
  }
  psal {
    Float64 _FillValue NaN;
    Float64 actual_range 0.0, 39.54999923706055;
    Float64 colorBarMaximum 37.0;
    Float64 colorBarMinimum 32.0;
    Float64 missing_value 99999.0;
    String standard_name "sea_water_practical_salinity";
    String units "PSU";
  }
  pi_name {
  }
  platform_number {
  }
  cycle_number {
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range -75.201, 78.198;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    Float64 missing_value 99999.0;
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -179.99900000000002, 179.99900000000002;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    Float64 missing_value 99999.0;
    String standard_name "longitude";
    String units "degrees_east";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 9.60509294e+8, 1.53778995e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Time";
    String source_name "JULD";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
 }
  NC_GLOBAL {
    String _NCProperties "version=1|netcdflibversion=4.6.1|hdf5libversion=1.10.3";
    String cdm_data_type "Point";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting 179.99900000000002;
    String featureType "Point";
    Float64 geospatial_lat_max 78.198;
    Float64 geospatial_lat_min -75.201;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 179.99900000000002;
    Float64 geospatial_lon_min -179.99900000000002;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-03-28T08:52:12Z (local files)
2024-03-28T08:52:12Z https://erddap.ifremer.fr/erddap/tabledap/ArgoFloats-ref.html";
    String infoUrl "http://www.argodatamgt.org/DMQC/Reference-data-base";
    String institution "Argo";
    String keywords "cycle, cycle_number, data, density, earth, Earth Science > Oceans > Ocean Pressure > Water Pressure, Earth Science > Oceans > Ocean Temperature > Water Temperature, Earth Science > Oceans > Salinity/Density > Salinity, equals, float, identifier, in-situ, its, its-90, latitude, level, local, longitude, number, ocean, oceans, pi_name, platform_number, practical, PRES, pressure, PSAL, ptmp, salinity, scale, science, sea, sea-level, sea_water_practical_salinity, sea_water_pressure, sea_water_temperature, seawater, situ, source, TEMP, temperature, time, unique, water";
    String keywords_vocabulary "GCMD Science Keywords";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    Float64 Northernmost_Northing 78.198;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -75.201;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "pi_name, platform_number";
    String summary "Argo float vertical profiles from Coriolis Global Data Assembly Centres (GDAC). Argo is an international collaboration that collects high-quality temperature and salinity profiles from the upper 2000m of the ice-free global ocean and currents from intermediate depths. The data come from battery-powered autonomous floats that spend most of their life drifting at depth where they are stabilised by being neutrally buoyant at the \"parking depth\" pressure by having a density equal to the ambient pressure and a compressibility that is less than that of sea water. At present there are several models of profiling float used in Argo. All work in a similar fashion but differ somewhat in their design characteristics. At typically 10-day intervals, the floats pump fluid into an external bladder and rise to the surface over about 6 hours while measuring temperature and salinity. Satellites or GPS determine the position of the floats when they surface, and the floats transmit their data to the satellites. The bladder then deflates and the float returns to its original density and sinks to drift until the cycle is repeated. Floats are designed to make about 150 such cycles. Data Management URL: http://www.argodatamgt.org/Documentation";
    String time_coverage_end "2018-09-24T11:52:30Z";
    String time_coverage_start "2000-06-09T00:08:14Z";
    String title "Argo Reference Measurements";
    String version "2019V3";
    Float64 Westernmost_Easting -179.99900000000002;
  }
}

 

Using tabledap to Request Data and Graphs from Tabular Datasets

tabledap lets you request a data subset, a graph, or a map from a tabular dataset (for example, buoy data), via a specially formed URL. tabledap uses the OPeNDAP (external link) Data Access Protocol (DAP) (external link) and its selection constraints (external link).

The URL specifies what you want: the dataset, a description of the graph or the subset of the data, and the file type for the response.

Tabledap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/pmelTaoDySst.htmlTable?longitude,latitude,time,station,wmo_platform_code,T_25&time>=2015-05-23T12:00:00Z&time<=2015-05-31T12:00:00Z
Thus, the query is often a comma-separated list of desired variable names, followed by a collection of constraints (e.g., variable<value), each preceded by '&' (which is interpreted as "AND").

For details, see the tabledap Documentation.


 
ERDDAP, Version 2.18
Disclaimers | Privacy Policy | Contact