Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Institution:  Canada Water Office   (Dataset ID: ca_hydro_02OA041)
Range: longitude = -73.50586 to -73.50586°E, latitude = 45.46486 to 45.46486°N, time = 2019-10-01T00:00:00Z to 2019-10-29T00:00: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 {
    UInt32 _ChunkSizes 512;
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.569888e+9, 1.5723072e+9;
    String axis "T";
    String calendar "gregorian";
    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";
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 45.46486, 45.46486;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -73.50586, -73.50586;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  z {
    UInt32 _ChunkSizes 504;
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "up";
    Float64 _FillValue NaN;
    Float64 actual_range 0.0, 0.0;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Altitude";
    String positive "up";
    String standard_name "altitude";
    String units "m";
  water_surface_height_above_reference_datum_geoid_localstationdatum {
    UInt32 _ChunkSizes 512;
    Float64 _FillValue -9999.0;
    Float64 actual_range 9.938, 10.408;
    String id "1004876";
    String ioos_category "Other";
    String long_name "Water Surface Height above Datum";
    Float64 missing_value -9999.0;
    String platform "station";
    String short_name "water_surface_height_above_reference_datum";
    String standard_name "water_surface_height_above_reference_datum";
    String standard_name_url "";
    String units "m";
    String vertical_datum "LOCALSTATIONDATUM";
  station {
    String cf_role "timeseries_id";
    String ioos_category "Identifier";
    String ioos_code "urn:ioos:station:com.axiomdatascience:100971";
    String long_name "SAINT-LAURENT (FLEUVE) A LA PRAIRIE";
    String short_name "ca_hydro_02OA041";
    String type "fixed";
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "station,longitude,latitude";
    String contributor_email "";
    String contributor_name "Axiom Data Science";
    String contributor_role "processor";
    String contributor_role_vocabulary "NERC";
    String contributor_url "";
    String Conventions "IOOS-1.2, CF-1.6, ACDD-1.3, NCCSV-1.2";
    String creator_country "CAN";
    String creator_email "None";
    String creator_institution "Canada Water Office";
    String creator_name "Canada Water Office";
    String creator_sector "gov_federal";
    String creator_type "institution";
    String creator_url "";
    String defaultDataQuery "z,time,water_surface_height_above_reference_datum_geoid_localstationdatum&time>=max(time)-3days";
    Float64 Easternmost_Easting -73.50586;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 45.46486;
    Float64 geospatial_lat_min 45.46486;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -73.50586;
    Float64 geospatial_lon_min -73.50586;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 0.0;
    Float64 geospatial_vertical_min 0.0;
    String geospatial_vertical_positive "up";
    String geospatial_vertical_units "m";
    String history 
"Downloaded from Canada Water Office at
    Int32 id 100971;
    String infoUrl "";
    String institution "Canada Water Office";
    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 naming_authority "com.axiomdatascience";
    Float64 Northernmost_Northing 45.46486;
    String platform "fixed";
    String platform_name "SAINT-LAURENT (FLEUVE) A LA PRAIRIE";
    String platform_vocabulary "";
    String processing_level "Level 2";
    String publisher_country "CAN";
    String publisher_email "None";
    String publisher_institution "Canada Water Office";
    String publisher_name "Canada Water Office";
    String publisher_sector "gov_federal";
    String publisher_type "institution";
    String publisher_url "";
    String references ",,";
    String sourceUrl "";
    Float64 Southernmost_Northing 45.46486;
    String standard_name_vocabulary "CF Standard Name Table v72";
    String station_id "100971";
    String summary "Timeseries data from 'SAINT-LAURENT (FLEUVE) A LA PRAIRIE' (ca_hydro_02OA041)";
    String time_coverage_end "2019-10-29T00:00:00Z";
    String time_coverage_start "2019-10-01T00:00:00Z";
    Float64 Westernmost_Easting -73.50586;


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.23
Disclaimers | Privacy Policy | Contact