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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  CTD data from R/V Oceanus cruise OC333 to Georges Bank in November, 1998 as
part of the U.S. GLOBEC Georges Bank project (GB project)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_2404)
Range: longitude = -66.70276 to -65.642044°E, latitude = 41.382336 to 42.323433°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 {
  cast {
    Byte _FillValue 127;
    Byte actual_range 1, 50;
    String bcodmo_name "cast";
    String description "cast number";
    String long_name "Cast";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 41.382337, 42.323433;
    String axis "Y";
    String bcodmo_name "latitude";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "latitude, negative = south";
    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 -66.702758, -65.642045;
    String axis "X";
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "longitude, negative = west";
    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 {
    Int16 _FillValue 32767;
    Int16 actual_range 6, 1064;
    String bcodmo_name "depth_w";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String description "water depth";
    String long_name "Depth";
    String standard_name "depth";
    String units "meters";
  }
  day_gmt {
    Byte _FillValue 127;
    Byte actual_range 16, 20;
    String bcodmo_name "day_gmt";
    String description "day of month";
    String long_name "Day Gmt";
    String units "GMT";
  }
  month_gmt {
    Byte _FillValue 127;
    Byte actual_range 11, 11;
    String bcodmo_name "month_gmt";
    String description "month of year";
    String long_name "Month Gmt";
    String units "GMT";
  }
  year {
    Int16 _FillValue 32767;
    Int16 actual_range 1998, 1998;
    String bcodmo_name "year";
    String description "year";
    String long_name "Year";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/YEARXXXX/";
    String units "GMT";
  }
  time_gmt {
    String bcodmo_name "time_gmt";
    String description "time, in hours and minutes";
    String long_name "Time Gmt";
    String units "GMT";
  }
  press {
    Float64 _FillValue NaN;
    Float64 actual_range 2.0, 913.0;
    String bcodmo_name "pressure";
    String description "pressure, depth of sample";
    String long_name "Press";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/PRESPR01/";
    String units "decibars";
  }
  temp {
    Float32 _FillValue NaN;
    Float32 actual_range 4.0836, 9.6553;
    String bcodmo_name "temperature";
    String description "water temperature";
    String long_name "Temperature";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/TEMPP901/";
    String units "degrees centigrade, ITS-90";
  }
  sal {
    Float32 _FillValue NaN;
    Float32 actual_range 30.6974, 35.0515;
    String bcodmo_name "sal";
    String description "salinity";
    String long_name "Sal";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/PSALST01/";
    String units "psu";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson";
    String acquisition_description "CTD Data from Mooring Cruise Oceanus 333.";
    String awards_0_award_nid "54610";
    String awards_0_award_number "unknown GB NSF";
    String awards_0_funder_name "National Science Foundation";
    String awards_0_funding_acronym "NSF";
    String awards_0_funding_source_nid "350";
    String awards_0_program_manager "David L. Garrison";
    String awards_0_program_manager_nid "50534";
    String awards_1_award_nid "54626";
    String awards_1_award_number "unknown GB NOAA";
    String awards_1_funder_name "National Oceanic and Atmospheric Administration";
    String awards_1_funding_acronym "NOAA";
    String awards_1_funding_source_nid "352";
    String cdm_data_type "Other";
    String comment "Output of simple_read.pl, v1.00/11Mar1999, using oc333001.cdn";
    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 "2010-03-18T17:29:37Z";
    String date_modified "2019-03-13T16:57:00Z";
    String defaultDataQuery "&time<now";
    String doi "10.1575/1912/bco-dmo.2404.1";
    Float64 Easternmost_Easting -65.642045;
    Float64 geospatial_lat_max 42.323433;
    Float64 geospatial_lat_min 41.382337;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -65.642045;
    Float64 geospatial_lon_min -66.702758;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-03-29T01:01:57Z (local files)
2024-03-29T01:01:57Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_2404.das";
    String infoUrl "https://www.bco-dmo.org/dataset/2404";
    String institution "BCO-DMO";
    String instruments_0_acronym "CTD SBE 911";
    String instruments_0_dataset_instrument_description "CTD measurements taken by a SBE911 (SeaBird) CTD instrument package.";
    String instruments_0_dataset_instrument_nid "4113";
    String instruments_0_description "The Sea-Bird SBE 911 is a type of CTD instrument package.  The SBE 911 includes the SBE 9 Underwater Unit and the SBE 11 Deck Unit (for real-time readout using conductive wire) for deployment from a vessel. The combination of the SBE 9 and SBE 11 is called a SBE 911.  The SBE 9 uses Sea-Bird's standard modular temperature and conductivity sensors (SBE 3 and SBE 4). The SBE 9 CTD can be configured with auxiliary sensors to measure other parameters including dissolved oxygen, pH, turbidity, fluorescence, light (PAR), light transmission, etc.). More information from Sea-Bird Electronics.";
    String instruments_0_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L22/current/TOOL0035/";
    String instruments_0_instrument_name "CTD Sea-Bird 911";
    String instruments_0_instrument_nid "422";
    String instruments_0_supplied_name "CTD Seabird 911";
    String keywords "altimetry, bco, bco-dmo, biological, cast, chemical, data, dataset, day, day_gmt, depth, depth_w, dmo, erddap, laboratory, latitude, longitude, management, month, month_gmt, oceanography, office, preliminary, press, sal, satellite, temperature, time, time_gmt, year";
    String license "https://www.bco-dmo.org/dataset/2404/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/2404";
    Float64 Northernmost_Northing 42.323433;
    String param_mapping "{'2404': {'lat': 'master - latitude', 'press': 'flag - depth', 'lon': 'master - longitude'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/2404/parameters";
    String people_0_affiliation "Woods Hole Oceanographic Institution";
    String people_0_affiliation_acronym "WHOI";
    String people_0_person_name "Dr Richard Limeburner";
    String people_0_person_nid "50423";
    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 "Ms Dicky Allison";
    String people_1_person_nid "50382";
    String people_1_role "BCO-DMO Data Manager";
    String people_1_role_type "related";
    String project "GB";
    String projects_0_acronym "GB";
    String projects_0_description 
"The U.S. GLOBEC Georges Bank Program is a large multi- disciplinary multi-year oceanographic effort. The proximate goal is to understand the population dynamics of key species on the Bank - Cod, Haddock, and two species of zooplankton (Calanus finmarchicus and Pseudocalanus) - in terms of their coupling to the physical environment and in terms of their predators and prey. The ultimate goal is to be able to predict changes in the distribution and abundance of these species as a result of changes in their physical and biotic environment as well as to anticipate how their populations might respond to climate change.
The effort is substantial, requiring broad-scale surveys of the entire Bank, and process studies which focus both on the links between the target species and their physical environment, and the determination of fundamental aspects of these species' life history (birth rates, growth rates, death rates, etc).
Equally important are the modelling efforts that are ongoing which seek to provide realistic predictions of the flow field and which utilize the life history information to produce an integrated view of the dynamics of the populations.
The U.S. GLOBEC Georges Bank Executive Committee (EXCO) provides program leadership and effective communication with the funding agencies.";
    String projects_0_geolocation "Georges Bank, Gulf of Maine, Northwest Atlantic Ocean";
    String projects_0_name "U.S. GLOBEC Georges Bank";
    String projects_0_project_nid "2037";
    String projects_0_project_website "http://globec.whoi.edu/globec_program.html";
    String projects_0_start_date "1991-01";
    String publisher_name "Biological and Chemical Oceanographic Data Management Office (BCO-DMO)";
    String publisher_type "institution";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 41.382337;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "month_gmt,year";
    String summary "CTD data from R/V Oceanus cruise OC333 to Georges Bank in November, 1998 as part of the U.S. GLOBEC Georges Bank project";
    String title "CTD data from R/V Oceanus cruise OC333 to Georges Bank in November, 1998 as part of the U.S. GLOBEC Georges Bank project (GB project)";
    String version "1";
    Float64 Westernmost_Easting -66.702758;
    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