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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [GP15 Water Column Dissolved 227Ac Leg 1] - Activity of actinium-227 from
water samples collected on Leg 1 (Seattle, WA to Hilo, HI) of the US GEOTRACES
Pacific Meridional Transect (PMT) cruise (GP15, RR1814) on R/V Roger Revelle
from September to October 2018 (US GEOTRACES Pacific Meridional Transect (GP15))
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_940589_v1)
Range: longitude = -155.17 to -152.0°E, latitude = 19.681 to 54.66°N, depth = 22.0 to 5547.0m, time = 2018-09-24T11:54:00Z to 2018-10-21T18:24:00Z
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 {
  Station_ID {
    String long_name "Station_id";
    String units "unitless";
  }
  Event_ID {
    Int32 actual_range 6523, 6769;
    String long_name "Event_id";
    String units "unitless";
  }
  Gear_ID {
    String long_name "Gear_id";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.53779004e+9, 1.54014624e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Start_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";
  }
  Start_Date_UTC {
    String long_name "Start_date_utc";
    String units "unitless";
  }
  Start_Time_UTC {
    String long_name "Start_time_utc";
    String units "unitless";
  }
  End_ISO_DateTime_UTC {
    Float64 actual_range 1.53780444e+9, 1.54015716e+9;
    String ioos_category "Time";
    String long_name "End_iso_datetime_utc";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  End_Date_UTC {
    String long_name "End_date_utc";
    String units "unitless";
  }
  End_Time_UTC {
    String long_name "End_time_utc";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 19.681, 54.66;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Start_latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -155.17, -152.0;
    String axis "X";
    String ioos_category "Location";
    String long_name "Start_longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Sample_ID {
    Int32 actual_range 12361, 13892;
    String long_name "Sample_id";
    String units "unitless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 22, 5547;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Sample_depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Ac_227_D_CONC_PUMP_lfvbby {
    Float32 actual_range -0.7, 129.7;
    String long_name "Ac_227_d_conc_pump_lfvbby";
    String units "micro becquerel per kilogram (uBq/kg)";
  }
  SD1_Ac_227_D_CONC_PUMP_lfvbby {
    Float32 actual_range 0.2, 14.9;
    String long_name "Sd1_ac_227_d_conc_pump_lfvbby";
    String units "micro becquerel per kilogram (uBq/kg)";
  }
  Flag_Ac_227_D_CONC_PUMP_lfvbby {
    Int32 actual_range 1, 9;
    String long_name "Flag_ac_227_d_conc_pump_lfvbby";
    String units "unitless";
  }
  Pa231_uBq_kg {
    Float32 actual_range 0.2, 10.6;
    String long_name "Pa231_ubq_kg";
    String units "micro becquerel per kilogram (uBq/kg)";
  }
  Excess_227Ac_D_uBq_kg {
    Float32 actual_range -3.2, 122.7;
    String long_name "Excess_227ac_d_ubq_kg";
    String units "micro becquerel per kilogram (uBq/kg)";
  }
  SD1_Ex_227Ac_D_uBq_kg {
    Float32 actual_range 0.2, 14.9;
    String long_name "Sd1_ex_227ac_d_ubq_kg";
    String units "micro becquerel per kilogram (uBq/kg)";
  }
  DAB_m {
    Int32 actual_range 16, 5568;
    String long_name "Dab_m";
    String units "meters (m)";
  }
  Ac227_D_dpm_m3 {
    Float32 actual_range -0.04, 7.98;
    String long_name "Ac227_d_dpm_m3";
    String units "disintegrations per minute per cubic meter (dpm/m3)";
  }
  SD1_227Ac_D_dpm_m3 {
    Float32 actual_range 0.01, 0.92;
    String long_name "Sd1_227ac_d_dpm_m3";
    String units "disintegrations per minute per cubic meter (dpm/m3)";
  }
  Pa231_dpm_m3 {
    Float32 actual_range 0.01, 0.65;
    String long_name "Pa231_dpm_m3";
    String units "disintegrations per minute per cubic meter (dpm/m3)";
  }
  Excess_227Ac_D_dpm_m3 {
    Float32 actual_range -0.2, 7.55;
    String long_name "Excess_227ac_d_dpm_m3";
    String units "disintegrations per minute per cubic meter (dpm/m3)";
  }
  SD1_Ex_227Ac_D_dpm_m3 {
    Float32 actual_range 0.01, 0.92;
    String long_name "Sd1_ex_227ac_d_dpm_m3";
    String units "disintegrations per minute per cubic meter (dpm/m3)";
  }
  Cartridges {
    String long_name "Cartridges";
    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 "&amp;time&lt;now";
    String doi "10.26008/1912/bco-dmo.940589.1";
    Float64 Easternmost_Easting -152.0;
    Float64 geospatial_lat_max 54.66;
    Float64 geospatial_lat_min 19.681;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -152.0;
    Float64 geospatial_lon_min -155.17;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 5547.0;
    Float64 geospatial_vertical_min 22.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2025-02-10T06:54:12Z (local files)
2025-02-10T06:54:12Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_940589_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/940589";
    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 54.66;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 19.681;
    String summary "Actinium-227 (227Ac) was captured on commercial water filters impregnated with manganese dioxide (MnO2) and placed downstream of the filters in submersible pumps deployed on GEOTRACES expedition GP15, aboard R/V Roger Revelle, in collaboration with groups from Woods Hole Oceanographic Institution (WHOI) and University of South Carolina who measured radium isotopes on the same cartridges. The activity of 227Ac was measured using RaDeCC (Radium Delayed Coincidence Counter) and used to calculate the concentration of dissolved  227Ac along the transect by PI Douglas Hammond and graduate student Nathan Kemnitz. Data have been summarized and will be submitted in a publication to be submitted to JGR Oceans, along with a companion data set for 227Ac, 228Ra, and 210Pb in sediments. This dataset has been used to evaluate deep ocean solute transport. This dataset includes data from Leg 1 of the cruise (RR1814). Leg 2 data (RR1815) are available in a separate BCO-DMO dataset.";
    String time_coverage_end "2018-10-21T18:24:00Z";
    String time_coverage_start "2018-09-24T11:54:00Z";
    String title "[GP15 Water Column Dissolved 227Ac Leg 1] - Activity of actinium-227 from water samples collected on Leg 1 (Seattle, WA to Hilo, HI) of the US GEOTRACES Pacific Meridional Transect (PMT) cruise (GP15, RR1814) on R/V Roger Revelle from September to October 2018 (US GEOTRACES Pacific Meridional Transect (GP15))";
    Float64 Westernmost_Easting -155.17;
  }
}

 

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