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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Meteorological & Ancillary - Currents Subscribe RSS
Institution:  NOAA NOS CO-OPS (Center for Operational Oceanographic Products and Services)   (Dataset ID: IOOS_Currents)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background | Data Access Form
 
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: 
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_ID {
    String cf_role "timeseries_id";
    String comment "To view the station id listing go to: https://opendap.co-ops.nos.noaa.gov/stations/index.jsp";
    String ioos_category "Identifier";
    String long_name "REQUIRED 7-character Station ID surrounded in double quotes";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  BEGIN_DATE {
    String comment "Examples: "20040321" OR "20030712 19:02"";
    String ioos_category "Time";
    String long_name "REQUIRED 8- to 14-character Begin Date (yyyymmdd hh:mi) surrounded in double quotes";
  }
  END_DATE {
    String comment "Up to one month";
    String ioos_category "Time";
    String long_name "REQUIRED 8- to 14-character End Date (yyyymmdd hh:mi) surrounded in double quotes";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String comment "Converted UTC date time stamp (E.g. 2016-10-06T14:12:00Z)";
    String ioos_category "Time";
    String long_name "The date time stamp";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  BIN_NBR {
    String ioos_category "Other";
    String long_name "Bin number";
    String standard_name "bin number";
  }
  SPEED {
    String coverage_content_type "physicalMeasurement";
    String ioos_category "Other";
    String long_name "Speed";
    String standard_name "speed";
    String units "meters per second";
  }
  DIRECTION {
    String coverage_content_type "physicalMeasurement";
    String ioos_category "Other";
    String long_name "Direction";
    String standard_name "direction";
    String units "degrees";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "STATION_ID,BEGIN_DATE,END_DATE";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String featureType "TimeSeries";
    String geospatial_lat_units "degrees_north";
    String geospatial_lon_units "degrees_east";
    String history 
"2020-09-30T09:50:35Z (source database)
2020-09-30T09:50:35Z https://opendap.co-ops.nos.noaa.gov/tabledap/IOOS_Currents.das";
    String infoUrl "https://opendap.co-ops.nos.noaa.gov/";
    String institution "NOAA NOS CO-OPS (Center for Operational Oceanographic Products and Services)";
    String keywords "altitude, atmosphere, co-ops, conductivity, density, Earth Science > Atmosphere > Altitude > Station Height, Earth Science > Oceans > Salinity/Density > Conductivity, electrical, experimental, height, identifier, noaa, nos, oceans, salinity, sea, sea_water_electrical_conductivity, seawater, sensor, station, time, water";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "The information on government servers are in the public domain, unless specifically annotated otherwise, and may be used freely by the public. Before using information obtained from this server, special attention should be given to the date and time of the data and products being displayed. This information shall not be modified in content and then presented as official government material.";
    String sourceUrl "(source database)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "These raw data have not been subjected to the National Ocean Service's quality control or quality assurance procedures and do not meet the criteria and standards of official National Ocean Service data. They are released for limited public use as preliminary data to be used only with appropriate caution.";
    String title "Meteorological & Ancillary - Currents";
  }
}

 

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