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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Water temperature data from stable isotope labeling experiments conducted from
2012. Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_669630)
Range: time = 2013-06-23T08:18:00Z to 2013-10-16T11:15:00Z
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: 
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 ? )
   
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 {
  month {
    Byte _FillValue 127;
    Byte actual_range 6, 10;
    String bcodmo_name "month";
    String description "Month of sampling; mm";
    String long_name "Month";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/MNTHXXXX/";
    String units "unitless";
  }
  date {
    String bcodmo_name "date";
    String description "Date of sampling; mm/dd/yy";
    String long_name "Date";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/ADATAA01/";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.37197548e+9, 1.3819221e+9;
    String axis "T";
    String bcodmo_name "ISO_DateTime_UTC";
    String description "Date/Time (UTC) ISO formatted";
    String ioos_category "Time";
    String long_name "ISO Date Time UTC";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/DTUT8601/";
    String source_name "ISO_DateTime_UTC";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  time2 {
    String bcodmo_name "time";
    String description "Time of sampling; HH:MM";
    String long_name "Time";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/AHMSAA01/";
    String units "unitless";
  }
  sampleID {
    String bcodmo_name "sample";
    String description "ID refers to the unique combination of month; creek; core replicate number";
    String long_name "Sample ID";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P02/current/ACYC/";
    String units "unitless";
  }
  bucket {
    String bcodmo_name "sample";
    String description "Sampling bucket ID";
    String long_name "Bucket";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P02/current/ACYC/";
    String units "unitless";
  }
  temp {
    Float32 _FillValue NaN;
    Float32 actual_range 12.4, 31.57;
    String bcodmo_name "temperature";
    String description "Temperature was recorded in a subset of sediment cores during each stable isotope labeling experiment";
    String long_name "Temperature";
    String units "celsius";
  }
  lntemp {
    Float32 _FillValue NaN;
    Float32 actual_range 2.52, 3.45;
    String bcodmo_name "temperature";
    String description "Natural log of temperature; temperature was recorded in a subset of sediment cores during each stable isotope labeling experiment";
    String long_name "Lntemp";
    String units "celsius";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv";
    String acquisition_description 
"Water temperature (deg C) was measured in a subset of cores with Onset HOBO
pendant loggers (UA-002-64).\\u00a0";
    String awards_0_award_nid "529582";
    String awards_0_award_number "OCE-1233678";
    String awards_0_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=1233678";
    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 
"Temperature Data 
  Amanda Spivak, PI 
  Version 8 December 2016";
    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 "2016-12-09T21:53:10Z";
    String date_modified "2019-04-09T16:12:43Z";
    String defaultDataQuery "&amp;time&lt;now";
    String doi "10.1575/1912/bco-dmo.669630.1";
    String history 
"2024-04-19T14:16:08Z (local files)
2024-04-19T14:16:08Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_669630.das";
    String infoUrl "https://www.bco-dmo.org/dataset/669630";
    String institution "BCO-DMO";
    String instruments_0_dataset_instrument_description "Used to collect core samples";
    String instruments_0_dataset_instrument_nid "669642";
    String instruments_0_description 
"Capable of being performed in numerous environments, push coring is just as it sounds. Push coring is simply pushing the core barrel (often an aluminum or polycarbonate tube) into the sediment by hand. A push core is useful in that it causes very little disturbance to the more delicate upper layers of a sub-aqueous sediment.

Description obtained from: http://web.whoi.edu/coastal-group/about/how-we-work/field-methods/coring/";
    String instruments_0_instrument_name "Push Corer";
    String instruments_0_instrument_nid "628287";
    String instruments_0_supplied_name "Core";
    String instruments_1_dataset_instrument_description "Used to measure temperature in cores";
    String instruments_1_dataset_instrument_nid "669643";
    String instruments_1_description "Records temperature data over a period of time.";
    String instruments_1_instrument_name "Temperature Logger";
    String instruments_1_instrument_nid "639396";
    String instruments_1_supplied_name "Onset HOBO pendant loggers";
    String keywords "bco, bco-dmo, biological, bucket, chemical, data, dataset, date, dmo, erddap, iso, lntemp, management, month, oceanography, office, preliminary, sample, sampleID, temperature, time, time2";
    String license "https://www.bco-dmo.org/dataset/669630/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/669630";
    String param_mapping "{'669630': {'ISO_DateTime_UTC': 'flag - time'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/669630/parameters";
    String people_0_affiliation "Woods Hole Oceanographic Institution";
    String people_0_affiliation_acronym "WHOI";
    String people_0_person_name "Amanda Spivak";
    String people_0_person_nid "529580";
    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 "Hannah Ake";
    String people_1_person_nid "650173";
    String people_1_role "BCO-DMO Data Manager";
    String people_1_role_type "related";
    String project "benthic_PP_at_TIDE";
    String projects_0_acronym "benthic_PP_at_TIDE";
    String projects_0_description 
"Extracted from the NSF award abstract:
This project will address how rates of benthic microalgal production respond to eutrophication and geomorphological changes in human-impacted tidal creeks. Excess nutrient loading increases benthic algal biomass and likely stimulates production rates but the magnitude of nutrient and geomorphological effects on rates of production is unknown. Will changes in benthic algal productivity affect algal-bacterial coupling? Furthermore, how is algal-bacterial coupling affected by geomorphological changes, which may be exacerbated by excess nutrient loading but can also occur in pristine marshes?
This project will take advantage of the infrastructure of the TIDE project, a long-term saltmarsh eutrophication experiment at the Plum Island Ecosystem - Long Term Ecological Research site in Northeastern Massachusetts. Specifically, the PIs will measure benthic metabolism and examine algal- bacterial coupling in fertilized and ambient nutrient tidal creeks in the first field season. The following field season, they will compare sediment metabolism and carbon dynamics on slumped tidal creek walls (i.e. areas where low marsh has collapsed into the tidal creek) to that on the bottom of tidal creeks. In both years, gross and net production will be determined using an innovative triple oxygen isotope technique and traditional dissolved oxygen and inorganic carbon flux measurements. Comparisons between these methods will be useful in informing studies of sediment metabolism. Lipid biomarkers will be used to characterize the sources of organic matter to creek sediments, and stable isotope analysis of bacterial specific biomarkers to identify the sources of organic carbon utilized by sediment bacteria. The biomarkers will reveal whether sediment bacteria use organic matter substrates, such as benthic microalgal carbon, selectively or in proportion to availability. Overall, results from the proposed study will provide important information about how sediment carbon dynamics in shallow tidal creeks respond to long term eutrophication. Furthermore, findings will enhance understanding of the role of tidal creeks in coastal biogeochemistry.";
    String projects_0_end_date "2015-08";
    String projects_0_geolocation "Plum Island Estuary, Rowley Massachusetts";
    String projects_0_name "Eutrophication Effects on Sediment Metabolism and Benthic Algal-bacterial Coupling: An Application of Novel Techniques in a LTER Estuary";
    String projects_0_project_nid "529583";
    String projects_0_start_date "2012-09";
    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 summary "Water temperature data from stable isotope labeling experiments conducted from 2012.";
    String time_coverage_end "2013-10-16T11:15:00Z";
    String time_coverage_start "2013-06-23T08:18:00Z";
    String title "Water temperature data from stable isotope labeling experiments conducted from 2012.";
    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