ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Southern California Water Temperature Index, 10-day, v1.0 Subscribe RSS
Institution:  Scripps Institution of Oceanography   (Dataset ID: socal_index_10day_v1)
Range: time = 2007-01-03T05:20:00Z to 2024-03-21T00:00:00Z
Information:  Summary ? | License ? | Metadata | Background | 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: 
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 ? )
   
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.1678016e+9, 1.7109792e+9;
    String axis "T";
    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";
  }
  scti_10day {
    Float64 actual_range -1.32038104920899, 3.37834399897155;
    String long_name "SCTI 10day";
    String standard_name "sea_water_temperature_anomaly";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String contributor_name "Daniel Rudnick, Jennifer Sevadjian";
    String contributor_role "principalInvestigator, resourceProvider";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "idgdata@ucsd.edu";
    String creator_name "Scripps Institution of Oceanography";
    String creator_url "https://spraydata.ucsd.edu/";
    String doi "10.21238/S8SPRAY7292";
    String history 
"2024-05-13T07:12:54Z (local files)
2024-05-13T07:12:54Z https://spraydata.ucsd.edu/tabledap/socal_index_10day_v1.das";
    String infoUrl "https://spraydata.ucsd.edu/";
    String institution "Scripps Institution of Oceanography";
    String keywords "california, ocean, oni, temperature";
    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 publisher_email "idgdata@ucsd.edu";
    String publisher_name "Instrument Development Group";
    String publisher_type "group";
    String publisher_url "https://spraydata.ucsd.edu";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary 
"The Southern California Temperature Index (SCTI) is derived from the sea water temperature records of the California Underwater Glider Network (CUGN), a collection of over 15 years of Spray underwater glider measurements. The CUGN data provides climatologies and the interannual anomaly of the sea water temperature near the California Coast which are used to generate the SCTI.
        The Southern California Temperature Index represents a smoothed temperature anomaly variability near the coast of California, similar to the Oceanic Nino Index (ONI), using local in-situ data to provide a regional index. The Socal Index is calculated using a subset of the CUGN Line 90 glider climatology data. The index is created using water temperature data at 50-m depth for the nearhsore 200-km section of all Line 90 data extending back to 2006. These data are averaged over the 200-km section to provide a time-series of the average temperature for this area at 50-m depth. The glider data is then averaged at a 3-month (90-day) interval. This aligns the time signature of the index with the ONI and allows for comparison of the two data products. The SCTI data are updated monthly after the monthly NOAA Nino 3.4 data are released. 
        An Oceanic Niño Index variable is included with the SCTI. This variable is calculated using the Niño 3.4 index, and applying a 3-month average to it. The Niño 3.4 index is obtained from the NOAA Climate Prediction Center.";
    String time_coverage_end "2024-03-21T00:00:00Z";
    String time_coverage_start "2007-01-03T05:20:00Z";
    String title "Southern California Water Temperature Index, 10-day, v1.0";
  }
}

 

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