NOAA ERDDAP
Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  ROMS ESPRESSO Forcing file - Discharge Data Subscribe RSS
Institution:  Institute for Marine and Coastal Sciences, Rutgers University   (Dataset ID: ROMS_DISCHARGE)
Range: longitude = -77.0555 to -72.2526°E, latitude = 37.241 to 41.3668°N, time = 2003-01-01T00:00:00Z to 2018-10-16T00:00:00Z
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: 
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 {
    UInt32 _ChunkSizes 1;
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.0413792e+9, 1.539648e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Time";
    String maximum "2018-10-16 00:00:00";
    String minimum "2003-01-01 00:00:00";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    UInt32 _ChunkSizes 7;
    String _CoordinateAxisType "Lat";
    Float32 actual_range 37.241, 41.3668;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    Float64 maximum 41.3668;
    Float64 minimum 37.241;
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    UInt32 _ChunkSizes 7;
    String _CoordinateAxisType "Lon";
    Float32 actual_range -77.0555, -72.2526;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    Float64 maximum -72.2526;
    Float64 minimum -77.0555;
    String standard_name "longitude";
    String units "degrees_east";
  }
  station {
    UInt32 _ChunkSizes 7;
    Float32 actual_range 1.0, 7.0;
    String cf_role "timeseries_id";
    String ioos_category "Other";
  }
  discharge {
    UInt32 _ChunkSizes 7, 1;
    Float32 _FillValue -99999.0;
    Float32 actual_range -32122.63, -0.0;
    String featureType "TimeSeries";
    String ioos_category "Stream Flow";
    String long_name "Discharge";
    Float64 station_list NaN;
    String units "meter3 second-1";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "station,latitude,longitude";
    String Conventions "CF-1.6";
    Float64 Easternmost_Easting -72.2526;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 41.3668;
    Float64 geospatial_lat_min 37.241;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -72.2526;
    Float64 geospatial_lon_min -77.0555;
    String geospatial_lon_units "degrees_east";
    String history 
"Created by Eli Hunter (hunter@marine.rutgers.edu),15-Oct-2018 11:01:11
2024-03-29T13:23:08Z http://marine.rutggers.edu
2024-03-29T13:23:08Z https://tds.marine.rutgers.edu/tabledap/ROMS_DISCHARGE.das";
    String infoUrl "http://waterdata.usgs.gov/nwis";
    String institution "Institute for Marine and Coastal Sciences, Rutgers University";
    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 41.3668;
    String Source "http://nwis.waterservices.usgs.gov/";
    String sourceUrl "http://marine.rutggers.edu";
    Float64 Southernmost_Northing 37.241;
    String subsetVariables "station,latitude,longitude";
    String summary "Discharge data used for ROMS forcing";
    String time_coverage_end "2018-10-16T00:00:00Z";
    String time_coverage_start "2003-01-01T00:00:00Z";
    String Title "ROMS Forcing = Disharge Data";
    String title "ROMS ESPRESSO Forcing file - Discharge Data";
    Float64 Westernmost_Easting -77.0555;
  }
}

 

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