BCO-DMO ERDDAP
Accessing BCO-DMO data
log in    
Brought to you by BCO-DMO    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Baltic GasEx 1 SF6 and Helium] - SF6 and helium data from a tracer release
experiment conducted June 2018 in the coastal Baltic Sea during FS Alkor cruise
AL510 (Collaborative Research: Influence of Surfactants on Air-Sea Gas
Exchange: 3He/SF6 Experiments in the Baltic Sea)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_915772_v1)
Range: longitude = 10.0724 to 10.1787°E, depth = 1.4 to 20.8m, time = 2018-06-06T16:07:00Z to 2018-06-12T04:11:00Z
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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.52830122e+9, 1.52877666e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Iso_datetime_utc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Station {
    String long_name "Station";
    String units "unitless";
  }
  Latitude {
    Float32 actual_range 54.5343, 54.7075;
    String long_name "Latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range 10.0724, 10.1787;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 1.4, 20.8;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Temperature {
    Float32 actual_range 6.06, 19.2;
    String long_name "Temperature";
    String units "degrees Celsius (°C)";
  }
  Salinity {
    Float32 actual_range 11.8, 18.3;
    String long_name "Salinity";
    String units "PSU";
  }
  He3_excess {
    Float32 actual_range -13.3, 4790.0;
    String long_name "He3_excess";
    String units "cubic centimeters at standard temperature and pressure per gram times 10^-16 (ccSTP/g*10-16)";
  }
  SF6_rep1 {
    Float32 actual_range 0.00188, 0.75;
    String long_name "Sf6_rep1";
    String units "picomoles per kilogram (pmol/kg)";
  }
  SF6_rep2 {
    Float32 actual_range 0.00508, 0.824;
    String long_name "Sf6_rep2";
    String units "picomoles per kilogram (pmol/kg)";
  }
  SF6_rep3 {
    Float32 actual_range 0.0754, 0.196;
    String long_name "Sf6_rep3";
    String units "picomoles per kilogram (pmol/kg)";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_url "https://www.bco-dmo.org/";
    String doi "10.26008/1912/bco-dmo.915772.1";
    Float64 Easternmost_Easting 10.1787;
    Float64 geospatial_lon_max 10.1787;
    Float64 geospatial_lon_min 10.0724;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 20.8;
    Float64 geospatial_vertical_min 1.4;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-15T14:03:55Z (local files)
2024-11-15T14:03:55Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_915772_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/915772";
    String institution "BCO-DMO";
    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.";
    String sourceUrl "(local files)";
    String summary "These data are 3He and SF6 from a tracer release experiment conducted in the coastal Baltic Sea. The experiment was conducted in June 2018 and the goal was to determine gas transfer velocities in the Baltic Sea, where it is thought that excess surfactants and limited wind fetch would affect the relationship between wind speed and gas transfer velocity.";
    String time_coverage_end "2018-06-12T04:11:00Z";
    String time_coverage_start "2018-06-06T16:07:00Z";
    String title "[Baltic GasEx 1 SF6 and Helium] - SF6 and helium data from a tracer release experiment conducted June 2018 in the coastal Baltic Sea during FS Alkor cruise AL510 (Collaborative Research: Influence of Surfactants on Air-Sea Gas Exchange: 3He/SF6 Experiments in the Baltic Sea)";
    Float64 Westernmost_Easting 10.0724;
  }
}

 

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