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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [CliOMZ AT50-10 Trace Metal Rosette Log] - Trace metal rosette log of samples
taken on board of the R/V Atlantis during the CliOMZ AT50-10 expedition from
Golfito, Costa Rica to San Diego, USA that occurred in May - June of
2023. (Collaborative Research: Underexplored Connections between Nitrogen and
Trace Metal Cycling in Oxygen Minimum Zones Mediated by Metalloenzyme
Inventories)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_929694_v1)
Range: depth = 3.0 to 3950.0m, time = 2023-05-04T01:24:00Z to 2023-06-08T23:00: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 {
  Cruise_ID {
    String long_name "Cruise_id";
    String units "unitless";
  }
  Station_number {
    Int32 actual_range 2, 18;
    String long_name "Station_number";
    String units "unitless";
  }
  Cast_number {
    Int32 actual_range 1, 58;
    String long_name "Cast_number";
    String units "unitless";
  }
  Start_date_UTC {
    String long_name "Start_date_utc";
    String units "unitless";
  }
  Start_time_UTC {
    String long_name "Start_time_utc";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.68316344e+9, 1.6862652e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Iso_datetime_utc_start";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Start_Lat {
    Float32 actual_range -10.01076, 31.08341;
    String long_name "Start_lat";
    String units "decimal degrees";
  }
  Start_Long {
    Float32 actual_range -120.2323, -88.88752;
    String long_name "Start_long";
    String units "decimal degrees";
  }
  Cast_total_depth_m {
    Int32 actual_range 5, 4250;
    String long_name "Cast_total_depth_m";
    String units "m";
  }
  Niskin {
    Int32 actual_range 1, 12;
    String long_name "Niskin";
    String units "unitless";
  }
  program_depth {
    Int32 actual_range 5, 4250;
    String long_name "Program_depth";
    String units "meter (m)";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 3, 3950;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Real_depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Notes {
    String long_name "Notes";
    String units "unitless";
  }
  sample_number {
    String long_name "Sample_number";
    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.929694.1";
    Float64 geospatial_vertical_max 3950.0;
    Float64 geospatial_vertical_min 3.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-08T06:18:01Z (local files)
2024-11-08T06:18:01Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_929694_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/929694";
    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 "This is the log for the trace metal rosette niskin bottles deployed on the R/V Atlantis CliOMZ AT50-10 expedition from Golfito Costa Rica to San Diego USA that occurred in May - June of 2023.  The log contains metadata associated with each rosette deployment, including location, bottle depth, and time. The rosette was launched on 1/4\" kevlar line spooled on a MASH2K winch from the East Coast Winch Pool. The Science party included members from WHOI, UCSB, UTGRV, and Clark University.";
    String time_coverage_end "2023-06-08T23:00:00Z";
    String time_coverage_start "2023-05-04T01:24:00Z";
    String title "[CliOMZ AT50-10 Trace Metal Rosette Log] - Trace metal rosette log of samples taken on board of the R/V Atlantis during the CliOMZ AT50-10 expedition from Golfito, Costa Rica to San Diego, USA that occurred in May - June of 2023. (Collaborative Research: Underexplored Connections between Nitrogen and Trace Metal Cycling in Oxygen Minimum Zones Mediated by Metalloenzyme Inventories)";
  }
}

 

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