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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [cruise track AE1004] - Cruise track data from the R/V Atlantic Explorer
AE1004 cruise from the Bermuda Atlantic Time-Series, Hydrostation S in
2010 (Ocean Microbial Observatory project) (Transitions in the Surface Layer
and the Role of Vertically Stratified Microbial Communities in the Carbon
Cycle - An Oceanic Microbial Observatory)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_514440)
Range: longitude = -64.6623 to -64.4745°E, latitude = 32.1578 to 32.3789°N, time = 2010-03-02T12:21:02Z to 2010-03-02T21:34:54Z
Information:  Summary ? | License ? | FGDC | 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: 
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 {
  date {
    Int32 _FillValue 2147483647;
    Int32 actual_range 20100302, 20100302;
    String bcodmo_name "date";
    String description "Date (UTC) in YYYYMMDD format.";
    String long_name "Date";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/ADATAA01/";
    String units "unitless";
  }
  time2 {
    Int32 _FillValue 2147483647;
    Int32 actual_range 122102, 213454;
    String bcodmo_name "time";
    String description "TIme (UTC).";
    String long_name "Time";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/AHMSAA01/";
    String units "HHMMSS";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 32.1578, 32.3789;
    String axis "Y";
    String bcodmo_name "latitude";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "Latitude component of geographic position.";
    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";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -64.6623, -64.4745;
    String axis "X";
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "Longitude component of geographic position.";
    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";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.267532462e+9, 1.267565694e+9;
    String axis "T";
    String bcodmo_name "ISO_DateTime_UTC";
    String description "Date/Time (UTC) ISO formatted. This standard is based on ISO 8601:2004(E) formatted as YYYY-MM-DDTHH:MM:SS[.xx]Z.";
    String ioos_category "Time";
    String long_name "ISO Date Time UTC";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/DTUT8601/";
    String source_name "ISO_DateTime_UTC";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson,.odvTxt";
    String acquisition_description 
"Control point navigation was obtained from the R2R catalog:
\\u00a0[https://www.rvdata.us/search/cruise/AE1004](\\\\\"https://www.rvdata.us/search/cruise/AE1004\\\\\")";
    String awards_0_award_nid "514363";
    String awards_0_award_number "OCE-0802004";
    String awards_0_data_url "http://www.nsf.gov/awardsearch/showAward?AWD_ID=0802004";
    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 "David L. Garrison";
    String awards_0_program_manager_nid "50534";
    String cdm_data_type "Other";
    String comment 
"Cruise track for deployment AE1004 
  Project: Ocean Microbial Observatory 
  PIs:  Carlson (UCSB) and Giovanonni (OSU) 
  
  version 20140506";
    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 "2014-05-06T19:34:18Z";
    String date_modified "2019-09-04T15:08:30Z";
    String defaultDataQuery "&time<now";
    String doi "10.1575/1912/bco-dmo.514440.1";
    Float64 Easternmost_Easting -64.4745;
    Float64 geospatial_lat_max 32.3789;
    Float64 geospatial_lat_min 32.1578;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -64.4745;
    Float64 geospatial_lon_min -64.6623;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-08T06:18:51Z (local files)
2024-11-08T06:18:51Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_514440.das";
    String infoUrl "https://www.bco-dmo.org/dataset/514440";
    String institution "BCO-DMO";
    String instruments_0_acronym "GPS";
    String instruments_0_dataset_instrument_nid "543609";
    String instruments_0_description "The Global Positioning System (GPS) is a U.S. space-based radionavigation system that provides reliable positioning, navigation, and timing services to civilian users on a continuous worldwide basis. The U.S. Air Force develops, maintains, and operates the space and control segments of the NAVSTAR GPS transmitter system. Ships use a variety of receivers (e.g. Trimble and Ashtech) to interpret the GPS signal and determine accurate latitude and longitude.";
    String instruments_0_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L05/current/POS03/";
    String instruments_0_instrument_name "Global Positioning System Receiver";
    String instruments_0_instrument_nid "560";
    String instruments_0_supplied_name "GPS";
    String keywords "bco, bco-dmo, biological, chemical, data, dataset, date, dmo, erddap, iso, latitude, longitude, management, oceanography, office, preliminary, time, time2";
    String license "https://www.bco-dmo.org/dataset/514440/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/514440";
    Float64 Northernmost_Northing 32.3789;
    String param_mapping "{'514440': {'lat': 'master - latitude', 'lon': 'master - longitude', 'ISO_DateTime_UTC': 'flag - time'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/514440/parameters";
    String people_0_affiliation "University of California-Santa Barbara";
    String people_0_affiliation_acronym "UCSB-MSI";
    String people_0_person_name "Craig Carlson";
    String people_0_person_nid "50575";
    String people_0_role "Lead 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 "Danie Kinkade";
    String people_1_person_nid "51549";
    String people_1_role "BCO-DMO Data Manager";
    String people_1_role_type "related";
    String project "Ocean Microbial Observatory";
    String projects_0_acronym "Ocean Microbial Observatory";
    String projects_0_description 
"(Adapted from the NSF award abstract)
The premise of this project is that stratified bacterioplankton clades engage in specialized biogeochemical activities that can be identified by integrated oceanographic and microbiological approaches. Specifically, the objective of this project is to assess if the mesopelagic microbial community rely on diagenetically altered organic matter and subcellular fragments that are produced by microbial processes in the euphotic zone and delivered into the upper mesopelagic by sinking or mixing. In past efforts this microbial observatory had greater success cultivating members of the euphotic zone microbial community, and revealed an unanticipated growth requirement for reduced sulfur compounds in alphaproteobacteria of the SAR11 clade. Genomic information showed that intense competition for substrates imposes trade-offs on bacterioplankton - there are regions of N dimensional nutrient space where specialists win. We postulate that specific growth requirements may explain some the regular spatial and temporal patterns that have been observed in upper mesopelagic bacterioplankton communities, and the difficulties of culturing some of these organisms.
The specific objectives of this project are: 1) to produce 13C and 15N labeled subcellular (e.g., soluble, cell wall, and membrane) and DOM fractions from photosynthetic plankton cultures and use stable isotope probing to identify specific clades in the surface and upper mesopelagic microbial community that assimilate fractions of varying composition and lability. 2) to use fluorescence in situ hybridization approaches to monitor temporal and spatial variability of specific microbial populations identified from the SIP and HTC experiments. To increase resolution we will use CARD-FISH protocols. 3) to measure the proteomes of bacterioplankton communities to identify highly translated genes in the surface layer and upper mesopelagic, and community responses to seasonal nutrient limitation. 4) and, to cultivate these organisms via high throughput culturing (HTC) by pursuing the hypothesis that they require specific nutrient factors and/or diagenetically altered organic substrates. Complete genome sequences from key organisms will be sought and used as queries to study patterns of natural variation in genes and populations that have been associated with biogeochemically important functions.";
    String projects_0_end_date "2014-07";
    String projects_0_geolocation "Bermuda Atlantic Time-Series study site";
    String projects_0_name "Transitions in the Surface Layer and the Role of Vertically Stratified Microbial Communities in the Carbon Cycle - An Oceanic Microbial Observatory";
    String projects_0_project_nid "514365";
    String projects_0_project_website "http://www.bios.edu/research/projects/oceanic-microbial-observatory/";
    String projects_0_start_date "2008-08";
    String publisher_name "Biological and Chemical Oceanographic Data Management Office (BCO-DMO)";
    String publisher_type "institution";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 32.1578;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "date";
    String summary "Cruise track data from the R/V Atlantic Explorer AE1004 cruise from the Bermuda Atlantic Time-Series, Hydrostation S in 2010.";
    String time_coverage_end "2010-03-02T21:34:54Z";
    String time_coverage_start "2010-03-02T12:21:02Z";
    String title "[cruise track AE1004] - Cruise track data from the R/V Atlantic Explorer AE1004 cruise from the Bermuda Atlantic Time-Series, Hydrostation S in 2010 (Ocean Microbial Observatory project) (Transitions in the Surface Layer and the Role of Vertically Stratified Microbial Communities in the Carbon Cycle - An Oceanic Microbial Observatory)";
    String version "1";
    Float64 Westernmost_Easting -64.6623;
    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.22
Disclaimers | Privacy Policy | Contact