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

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [Mumford Cove Monitoring Data] - Temperature, pH, DO, and salinity data from
Mumford Cove, Connecticut, USA from 2015-2022 (Collaborative research:
Understanding the effects of acidification and hypoxia within and across
generations in a coastal marine fish)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_659874_v3)
Information:  Summary ? | License ? | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 location (unitless) ?          "Mumford Cove"    "Mumford Cove"
 lat (degrees_north) ?          41.0    41.32526
 lon (degrees_east) ?          -72.02088    -72.02088
 serial_number (unitless) ?          3151818    31522273
 ISO_DateTime_EST (unitless) ?          "2015-04-14T14:30"    "2022-12-09T13:00"
 temp (degrees Celsius) ?          -1.73    29.02
 pH (pH units) ?          7.130521    9.469908
 cond (microsiemens per centimeter (µS/cm)) ?          9613    100800
 HDO_mgl (milligrams per liter (mg/L)) ?          0.0    21.03
 HDO_percentSat (percent) ?          0.0    214.2
 salinity (PSS) ?          11.48455    35.83
 depth (m) ?          0.83    4.25
  < slider >
 ISO_DateTime_UTC (unitless) ?          "2015-04-14T18:30Z"    "2022-12-09T18:00Z"
 comments (unitless) ?          "(0.51+0.4+0.63)/3=..."    "temp/cond/salinity..."
 
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.Hover here to see a list of options. Click on an option to select it.")

File type: (more information)

(Documentation / Bypass this form ? )
 
(Please be patient. It may take a while to get the data.)


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  location {
    String long_name "Location";
    String units "unitless";
  }
  lat {
    Float32 actual_range 41.0, 41.32526;
    String long_name "Lat";
    String units "degrees_north";
  }
  lon {
    Float32 actual_range -72.02088, -72.02088;
    String long_name "Lon";
    String units "degrees_east";
  }
  serial_number {
    Int32 actual_range 3151818, 31522273;
    String long_name "Serial_number";
    String units "unitless";
  }
  ISO_DateTime_EST {
    String long_name "Iso_datetime_est";
    String units "unitless";
  }
  temp {
    Float32 actual_range -1.73, 29.02;
    String long_name "Temp";
    String units "degrees Celsius";
  }
  pH {
    Float32 actual_range 7.130521, 9.469908;
    String long_name "Ph";
    String units "pH units";
  }
  cond {
    Int32 actual_range 9613, 100800;
    String long_name "Cond";
    String units "microsiemens per centimeter (µS/cm)";
  }
  HDO_mgl {
    Float32 actual_range 0.0, 21.03;
    String long_name "Hdo_mgl";
    String units "milligrams per liter (mg/L)";
  }
  HDO_percentSat {
    Float32 actual_range 0.0, 214.2;
    String long_name "Hdo_percentsat";
    String units "percent";
  }
  salinity {
    Float32 actual_range 11.48455, 35.83;
    String long_name "Salinity";
    String units "PSS";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 0.83, 4.25;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  ISO_DateTime_UTC {
    String long_name "Iso_datetime_utc";
    String units "unitless";
  }
  comments {
    String long_name "Comments";
    String units "unitless";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_url "https://www.bco-dmo.org/";
    String doi "10.26008/1912/bco-dmo.659874.3";
    Float64 geospatial_vertical_max 4.25;
    Float64 geospatial_vertical_min 0.83;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-12-21T16:12:31Z (local files)
2024-12-21T16:12:31Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_659874_v3.html";
    String infoUrl "https://www.bco-dmo.org/dataset/659874";
    String institution "BCO-DMO";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    String sourceUrl "(local files)";
    String summary "Despite their importance for research and environmental protection, there's still a shortage of high quality and high-resolution temperature, pH, and oxygen data particularly in shallow coastal habitats. We monitor five important environmental parameters (i.e., depth, temperature, salinity, pH, and dissolved oxygen) at 30 minute intervals in Mumford Cove, CT (41 degrees 19'25\"N, 72 degrees 01'07\"W), a small (2 km N-S × 0.5 km E-W), shallow (1-5 meters), cone-shaped embayment opening to northeastern Long Island Sound, with protected marsh habitat along its western side, marsh and beach habitat along its eastern side, and an extensive seagrass (Zostera marina) cover. Continuous monitoring is achieved by swapping identical and recalibrated probes (Eureka Manta Sub2) every 3-5 weeks.";
    String title "[Mumford Cove Monitoring Data] - Temperature, pH, DO, and salinity data from Mumford Cove, Connecticut, USA from 2015-2022 (Collaborative research: Understanding the effects of acidification and hypoxia within and across generations in a coastal marine fish)";
  }
}

 

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