NOAA ERDDAP
Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Manmade Platform Subscribe RSS
Institution:  Ocean Tracking Network   (Dataset ID: otn_aat_manmade_platform)
Range: longitude = -175.85747 to 148.82°E, latitude = -49.3686 to 74.74993°N
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | 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: 
[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 {
  platform_project_reference {
    String ioos_category "Identifier";
    String long_name "Platform Project Reference Code";
  }
  datacenter_reference {
    String ioos_category "Identifier";
    String long_name "Datacenter Reference";
  }
  platform_reference_id {
    String ioos_category "Identifier";
    String long_name "Platform Reference ID";
  }
  platform_guid {
    String ioos_category "Identifier";
    String long_name "Platform GUID";
  }
  platform_type {
    String ioos_category "Other";
    String long_name "Platform Type";
  }
  platform_depth {
    String ioos_category "Location";
    String long_name "Platform Depth";
  }
  platform_name {
    String ioos_category "Identifier";
    String long_name "Platform Name";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range -49.3686, 74.74993;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Platform Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -175.85747, 148.82;
    String axis "X";
    String ioos_category "Location";
    String long_name "Platform Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "AAT, COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting 148.82;
    Float64 geospatial_lat_max 74.74993;
    Float64 geospatial_lat_min -49.3686;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 148.82;
    Float64 geospatial_lon_min -175.85747;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-04-30T00:25:04Z (source database)
2024-04-30T00:25:04Z https://members.oceantrack.org/tabledap/otn_aat_manmade_platform.das";
    String infoUrl "http://oceantrackingnetwork.org/";
    String institution "Ocean Tracking Network";
    String keywords "ACOUSTIC RECEIVERS, ACOUSTIC TAGS, Earth Science > Biological Classification > Animals/Vertebrates > Fish";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "By accessing or using OTN Data you agree to: a) give proper attribution to all Data Providers and to OTN by using the preformed citations contained in OTN metadata reports and in the data records, b) inform OTN of publications, products or commercial applications using the data, c) acknowledge that neither the OTN nor the provider is liable for inaccuracies in the data, d) assume responsibility for investigating and understanding the limitations of the data, e) report all problems with respect to data to otndc@dal.ca. For full policy, see: https://members.oceantrack.org/data/policies.";
    Float64 Northernmost_Northing 74.74993;
    String publisher_email "otndc@dal.ca";
    String publisher_name "OTN Data Centre";
    String publisher_url "http://members.oceantrack.org";
    String sourceUrl "(source database)";
    Float64 Southernmost_Northing -49.3686;
    String standard_name_vocabulary "CF-11";
    String summary "Manmade Platform data.";
    String title "Manmade Platform";
    Float64 Westernmost_Easting -175.85747;
  }
}

 

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