NOAA ERDDAP
Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  DOPPIO River Forcing Subscribe RSS
Institution:  Rutgers University   (Dataset ID: ROMS_DOPPIO_DISCHARGE)
Range: longitude = -77.22298 to -63.50177°E, latitude = 34.62787 to 45.50915°N, time = 2007-01-01T00:00:00Z to 2024-04-11T00: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 {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.1676096e+9, 1.7127936e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "river runoff time";
    String source_name "river_time";
    String standard_name "time";
    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 34.627872, 45.509148;
    String axis "Y";
    String ioos_category "Location";
    String long_name "river position latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -77.222984, -63.50177;
    String axis "X";
    String ioos_category "Location";
    String long_name "river position longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  station_id {
    Float64 actual_range 1.0, 27.0;
    String cf_role "timeseries_id";
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Other";
    String long_name "river runoff identification number";
  }
  discharge {
    Float64 actual_range -14433.877824799369, 2461.0741108452557;
    String featureType "TimeSeries";
    String ioos_category "Stream Flow";
    String long_name "river runoff vertically integrated mass transport";
    String negative "LuvSrc=T flow in negative u,v direction, LwSrc=T flow out of RHO-cell";
    String positive "LuvSrc=T flow in positive u,v direction, LwSrc=T flow into RHO-cell";
    String time "river_time";
    String units "meter3 second-1";
  }
  temperature {
    Float64 actual_range 0.0, 34.11217814300972;
    String cell_methods "s_rho: mean";
    Float64 colorBarMaximum 40.0;
    Float64 colorBarMinimum -10.0;
    String ioos_category "Temperature";
    String long_name "river runoff potential temperature";
    String time "river_time";
    String units "degree_C";
  }
  salinity {
    Float64 actual_range 0.0, 0.0;
    String cell_methods "s_rho: mean";
    Float64 colorBarMaximum 37.0;
    Float64 colorBarMinimum 32.0;
    String ioos_category "Salinity";
    String long_name "river runoff salinity";
    String standard_name "sea_water_practical_salinity";
    String time "river_time";
    String units "PSU";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "station_id,latitude,longitude";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting -63.50177;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 45.50915;
    Float64 geospatial_lat_min 34.62787;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -63.50177;
    Float64 geospatial_lon_min -77.22298;
    String geospatial_lon_units "degrees_east";
    String grd_file "grid_doppio_JJA_v9.nc";
    String history 
"Thu Feb 13 09:41:59 2020: ncwa -a s_rho /home/om/cron/rivers_doppio/doppio_rivers_1x_27.nc -O /home/om/cron/rivers_doppio/doppio_rivers_1x_27_FORERDDAP.nc
2024-03-29T09:59:12Z (local files)
2024-03-29T09:59:12Z https://tds.marine.rutgers.edu/tabledap/ROMS_DOPPIO_DISCHARGE.das";
    String infoUrl "marine.rutgers.edu";
    String institution "Rutgers University";
    String keywords "data, density, earth, Earth Science > Oceans > Salinity/Density > Salinity, forcing, hydrology, identification, integrated, mass, nena, number, ocean, oceans, potential, practical, river, river_salt, river_temp, river_transport, runoff, salinity, science, sea, sea_water_practical_salinity, seawater, statistics, temperature, time, transport, vertically, 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 NCO "netCDF Operators version 4.7.7 (Homepage = http://nco.sf.net, Code = https://github.com/nco/nco)";
    Float64 Northernmost_Northing 45.50915;
    String note "formatted to allow conversion between LuvSrc and LwSrc using function /Users/wilkin/Dropbox/sandbox/roms_rivers_shift_source_locations.m";
    String rivers "(1) Mersey R, NS; (2) Salmon R, NS; (3) Penobscot R, ME; (4) Kennebec R, ME; (5) Piscataqua R, ME; (6) Quashnet R, NH; (7) Connecticut R, CT; (8) Carmans R, NY; (9) Delaware R, NJ; (10) Susquehanna R (Chesapeake), MD; (11) Potomac R, MD; (12) James R, VA; (13) Cashie R, NC; (14) Neuse R, NC; (15) New R, NC; (16) Sackville R, NS; (17) Saint John R, ME; (18) Hudson R, NY; (19) Mullica R, NJ; (20) Pocomoke R, MD; (21) Blackstone R, RI; (22) Nanticoke R, DE;  (23) York R, VA; (24) Rappahanock R, MD; (25) Merrimack R, MA; (26) Mousam R, ME; (27) Saco R, ME;";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 34.62787;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "station_id,latitude,longitude";
    String summary "DOPPIO River Forcing. Data from a local source.";
    String testOutOfDate "now+6days";
    String time_coverage_end "2024-04-11T00:00:00Z";
    String time_coverage_start "2007-01-01T00:00:00Z";
    String Title "DOPPIO River Forcing";
    String title "DOPPIO River Forcing";
    String type "ROMS FORCING file";
    Float64 Westernmost_Easting -77.22298;
  }
}

 

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