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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Florida Bay DIN, DOC, and Chl-a 2017-2018] - (RAPID: Hurricane Irma Impacts
on Nitrogen Cycling in Florida Bay)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_905393_v1)
Range: longitude = -80.8333 to -80.8045°E, latitude = 24.9371 to 24.9589°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 {
  Date {
    String long_name "Date";
    String units "unitless";
  }
  Station {
    String long_name "Station";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 24.9371, 24.9589;
    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 -80.8333, -80.8045;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  NOx_avg {
    Float32 actual_range 0.03, 1.34;
    String long_name "Nox_avg";
    String units "micromolar (uM)";
  }
  NOx_sd {
    Float32 actual_range 0.01, 0.57;
    String long_name "Nox_sd";
    String units "micromolar (uM)";
  }
  NH4_avg {
    Float32 actual_range 0.01, 2.9;
    String long_name "Nh4_avg";
    String units "micromolar (uM)";
  }
  NH4_sd {
    Float32 actual_range 0.0, 1.82;
    String long_name "Nh4_sd";
    String units "micromolar (uM)";
  }
  DIN_avg {
    Float32 actual_range 0.12, 4.23;
    String long_name "Din_avg";
    String units "micromolar (uM)";
  }
  DIN_sd {
    Float32 actual_range 0.0, 1.82;
    String long_name "Din_sd";
    String units "micromolar (uM)";
  }
  DOC_avg {
    Int32 actual_range 296, 954;
    String long_name "Doc_avg";
    String units "micromolar (uM)";
  }
  DOC_sd {
    Int32 actual_range 3, 76;
    String long_name "Doc_sd";
    String units "micromolar (uM)";
  }
  TN_avg {
    Float32 actual_range 9.0, 68.0;
    String long_name "Tn_avg";
    String units "micromolar (uM)";
  }
  TN_sd {
    Float32 actual_range 0.0, 20.0;
    String long_name "Tn_sd";
    String units "micromolar (uM)";
  }
  Chla_avg {
    Float32 actual_range 0.05, 14.93;
    String long_name "Chla_avg";
    String units "micrograms per liter (ug/L)";
  }
  Chla_sd {
    Float32 actual_range 0.0, 3.17;
    String long_name "Chla_sd";
    String units "micrograms per liter (ug/L)";
  }
 }
  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.905393.1";
    Float64 Easternmost_Easting -80.8045;
    Float64 geospatial_lat_max 24.9589;
    Float64 geospatial_lat_min 24.9371;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -80.8045;
    Float64 geospatial_lon_min -80.8333;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-11-05T19:05:42Z (local files)
2025-11-05T19:05:42Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_905393_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/905393";
    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 24.9589;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 24.9371;
    String summary 
"These data are tabular results of investigations focused on temporal changes in dissolved inorganic nitrogen (DIN) over a 15-month period starting in October 2017, following the passage of Hurricane Irma over the Middle Keys, Florida, United States. Post-Irma time-series measurements focused on determination of the impacts of episodic storm events on temporal variability in DIN. 

Three areas in Florida Bay north of the Middle Keys were chosen for sampling based on previous work conducted between 2012 and 2015 by colleagues at the University of North Carolina (UNC) and FWC-M. Together, the study sites are representative of the range of nearshore environments along the southern portion of Florida Bay. Monthly whole water samples were filtered for chlorophyll-a (Chl-a) measurements, then analyzed for nitrate/nitrite (NOx-) and ammonium (NH4+). Drastic, systematic changes in all water quality parameters initially occurred, including spiked DIN concentrations following release of NH4+-enriched pore-waters during sediment resuspension and rapid declines in DIN during phytoplankton blooms. However, four months post-Irma, concentrations returned to seasonally variable pre-Irma levels observed in previous multi-year surveys.";
    String title "[Florida Bay DIN, DOC, and Chl-a 2017-2018] -  (RAPID: Hurricane Irma Impacts on Nitrogen Cycling in Florida Bay)";
    Float64 Westernmost_Easting -80.8333;
  }
}

 

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