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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [drifter_start_positions] - Initial drifter deployment positions from R/V
Endeavor, R/V Albatross IV, R/V Oceanus, R/V Delaware, R/V Cape Hatteras, CCGS
Cygnus, and R/V Parizeau in the Gulf of Maine and Georges Bank from 1995-
1999 (U.S. GLOBEC Georges Bank)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_2305)
Range: longitude = -70.64293 to -62.383°E, latitude = 40.23 to 43.612°N
Information:  Summary ? | License ? | FGDC | 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: 
[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 {
  year {
    Int16 _FillValue 32767;
    Int16 actual_range 1995, 1999;
    String bcodmo_name "year";
    String description "Year the drifter was initially deployed (GMT). Format: yyyy";
    String long_name "Year";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/YEARXXXX/";
    String units "unitless";
  }
  drifterid {
    String bcodmo_name "drifterid";
    String description "GLOBEC drifter identification number 1.";
    String long_name "Drifterid";
    String units "dimensionless";
  }
  argosid {
    Int16 _FillValue 32767;
    Int16 actual_range 3012, 24976;
    String bcodmo_name "argosid";
    String description "ARGOS drifter identification number.";
    String long_name "Argosid";
    String units "dimensionless";
  }
  cruiseid {
    String bcodmo_name "cruiseid";
    String description "Identifier of the cruise on which the drifter was deployed.";
    String long_name "Cruiseid";
    String units "dimensionless";
  }
  month_gmt {
    String bcodmo_name "month_gmt";
    String description "Month of year, GMT, of initial deployment.";
    String long_name "Month Gmt";
    String units "month (1-12), MM";
  }
  day_gmt {
    String bcodmo_name "day_gmt";
    String description "Day of month of initial deployment, GMT.";
    String long_name "Day Gmt";
    String units "day (1-31), dd";
  }
  time_gmt {
    String bcodmo_name "time_gmt";
    String description "Time of deployment, GMT.";
    String long_name "Time Gmt";
    String units "HHmm";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 40.23, 43.612;
    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 -70.64293, -62.383;
    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";
  }
  status {
    String bcodmo_name "status";
    String description "Drifter deployment status (e.g.  new).";
    String long_name "Status";
    String units "dimensionless";
  }
  inst {
    String bcodmo_name "instrument";
    String description "Drifter deployment type2 (i.e.  drogued at 10 or 40 meters)";
    String long_name "Inst";
    String units "dimensionless";
  }
  comments {
    String bcodmo_name "comment";
    String description "Comments pertaining to a specific drifter deployment.";
    String long_name "Comments";
    String units "dimensionless";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson";
    String acquisition_description 
"Satellite-tracked drifters with holey sock drogues centered at 10, 15 and 40-m
depths were deployed over Georges Bank during 1995-99 in support of the U.S.
GLOBEC/Georges Bank Program. Some drifters were deployed in regions of strong
vertical shear over the Bank and these drifters had a drogue that was twice as
wide and half as long as the standard drogue and are designated as having
\\u2018wide\\u2019 drogues (see note 2 above). Drifter types containing a gps
system reported positions every 30 minutes.";
    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 
"Initial Drifter deployment positions 
 GLOBEC Georges Bank, 1995-1999 
  Contributer: Richard Limeburner (WHOI) 
  DMO corrected cruiseid for the following: g31, g47, g84, g85, 
   g98, g99, g140, g142, g157 to g159, n6 to n10 (see metadata).";
    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 "2009-11-25T13:13:55Z";
    String date_modified "2019-02-11T15:09:24Z";
    String defaultDataQuery "&time<now";
    String doi "10.1575/1912/bco-dmo.2305.1";
    Float64 Easternmost_Easting -62.383;
    Float64 geospatial_lat_max 43.612;
    Float64 geospatial_lat_min 40.23;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -62.383;
    Float64 geospatial_lon_min -70.64293;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-08T06:04:54Z (local files)
2024-11-08T06:04:54Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_2305.das";
    String infoUrl "https://www.bco-dmo.org/dataset/2305";
    String institution "BCO-DMO";
    String instruments_0_acronym "BDFT";
    String instruments_0_dataset_instrument_description "Satellite-tracked drifters with holey sock drogues centered at 10, 15 and 40-m depths were deployed over Georges Bank during 1995-99. The GLOBEC Georges Bank drifters were made by Clearwater (CW), Seimac (SE), Technocean (TE), and MEtocean (ME).";
    String instruments_0_dataset_instrument_nid "5626";
    String instruments_0_description "Drifter buoy to include the Beardsley Drifter.  Generic drifter buoys may be surface or sub-surface buoys that move with the current.  They have a variety of instruments attached, providing a platform that allows for the measurement of surface drifts, air pressure and other variables.  The Beardsley Drifters  are near-surface satellite-tracked drifters used for observations of circulation patterns.  They are WOCE-style drifters featuring holey sock drogues. Each drifter has a small (~ 30 cm diameter) surface float with ARGOS transmitter and batteries tethered to a holey sock drogue centered at 15 m below the surface. The drogue, about 10 m tall and 1 m in diameter, is designed to \"lock\" itself to the water so that the surface float follows the mean water motion at 15 m depth with very little slippage even in high winds. Thus measuring the drifter's position as a function of time provides a Lagrangian measurement of the 15-m ocean current. (http://globec.whoi.edu/jg/info/globec/soglobec/drifters_argos%7Bdir=globec.whoi.edu/jg/dir/globec/soglobec/,data=globec.whoi.edu:80/jg/serv/globec/soglobec/drifters_argos.html1%7D?)   WOCE-drifters: https://www.nodc.noaa.gov/woce/woce_v3/wocedata_1/diu_summaries/svp/index.htm";
    String instruments_0_instrument_name "Drifter Buoy";
    String instruments_0_instrument_nid "424";
    String instruments_0_supplied_name "Drifter Buoy";
    String keywords "argosid, bco, bco-dmo, biological, chemical, comments, cruiseid, data, dataset, day, day_gmt, dmo, drifterid, erddap, inst, latitude, longitude, management, month, month_gmt, oceanography, office, preliminary, status, time, time_gmt, year";
    String license "https://www.bco-dmo.org/dataset/2305/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/2305";
    Float64 Northernmost_Northing 43.612;
    String param_mapping "{'2305': {'lat': 'master - latitude', 'lon': 'master - longitude'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/2305/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 people_2_affiliation "Woods Hole Oceanographic Institution";
    String people_2_affiliation_acronym "WHOI BCO-DMO";
    String people_2_person_name "Robert C. Groman";
    String people_2_person_nid "50380";
    String people_2_role "BCO-DMO Data Manager";
    String people_2_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 40.23;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Initial positions of drifters deployed from 1995 to 1999 in support of the U.S. GLOBEC Georges Bank program.";
    String title "[drifter_start_positions] - Initial drifter deployment positions from R/V Endeavor, R/V Albatross IV, R/V Oceanus, R/V Delaware, R/V Cape Hatteras, CCGS Cygnus, and R/V Parizeau in the Gulf of Maine and Georges Bank from 1995-1999 (U.S. GLOBEC Georges Bank)";
    String version "1";
    Float64 Westernmost_Easting -70.64293;
    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