CEOTR ERDDAP
Ocean Observing System
Compliance Complete Report
Compliance Dataset Results

CF 1.8 IOOS Compliance Report on ERDDAP datasets
You can translate the content of this page by selecting a language in the select box.

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  BIO/DFO CTD Stations Subscribe RSS
Institution:  DFO   (Dataset ID: bio_ctd_public_bio_ctd_stations)
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: 
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 ioos_category "Identifier";
    String long_name "Station Id";
  }
  bio_mission_number {
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Statistics";
    String long_name "Bio Mission Number";
  }
  mission_event_number {
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Statistics";
    String long_name "Mission Event Number";
  }
  station_name {
    String ioos_category "Unknown";
    String long_name "Station Name";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    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";
    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";
  }
  geom {
    String ioos_category "Unknown";
    String long_name "Geom";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String ioos_category "Time";
    String long_name "Timestamp";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00.000Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  max_pressure {
    String ioos_category "Pressure";
    String long_name "Max Pressure";
  }
  records {
    String ioos_category "Unknown";
    String long_name "Records";
  }
  file_name {
    String ioos_category "Unknown";
    String long_name "File Name";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_name "DFO";
    String creator_url "http://www.bio.gc.ca/science/monitoring-monitorage/bbmp-pobb/bbmp-pobb-en.php";
    String featureType "Point";
    String geospatial_lat_units "degrees_north";
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-21T08:39:18Z (source database)
2024-11-21T08:39:18Z https://data.ceotr.ca/tabledap/bio_ctd_public_bio_ctd_stations.das";
    String infoUrl "http://www.bio.gc.ca/science/monitoring-monitorage/bbmp-pobb/bbmp-pobb-en.php";
    String institution "DFO";
    String keywords "basin, bedford, bio, bio_mission_number, conductivity, ctd, data, department, depth, dfo, event, file, file_name, fisheries, geom, identifier, latitude, longitude, max, max_pressure, mission, mission_event_number, name, number, ocean, oceans, pressure, records, sonde, station, station_id, station_name, stations, statistics, temperature, time, timestamp";
    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 sourceUrl "(source database)";
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary "Stations where Department of Fisheries and Oceans (DFO) gathered Conductivity, Temperature, Depth (CTD) data for the Bedford Basin Monitoring Program";
    String title "BIO/DFO CTD Stations";
  }
}

 

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