NOAA ERDDAP
Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > griddap > Make A Graph ?

Dataset Title:  Compilation of Raritan Rivier cruises from 2009-2015. Subscribe RSS
Institution:  Rutgers University   (Dataset ID: RARITAN_SURVEYS)
Information:  Summary ? | License ? | Metadata | Background (external link) | Data Access Form
 
Graph Type:  ?
X Axis:  ?
Y Axis:  ?
Color:  ?
 
Dimensions ?    Start ?    Stop ?
depth (m) ?     specify just 1 value →
    |< - >|
< <
time (UTC) ?
    |< - +
    -
< slider >
 
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 ? )
    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 {
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 actual_range -15.0, -0.0;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  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;
    String coordinates "time latitude longitude depth";
    String ioos_category "Optical Properties";
    String long_name "optical backscatter";
    String units "Volts";
  }
  salinity {
    Float64 _FillValue -99999.0;
    Float64 _Fillvalue -99999.0;
    Float64 colorBarMaximum 37.0;
    Float64 colorBarMinimum 32.0;
    String coordinates "time latitude longitude depth";
    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 colorBarMaximum 40.0;
    Float64 colorBarMinimum -10.0;
    String coordinates "time latitude longitude depth";
    String ioos_category "Temperature";
    String long_name "Temperature";
    String units "degrees C";
  }
  latitude {
    UInt32 _ChunkSizes 61, 1;
    String ioos_category "Location";
    String long_name "Latitude";
    Float64 maximum 40.56827810240957;
    Float64 minimum 40.435928341004704;
    String units "degrees_east";
  }
  longitude {
    UInt32 _ChunkSizes 61, 1;
    String ioos_category "Location";
    String long_name "Longitude";
    Float64 maximum -74.07179769894904;
    Float64 minimum -74.43683203319485;
    String units "degrees_west";
  }
  NC_GLOBAL {
    String cdm_data_type "TrajectoryProfile";
    String Conventions "CF-1.6, COARDS, ACDD-1.3";
    String featureType "TrajectoryProfile";
    String history 
"Created by Eli Hunter (hunter@marine.rutgers.edu),15-Jun-2017 09:10:08
2024-03-28T13:52:40Z (local files)
2024-03-28T13:52:40Z https://tds.marine.rutgers.edu/griddap/RARITAN_SURVEYS.das";
    String infoUrl "marine.rutgers.edu";
    String institution "Rutgers University";
    String keywords "2009-2015, backscatter, compilation, cruises, data, density, depth, Earth Science > Oceans > Salinity/Density > Salinity, obs, observations, ocean, oceans, optical, optical properties, practical, properties, raritan, rivier, s\\nea, salinity, 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.";
    String Source "Raritan River Cruise Data";
    String sourceUrl "(local files)";
    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";
    String title "Compilation of Raritan Rivier cruises from 2009-2015.";
  }
}

 

Using griddap to Request Data and Graphs from Gridded Datasets

griddap lets you request a data subset, graph, or map from a gridded dataset (for example, sea surface temperature data from a satellite), via a specially formed URL. griddap uses the OPeNDAP (external link) Data Access Protocol (DAP) (external link) and its projection 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.

griddap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/griddap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/griddap/jplMURSST41.htmlTable?analysed_sst[(2002-06-01T09:00:00Z)][(-89.99):1000:(89.99)][(-179.99):1000:(180.0)]
Thus, the query is often a data variable name (e.g., analysed_sst), followed by [(start):stride:(stop)] (or a shorter variation of that) for each of the variable's dimensions (for example, [time][latitude][longitude]).

For details, see the griddap Documentation.


 
ERDDAP, Version 2.23
Disclaimers | Privacy Policy | Contact