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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [AE1913 CTD data] - CTD profiles from R/V Atlantic Explorer cruise AE1913 in
the Sargasso Sea in June of 2019 (Collaborative Research: Direct
Characterization of Adaptive Nutrient Stress Responses in the Sargasso Sea
using Protein Biomarkers and a Biogeochemical AUV)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_916411_v2)
Range: longitude = -71.51041 to -64.16494°E, latitude = 31.37121 to 38.52899°N, depth = 0.993 to 5187.238m, time = 2019-06-16T17:36:29Z to 2019-06-27T03:02:35Z
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 {
  Cast {
    String long_name "Cast";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.560706589e+9, 1.561604555e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Nmea_datetime_utc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 31.37121, 38.52899;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -71.51041, -64.16494;
    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 0.993, 5187.238;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depsm";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  c1mS_cm {
    Float32 actual_range 32.17903, 60.93279;
    String long_name "C1ms_cm";
    String units "milliSiemens per centimeter (mS/cm)";
  }
  c0mS_cm {
    String long_name "C0ms_cm";
    String units "milliSiemens per centimeter (mS/cm)";
  }
  t090C {
    Float32 actual_range 2.195, 27.8802;
    String long_name "T090c";
    String units "degrees Celsius (deg C)";
  }
  prDM {
    Float32 actual_range 1.0, 5289.0;
    String long_name "Prdm";
    String units "Digiquartz (db)";
  }
  sbeox0Mm_L {
    Float32 actual_range -8.92, 286.79;
    String long_name "Sbeox0mm_l";
    String units "micromoles per liter (umol/l)";
  }
  flC {
    Float32 actual_range -0.0063, 4.9798;
    String long_name "Flc";
    String units "Micrograms per liter (ug/l)";
  }
  CStarTr0 {
    Float32 actual_range 85.7565, 100.479;
    String long_name "Cstartr0";
    String units "Percent (%)";
  }
  sal00 {
    String long_name "Sal00";
    String units "Practical Salinity Units (PSU)";
  }
  flag {
    String long_name "Flag";
    String units "unitless";
  }
 }
  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.916411.2";
    Float64 Easternmost_Easting -64.16494;
    Float64 geospatial_lat_max 38.52899;
    Float64 geospatial_lat_min 31.37121;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -64.16494;
    Float64 geospatial_lon_min -71.51041;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 5187.238;
    Float64 geospatial_vertical_min 0.993;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-08T06:03:16Z (local files)
2024-11-08T06:03:16Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_916411_v2.das";
    String infoUrl "https://www.bco-dmo.org/dataset/916411";
    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 38.52899;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 31.37121;
    String summary "Oceanographic samples were collected onboard the R/V Atlantic Explorer between June 16th - 28th 2019, along a transect beginning at the Bermuda Atlantic Time-series Station (BATS) in the Sargasso Sea and terminating in northeast US continental shelf waters. The R/V Atlantic Explorer CTD provided physicochemical contextualization (temperature, oxygen, fluorescence, turbidity) and was deployed at all stations except the last one, St. 9, due to time restrictions.";
    String time_coverage_end "2019-06-27T03:02:35Z";
    String time_coverage_start "2019-06-16T17:36:29Z";
    String title "[AE1913 CTD data] - CTD profiles from R/V Atlantic Explorer cruise AE1913 in the Sargasso Sea in June of 2019 (Collaborative Research: Direct Characterization of Adaptive Nutrient Stress Responses in the Sargasso Sea using Protein Biomarkers and a Biogeochemical AUV)";
    Float64 Westernmost_Easting -71.51041;
  }
}

 

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