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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Forecast Uncertianty Cones Subscribe RSS
Institution:  NOAA PMEL   (Dataset ID: osmc_cones)
Range: longitude = 0.0 to 0.0°E, latitude = 0.0 to 0.0°N, time = 1970-01-01T00:00:00Z to 1970-01-01T00:00:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | 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: 
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 {
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 0.0, 0.0;
    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 0.0, 0.0;
    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";
  }
  name {
    String cf_role "trajectory_id";
    String ioos_category "Identifier";
    String long_name "Name";
  }
  index {
    Int32 _FillValue 2147483647;
    Int32 actual_range 1, 1;
    String ioos_category "Identifier";
    String long_name "Index";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 0.0, 0.0;
    String axis "T";
    String ioos_category "Time";
    String long_name "observation date";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Trajectory";
    String cdm_trajectory_variables "name";
    String Conventions "NCCSV-1.0, COARDS, CF-1.6, ACDD-1.3";
    String creator_email "pmel.info@noaa.gov";
    String creator_name "NOAA PMEL";
    String creator_type "institution";
    String creator_url "https://www.pmel.noaa.gov/";
    Float64 Easternmost_Easting 0.0;
    String featureType "Trajectory";
    Float64 geospatial_lat_max 0.0;
    Float64 geospatial_lat_min 0.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 0.0;
    Float64 geospatial_lon_min 0.0;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-04-19T19:38:45Z (local files)
2024-04-19T19:38:45Z https://data.pmel.noaa.gov/pmel/tabledap/osmc_cones.das";
    String infoUrl "https://www.nhc.noaa.gov/gis/rss.php";
    String institution "NOAA PMEL";
    String keywords "cones, data, date, environmental, forecast, identifier, index, laboratory, latitude, longitude, marine, name, noaa, observation, pacific, pmel, time, uncertianty";
    String license 
"Data Licenses / Data Usage Restrictions
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.

Unless otherwise noted, data served through this ERDDAP server are 
not quality controlled.  Users may need to do quality control when using 
these data. These data are made available at the users own risk.";
    Float64 Northernmost_Northing 0.0;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 0.0;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary 
"These are the coordinates of the forecast track uncertainty cones. They were extract
                from the KML files which are syndicated via the RSS feed in the description.";
    String time_coverage_end "1970-01-01T00:00:00Z";
    String time_coverage_start "1970-01-01T00:00:00Z";
    String title "Forecast Uncertianty Cones";
    Float64 Westernmost_Easting 0.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.18
Disclaimers | Privacy Policy | Contact