NOAA PMEL Easy Access to PMEL Scientific Data
The Pacific Marine Environmental Laboratory's ERDDAP data server for public access to scientific data
?    
NOAA OAR PMEL    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  PMEL Atmospheric Chemistry ATOMIC Radon data Subscribe RSS
Institution:  NOAA   (Dataset ID: ACG_ATOMIC_RHBrown_radon)
Range: longitude = -59.6542 to -50.9295°E, latitude = 12.8039 to 15.8647°N, altitude = 18.0 to 18.0m, time = 2020-01-07T18:00:00Z to 2020-02-11T23:30:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | 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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.57842e+9, 1.5814638e+9;
    String axis "T";
    String comment "Start of sampling period";
    String coords "time";
    String ioos_category "Time";
    String long_name "Datetime UTC";
    String source_name "datetime_utc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  trajectory_id {
    String cf_role "trajectory_id";
    String coords "time";
    String ioos_category "Identifier";
    String long_name "Trajectory ID";
  }
  duration {
    Int32 _FillValue 2147483647;
    Int32 actual_range 1800, 1800;
    String coords "time";
    String ioos_category "Time";
    String long_name "Duration";
    String units "second";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 12.8039, 15.8647;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String coords "time";
    String instrument "GPS";
    String ioos_category "Location";
    String long_name "Latitude";
    String source "surface observation";
    String standard_name "latitude";
    String units "degrees_north";
    Float64 valid_max 90.0;
    Float64 valid_min -90.0;
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -59.6542, -50.9295;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String coords "time";
    String instrument "GPS";
    String ioos_category "Location";
    String long_name "Longitude";
    String source "surface observation";
    String standard_name "longitude";
    String units "degrees_east";
    Float64 valid_max 180.0;
    Float64 valid_min -180.0;
  }
  altitude {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "up";
    Float64 actual_range 18.0, 18.0;
    String axis "Z";
    Float64 colorBarMinimum 0.0;
    String coords "time";
    String ioos_category "Location";
    String long_name "height above mean sea level";
    String positive "up";
    String standard_name "altitude";
    String units "m";
    Float64 valid_min 0.0;
  }
  radon {
    Float64 actual_range -102.0, 5025.0;
    Float64 colorBarMaximum 40000.0;
    Float64 colorBarMinimum 0.0;
    String coords "time";
    String instrument "Dual flow loop";
    String ioos_category "Unknown";
    String long_name "Radon";
    String source "surface observation";
    String standard_name "radioactivity_concentration_of_222rn_in_air";
    String units "mBq m-3";
    Float64 valid_max 30000.0;
    Float64 valid_min 0.0;
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Trajectory";
    String cdm_trajectory_variables "trajectory_id";
    String comment 
"Radon:
The PMEL radon instrument is a \"dual flow loop, two filtered radon detector\". The general features of the instrument are described in Whittlestone and Zahorowski, Baseline radon detectors for shipboard use: Development and deployment in the First Aerosol Characterization Experiment (ACE1), J. Geophys. Res., 103, 16,743-16,751, 1998. The instrument response is due to radon gas, not radon daughters (all of the existing radon daughters are filtered out before entering the decay/counting tank). The instrument registers the total number of decay counts per 30 minute interval on a filter (wire screen) arising from the decay of radon in the tank. The volume of the decay/counting tank was 905 l and the sample flow rate into and out of the tank was typically 70 l/min. The response time of the radon instrument is limited to about 30 minutes by the radiological decay time constants of the radon daughters on the wire screen filter. Thus, the start time given in the data file is 15 minutes prior to the midpoint of the counting interval. The instrument was calibrated with a known radon source in Seattle before the cruise and a second calibration was performed after the instrument was shipped back to PMEL. Radon concentrations are given in mBq m-3.";
    String contributor_name "Coffman, Derek/NOAA-PMEL/Address: 7600 Sand Pt. Wy. NE,Seattle,WA 98115 /email: derek.coffman@noaa.gov";
    String Conventions "COARDS, CF-1.6, ACDD-1.3, NCCSV-1.0";
    String creator_email "derek.coffman@noaa.gov";
    String creator_name "Coffman, Derek";
    String creator_url "https://www.pmel.noaa.gov/";
    String dimensions "time=1692";
    Float64 Easternmost_Easting -50.9295;
    String featureType "Trajectory";
    Float64 geospatial_lat_max 15.8647;
    Float64 geospatial_lat_min 12.8039;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -50.9295;
    Float64 geospatial_lon_min -59.6542;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 18.0;
    Float64 geospatial_vertical_min 18.0;
    String geospatial_vertical_positive "up";
    String geospatial_vertical_units "m";
    String history 
"2025-05-09T23:04:30Z (local files)
2025-05-09T23:04:30Z https://data.pmel.noaa.gov/pmel/tabledap/ACG_ATOMIC_RHBrown_radon.das";
    String infoUrl "https://www.pmel.noaa.gov/acg/data/index.html";
    String institution "NOAA";
    String keywords "222rn, above, air, altitude, atmosphere, atmospheric, atomic, chemistry, concentration, data, datetime, duration, earth, Earth Science > Atmosphere > Altitude > Station Height, environmental, height, identifier, laboratory, latitude, level, longitude, marine, mean, noaa, pacific, pmel, radioactivity, radioactivity_concentration_of_222rn_in_air, radon, science, sea, station, time, trajectory, trajectory_id";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "These data were produced by NOAA and are not subject to copyright protection in the United States. NOAA waives any potential copyright and related rights in these data worldwide through the Creative Commons Zero 1.0 Universal Public Domain Dedication (CC0-1.0).";
    Float64 Northernmost_Northing 15.8647;
    String platform "RHBrown";
    String product_version "0";
    String project "ATOMIC";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 12.8039;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "trajectory_id, duration, altitude";
    String summary 
"From early January through mid-February 2020, NOAA is partnering with several universities and other programs to lead the Atlantic Tradewind Ocean-Atmosphere Mesoscale Interaction Campaign (ATOMIC). The field study will take place in the tropical North Atlantic east of Barbados and investigate cloud and air-sea interaction processes with the goal of advancing understanding and prediction of U.S. weather and climate. ATOMIC is the U.S. complement to the European field campaign called EUREC4A. This collaborative effort involves a unique combination of ships, piloted and remotely-controlled aircraft, and remotely-controlled ocean vehicles to characterize ocean and atmospheric properties. A suite of instruments will be deployed from NOAA's research ship Ronald H. Brown and WP-3D Orion \"Hurricane Hunter\" aircraft, and on land.

The focus area of ATOMIC is in the heart of the trade winds and representative of other regions across the global ocean with shallow convective clouds. Some of the Earth's largest ocean eddies (circular currents) also shed into this region from the Amazon and Orinoco Rivers. Conducting the study during winter allows researchers to observe the ocean, air, and clouds in near isolation from hurricane impacts, and to gain better insight into the ocean's involvement in making clouds that affect larger weather and climate patterns.

Improved understanding of air-sea interactions in this region will help advance representations of these processes in NOAA's model forecast systems. This effort will also improve the numerical guidance used to predict weather and climate extremes.";
    String time_coverage_end "2020-02-11T23:30:00Z";
    String time_coverage_start "2020-01-07T18:00:00Z";
    String title "PMEL Atmospheric Chemistry ATOMIC Radon data";
    Float64 Westernmost_Easting -59.6542;
  }
}

 

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.18
Disclaimers | Privacy Policy | Contact