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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Salt pond monitoring] - Continuously monitored water quality measurements
from five salt marsh ponds in New Jersey, USA from Apr 2023 to Jun
2024 (Sediment transport and water quality in watersheds and coastlines of the
United States)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_988873_v1)
Range: longitude = -74.80179 to -74.74948°E, latitude = 39.0438 to 39.08802°N, depth = 0.004 to 0.1m
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: 
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 {
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String ioos_category "Time";
    String long_name "Datetime_utc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  site {
    String long_name "Site";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 39.0438, 39.08802;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -74.80179, -74.74948;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 0.004, 0.1;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  salinity {
    Float32 actual_range 22.6, 36.2;
    String long_name "Salinity";
    String units "unitless";
  }
  temperature {
    Float32 actual_range -1.77, 36.37;
    String long_name "Temperature";
    String units "degrees Celsius";
  }
  DOconc {
    Float32 actual_range 0.0, 748.5;
    String long_name "Doconc";
    String units "μmol/kg";
  }
  DOeqsat {
    Float32 actual_range 180.0, 379.6;
    String long_name "Doeqsat";
    String units "μmol/kg";
  }
  DOsat {
    Float32 actual_range 0.0, 329.5;
    String long_name "Dosat";
    String units "percent";
  }
  pH {
    Float32 actual_range 6.4, 9.5;
    String long_name "Ph";
    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 defaultDataQuery "&time<now";
    String doi "10.26008/1912/bco-dmo.988873.1";
    Float64 Easternmost_Easting -74.74948;
    Float64 geospatial_lat_max 39.08802;
    Float64 geospatial_lat_min 39.0438;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -74.74948;
    Float64 geospatial_lon_min -74.80179;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 0.1;
    Float64 geospatial_vertical_min 0.004;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2026-11-21T11:24:52Z (local files)
2026-11-21T11:24:52Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_988873_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/988873";
    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.";
    Float64 Northernmost_Northing 39.08802;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 39.0438;
    String summary "This dataset consists of 10-minute resolution measurements of temperature, salinity, depth, dissolved oxygen concentration, and pH collected from five salt ponds in a tidal salt marsh within the Seven Mile Island Innovation Laboratory (SMIIL), located landward of Seven Mile Island in Cape May County, New Jersey. The ponds were selected based on aerial imagery from the New Jersey Office of Geographic Information Systems (NJOGIS) and in situ physical inspection to identify ponds spanning a range of sizes (150-19,000 m2), ages (40-100+ years), and instrumentable depths (0.5-1.5 m). Data from each salt pond was collected using four Onset Computer Corp. HOBO data loggers that measured pressure, temperature, conductivity/salinity, dissolved oxygen, and pH. Each of the four sensors measured temperature, with the finalized temperature data reflecting the median of the four sensors in each pond. An additional HOBO pressure sensor was deployed in a central location recording air temperature and barometric pressure. Sensors were cleaned, calibrated, and redeployed every 4-16 weeks, and discrete dissolved oxygen and carbonate chemistry samples were collected for sensor validation at the beginning and end of each deployment (see discrete sample dataset, also in this project). This dataset presents quality controlled data from each of the five ponds across five deployments, covering a period from April 2023 to June 2024.";
    String title "[Salt pond monitoring] - Continuously monitored water quality measurements from five salt marsh ponds in New Jersey, USA from Apr 2023 to Jun 2024 (Sediment transport and water quality in watersheds and coastlines of the United States)";
    Float64 Westernmost_Easting -74.80179;
  }
}

 

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