Make A Graph

Dataset Title:	[event log] - Scientific sampling event log from R/V Knorr cruise KN207-03 in the North Atlantic (transect from Ponta Delgada, Azores to Reykjavik, Iceland) in 2012 (NA-VICE project) (Lipid lubrication of oceanic carbon and sulfur biogeochemistry via a host-virus chemical arms race)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_3739)
Range:	longitude = -35.07394 to -21.93818°E, latitude = 37.73759 to 65.44701°N, time = 2012-06-15T16:41:00Z to 2012-07-18T18:23:00Z
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Data Access Form \| Files

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:

X Axis:

Y Axis:

Color:

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.

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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  event {
    String bcodmo_name "event";
    String description 
"ID number for the event composed of date (YYYYmmdd), time (HHMM), and the event number (xxx). Record of the date/time when the event was originally logged.
format: YYYYmmdd.HHMM.xxx";
    String long_name "Event";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/EVTAGFL/";
    String units "unitless";
  }
  date_utc {
    Int32 _FillValue 2147483647;
    Int32 actual_range 20120615, 20120718;
    String bcodmo_name "date";
    String description "Date (UTC), in YYYYmmdd format, that the event took place.";
    String long_name "Date Utc";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/ADATAA01/";
    String units "unitless";
  }
  time_utc {
    String bcodmo_name "time_utc";
    String description "Time (UTC), in HHMM format, that the event took place.";
    String long_name "Time Utc";
    String units "HHMM";
  }
  instrument {
    String bcodmo_name "instrument";
    String description "Name of instrument.";
    String long_name "Instrument";
    String units "text";
  }
  action {
    String bcodmo_name "action";
    String description "Activity performed with the instrument.";
    String long_name "Action";
    String units "text";
  }
  transect {
    String bcodmo_name "transect";
    String description "Transect name.";
    String long_name "Transect";
    String units "dimensionless";
  }
  station {
    String bcodmo_name "station";
    String description "Alpha-numeric code representing the sampling station.";
    String long_name "Station";
    String units "dimensionless";
  }
  cast {
    String bcodmo_name "cast";
    String description "Cast number.";
    String long_name "Cast";
    String units "dimensionless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 37.73759, 65.44701;
    String axis "Y";
    String bcodmo_name "latitude";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "Latitude in decimal degrees.";
    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 -35.07394, -21.93818;
    String axis "X";
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "Longitude, in decimal degrees.";
    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";
  }
  depth_w {
    String bcodmo_name "depth_w";
    String description "Water depth (in meters). Originally named 'Seafloor'.";
    String long_name "Depth";
    String standard_name "depth";
    String units "meters";
  }
  author {
    String bcodmo_name "investigator";
    String description "Name of person entering the event.";
    String long_name "Author";
    String units "text";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.33977846e+9, 1.34263578e+9;
    String axis "T";
    String bcodmo_name "ISO_DateTime_UTC";
    String description "Date and time (UTC) formatted to ISO8601 standard. T indicates start of time string; Z indicates UTC.";
    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";
  }
  comment {
    String bcodmo_name "comment";
    String description "Free-text comment entered about the sampling event and post-cruise corrections.";
    String long_name "Comment";
    String units "text";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson,.odvTxt";
    String acquisition_description 
"The event log was created using the Rolling Deck to Repository (R2R) event log
application (ELOG). The log includes a record of all scientific sampling
events from the cruise. In addition to event identification numbers unique for
the cruise, the scientific sampling event log includes date and time (GMT),
position (latitude and longitude), station and cast identifier as appropriate
to the sampling event, sampling instrument name, name of person responsible
for the sampling event, and a comment field to record additional information.
See more information about the [R2R event
log](\\\\\"https://www.rvdata.us/about/eventlog\\\\\").";
    String awards_0_award_nid "54797";
    String awards_0_award_number "OCE-1061883";
    String awards_0_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=1061883";
    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 
"Event log from cruise KN207-03 
 Chief Scientist: K. Bidle (Rutgers) 
 Version: 10 April 2013 
  
 Note: Post-cruise corrections to position, date, time have been applied and are 
  described in comment column. Original event numbers have been preserved, 
  indicating the date and time each event was originally logged.";
    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 "2012-10-02T17:12:38Z";
    String date_modified "2019-03-05T16:46:45Z";
    String defaultDataQuery "&amp;time&lt;now";
    String doi "10.1575/1912/bco-dmo.3739.1";
    Float64 Easternmost_Easting -21.93818;
    Float64 geospatial_lat_max 65.44701;
    Float64 geospatial_lat_min 37.73759;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -21.93818;
    Float64 geospatial_lon_min -35.07394;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-08T06:13:36Z (local files)
2024-11-08T06:13:36Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_3739.das";
    String infoUrl "https://www.bco-dmo.org/dataset/3739";
    String institution "BCO-DMO";
    String keywords "action, author, bco, bco-dmo, biological, cast, chemical, comment, data, dataset, date, date_utc, depth, depth_w, dmo, erddap, event, instrument, iso, latitude, longitude, management, oceanography, office, preliminary, station, time, time_utc, transect";
    String license "https://www.bco-dmo.org/dataset/3739/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/3739";
    Float64 Northernmost_Northing 65.44701;
    String param_mapping "{'3739': {'lat': 'master - latitude', 'lon': 'master - longitude', 'ISO_DateTime_UTC': 'flag - time'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/3739/parameters";
    String people_0_affiliation "Rutgers University";
    String people_0_affiliation_acronym "Rutgers IMCS";
    String people_0_person_name "Kay D Bidle";
    String people_0_person_nid "51281";
    String people_0_role "Chief Scientist";
    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 "Shannon Rauch";
    String people_1_person_nid "51498";
    String people_1_role "BCO-DMO Data Manager";
    String people_1_role_type "related";
    String project "NA-VICE";
    String projects_0_acronym "NA-VICE";
    String projects_0_description 
"This project is also called \"NA-VICE\" (North Atlantic Virus Infection of Coccolithophores Expedition).
Project description from NSF award abstract:
Despite the critical importance of viruses in shaping marine microbial ecosystems, very little is known about the molecular mechanisms mediating phytoplankton-virus interactions. As a consequence, we currently lack biomarkers to quantify active viral infection in the oceans, significantly hindering our understanding of its ecological and biogeochemical impacts.
The coccolithophore Emiliania huxleyi (Prymnesiophyceae, Haptophyte) is a cosmopolitan unicellular photoautotroph whose calcite skeletons account for about a third of the total marine CaCO3 production. E. huxleyi forms massive annual spring blooms in the North Atlantic that are infected and terminated by lytic, giant double-stranded DNA containing coccolithoviruses. Findings that lytic viral infection of E. huxleyi recruits the hosts programmed cell death (PCD) machinery demonstrate that viruses employ a sophisticated, co-evolutionary “arms race” in mediating host-virus interactions. The investigators recently demonstrated that viral glycosphingolipids (vGSLs), derived from unexpected cluster of sphingolipid biosynthetic genes, a pathway never before described in a viral genome, play a crucial functional role in facilitating infection of E. huxleyi. The observations of vGSLs in the North Atlantic and Norwegian fjords further suggest that they may be novel, diagnostic biomarkers for viral infection of coccolithophore populations. At the same time, the discovery of vGSLs and a distinct, protective 802 lipid argues that a host-virus, co-evolutionary chemical arms race plays a pivotal role in regulating viral infection and in lubricating upper ocean biogeochemical fluxes of carbon and sulfur.
The focus of this collaborative research project is to elucidate the molecular, ecological, and biogeochemical links between vGSLs (and other polar lipids) and the global cycles of carbon and sulfur.
The team of investigators proposes a multi-pronged approach combing a suite of lab-based, mechanistic studies using several haptophyte-virus model systems along with observational studies and manipulative field-based experiments the Northeast Atlantic. Using these diagnostic markers, they will document active viral infection of natural coccolithophore populations and couple it with a suite of oceanographic measurements in order to quantify how viral infection (via vGSLs) influences cell fate, the dissolved organic carbon (DOC) pool, vertical export of particular organic (POC) and inorganic carbon (PIC; as calcium carbonate, CaCO3) (along with associated alkenone lipid biomarkers and genetic signatures of viruses and their hosts) and the upper ocean sulfur cycle (via the cycling of dimethylsulfide [DMS] and other biogenic sulfur compounds). Furthermore, given they are unique to viruses, the investigators propose that vGSLs can be used to trace the flow of virally-derived carbon and provide quantitative insights into a “viral shunt” that diverts fixed carbon from higher trophic levels and the deep sea.
The overarching hypothesis for this study is that vGSLs are cornerstone molecules in the upper ocean, which facilitate viral infection on massive scales and thereby mechanistically \"lubricate\" the biogeochemical fluxes of C and S in the ocean.";
    String projects_0_end_date "2014-02";
    String projects_0_geolocation "North Atlantic; Azores to Iceland";
    String projects_0_name "Lipid lubrication of oceanic carbon and sulfur biogeochemistry via a host-virus chemical arms race";
    String projects_0_project_nid "2136";
    String projects_0_start_date "2011-03";
    String publisher_name "Biological and Chemical Oceanographic Data Management Office (BCO-DMO)";
    String publisher_type "institution";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 37.73759;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Scientific sampling event log from R/V Knorr cruise KN207-03 in the North Atlantic (transect from Ponta Delgada, Azores to Reykjavik, Iceland) in 2012. The scientific sampling event log was created using v1.0 of the Rolling Deck to Repository (R2R) event log application.";
    String time_coverage_end "2012-07-18T18:23:00Z";
    String time_coverage_start "2012-06-15T16:41:00Z";
    String title "[event log] - Scientific sampling event log from R/V Knorr cruise KN207-03 in the North Atlantic (transect from Ponta Delgada, Azores to Reykjavik, Iceland) in 2012 (NA-VICE project) (Lipid lubrication of oceanic carbon and sulfur biogeochemistry via a host-virus chemical arms race)";
    String version "1";
    Float64 Westernmost_Easting -35.07394;
    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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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.