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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Hydrothermal Estuaries Noble Gases] - Noble gas concentrations and saturation
anomalies from water samples collected on R/V Atlantis cruise AT50-15 in the
Juan de Fuca Ridge from August to September 2023 (Collaborative Research:
Hydrothermal Estuaries: What Sets the Hydrothermal Flux of Fe and Mn to the
Oceans?)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_986923_v1)
Range: longitude = -129.235 to -129.0603°E, latitude = 47.9236 to 48.0034°N, time = 2023-08-28T00:15:00Z to 2023-09-15T03:11:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | 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: 
Draw land mask: 
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 ? )
    Click on the map to specify a new center point. ?
Zoom: 
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 {
  Sta {
    Int32 actual_range 2, 19;
    String long_name "Sta";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.6931817e+9, 1.69474746e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Cast_start_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";
  }
  Cast_End_ISO_DateTime_UTC {
    Float64 actual_range 1.69318896e+9, 1.69475436e+9;
    String ioos_category "Time";
    String long_name "Cast_end_iso_datetime_utc";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -129.235, -129.0603;
    String axis "X";
    String ioos_category "Location";
    String long_name "Long";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 47.9236, 48.0034;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  Cast {
    Int32 actual_range 1, 7;
    String long_name "Cast";
    String units "unitless";
  }
  Bott {
    Int32 actual_range 2, 12;
    String long_name "Bott";
    String units "unitless";
  }
  Press {
    Float32 actual_range 1817.5, 2326.6;
    String long_name "Press";
    String units "decibars";
  }
  Dup {
    Int32 actual_range 0, 1;
    String long_name "Dup";
    String units "unitless";
  }
  Temp {
    Float32 actual_range 1.84, 2.123;
    String long_name "Temp";
    String units "degrees Celsius";
  }
  Salt {
    Float32 actual_range 34.557, 34.611;
    String long_name "Salt";
    String units "PSU";
  }
  Theta {
    Float32 actual_range 1.679, 1.999;
    String long_name "Theta";
    String units "kilograms per cubic meter";
  }
  He_conc {
    Float32 actual_range 1.9e-9, 3.4e-9;
    String long_name "He_conc";
    String units "nM/kg";
  }
  Ne_conc {
    Float32 actual_range 8.07e-9, 1.28e-8;
    String long_name "Ne_conc";
    String units "nM/kg";
  }
  Ar_conc {
    Float32 actual_range 1.62e-5, 1.87e-5;
    String long_name "Ar_conc";
    String units "uM/kg";
  }
  Kr_conc {
    Float32 actual_range 3.86e-9, 4.28e-9;
    String long_name "Kr_conc";
    String units "nM/kg";
  }
  Xe_conc {
    Float32 actual_range 5.91e-10, 6.23e-10;
    String long_name "Xe_conc";
    String units "nM/kg";
  }
  DelHe {
    Float32 actual_range 5.7, 89.06;
    String long_name "Delhe";
    String units "percent";
  }
  DelNe {
    Float32 actual_range 1.69, 61.97;
    String long_name "Delne";
    String units "percent";
  }
  DelAr {
    Float32 actual_range -1.41, 14.18;
    String long_name "Delar";
    String units "percent";
  }
  DelKr {
    Float32 actual_range -3.59, 7.09;
    String long_name "Delkr";
    String units "percent";
  }
  DelXe {
    Float32 actual_range -2.85, 2.47;
    String long_name "Delxe";
    String units "percent";
  }
  del3He {
    Float32 actual_range 23.75, 151.37;
    String long_name "Del3he";
    String units "percent";
  }
  XS3He {
    Float32 actual_range 0.808, 5.65;
    String long_name "Xs3he";
    String units "fmol/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 defaultDataQuery "&amp;time&lt;now";
    String doi "10.26008/1912/bco-dmo.986923.1";
    Float64 Easternmost_Easting -129.0603;
    Float64 geospatial_lat_max 48.0034;
    Float64 geospatial_lat_min 47.9236;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -129.0603;
    Float64 geospatial_lon_min -129.235;
    String geospatial_lon_units "degrees_east";
    String history 
"2026-01-27T18:31:44Z (local files)
2026-01-27T18:31:44Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_986923_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/986923";
    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.";
    Float64 Northernmost_Northing 48.0034;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 47.9236;
    String summary "This dataset contains the analytical results from 126 samples collected from the complex hydrothermal plume system overlying, and dispersing away from, the Endeavour segment of the Juan de Fuca Ridge. The samples were collected in August and September 2023 aboard R/V Atlantis cruise AT50-15 and analyzed at WHOI in the isotope geochemistry facility. The samples were collected, primarily, to trace dilution within a hydrothermal plume whose physical dispersion was predicted from theoretical modelling and traced by the AUV Sentry. Multiple tracers were sampled for, from both the Sentry AUV and from vertical casts of the Texas A&M's trace metal clean CTD-rosette, with noble gas samples collected from the CTD-rosette only because of sample volume requirements.  Measurement of these samples for XS3He, in particular, provides a frame of reference against which all other trace element data in the same samples can be normalized to allow for effects that are due to dilution rather than any biogeochemical reactivity.";
    String time_coverage_end "2023-09-15T03:11:00Z";
    String time_coverage_start "2023-08-28T00:15:00Z";
    String title "[Hydrothermal Estuaries Noble Gases] - Noble gas concentrations and saturation anomalies from water samples collected on R/V Atlantis cruise AT50-15 in the Juan de Fuca Ridge from August to September 2023 (Collaborative Research: Hydrothermal Estuaries: What Sets the Hydrothermal Flux of Fe and Mn to the Oceans?)";
    Float64 Westernmost_Easting -129.235;
  }
}

 

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