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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  USGS, Hudson River, 01392650 Subscribe RSS
Institution:  USGS   (Dataset ID: usgs_01392650)
Range: longitude = -74.123055 to -74.12286°E, latitude = 40.711277 to 40.713333°N, depth = 0.0 to 0.0m, time = 2019-11-01T04:03:00Z to 2024-06-13T15:42:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form
Graph Type:  ?
X Axis: 
Y Axis: 
Constraints ? Optional
Constraint #1 ?
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 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.)
Then set the File Type: (File Type information)
or view the URL:
(Documentation / Bypass this form ? )
    Click on the map to specify a new center point. ?
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.57258098e+9, 1.71829332e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "time of observation";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  station_name {
    String cf_role "timeseries_id";
    String ioos_category "Identifier";
    String long_name "Platform Name";
    String standard_name "platform_name";
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 40.71127778, 40.7133333;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "station latitude";
    String standard_name "latitude";
    String units "degrees_north";
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -74.1230556, -74.1228611;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "station longitude";
    String standard_name "longitude";
    String units "degrees_east";
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 actual_range 0.0, 0.0;
    String axis "Z";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String ioos_category "Location";
    String long_name "depth of the sensor relative to sea surface";
    String positive "down";
    String standard_name "depth";
    String units "m";
  sea_water_temperature {
    Float64 _FillValue -9999.0;
    Float64 actual_range -999999.0, 37.3;
    Float64 colorBarMaximum 40.0;
    Float64 colorBarMinimum -10.0;
    String coverage_content_type "physicalMeasurement";
    String description "Temperature, water, degrees Celsius";
    String ioos_category "Temperature";
    String long_name "Sea Water Temperature";
    Float64 missing_value -9999.0;
    String platform "station_name";
    String standard_name "00010";
    String units "deg C";
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "station_name, latitude, longitude";
    String Conventions "CF-1.6, ACDD-1.3, COARDS";
    String creator_name "USGS";
    String creator_type "institution";
    String date_created "2024-06-13T15:55:57Z";
    String date_issued "2024-06-13T15:55:57Z";
    String date_metadata_modified "2024-06-13T15:55:57Z";
    String date_modified "2024-06-13T15:55:57Z";
    Float64 Easternmost_Easting -74.1228611;
    String featureType "TimeSeries";
    String geospatial_bounds "POINT(40.71127778 -74.1228611)";
    String geospatial_bounds_crs "EPSG:4326";
    String geospatial_bounds_vertical_crs "EPSG:4297";
    Float64 geospatial_lat_max 40.7133333;
    Float64 geospatial_lat_min 40.71127778;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -74.1228611;
    Float64 geospatial_lon_min -74.1230556;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 0.0;
    Float64 geospatial_vertical_min 0.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
2024-06-14T18:18:39Z (local files)
    String id "01392650";
    String infoUrl "";
    String institution "USGS";
    String keywords "above, air, air_pressure, air_temperature, between, concentration, conductivity, data, depth, difference, Difference_between_observed_and_predicted_water_surface_elevation, direction, dissolved, dissolved o2, electrical, elevation, estuary, Estuary_or_ocean_water_surface_elevation_above_NAVD_1988, Estuary_or_ocean_water_surface_elevation_above_NGVD_1929, fractional, fractional_saturation_of_oxygen_in_sea_water, hrecos, hudson, humidity, hydrology, identifier, latitude, longitude, mass, mass_concentration_of_oxygen_in_sea_water, meteorology, name, navd, ngvd, O2, observation, observed, ocean, oxygen, piermont, platform, platform_name, precipitation, predicted, pressure, radiation, rain, rainfall, relative, relative_humidity, reported, river, salinity, saturation, scale, sea, sea_water_electrical_conductivity, sea_water_ph_reported_on_total_scale, sea_water_salinity, sea_water_temperature, seawater, sensor, solar, speed, station, station_name, surface, temperature, time, total, total_solar_radiation, turbidity, water, wind, wind_from_direction, wind_speed";
    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 nodc_template_version "NODC_NetCDF_TimeSeries_Orthogonal_Template_v2.0";
    Float64 Northernmost_Northing 40.7133333;
    String platform "fixed";
    String platform_vocabulary "";
    String publisher_address "PO BOX 4610";
    String publisher_city "Newark";
    String publisher_country "USA";
    String publisher_email "";
    String publisher_institution "MARACOOS";
    String publisher_name "MARACOOS";
    String publisher_phone "(401) 789-6224";
    String publisher_postalcode "19715";
    String publisher_state "DE";
    String publisher_type "institution";
    String publisher_url "";
    String source "";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 40.71127778;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "USGS, HUDSON RIVER AT 01392650.";
    String testOutOfDate "now-1day";
    String time_coverage_duration "PT42120S";
    String time_coverage_end "2024-06-13T15:42:00Z";
    String time_coverage_resolution "PT60S";
    String time_coverage_start "2019-11-01T04:03:00Z";
    String title "USGS, Hudson River, 01392650";
    Float64 Westernmost_Easting -74.1230556;


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{?query}
For example,,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.02
Disclaimers | Privacy Policy | Contact