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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Event log for GEOTRACES Southwestern Atlantic Transect cruise RSS/James Cook
JC057 leg 3, March 2011 (GEOTRACES-SWAT project)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_672511)
Range: longitude = -52.6885 to -27.9988°E, latitude = -49.5475 to -2.6385°N
Information:  Summary ? | License ? | ISO 19115 | Metadata | Background (external link) | Subset | 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: 
[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 {
  cruise_id {
    String bcodmo_name "cruise_id";
    String description "cruise identifier";
    String long_name "Cruise Id";
    String units "unitless";
  }
  station {
    Byte _FillValue 127;
    Byte actual_range 1, 17;
    String bcodmo_name "station";
    String description "consecutive station number";
    String long_name "Station";
    String units "unitless";
  }
  cast {
    Byte _FillValue 127;
    Byte actual_range 1, 5;
    String bcodmo_name "cast";
    String description "cast number";
    String long_name "Cast";
    String units "unitless";
  }
  instrument {
    String bcodmo_name "instrument";
    String description "type of instrument used for event: UCC = Ultra Clean Cast; CTD25L = high volme 25 liter CTD; ISP = in situ pump";
    String long_name "Instrument";
    String units "unitless";
  }
  action {
    String bcodmo_name "action";
    String description "start or end of event";
    String long_name "Action";
    String units "unitless";
  }
  date {
    String bcodmo_name "date";
    String description "date formatted as yyyy-mm-dd";
    String long_name "Date";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/ADATAA01/";
    String source_name "date";
    String time_precision "1970-01-01";
    String units "unitless";
  }
  time2 {
    String bcodmo_name "time";
    String description "time of day formatted as HH:MM";
    String long_name "Time";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/AHMSAA01/";
    String units "unitless";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -52.6885, -27.9988;
    String axis "X";
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "longitude; east is positive";
    String ioos_category "Location";
    String long_name "Longitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LONX/";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range -49.5475, -2.6385;
    String axis "Y";
    String bcodmo_name "latitude";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "latitude; north is positive";
    String ioos_category "Location";
    String long_name "Latitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LATX/";
    String standard_name "latitude";
    String units "degrees_north";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson";
    String acquisition_description "\"\"";
    String awards_0_award_nid "672206";
    String awards_0_award_number "OCE-1260514";
    String awards_0_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=1260514";
    String awards_0_funder_name "NSF Division of Ocean Sciences";
    String awards_0_funding_acronym "NSF OCE";
    String awards_0_funding_source_nid "355";
    String awards_0_program_manager "Candace O. Major";
    String awards_0_program_manager_nid "51690";
    String cdm_data_type "Other";
    String comment 
"JC057 leg 3 event log 
   PI: M. Rijkenberg (NIOZ) 
     extracted from cruise report v.250511 
   version: 2017-01-05";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_type "institution";
    String creator_url "https://www.bco-dmo.org/";
    String data_source "extract_data_as_tsv version 2.3  19 Dec 2019";
    String date_created "2017-01-05T21:00:36Z";
    String date_modified "2020-03-26T18:40:45Z";
    String defaultDataQuery "&time<now";
    String doi "10.26008/1912/bco-dmo.672511.1";
    Float64 Easternmost_Easting -27.9988;
    Float64 geospatial_lat_max -2.6385;
    Float64 geospatial_lat_min -49.5475;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -27.9988;
    Float64 geospatial_lon_min -52.6885;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-03-29T01:15:19Z (local files)
2024-03-29T01:15:19Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_672511.das";
    String infoUrl "https://www.bco-dmo.org/dataset/672511";
    String institution "BCO-DMO";
    String keywords "action, bco, bco-dmo, biological, cast, chemical, cruise, cruise_id, data, dataset, date, dmo, erddap, instrument, latitude, longitude, management, oceanography, office, preliminary, station, time, time2";
    String license "https://www.bco-dmo.org/dataset/672511/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/672511";
    Float64 Northernmost_Northing -2.6385;
    String param_mapping "{'672511': {'lat': 'master - latitude', 'lon': 'master - longitude'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/672511/parameters";
    String people_0_affiliation "Royal Netherlands Institute  for Sea Research";
    String people_0_affiliation_acronym "NIOZ";
    String people_0_person_name "Micha J. A. Rijkenberg";
    String people_0_person_nid "672404";
    String people_0_role "Principal Investigator";
    String people_0_role_type "originator";
    String people_1_affiliation "Woods Hole Oceanographic Institution";
    String people_1_affiliation_acronym "WHOI BCO-DMO";
    String people_1_person_name "Nancy Copley";
    String people_1_person_nid "50396";
    String people_1_role "BCO-DMO Data Manager";
    String people_1_role_type "related";
    String project "Nd Paleocirculation Proxy";
    String projects_0_acronym "Nd Paleocirculation Proxy";
    String projects_0_description 
"Extracted from the NSF award abstract:
Neodymium (Nd) isotopes are increasingly used in paleoceanographic studies as \"quasi-conservative\" water mass tracers. However, the limitations of this proxy are not yet fully understood. The proposed work aims to address this uncertainty by critically evaluating the behavior of Nd isotopes as tracers of water mass mixing. The project, led by researchers at Columbia University's Lamont-Doherty Earth Observatory, will analyze in-hand seawater and surface sediment samples collected along a meridional transect in the southwest Atlantic (0 to 50 degrees S) during a GEOTRACES cruise. The sample suite will be used to test 1) whether Nd isotope ratios deviate from expected values for mixing along circulation transport paths, 2) whether Nd isotopes behave quasi-conservatively away from continental margins, 3) whether seafloor features (e.g., continental shelf, volcanic seamounts) add significant external Nd to the system, and 4) whether the Southern Hemisphere wind zones impact Nd isotope values through aeolian deposition. The relationship between Nd isotopes in authigenic surface sediments and those in the overlying seawater will be calibrated for the first time.
By testing an emerging tool in the study of past ocean dynamics, this research will enable a more accurate understanding of changes in the ocean-climate system. The project will support an early-career researcher and a graduate student. Undergraduate students will be involved through an NSF-supported summer internship program at LDEO.";
    String projects_0_end_date "2017-08";
    String projects_0_geolocation "SW Atlantic Ocean";
    String projects_0_name "A Critical Test of the Nd Paleocirculation Proxy";
    String projects_0_project_nid "672207";
    String projects_0_start_date "2013-09";
    String publisher_name "Biological and Chemical Oceanographic Data Management Office (BCO-DMO)";
    String publisher_type "institution";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -49.5475;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "cruise_id";
    String summary "Event log for GEOTRACES Southwestern Atlantic Transect cruise RSS/James Cook JC057 leg 3, March 2011 (GEOTRACES-SWAT project).";
    String title "Event log for GEOTRACES Southwestern Atlantic Transect cruise RSS/James Cook JC057 leg 3, March 2011 (GEOTRACES-SWAT project)";
    String version "1";
    Float64 Westernmost_Easting -52.6885;
    String xml_source "osprey2erddap.update_xml() v1.3";
  }
}

 

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