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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Thermistor data at 10 cm intervals in air, ice, water from autonomous buoys
from ARSV Laurence M. Gould LMG0106 in the Southern Ocean, August to November,
2001 (SOGLOBEC project)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_3115)
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: 
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 ? )
    [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 {
  therm_pos {
    Byte _FillValue 127;
    Byte actual_range -100, 60;
    String bcodmo_name "unknown";
    String description "height of thermistor relative to ice.  Positive values are above the ice; negative values are in the ice and underlying ocean.";
    String long_name "Therm Pos";
    String units "centimeters";
  }
  yrday_gmt {
    Float32 _FillValue NaN;
    Float32 actual_range 218.5, 314.25;
    String bcodmo_name "yrday_gmt";
    String description "GMT day and decimal time, as 326.5 for the 326th day of the year, or November 22 at 1200 hours (noon)";
    String long_name "Yrday Gmt";
  }
  date_gmt {
    String bcodmo_name "date_gmt";
    String description "gmt month, day and year, usually as a text string, e.g. feb10_1995.";
    String long_name "Date Gmt";
    String source_name "date_gmt";
    String time_precision "1970-01-01";
  }
  year {
    Int16 _FillValue 32767;
    Int16 actual_range 2001, 2001;
    String bcodmo_name "year";
    String description "year, reported as YYYY, e.g. 1995";
    String long_name "Year";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/YEARXXXX/";
  }
  month_gmt {
    String bcodmo_name "month_gmt";
    String description "month of year, GMT time , i.e. 01-12";
    String long_name "Month Gmt";
  }
  day_gmt {
    String bcodmo_name "day_gmt";
    String description "day, GMT time e.g. 22.";
    String long_name "Day Gmt";
  }
  time_gmt {
    String bcodmo_name "time_gmt";
    String description "time of day, reported in GMT time, 24 hour clock";
    String long_name "Time Gmt";
  }
  temp {
    String bcodmo_name "temperature";
    String description "temperature at measurement depth";
    String long_name "Temperature";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/TEMPP901/";
    String units "degrees Celsius";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv";
    String acquisition_description 
"During the July-September 2001 Southern Globec cruises of the Palmer and Gould
we installed four buoys. Two of the buoys (07413, 07440) were standard off-
the-shelf Met-Ocean Ice buoys (see above photograph). These buoys measured
barometric pressure, air temperature, and GPS position. The data were
transmitted via ARGOS. A radar reflector was mounted on a wooden 4 x 4 to help
find the site if there was an opportunity to return, however the reflector
return was difficult to discern among all the backscatter clutter caused by
deformed ice and icebergs.
 
The other two buoys (07949, 07950) were custom made CRREL ice mass balance
buoys (photo on right). These buoys reported barometric pressure, Argos
position, and air temperature. In addition they had a thermistor string that
measured a vertical profile of temperature, at 10 cm spacing, from the air,
through the snow and ice, and into the upper ocean. There were acoustic
sensors measuring the positions of the snow surface and ice bottom. A
fluorometer was mounted under the ice. One of the buoys (07949) had three
spectroradiometers; one mounted about the ice, one mounted directly below the
ice, and one a few meters deep in the upper ocean. Results from all buoys are
compared.
 
 Positive values are above the ice; negative values are in the ice and
underlying ocean. Due to surface flooding and freezing, the position of the
snow-ice interface changed during the measurement period.  
 \\u00a0
 
Tracks from all 2001 buoys:";
    String awards_0_award_nid "54617";
    String awards_0_award_number "unknown SOGLOBEC NSF ANT";
    String awards_0_funder_name "NSF Antarctic Sciences";
    String awards_0_funding_acronym "NSF ANT";
    String awards_0_funding_source_nid "369";
    String cdm_data_type "Other";
    String comment 
"Thermistor temps at 10 cm intervals in air, ice, water from autonomous buoys 
  PI: C. Fristen 
  
     Thermistor position (cm) is at installation.  
     Positive values are above the ice;  
        negative values are in the ice and underlying ocean. 
     Due to surface flooding and freezing the position of  
        the snow-ice interfacechanged during the measurement period. 
  
  data version 2: 31 Dec 2004";
    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-22T14:28:01Z";
    String defaultDataQuery "&time<now";
    String doi "10.1575/1912/bco-dmo.3115.1";
    String history 
"2024-04-19T07:04:10Z (local files)
2024-04-19T07:04:10Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_3115.das";
    String infoUrl "https://www.bco-dmo.org/dataset/3115";
    String institution "BCO-DMO";
    String instruments_0_acronym "BDFT";
    String instruments_0_dataset_instrument_description "4 buoys in ice";
    String instruments_0_dataset_instrument_nid "4867";
    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 "bco, bco-dmo, biological, chemical, data, dataset, date, day, day_gmt, dmo, erddap, management, month, month_gmt, oceanography, office, pos, preliminary, temperature, therm, therm_pos, time, time_gmt, year, yrday, yrday_gmt";
    String license "https://www.bco-dmo.org/dataset/3115/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/3115";
    String param_mapping "{'3115': {}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/3115/parameters";
    String people_0_affiliation "University of California-Santa Cruz";
    String people_0_affiliation_acronym "UC Santa Cruz";
    String people_0_person_name "Daniel P. Costa";
    String people_0_person_nid "50488";
    String people_0_role "Principal Investigator";
    String people_0_role_type "originator";
    String people_1_affiliation "Desert Research Institute";
    String people_1_affiliation_acronym "DRI";
    String people_1_person_name "Dr Chris H. Fritsen";
    String people_1_person_nid "50502";
    String people_1_role "Co-Principal Investigator";
    String people_1_role_type "originator";
    String people_2_affiliation "Woods Hole Oceanographic Institution";
    String people_2_affiliation_acronym "WHOI BCO-DMO";
    String people_2_person_name "Nancy Copley";
    String people_2_person_nid "50396";
    String people_2_role "BCO-DMO Data Manager";
    String people_2_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)";
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "year";
    String summary "Thermistor data at 10 cm intervals in air, ice, water from autonomous buoys from ARSV Laurence M. Gould LMG0106 in the Southern Ocean, August to November, 2001 for the Southern Ocean GLOBEC project.";
    String title "Thermistor data at 10 cm intervals in air, ice, water from autonomous buoys from ARSV Laurence M. Gould LMG0106 in the Southern Ocean, August to November, 2001 (SOGLOBEC project)";
    String version "1";
    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