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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  West Coast Observing System (WCOS) Temperature Data, 2004-2011 Subscribe RSS
Institution:  NOAA NMSP   (Dataset ID: nmspWcosTemp)
Range: longitude = -124.932 to -119.66934°E, latitude = 33.89511 to 48.325°N, depth = 0.0 to 99.0m, time = 2004-10-07T21:10:00Z to 2011-02-12T07:32:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
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 {
  station {
    String cf_role "timeseries_id";
    String ioos_category "Identifier";
    String long_name "Station";
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -124.932, -119.66934;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 33.89511, 48.325001;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.0971834e+9, 1.29749592e+9;
    String axis "T";
    String cf_role "profile_id";
    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";
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 _FillValue -9999.0;
    Float64 actual_range 0.0, 99.0;
    String axis "Z";
    String description "Relative to Mean Sea Level (MSL)";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  Temperature {
    Float64 _FillValue 9999.0;
    Float64 actual_range 6.68, 38.25;
    Float64 colorBarMaximum 32.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Temperature";
    String long_name "Sea Water Temperature";
    String quantity "Temperature";
    String standard_name "sea_water_temperature";
    String units "degree_C";
  Temperature_flag {
    Byte actual_range 0, 9;
    String description "flag for data column, 0: no problems, 1: bad data due to malfunction or fouling, 2: suspicious data, 9: missing data";
    String ioos_category "Quality";
    String long_name "Temperature Flag";
    String standard_name "sea_water_temperature status_flag";
    String cdm_data_type "TimeSeriesProfile";
    String cdm_profile_variables "time";
    String cdm_timeseries_variables "station, longitude, latitude";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting -119.66934;
    String featureType "TimeSeriesProfile";
    Float64 geospatial_lat_max 48.325001;
    Float64 geospatial_lat_min 33.89511;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -119.66934;
    Float64 geospatial_lon_min -124.932;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 99.0;
    Float64 geospatial_vertical_min 0.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"Created by the NCDDC PISCO Temperature Profile to NetCDF converter.
    String infoUrl "";
    String institution "NOAA NMSP";
    String keywords "Earth Science > Oceans > Ocean Temperature > Water Temperature";
    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.";
    Float64 Northernmost_Northing 48.325001;
    String sourceUrl "";
    Float64 Southernmost_Northing 33.89511;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "station, longitude, latitude";
    String summary 
"The West Coast Observing System (WCOS) project provides access to temperature and currents data collected at four of the five National Marine Sanctuary sites, including Olympic Coast, Gulf of the Farallones, Monterey Bay, and Channel Islands. A semi-automated end-to-end data management system transports and transforms the data from source to archive, making the data acessible for discovery, access and analysis from multiple Internet points of entry.

The stations (and their code names) are Ano Nuevo (ANO001), San Miguel North (BAY), Santa Rosa North (BEA), Big Creek (BIG001), Bodega Head (BOD001), Cape Alava 15M (CA015), Cape Alava 42M (CA042), Cape Alava 65M (CA065), Cape Alava 100M (CA100), Cannery Row (CAN001), Cape Elizabeth 15M (CE015), Cape Elizabeth 42M (CE042), Cape Elizabeth 65M (CE065), Cape Elizabeth 100M (CE100), Cuyler Harbor (CUY), Esalen (ESA001), Point Joe (JOE001), Kalaloch 15M (KL015), Kalaloch 27M (KL027), La Cruz Rock (LAC001), Lopez Rock (LOP001), Makah Bay 15M (MB015), Makah Bay 42M (MB042), Pelican/Prisoners Area (PEL), Pigeon Point (PIG001), Plaskett Rock (PLA001), Southeast Farallon Island (SEF001), San Miguel South (SMS), Santa Rosa South (SRS), Sunset Point (SUN001), Teawhit Head 15M (TH015), Teawhit Head 31M (TH031), Teawhit Head 42M (TH042), Terrace Point 7 (TPT007), Terrace Point 8 (TPT008), Valley Anch (VAL), Weston Beach (WES001).";
    String time_coverage_end "2011-02-12T07:32:00Z";
    String time_coverage_start "2004-10-07T21:10:00Z";
    String title "West Coast Observing System (WCOS) Temperature Data, 2004-2011";
    String Version "2";
    Float64 Westernmost_Easting -124.932;


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