Easier access to all of NOAA's data
log in    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  OSMC Argo Profile data Subscribe RSS
Institution:  OSMC   (Dataset ID: OSMC_PROFILERS)
Range: longitude = -180.0 to 180.0°E, latitude = -89.0 to 89.0°N
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form
Graph Type:  ?
X Axis: 
Y Axis: 
-1 +1
Constraints ? Optional
Constraint #1 ?
Constraint #2 ?
Server-side Functions ?
 distinct() ?
? (" ")
Graph Settings
Marker Type:   Size: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Draw land mask: 
Y Axis Minimum:   Maximum:   Ascending: 
(Please be patient. It may take a while to get the data.)
Then set the File Type: (File Type information)
or view the URL:
(Documentation / Bypass this form ? )
    Click on the map to specify a new center point. ?
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 {
  platform_code {
    String cf_role "profile_id";
    String ioos_category "Identifier";
    String long_name "PLATFORM CODE";
  organization_name {
    String ioos_category "Unknown";
    String long_name "ORGANIZATION NAME";
  country_name {
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Statistics";
    String long_name "COUNTRY NAME";
  platform_type_name {
    String ioos_category "Unknown";
    String long_name "PLATFORM TYPE NAME";
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String ioos_category "Time";
    String long_name "OBSERVATION DATE";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  parameter_name {
    String ioos_category "Unknown";
    String long_name "PARAMETER NAME";
  daily_obs_count {
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Unknown";
    String long_name "DAILY OBS COUNT";
  observation_depth {
    String _CoordinateAxisType "Height";
    String axis "Z";
    String cdm_altitude_proxy "observation_depth";
    String ioos_category "Location";
    String long_name "OBSERVATION DEPTH";
  observation_value {
    String ioos_category "Unknown";
    String long_name "OBSERVATION VALUE";
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range -89.0, 89.0;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -180.0, 180.0;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
    String cdm_altitude_proxy "observation_depth";
    String cdm_data_type "Profile";
    String cdm_profile_variables "platform_code";
    String Conventions "COARDS, CF-1.6, Unidata Dataset Discovery v1.0";
    Float64 Easternmost_Easting 180.0;
    String featureType "Profile";
    Float64 geospatial_lat_max 89.0;
    Float64 geospatial_lat_min -89.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 180.0;
    Float64 geospatial_lon_min -180.0;
    String geospatial_lon_units "degrees_east";
    String history 
"2018-07-14T10:46:23Z (source database)
2018-07-16T03:05:57Z (source database)
    String infoUrl "";
    String institution "OSMC";
    String keywords "code, count, country, daily, data, date, depth, from, last, local, max, name, observation, observations, organization, parameter, platform, reported, sensor, source., time, timestamp, type, value";
    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 Metadata_Conventions "COARDS, CF-1.6, Unidata Dataset Discovery v1.0";
    Float64 Northernmost_Northing 89.0;
    String sourceUrl "(source database)";
    Float64 Southernmost_Northing -89.0;
    String standard_name_vocabulary "CF-12";
    String subsetVariables "parameter_name";
    String summary "OSMC Argo Profile data";
    String title "OSMC Argo Profile data";
    Float64 Westernmost_Easting -180.0;


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{?query}
For example,,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 1.82
Disclaimers | Privacy Policy | Contact