SO-CHIC ERDDAP
Easier access to scientific data
   
Brought to you by SO-CHIC    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  SOCHIC-SOSCEx_STORM2_Glider_Data/slocum_data Subscribe RSS
Institution:  University of Gothenburg   (Dataset ID: SOCHIC_SOSCEx_STORM2_Glider_Data_slocum_data)
Range: depth = -1.3962421 to 1019.7979m, time = 2018-12-19T00:00:01Z to 2019-03-08T23:48:01Z
Information:  Summary ? | License ? | Metadata | Background (external link) | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
       
       
       
 
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.")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Y Axis Minimum:   Maximum:   
 
(Please be patient. It may take a while to get the data.)
 
Optional:
Then set the File Type: (File Type information)
and
or view the URL:
(Documentation / Bypass this form ? )
   
Time range:    |<   -       
[The graph you specified. Please be patient.]

 

Things You Can Do With Your Graphs

Well, you can do anything you want with your graphs, of course. But some things you might not have considered are:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  index {
    Float64 actual_range 343210, 6962595;
    String long_name "Index";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.545177601e+9, 1.552088881e+9;
    String axis "T";
    String calendar "proleptic_gregorian";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 _FillValue NaN;
    Float64 actual_range -1.3962421362751642, 1019.7978918648507;
    String axis "Z";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String ioos_category "Location";
    String long_name "Depth";
    Float64 missing_value NaN;
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  date_av {
    Float64 actual_range 1.545182429e+9, 1.552087548e+9;
    String calendar "proleptic_gregorian";
    String ioos_category "Time";
    String long_name "Date Av";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Potential_Density {
    Float64 _FillValue NaN;
    Float64 actual_range 1027.0577757938677, 1027.8447749390793;
    String long_name "Potential Density";
    Float64 missing_value NaN;
  }
  Absolute_Salinity {
    Float64 _FillValue NaN;
    Float64 actual_range 34.024623543822585, 34.94953739825218;
    Float64 colorBarMaximum 37.0;
    Float64 colorBarMinimum 32.0;
    String long_name "Sea Water Practical Salinity";
    Float64 missing_value NaN;
    String standard_name "sea_water_practical_salinity";
    String units "PSU";
  }
  dives {
    Float64 _FillValue NaN;
    Float64 actual_range 79.0, 482.5;
    String long_name "Dives";
  }
 }
  NC_GLOBAL {
    String _NCProperties "version=2,netcdf=4.6.3,hdf5=1.10.4";
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String EDMO_code "3984";
    Float64 geospatial_vertical_max 1019.7978918648507;
    Float64 geospatial_vertical_min -1.3962421362751642;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-05-20T09:59:38Z (local files)
2024-05-20T09:59:38Z https://erddap.sochic-h2020.eu/tabledap/SOCHIC_SOSCEx_STORM2_Glider_Data_slocum_data.das";
    String infoUrl "https://doi.org/10.1029/2021JC017760";
    String institution "University of Gothenburg";
    String keywords "Absolute_Salinity, data, date, date_av, density, depth, dives, earth, Earth Science > Oceans > Salinity/Density > Salinity, index, local, ocean, oceans, potential, Potential_Density, practical, salinity, science, sea, sea_water_practical_salinity, seawater, source, time, water";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "CC BY-NC 4.0 https://creativecommons.org/licenses/by-nc/4.0/";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "SOCHIC-SOSCEx_STORM2_Glider_Data/slocum_data";
    String time_coverage_end "2019-03-08T23:48:01Z";
    String time_coverage_start "2018-12-19T00:00:01Z";
    String title "SOCHIC-SOSCEx_STORM2_Glider_Data/slocum_data";
  }
}

 

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.22
Disclaimers | Privacy Policy | Contact