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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Event logs from R/V Oceanus, R/V Endeavor cruises OC468-02, EN496, EN509,
EN510 in the Gulf of Mexico; 2010-2012 (GoMX - N2 Fixation project)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_3895)
Range: longitude = -95.51763 to -75.00037°E, latitude = 25.81505 to 30.35938°N, time = 1999-11-30T00:00:00Z to (now?)
Information:  Summary ? | License ? | 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 {
  CruiseId {
    String bcodmo_name "cruiseid";
    String description "Cruise Id";
    String long_name "Cruise Id";
    String units "text";
  }
  Op_Number {
    String bcodmo_name "operation";
    String description "Operation Number in xxx.xx format";
    String long_name "Op Number";
    String units "unitless";
  }
  Stn {
    String bcodmo_name "station";
    String description "Station Number (First 3 digits of Op_Number)";
    String long_name "STN";
    String units "dimensionless";
  }
  Evt {
    String bcodmo_name "event";
    String description "Event Number (Last digits after decimal point of Op_Number)";
    String long_name "Evt";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/EVTAGFL/";
    String units "dimensionless";
  }
  Date_Local {
    String bcodmo_name "date_local";
    String description "Date Local in YYYYMMDD format";
    String long_name "Date Local";
    String units "unitless";
  }
  Time_Local {
    String bcodmo_name "time_local";
    String description "Time Local in HHMM format";
    String long_name "Time Local";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 9.4392e+8, NaN;
    String axis "T";
    String bcodmo_name "ISO_DateTime_UTC";
    String description "Date/Time 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 standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Latitude_Deg_N {
    Byte _FillValue 127;
    Byte actual_range 25, 30;
    String bcodmo_name "latitude";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "Latitude Degrees North";
    String long_name "Latitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LATX/";
    String standard_name "latitude";
    String units "whole degrees";
  }
  Latitude_Min_N {
    String bcodmo_name "latitude";
    String description "Latitude Minutes North";
    String long_name "Latitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LATX/";
    String standard_name "latitude";
    String units "decimal minutes";
  }
  Longitude_Deg_W {
    Byte _FillValue 127;
    Byte actual_range 75, 95;
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "Longitude Degrees West";
    String long_name "Longitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LONX/";
    String standard_name "longitude";
    String units "whole degrees";
  }
  Longitude_Min_W {
    String bcodmo_name "longitude";
    String description "Longitude Minutes West";
    String long_name "Longitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LONX/";
    String standard_name "longitude";
    String units "decimal minutes";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 25.81505, 30.35938;
    String axis "Y";
    String bcodmo_name "latitude";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "Latitude (South is negative)";
    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 -95.51763, -75.00037;
    String axis "X";
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "Longitude (West is negative)";
    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";
  }
  Lease_Block {
    String bcodmo_name "site";
    String description "Lease Block";
    String long_name "Lease Block";
    String units "text";
  }
  Operation {
    String bcodmo_name "operation";
    String description "Operation";
    String long_name "Operation";
    String units "text";
  }
  Seq_Number {
    String bcodmo_name "sampling_sequence";
    String description 
"Sequence Number:
Things that happen multiple times, are given a unique sequence number (ROV dives, CTD, MUC)
ROV dives will be sequentially numbered (1,2,3,4,5) across stations
CTDs will be sequentially numbered (1,2,3,4,5) across stations
MUCs will be sequentially numbered (1,2,3,4,5) across stations";
    String long_name "Seq Number";
    String units "dimensionless";
  }
  Notes {
    String bcodmo_name "activity_and_comments";
    String description "Activity and Comments";
    String long_name "Notes";
    String units "text";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson,.odvTxt";
    String acquisition_description "Generated by science party aboard vessel";
    String awards_0_award_nid "54918";
    String awards_0_award_number "OCE-0928495";
    String awards_0_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0928495";
    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 
"Version: 15 March 2013 
  PIs: Montoya, Villareal 
  Event Logs - All Cruises";
    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 "2013-03-15T18:45:00Z";
    String date_modified "2019-10-29T16:24:06Z";
    String defaultDataQuery "&amp;time&lt;now";
    String doi "10.1575/1912/bco-dmo.3895.1";
    Float64 Easternmost_Easting -75.00037;
    Float64 geospatial_lat_max 30.35938;
    Float64 geospatial_lat_min 25.81505;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -75.00037;
    Float64 geospatial_lon_min -95.51763;
    String geospatial_lon_units "degrees_east";
    String history 
"2022-08-17T11:35:28Z (local files)
2022-08-17T11:35:28Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_3895.das";
    String infoUrl "https://www.bco-dmo.org/dataset/3895";
    String institution "BCO-DMO";
    String keywords "bco, bco-dmo, biological, block, chemical, cruise, CruiseId, data, dataset, date, Date_Local, dmo, erddap, evt, iso, ISO_DateTime_UTC, latitude, Latitude_Deg_N, Latitude_Min_N, lease, Lease_Block, local, longitude, Longitude_Deg_W, Longitude_Min_W, management, notes, number, oceanography, office, Op_Number, operation, preliminary, seq, Seq_Number, stn, time, Time_Local";
    String license "https://www.bco-dmo.org/dataset/3895/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/3895";
    Float64 Northernmost_Northing 30.35938;
    String param_mapping "{'3895': {'Latitude': 'flag - latitude', 'Longitude': 'flag - longitude', 'ISO_DateTime_UTC': 'flag - time'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/3895/parameters";
    String people_0_affiliation "Georgia Institute of Technology";
    String people_0_affiliation_acronym "Georgia Tech";
    String people_0_person_name "Joseph P. Montoya";
    String people_0_person_nid "51125";
    String people_0_role "Principal Investigator";
    String people_0_role_type "originator";
    String people_1_affiliation "University of Texas at Austin";
    String people_1_affiliation_acronym "UT Austin";
    String people_1_person_name "Tracy A. Villareal";
    String people_1_person_nid "51591";
    String people_1_role "Co-Principal Investigator";
    String people_1_role_type "originator";
    String people_2_affiliation "Georgia Institute of Technology";
    String people_2_affiliation_acronym "Georgia Tech";
    String people_2_person_name "Joseph P. Montoya";
    String people_2_person_nid "51125";
    String people_2_role "Contact";
    String people_2_role_type "related";
    String people_3_affiliation "Woods Hole Oceanographic Institution";
    String people_3_affiliation_acronym "WHOI BCO-DMO";
    String people_3_person_name "Stephen R. Gegg";
    String people_3_person_nid "50910";
    String people_3_role "Data Manager";
    String people_3_role_type "related";
    String people_4_affiliation "Woods Hole Oceanographic Institution";
    String people_4_affiliation_acronym "WHOI BCO-DMO";
    String people_4_person_name "Stephen R. Gegg";
    String people_4_person_nid "50910";
    String people_4_role "BCO-DMO Data Manager";
    String people_4_role_type "related";
    String project "GoMX - N2 Fixation";
    String projects_0_acronym "GoMX - N2 Fixation";
    String projects_0_description 
"From the NSF proposal abstract
This project will study the interplay of physical, chemical, and biological factors in supplying nitrogen, an essential nutrient, to temperate coastal and offshore waters of the Gulf of Mexico. The Gulf is an economically important but understudied marginal sea with major commercial and recreational fisheries as well as extensive fossil fuel deposits. Diazotrophic (N2-fixing) cyanobacteria bloom regularly in offshore and coastal waters of the Gulf and the limited data suggest that they contribute significant quantities of both nitrogen and carbon to the pelagic food web. These diazotrophs may play also a critical role in supplying N to other organisms, including the ichthyotoxic red tide dinoflagellate Karenia brevis. Despite its importance, little is currently known of the factors that promote N2-fixation in the Gulf or the relative significance of different physical and biological processes in creating conditions that favor N limitation in the water column. The Gulf of Mexico is strongly influenced by both riverine inputs and advective processes, providing an excellent model system for studying nutrient dynamics, physical forcing of productivity, terrestrial-oceanic linkages, and the potential impact of land use and climate change on marine ecosystems.
The relatively small basin of the Gulf of Mexico provides an opportunity to quantify and study interactions among physical, chemical, and biological processes relevant to a broad range of other coastal and oceanic systems. Land-use and climate change are likely to affect the circulation and hydrography of the Gulf, as well as the magnitude and nature of riverine inputs, all with uncertain impacts on the biogeochemistry of the Gulf of Mexico. This research will provide timely insights into these processes and will generate a baseline of understanding for evaluating and predicting the impact of future land use and climate changes in the system. This project will make an important contribution to our understanding of the factors that regulate N2-fixation and its role in supporting the biota in temperate waters. The following specific goals are included in the work:
1. Identify the major diazotroph groups in the Gulf of Mexico and characterize their distribution and activity in different regions and water masses.
2. Quantify the impact of advective processes, mesoscale features, and riverine inputs on nutrient limitation and N2-fixation in the Gulf, and evaluate the controls on N2-fixation and the degree of spatial and temporal niche differentiation among diazotroph assemblages in different regions affected by these processes.
3. Use satellite data and physical models to scale up our measurements spatially and to evaluate the regional significance of N2-fixation in the Gulf of Mexico. The researchers will also use a coupled physical/biological model to explore variability in the physical forcing and the potential impact of likely land use and climate change scenarios in altering nutrient dynamics and N2-fixation in the Gulf of Mexico.
The investigators and their institutions have a strong commitment to undergraduate and graduate education. This project includes support for graduate students, a technician, and undergraduates. In addition to peer-reviewed papers and websites, workshops aimed at K-12 teachers, and a program involving high school teachers in research will be used to disseminate the results of this project broadly in the local community. The investigators are committed to increasing the diversity of the ocean science community and are active in recruiting and training efforts at their institutions.";
    String projects_0_end_date "2012-10";
    String projects_0_geolocation "Northern Gulf of Mexico";
    String projects_0_name "Nitrogen fixation, nutrient supply and biological production in the Gulf of Mexico";
    String projects_0_project_nid "2144";
    String projects_0_start_date "2009-10";
    String publisher_name "Biological and Chemical Oceanographic Data Management Office (BCO-DMO)";
    String publisher_type "institution";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 25.81505;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Event logs from R/V Oceanus, R/V Endeavor cruises OC468-02, EN496, EN509, EN510 in the Gulf of Mexico; 2010-2012 (GoMX - N2 Fixation project)";
    String time_coverage_start "1999-11-30T00:00:00Z";
    String title "Event logs from R/V Oceanus, R/V Endeavor cruises OC468-02, EN496, EN509, EN510 in the Gulf of Mexico; 2010-2012 (GoMX - N2 Fixation project)";
    String version "1";
    Float64 Westernmost_Easting -95.51763;
    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