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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Ocean Observatory Initiative, Pioneer Mobile Asset Data: GL388   RSS
Institution:  Rutgers University   (Dataset ID: PIONEER_MOAS_TEMP_SALT_GL388)
Range: longitude = -74.48756 to -69.91571°E, latitude = 38.38585 to 43.94574°N, depth = -1003.65 to 0.21m, time = 2014-10-06T20:24:24Z to 2020-02-20T17:15:51Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | 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: 
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 ? )
    [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.41262706460559e+9, 1.58221895186151e+9;
    String axis "T";
    String calender "julian";
    String ioos_category "Time";
    String long_name "UTC Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -74.48756, -69.91571;
    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";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 38.38585, 43.94574;
    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";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 _FillValue 9.999e+20;
    Float32 actual_range -1003.65, 0.21;
    String axis "Z";
    Float64 colorBarMaximum 0.0;
    Float64 colorBarMinimum -1000.0;
    String ioos_category "Location";
    String long_name "Depth";
    Float32 missing_value 9.999e+20;
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  temperature {
    Float32 _FillValue 9.999e+20;
    Float32 actual_range 4.1489, 28.931;
    Float64 colorBarMaximum 32.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Temperature";
    String long_name "Temperature";
    Float32 missing_value 9.999e+20;
    String standard_name "sea_water_temperature";
    String units "Celsius";
  }
  salinity {
    Float32 _FillValue 9.999e+20;
    Float32 actual_range 32.43381, 36.79057;
    Float64 colorBarMaximum 37.0;
    Float64 colorBarMinimum 32.0;
    String ioos_category "Salinity";
    String long_name "Salinity";
    Float32 missing_value 9.999e+20;
    String standard_name "sea_water_practical_salinity";
    String units "PSU";
  }
 }
  NC_GLOBAL {
    String _NCProperties "version=2,netcdf=4.7.1,hdf5=1.10.5";
    String cdm_data_type "Point";
    String Conventions "CF-1.6, COARDS, ACDD-1.3";
    String creator_email "hunter@marine.rutgers.edu";
    String creator_name "Elias Hunter";
    String creator_url "https://marine.rutgers.edu/main/";
    String defaultGraphQuery "time,depth,temperature&time>=max(time)-14days&.draw=markers&.marker=3|5";
    Float64 Easternmost_Easting -69.91571;
    String featureType "Point";
    Float64 geospatial_lat_max 43.94574;
    Float64 geospatial_lat_min 38.38585;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -69.91571;
    Float64 geospatial_lon_min -74.48756;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 0.21;
    Float64 geospatial_vertical_min -1003.65;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"File created on 2017-09-25 13:27:45
2024-04-20T05:07:37Z (local files)
2024-04-20T05:07:37Z https://www.myroms.org:8443/tabledap/PIONEER_MOAS_TEMP_SALT_GL388.das";
    String infoUrl "https://marine.rutgers.edu/main/";
    String institution "Rutgers University";
    String keywords "asset, auv, data, density, depth, Earth Science > Oceans > Ocean Temperature > Water Temperature, Earth Science > Oceans > Salinity/Density > Salinity, GL388, glider, initiative, latitude, longitude, moule, observatory, ocean, oceans, pioneer, practical, rutgers, salinity, sea, sea_water_practical_salinity, sea_water_temperature, seawater, temperature, time, university, water";
    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 43.94574;
    String platform "GL388";
    String source_URL "http://oceanobservatories.org/";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 38.38585;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary "Ocean Observatory Initiative, Pioneer Mobile Asset Data: GL388";
    String time_coverage_end "2020-02-20T17:15:51Z";
    String time_coverage_start "2014-10-06T20:24:24Z";
    String title "Ocean Observatory Initiative, Pioneer Mobile Asset Data: GL388";
    Float64 Westernmost_Easting -74.48756;
  }
}

 

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