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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Seabird Survey Observations from RVIB Nathaniel B. Palmer during cruises
NBP0103, NBP0104, NBP0202, and NBP0204 in the Southern Ocean from 2001-
2002 (SOGLOBEC project)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_2353)
Range: longitude = -77.4454 to -67.6244°E, latitude = -69.4975 to -65.6515°N
Information:  Summary ? | License ? | ISO 19115 | Metadata | Background (external link) | Data Access Form | Files
Graph Type:  ?
X Axis: 
Y Axis: 
Constraints ? Optional
Constraint #1 ?
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 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.)
Then set the File Type: (File Type information)
or view the URL:
(Documentation / Bypass this form ? )
    Click on the map to specify a new center point. ?
[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 identification";
    String long_name "Cruiseid";
  year {
    Int16 _FillValue 32767;
    Int16 actual_range 2001, 2002;
    String bcodmo_name "year";
    String description "year, i.e. 2001";
    String long_name "Year";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/YEARXXXX/";
  yrday_gmt {
    Float64 _FillValue NaN;
    Float64 actual_range 104.498, 252.894;
    String bcodmo_name "yrday_gmt";
    String description "year day, GMT, i.e, 119";
    String long_name "Yrday Gmt";
    String units "whole day";
  time_gmt {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 2358;
    String bcodmo_name "time_gmt";
    String description "time of day, GMT, 24 hour clock.";
    String long_name "Time Gmt";
    String units "HHmm.m";
  date_gmt {
    String bcodmo_name "date_utc";
    String description "observation date formatted as mondd-yyyy; UTC";
    String long_name "Date Gmt";
    String units "unitless";
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range -69.4975, -65.6515;
    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";
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -77.4454, -67.6244;
    String axis "X";
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "longitude; east is positivie";
    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_of_day {
    String bcodmo_name "time_of_day";
    String description "reference to day or night observations; D=day, N=night";
    String long_name "Time Of Day";
  species {
    String bcodmo_name "species";
    String description "species name, as a code, see species code table.";
    String long_name "Species";
  number {
    Byte _FillValue 127;
    Byte actual_range 1, 80;
    String bcodmo_name "number";
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String description "number of organisms counted per species per observation";
    String long_name "Number";
    String units "n/observation";
  flight_dir {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 355;
    String bcodmo_name "flight_dir";
    String description "direction bird(s) are flying toward, in degrees relative to ship";
    String long_name "Flight Dir";
    String units "degrees";
  behav_code {
    Byte _FillValue 127;
    Byte actual_range 0, 8;
    String bcodmo_name "behav_code";
    String description "behavior of organism(s) at time of sighting, as a code, see behavior code table.";
    String long_name "Behav Code";
  transect_code {
    Byte _FillValue 127;
    Byte actual_range 0, 9;
    String bcodmo_name "transect_code";
    String description "specifies observational methods during transect, as a code, see transect code table.";
    String long_name "Transect Code";
  comments {
    String bcodmo_name "comment";
    String description "general comments to include features associated with sighting.";
    String long_name "Comments";
  association {
    String bcodmo_name "comment";
    String description "environmental features associated with sighting";
    String long_name "Association";
    String units "unitless";
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson";
    String acquisition_description 
"Seabird abundance and distribution within the SO GLOBEC study area was
investigated using daytime and nighttime (using night vision viewers) survey
work. We also recorded seal observations made within the transect area.
Nighttime surveys were designed to complement daytime surveys.
Seabird Daytime Surveys  
 Strip transects were conducted simultaneously at 300 m and 600 m widths for
birds. Surveys were conducted continuously while the ship was underway within
the study area and when visibility was >300 m. For strip transects, two
observers continuously scanned a 90\\u00ef\\u00bf\\u00bd area extending the
transect distance (300 m and 600 m) to the side and forward along the transect
line. Binoculars of 10X and 7X magnification were used to confirm species
identifications. The 7X pair of binoculars also included a laser range finder.
Ship followers and bird observed to be attracted to the ship were noted at
first occurrence. These observations will be down-weighted in the analyses
because these individuals may have been attracted to the ship from habitats at
a distance from the ship. For each sighting, transect (300 m or 600 m),
species, number of birds, behavior, flight direction, and any association with
visible physical features, such as ice, were recorded. Distances were measured
either by a range finder device as suggested by Heinemann (1981) or by the
laser distance finder (when in the ice). Marine mammal sightings within the
transect were also recorded.
Surveys were conducted from an outside observation post located on the port
bridge wing of the RVIB N.B. Palmer. When it was not feasible to conduct
surveys from this observation post, we surveyed from the inside port bridge
Seabird Nighttime Surveys  
 ITT 200/210 Binocular Night Vision Viewers were used during one half-hour
survey periods while on the survey grid. Surveys were a minimum of an hour
apart. Observations were made from the bridge wing during NBP0104 and outside,
from a dark area on the 01 deck, during NBP0103. Observers scanned back and
forth looking for birds. Species and behavior of the bird was recorded for
each observation. Observations were not conducted when visibility with the
night vision viewer was less than 100 m from the ship.";
    String awards_0_award_nid "54715";
    String awards_0_award_number "ANT-9910096";
    String awards_0_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=9910096";
    String awards_0_funder_name "NSF Antarctic Sciences";
    String awards_0_funding_acronym "NSF ANT";
    String awards_0_funding_source_nid "369";
    String awards_0_program_manager "Dr Polly  A Penhale";
    String awards_0_program_manager_nid "51478";
    String cdm_data_type "Other";
    String comment 
"Observations of Birds  
  Chris Ribic and Erik Chapman, PIs 
   Notes: N = Night;  D = Day; 
    Flight_dir = Degrees relative to ship. (Ship's heading available from alongtrack data: https://www.bco-dmo.org/dataset/2345 
    Behavior_code = see documentation 
    Transect = see documentation 
    Association = those environmental features associated with sighting. 
 For an explanation of the species code, see landing page https://www.bco-dmo.org/dataset/2353";
    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-06-16T20:40:39Z";
    String date_modified "2020-01-29T19:39:28Z";
    String defaultDataQuery "&time<now";
    String doi "10.1575/1912/bco-dmo.2353.1";
    Float64 Easternmost_Easting -67.6244;
    Float64 geospatial_lat_max -65.6515;
    Float64 geospatial_lat_min -69.4975;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -67.6244;
    Float64 geospatial_lon_min -77.4454;
    String geospatial_lon_units "degrees_east";
    String history 
"2022-08-10T23:59:07Z (local files)
2022-08-10T23:59:07Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_2353.das";
    String infoUrl "https://www.bco-dmo.org/dataset/2353";
    String institution "BCO-DMO";
    String keywords "association, bco, bco-dmo, behav, behav_code, biological, chemical, code, comments, cruiseid, data, dataset, date, date_gmt, day, dir, dmo, erddap, flight, flight_dir, latitude, longitude, management, number, oceanography, office, preliminary, species, time, time_gmt, time_of_day, transect, transect_code, year, yrday, yrday_gmt";
    String license "https://www.bco-dmo.org/dataset/2353/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/2353";
    Float64 Northernmost_Northing -65.6515;
    String param_mapping "{'2353': {'lat': 'master - latitude', 'lon': 'master - longitude'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/2353/parameters";
    String people_0_affiliation "Old Dominion University";
    String people_0_affiliation_acronym "ODU";
    String people_0_person_name "Dr Erik Chapman";
    String people_0_person_nid "50503";
    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 "SOGLOBEC";
    String projects_0_acronym "SOGLOBEC";
    String projects_0_description "The fundamental objectives of United States Global Ocean Ecosystems Dynamics (U.S. GLOBEC) Program are dependent upon the cooperation of scientists from several disciplines. Physicists, biologists, and chemists must make use of data collected during U.S. GLOBEC field programs to further our understanding of the interplay of physics, biology, and chemistry. Our objectives require quantitative analysis of interdisciplinary data sets and, therefore, data must be exchanged between researchers. To extract the full scientific value, data must be made available to the scientific community on a timely basis.";
    String projects_0_geolocation "Southern Ocean";
    String projects_0_name "U.S. GLOBEC Southern Ocean";
    String projects_0_project_nid "2039";
    String projects_0_project_website "http://www.ccpo.odu.edu/Research/globec_menu.html";
    String projects_0_start_date "2001-01";
    String publisher_name "Biological and Chemical Oceanographic Data Management Office (BCO-DMO)";
    String publisher_type "institution";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -69.4975;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Seabird Survey Observations from RVIB Nathaniel B. Palmer during cruises NBP0103, NBP0104, NBP0202, and NBP0204 in the Southern Ocean from 2001-2002 (SOGLOBEC project)";
    String title "Seabird Survey Observations from RVIB Nathaniel B. Palmer during cruises NBP0103, NBP0104, NBP0202, and NBP0204 in the Southern Ocean from 2001-2002 (SOGLOBEC project)";
    String version "1";
    Float64 Westernmost_Easting -77.4454;
    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
For example,
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