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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Del Mar Nearshore Mooring Temperature Data *** PRELIMINARY, No QA/QC info ***   RSS
Institution:  Scripps Institution of Oceanography, UC San Diego   (Dataset ID: delmar_temperature)
Range: longitude = 117.32 to 117.32°E, latitude = 32.93 to 32.93°N, time = 2006-02-28T09:20:00Z to 2021-05-05T21:00:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
 
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: 
[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 actual_range 
"DelMar
DelMar";
    String cf_role "timeseries_id";
    String ioos_category "Identifier";
    String long_name "Station";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 32.93, 32.93;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range 117.32, 117.32;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.1411184e+9, 1.6202484e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Unix Time GMT";
    String standard_name "time";
    String standardname "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  T_1m {
    Float32 _FillValue NaN;
    Float32 actual_range 11.56, 27.57;
    String ioos_category "Sea Level";
    String long_name "T 1M";
  }
  T_6m {
    Float32 _FillValue NaN;
    Float32 actual_range 12.29, 25.18;
    String ioos_category "Sea Level";
    String long_name "T 6M";
  }
  T_15m {
    Float32 _FillValue NaN;
    Float32 actual_range 10.2, 23.65;
    String ioos_category "Sea Level";
    String long_name "T 15M";
  }
  T_21m {
    Float32 _FillValue NaN;
    Float32 actual_range 10.66, 20.76;
    String ioos_category "Sea Level";
    String long_name "T 21M";
  }
  T_32m {
    Float32 _FillValue NaN;
    Float32 actual_range 1.76, 18.29;
    String ioos_category "Sea Level";
    String long_name "T 32M";
  }
  T_45m {
    Float32 _FillValue NaN;
    Float32 actual_range 9.84, 17.81;
    String ioos_category "Sea Level";
    String long_name "T 45M";
  }
  T_57m {
    Float32 _FillValue NaN;
    Float32 actual_range 9.63, 16.65;
    String ioos_category "Sea Level";
    String long_name "T 57M";
  }
  T_72m {
    Float32 _FillValue NaN;
    Float32 actual_range 9.69, 15.55;
    String ioos_category "Sea Level";
    String long_name "T 72M";
  }
  T_90m {
    Float32 _FillValue NaN;
    Float32 actual_range 9.53, 15.54;
    String ioos_category "Sea Level";
    String long_name "T 90M";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "station";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_name "Scripps, UC San Diego";
    String creator_url "https://scripps.ucsd.edu/";
    Float64 Easternmost_Easting 117.32;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 32.93;
    Float64 geospatial_lat_min 32.93;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 117.32;
    Float64 geospatial_lon_min 117.32;
    String geospatial_lon_units "degrees_east";
    String history 
"2021-12-04T16:51:49Z (local files)
2021-12-04T16:51:49Z http://erddap.sccoos.org/tabledap/delmar_temperature.das";
    String infoUrl "http://mooring.ucsd.edu/";
    String institution "Scripps Institution of Oceanography, UC San Diego";
    String keywords "15m, 21m, 32m, 45m, 57m, 72m, 90m, assurance, control, data, del, diego, mooring, nearshore, preliminary, quality, salinity, san, scripps, T_15m, T_1m, T_21m, T_32m, T_45m, T_57m, T_6m, T_72m, T_90m, time, unix, UnixTime_GMT";
    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 32.93;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 32.93;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "station";
    String summary "Del Mar Nearshore Mooring Temperature Data *** PRELIMINARY, No QA/QC info ***";
    String time_coverage_end "2021-05-05T21:00:00Z";
    String time_coverage_start "2006-02-28T09:20:00Z";
    String title "Del Mar Nearshore Mooring Temperature Data *** PRELIMINARY, No QA/QC info ***";
    Float64 Westernmost_Easting 117.32;
  }
}

 

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