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

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [AE1913 R2R ELOG] - Amended Rolling Deck to Repository (R2R) event log (ELOG)
taken on the 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_926526_v1)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 Message_ID (unitless) ?          "10"    "99"
 Date (unitless) ?          "Fri 21 Jun 2019 02..."    "Wed 26 Jun 2019 23..."
 Event (unitless) ?          "20190616.1736.001"    "20190628.1134.001"
 R2R_Event (unitless) ?          "ae1913-SE-20190616..."    "ae1913-SE-20190628..."
 Instrument (unitless) ?          "CLIO"    "Trace Metal Rosette"
 Action (unitless) ?          "deploy"    "stopSample"
 Transect (unitless) ?          "50055"    "BV55"
 Station (unitless) ?          "#2"    "St.5 to St. 6"
 Cast (unitless) ?          "1"    "pumpcast #5"
 latitude (degrees_north) ?          31.3678    41.45598
  < slider >
 longitude (degrees_east) ?          -71.24792    -64.16295
  < slider >
 depth (Seafloor, m) ?          4530    4700
  < slider >
 Author (unitless) ?          "Paloma"    "rChmiel"
 Comment (unitless) ?          "10am 6/24 flow met..."    "underwayAM"
 Cruise (unitless) ?          "AE1913"    "AE1913"
 dateTimeUTC (unitless) ?          "20190616.1720"    "20190628.1030"
 GPS_Time (unitless) ?          "2019/06/16 17:20:00"    "2019/06/28 10:30:01"
 dateTime8601 (unitless) ?          "2019-06-16T17:20:0..."    "2019-06-28T10:30:0..."
 Revisions (unitless) ?          "& Mon Jun 17 03:42..."    "& Wed Jun 26 11:38..."
 
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.Hover here to see a list of options. Click on an option to select it.")

File type: (more information)

(Documentation / Bypass this form ? )
 
(Please be patient. It may take a while to get the data.)


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Message_ID {
    String long_name "Message_id";
    String units "unitless";
  }
  Date {
    String long_name "Date";
    String units "unitless";
  }
  Event {
    String long_name "Event";
    String units "unitless";
  }
  R2R_Event {
    String long_name "R2r_event";
    String units "unitless";
  }
  Instrument {
    String long_name "Instrument";
    String units "unitless";
  }
  Action {
    String long_name "Action";
    String units "unitless";
  }
  Transect {
    String long_name "Transect";
    String units "unitless";
  }
  Station {
    String long_name "Station";
    String units "unitless";
  }
  Cast {
    String long_name "Cast";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 31.3678, 41.45598;
    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.24792, -64.16295;
    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";
    Int32 actual_range 4530, 4700;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Seafloor";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Author {
    String long_name "Author";
    String units "unitless";
  }
  Comment {
    String long_name "Comment";
    String units "unitless";
  }
  Cruise {
    String long_name "Cruise";
    String units "unitless";
  }
  dateTimeUTC {
    String long_name "Datetimeutc";
    String units "unitless";
  }
  GPS_Time {
    String long_name "Gps_time";
    String units "unitless";
  }
  dateTime8601 {
    String long_name "Datetime8601";
    String units "unitless";
  }
  Revisions {
    String long_name "Revisions";
    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.926526.1";
    Float64 Easternmost_Easting -64.16295;
    Float64 geospatial_lat_max 41.45598;
    Float64 geospatial_lat_min 31.3678;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -64.16295;
    Float64 geospatial_lon_min -71.24792;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 4700.0;
    Float64 geospatial_vertical_min 4530.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-21T08:50:53Z (local files)
2024-11-21T08:50:53Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_926526_v1.html";
    String infoUrl "https://www.bco-dmo.org/dataset/926526";
    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 41.45598;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 31.3678;
    String summary 
"The Electronic Logger (ELOG) tracked all deployments on the AE1913 cruise, including CTD, McLane pump, trace metal rosette, and AUV Clio deployment/recoveries, flow-through seawater sampling, sediment trap and plankton nets. Corresponding CTD files from each deployment are recorded in the \"comments\" column.

R/V Atlantic Explorer cruise AE1913 was conducted between June 16th - 28th, 2019 in the Sargasso Sea, beginning at Bermuda Atlantic Time-series Station (BATS) and ending in the northeast shelf of Woods Hole Oceanographic Institution (WHOI).";
    String title "[AE1913 R2R ELOG] - Amended Rolling Deck to Repository (R2R) event log (ELOG) taken on the 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.24792;
  }
}

 

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