NOAA ERDDAP
Easier access to scientific data
   
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  PMEL Atmospheric Chemistry ATOMIC Radon 30 minute data Subscribe RSS
Institution:  NOAA PMEL Atmospheric Chemistry   (Dataset ID: EUREC4A_ATOMIC_RonBrown_PMEL_Radon_v0)
Range: longitude = -59.6542 to -50.9295°E, latitude = 12.8039 to 15.8647°N, 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
 
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 calendar "gregorian";
    Float64 colorBarMaximum 1.582e+9;
    Float64 colorBarMinimum 1.578e+9;
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  trajectory_id {
    String cf_role "trajectory_id";
    String ioos_category "Identifier";
    String long_name "trajectory id";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue -1.0e+34;
    Float64 actual_range 12.8039, 15.8647;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String comment "In the one minute files the position is treated somewhat differently from all the other data. The position given is the ship's position at the start of the one minute 'averaging' period. All other data are a true average. The PMEL GPS was the primary source. The Ship's GPS was used when there were missing data in the PMEL record.";
    String epic_code "500";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
    Float64 valid_max 90.0;
    Float64 valid_min -90.0;
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue -1.0e+34;
    Float64 actual_range -59.6542, -50.9295;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String comment "In the one minute files the position is treated somewhat differently from all the other data. The position given is the ship's position at the start of the one minute 'averaging' period. All other data are a true average. The PMEL GPS was the primary source. The Ship's GPS was used when there were missing data in the PMEL record.";
    String epic_code "502";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
    Float64 valid_max 180.0;
    Float64 valid_min -180.0;
  }
  radon {
    Float64 _FillValue -1.0e+34;
    Float64 actual_range -102.0, 5025.0;
    Float64 colorBarMaximum 6000.0;
    Float64 colorBarMinimum -2000.0;
    String comment "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 epic_code "1810";
    String instrument "dual flow loop, two filtered radon detector";
    String ioos_category "Unknown";
    String long_name "Radon";
    Float64 missing_value -999.0;
    String source "surface observation";
    String standard_name "radioactivity_concentration_of_222rn_in_air";
    String units "mBq m-3";
    Float64 valid_max 50000.0;
    Float64 valid_min 0.0;
  }
 }
  NC_GLOBAL {
    String _NCProperties "version=2,netcdf=4.7.4,hdf5=1.10.6";
    String cdm_data_type "Trajectory";
    String cdm_trajectory_variables "trajectory_id";
    String contributor_name "Coffman, Derek;Johnson, James;Quinn, Patricia;Bates, Tim;Upchurch, Lucia";
    String Conventions "CF-1.6, COARDS, ACDD-1.3";
    String creator_email "james.e.johnson@noaa.gov";
    String creator_name "Johnson, James";
    String creator_url "https://saga.pmel.noaa.gov";
    String date_created "2020-11-30T17:24:01Z";
    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";
    String history 
"file created by NOAA/PMEL/ACG
2024-04-12T21:24:21Z (local files)
2024-04-12T21:24:21Z https://data.pmel.noaa.gov/pmel/tabledap/EUREC4A_ATOMIC_RonBrown_PMEL_Radon_v0.das";
    String infoUrl "https://saga.pmel.noaa.gov";
    String institution "NOAA PMEL Atmospheric Chemistry";
    String keywords "222rn, air, atmospheric, atomic, chemistry, concentration, data, environmental, identifier, laboratory, latitude, longitude, marine, minute, noaa, pacific, pmel, radioactivity, radioactivity_concentration_of_222rn_in_air, radon, time, trajectory, trajectory_id";
    String keywords_vocabulary "GCMD Science Keywords";
    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 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 v55";
    String subsetVariables "trajectory_id";
    String summary "ATOMIC (Atlantic Tradewind Ocean Atmosphere Mesoscale Interaction Campaign) 2020 Field campaign: Surface meteorological and ship navigation collected from the RV Ronald H. Brown by the National Oceanic and Atmospheric Administration (NOAA) Pacific Marine Environmental Laboratory (PMEL) Atmospheric Chemistry Group in the tropical North Atlantic ocean from 2020-01-09 to 2020-02-13";
    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 30 minute data";
    Float64 Westernmost_Easting -59.6542;
    Float64 Westernnmost_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