NOAA ERDDAP
Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Compilation of Raritan Rivier cruises from 2009-2015. Subscribe RSS
Institution:  Rutgers University, Department of Marine and Coastal Sciences   (Dataset ID: RARITAN_RIVER_SURVEYS_TABLE)
Range: longitude = -74.43683 to -74.0718°E, latitude = 40.43593 to 40.56828°N, depth = -15.0 to -0.25m, time = 2009-03-06T17:50:31Z to 2015-03-27T19:33:01Z
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: 
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.236361831797e+9, 1.427484781e+9;
    String axis "T";
    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";
  }
  obs {
    Float64 _FillValue -99999.0;
    Float64 _Fillvalue -99999.0;
    Float64 actual_range 0.0, 3.1418;
    String ioos_category "Optical Properties";
    String long_name "optical backscatter";
    String units "Volts";
  }
  salinity {
    Float64 _FillValue -99999.0;
    Float64 _Fillvalue -99999.0;
    Float64 actual_range 0.09988427, 29.819902294858956;
    Float64 colorBarMaximum 37.0;
    Float64 colorBarMinimum 32.0;
    String ioos_category "Salinity";
    String long_name "salinity";
    String standard_name "sea_water_practical_salinity";
    String units "PSU";
  }
  temperature {
    Float64 _FillValue -99999.0;
    Float64 _Fillvalue -99999.0;
    Float64 actual_range 2.4411333333333336, 30.92465;
    Float64 colorBarMaximum 40.0;
    Float64 colorBarMinimum -10.0;
    String ioos_category "Temperature";
    String long_name "Temperature";
    String units "degrees C";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -74.43683203319485, -74.07179769894904;
    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";
    Float64 actual_range 40.435928341004704, 40.56827810240957;
    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";
    Float64 actual_range -15.0, -0.25;
    String axis "Z";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Conventions "CF-1.6, COARDS, ACDD-1.3";
    Float64 Easternmost_Easting -74.07179769894904;
    String featureType "Point";
    Float64 geospatial_lat_max 40.56827810240957;
    Float64 geospatial_lat_min 40.435928341004704;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -74.07179769894904;
    Float64 geospatial_lon_min -74.43683203319485;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max -0.25;
    Float64 geospatial_vertical_min -15.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"Created by Eli Hunter (hunter@marine.rutgers.edu),15-Jun-2017 09:10:08
2024-04-19T12:30:55Z (local files)
2024-04-19T12:30:55Z https://tds.marine.rutgers.edu/tabledap/RARITAN_RIVER_SURVEYS_TABLE.das";
    String infoUrl "marine.rutgers.edu";
    String institution "Rutgers University, Department of Marine and Coastal Sciences";
    String keywords "2009-2015, backscatter, compilation, cruises, data, density, depth, Earth Science > Oceans > Salinity/Density > Salinity, latitude, longitude, obs, observations, ocean, oceans, optical, optical properties, practical, properties, raritan, rivier, salinity, sea, sea_water_practical_salinity, seawater, temperature, time, 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 40.56827810240957;
    String Source "Raritan River Cruise Data";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 40.435928341004704;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary "Compilation of Raritan Rivier cruises from 2009-2015.";
    String time_coverage_end "2015-03-27T19:33:01Z";
    String time_coverage_start "2009-03-06T17:50:31Z";
    String title "Compilation of Raritan Rivier cruises from 2009-2015.";
    Float64 Westernmost_Easting -74.43683203319485;
  }
}

 

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