ERDDAP
Easier access to scientific data |
Brought to you by SO-CHIC |
Dataset Title: | SOCHIC-SOSCEx_STORM2_Glider_Data/DIC_Broullon_WG |
Institution: | University of Gothenburg (Dataset ID: SOCHIC_SOSCEx_STORM2_Glider_Data_DIC_Broullon_WG) |
Information: | Summary | License | FGDC | ISO 19115 | Metadata | Background | Subset | Files | Make a graph |
Attributes { s { latitude { String _CoordinateAxisType "Lat"; Float64 _FillValue NaN; Float64 actual_range -60.0, -42.0; String axis "Y"; Float64 colorBarMaximum 90.0; Float64 colorBarMinimum -90.0; String ioos_category "Location"; String long_name "Latitude"; String standard_name "latitude"; String units "degrees_north"; } depth_level { Float64 _FillValue 99; Float64 actual_range 0, 98; Float64 colorBarMaximum 8000.0; Float64 colorBarMinimum -8000.0; String colorBarPalette "TopographyDepth"; String long_name "Depth"; String standard_name "depth"; } TCO2_NNGv2LDEO { Float64 _FillValue NaN; Float64 actual_range 2074.5265325742025, 2267.987018240153; String long_name "TCO2 NNGv2 LDEO"; Float64 missing_value NaN; String regrid_method "bilinear"; } longitude { String _CoordinateAxisType "Lon"; Float64 _FillValue NaN; Float64 actual_range 360.0, 360.0; String axis "X"; Float64 colorBarMaximum 180.0; Float64 colorBarMinimum -180.0; String ioos_category "Location"; String long_name "Longitude"; String standard_name "longitude"; String units "degrees_east"; } } NC_GLOBAL { String _NCProperties "version=1|netcdflibversion=4.6.1|hdf5libversion=1.10.2"; String cdm_data_type "Other"; String Conventions "COARDS, CF-1.6, ACDD-1.3"; Float64 Easternmost_Easting 360.0; String EDMO_code "3984"; Float64 geospatial_lat_max -42.0; Float64 geospatial_lat_min -60.0; String geospatial_lat_units "degrees_north"; Float64 geospatial_lon_max 360.0; Float64 geospatial_lon_min 360.0; String geospatial_lon_units "degrees_east"; String history "2024-11-21T10:53:01Z (local files) 2024-11-21T10:53:01Z https://erddap.sochic-h2020.eu/erddap/tabledap/SOCHIC_SOSCEx_STORM2_Glider_Data_DIC_Broullon_WG.html"; String infoUrl "https://doi.org/10.1029/2021JC017760"; String institution "University of Gothenburg"; String keywords "data, depth, depth_level, latitude, ldeo, local, longitude, nngv2, source, tco2, TCO2_NNGv2LDEO"; String license "CC BY-NC 4.0 https://creativecommons.org/licenses/by-nc/4.0/"; Float64 Northernmost_Northing -42.0; String sourceUrl "(local files)"; Float64 Southernmost_Northing -60.0; String standard_name_vocabulary "CF Standard Name Table v55"; String subsetVariables "longitude"; String summary "SOCHIC-SOSCEx_STORM2_Glider_Data/DIC_Broullon_WG"; String title "SOCHIC-SOSCEx_STORM2_Glider_Data/DIC_Broullon_WG"; Float64 Westernmost_Easting 360.0; } }
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.