BCO-DMO ERDDAP
Accessing BCO-DMO data

Make A Graph

Dataset Title:	[Consensus Reference Material Collection Data] - Consensus Reference Material Collection Data of marine dissolved organic matter collected in the Florida Strait between 2019 and 2023 (Preparation and Distribution of DOC Consensus Reference Materials)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_914491_v1)
Range:	longitude = -79.9 to -79.9°E
Information:	Summary \| License \| Metadata \| Background \| Data Access Form \| Files

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:

X Axis:

Y Axis:

Color:

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.

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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Cruise_ID {
    String long_name "Cruise_id";
    String units "unitless";
  }
  Collection_Date {
    String long_name "Collection_date";
    String units "unitless";
  }
  Latitude {
    Float32 actual_range 25.5, 25.5;
    String long_name "Latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -79.9, -79.9;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Batch_ID {
    String long_name "Batch_id";
    String units "unitless";
  }
  Designations {
    String long_name "Designations";
    String units "unitless";
  }
  Sampling_Depths {
    String long_name "Sampling_depths";
    String units "unitless";
  }
  DOC_Conc_uM_Min {
    Int32 actual_range 40, 76;
    String long_name "Doc_conc_um_min";
    String units "micromoles carbon per liter (uM/L)";
  }
  DOC_Conc_uM_Max {
    Int32 actual_range 41, 78;
    String long_name "Doc_conc_um_max";
    String units "micromoles carbon per liter (uM/L)";
  }
  TDN_Conc_uM_Min {
    Int32 actual_range 4, 31;
    String long_name "Tdn_conc_um_min";
    String units "micromoles nitrogen per liter (uM/L)";
  }
  TDN_Conc_uM_Max {
    Int32 actual_range 5, 33;
    String long_name "Tdn_conc_um_max";
    String units "micromoles nitrogen per liter (uM/L)";
  }
  Ship {
    String long_name "Ship";
    String units "unitless";
  }
  Ship_Data {
    String long_name "Ship_data";
    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.914491.1";
    Float64 Easternmost_Easting -79.9;
    Float64 geospatial_lon_max -79.9;
    Float64 geospatial_lon_min -79.9;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-09-23T19:29:55Z (local files)
2024-09-23T19:29:55Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_914491_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/914491";
    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 
"The laboratory of Prof. Dennis A. Hansell at the University of Miami is supported by the U.S. National Science Foundation to provide the international community of marine dissolved organic matter analysts the reference waters needed for testing their analytical results against those of a select group of expert analysts. 

Three depths of the water column are sampled in the Florida Strait, typically twice each year,  to collect and distribute those waters as reference materials. The deepest water (i.e., deep seawater reference (DSR)) is collected in the Florida Straits at 700 m depth. A mid depth seawater reference (MSR), is collected at 150 m depth and surface seawater reference (SSR) is collected at 5 m. In the data table that follows, the relevant information for each collection during NSF Grant OCE-1844886, awarded to the Hansell laboratory, is provided. These details include the ship employed and its cruise designations, the dates of collection, the batch and lot numbers designated for the reference waters, the locations and depths sampled, the concentrations of dissolved organic carbon (DOC) and total dissolved nitrogen (TDN) in each lot. Finally, hyperlinks to the associated CTD and underway data, archived by RVDATA.US, are provided.";
    String title "[Consensus Reference Material Collection Data] - Consensus Reference Material Collection Data of marine dissolved organic matter collected in the Florida Strait between 2019 and 2023 (Preparation and Distribution of DOC Consensus Reference Materials)";
    Float64 Westernmost_Easting -79.9;
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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