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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [BAIT Aerosol Fe data] - Atmospheric concentrations of aerosol iron from
samples collected at Tudor Hill Bermuda between November 2018 and March
2020. (Operation of a Community Marine-Atmospheric Sampling Facility at Tudor
Hill, Bermuda)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_906770_v1)
Range: longitude = -64.879 to -64.879°E, time = 2018-11-26T20:35:00Z to 2020-03-10T19:05: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 {
    Float32 actual_range 32.265, 32.265;
    String long_name "Latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -64.879, -64.879;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Aerosol_sample_ID {
    String long_name "Aerosol_sample_id";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.5432645e+9, 1.5838671e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Start_datetime_utc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  End_datetime_UTC {
    Float64 actual_range 1.5438582e+9, 1.58438742e+9;
    String ioos_category "Time";
    String long_name "End_datetime_utc";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Sampling_period {
    Int32 actual_range 4, 19;
    String long_name "Sampling_period";
    String units "day";
  }
  Pump_time {
    Float32 actual_range 1.8, 252.0;
    String long_name "Pump_time";
    String units "hour";
  }
  Air_volume {
    Float32 actual_range 7052.2, 1.23516e+7;
    String long_name "Air_volume";
    String units "liter";
  }
  Total_aerosol_Fe {
    Float32 actual_range 0.019, 21.99;
    String long_name "Total_aerosol_fe";
    String units "nanomoles per cubic meter (nmol m-3)";
  }
  DIW_soluble_aerosol_Fe {
    Float32 actual_range 0.001, 1.228;
    String long_name "Diw_soluble_aerosol_fe";
    String units "nanomoles per cubic meter (nmol m-3)";
  }
  HOAc_soluble_aerosol_Fe {
    Float32 actual_range 0.0, 0.836;
    String long_name "Hoac_soluble_aerosol_fe";
    String units "nanomoles per cubic meter (nmol m-3)";
  }
  Sample_flag {
    Int32 actual_range 1, 3;
    String long_name "Sample_flag";
    String units "unitless";
  }
  Start_datetime_local {
    String long_name "Start_datetime_local";
    String units "unitless";
  }
  End_datetime_local {
    String long_name "End_datetime_local";
    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.906770.1";
    Float64 Easternmost_Easting -64.879;
    Float64 geospatial_lon_max -64.879;
    Float64 geospatial_lon_min -64.879;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-09-21T20:31:33Z (local files)
2024-09-21T20:31:33Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_906770_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/906770";
    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 "These data include the atmospheric concentrations of aerosol iron (total, deionized-water-soluble, and dilute-acetic-acid-soluble) derived from analysis of composite aerosol samples collected during approximately weekly intervals on the sampling tower at Tudor Hill, Bermuda, between November 2018 and March 2020. The data allow estimates of the dry deposition of iron to the Bermuda region over the period of the BAIT project, which included cruises in the Bermuda Atlantic Time-series Study (BATS) region in March, May, August and November 2019. The rain samples were collected by staff of the Bermuda Institute of Ocean Sciences (the Tudor Hill tower facility is managed by Dr. Andrew Peters, with funding from NSF), and sample processing and analyses were completed in the laboratory of Dr. Peter Sedwick at Old Dominion University.";
    String time_coverage_end "2020-03-10T19:05:00Z";
    String time_coverage_start "2018-11-26T20:35:00Z";
    String title "[BAIT Aerosol Fe data] - Atmospheric concentrations of aerosol iron from samples collected at Tudor Hill Bermuda between November 2018 and March 2020. (Operation of a Community Marine-Atmospheric Sampling Facility at Tudor Hill, Bermuda)";
    Float64 Westernmost_Easting -64.879;
  }
}

 

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