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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Gulf of Alaska Al and Mn - Surface Samples] - Dissolved aluminum (Al) and
manganese (Mn) and total dissolvable Al and Mn from surface water samples
collected during three cruises in 2010 in the northern Gulf of Alaska (US
GEOTRACES Pacific Section-Shipboard Al, Mn and Fe) Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_891941_v1)
Range: longitude = -145.1725 to -144.9261°E, depth = 0.52 to 2.69m, time = 2010-04-08T18:45:00Z to 2010-07-29T20:41:00Z
Information:  Summary ? | License ? | 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 {
  Latitude_degN {
    Float32 actual_range 59.0789, 60.19258;
    String long_name "Latitude_degn";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -145.1725, -144.9261;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude_dege";
    String standard_name "longitude";
    String units "degrees_east";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.2707523e+9, 1.28043606e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Iso_datetime_utc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 0.52, 2.69;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Ysi_depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Surface_Salinity {
    Float32 actual_range 21.03, 32.23;
    String long_name "Surface_salinity";
    String units "PSU";
  }
  Distance_from_Shore {
    Float32 actual_range 2.9, 127.62;
    String long_name "Distance_from_shore";
    String units "kilometers (km)";
  }
  DAl {
    Float32 actual_range 3.68, 627.1;
    String long_name "Dal";
    String units "nanomolar concentration (nM)";
  }
  TDAl {
    Float32 actual_range 8.28, 148875.3;
    String long_name "Tdal";
    String units "nanomolar concentration (nM)";
  }
  DMn {
    Float32 actual_range 7.48, 60.99;
    String long_name "Dmn";
    String units "nanomolar concentration (nM)";
  }
  TDMn {
    Float32 actual_range 8.01, 2334.01;
    String long_name "Tdmn";
    String units "nanomolar concentration (nM)";
  }
 }
  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.891941.1";
    Float64 Easternmost_Easting -144.9261;
    Float64 geospatial_lon_max -144.9261;
    Float64 geospatial_lon_min -145.1725;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 2.69;
    Float64 geospatial_vertical_min 0.52;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-08T06:22:56Z (local files)
2024-11-08T06:22:56Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_891941_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/891941";
    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 
"Water samples were collected along a transect during three cruises in 2010 (7-9 April, 5-7 May, and 27-29 July) in the northern Gulf of Alaska, from the mouth of the Copper River to about 50 km past the shelf break. Surface samples were collected by underway pumping using Teflon-lined tubing, using a method modified from Vink et al. (2000). Filtered dissolved metal surface samples were collected using a 0.45 µm in-line Acropore filter under N₂ pressure. Water samples were processed in the shipboard clean lab within three hours of collection. Dissolved samples were filtered using acid-washed 0.45 µm Pall-Supor filters. All samples were acidified to pH 1.8 using Seastar grade HCl within 3 days and stored for 5 years before analysis.

Filtered samples were analyzed for dissolved Al and unfiltered samples were analyzed for total dissolvable Al using Flow Injection Analysis (Resing and Measures 1994) using fluorescent detection of lumogallion. Filtered samples were analyzed for dissolved Mn and unfiltered samples were analyzed for total dissolvable Mn according to the method of Resing and Mottl (1992), which uses spectroscopic detection of leuchomalachite green.";
    String time_coverage_end "2010-07-29T20:41:00Z";
    String time_coverage_start "2010-04-08T18:45:00Z";
    String title "[Gulf of Alaska Al and Mn - Surface Samples] - Dissolved aluminum (Al) and manganese (Mn) and total dissolvable Al and Mn from surface water samples collected during three cruises in 2010 in the northern Gulf of Alaska (US GEOTRACES Pacific Section-Shipboard Al, Mn and Fe)";
    Float64 Westernmost_Easting -145.1725;
  }
}

 

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