Ifremer ERDDAP
Easier access to scientific data

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  ArgoFloats index Subscribe RSS
Institution:  Argo   (Dataset ID: ArgoFloats-index)
Range: longitude = -999.999 to 346.813°E, latitude = -99.999 to 89.784°N
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: 
[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 {
  file {
    String long_name "File";
  }
  date {
    Float64 actual_range 8.7012158e+8, 1.634051961e+9;
    String ioos_category "Time";
    String long_name "Date";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -99.999, 89.784;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -999.999, 346.813;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  ocean {
    String long_name "Ocean";
  }
  profiler_type {
    Int16 actual_range 831, 879;
    String long_name "Profiler Type";
  }
  institution {
    String long_name "Institution";
  }
  date_update {
    Float64 actual_range 1.143156391e+9, 1.634054443e+9;
    String ioos_category "Time";
    String long_name "Date of update";
    String standard_name "date_update";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_name "Argo";
    Float64 Easternmost_Easting 346.813;
    Float64 geospatial_lat_max 89.784;
    Float64 geospatial_lat_min -99.999;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 346.813;
    Float64 geospatial_lon_min -999.999;
    String geospatial_lon_units "degrees_east";
    String history 
"2021-10-20T01:18:04Z ftp://ftp.ifremer.fr/ifremer/argo/ar_index_global_prof.txt
2021-10-20T01:18:04Z http://www.ifremer.fr/tabledap/ArgoFloats-index.das";
    String infoUrl "http://www.argodatamgt.org/DMQC/Reference-data-base";
    String institution "Argo";
    String keywords "argo, array, data, date, date_update, file, geostrophic, index, institution, latitude, longitude, ocean, oceanography, profiler, profiler_type, real, real time, real-time, realtime, time, type, update";
    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 89.784;
    String sourceUrl "ftp://ftp.ifremer.fr/ifremer/argo/ar_index_global_prof.txt";
    Float64 Southernmost_Northing -99.999;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "ocean, profiler_type, institution";
    String summary "Argo detailed index. Gathers data available at ftp://ftp.ifremer.fr/ifremer/argo/ar_index_global_prof.txt";
    String title "ArgoFloats index";
    Float64 Westernmost_Easting -999.999;
  }
}

 

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