UM Logo CanWIN ERDDAP
The Canadian Watershed Information Networks' ERDDAP server making scientific data more accessible
   
Brought to you by CEOS UM CCADI ECCC    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  IPY-CFL Ice Beacon Data Subscribe RSS
Institution:  Centre for Earth Observation Science   (Dataset ID: IPY_CFL_IceBeacon_1077_840c_8814)
Range: longitude = -172.5304 to 0.0°E, latitude = 69.8373 to 90.0°N, time = 2007-11-19 to 2008-08-12
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | 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 {
  project_name {
    String ioos_category "Identifier";
    String long_name "Project Name";
  }
  platform_name {
    String ioos_category "Unknown";
    String long_name "Platform Name";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.1954304e+9, 1.2184992e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Date (yyyymmdd)";
    String source_name "Date_(yyyymmdd)";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Time_hh24miss {
    String ioos_category "Time";
    String long_name "Time (hh24miss)";
  }
  beacon_ID {
    String ioos_category "Identifier";
    String long_name "Beacon ID";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 69.8373, 90.0;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String source_name "latitude_DD";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -172.5304, 0.0;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String source_name "longitude_DD";
    String standard_name "longitude";
    String units "degrees_east";
  }
  altitude_m {
    Float32 actual_range -7182.83, 8766.011;
    String ioos_category "Location";
    String long_name "Altitude";
    String standard_name "altitude";
  }
  altitude_result_value_type {
    String ioos_category "Location";
    String long_name "Altitude";
    String standard_name "altitude";
  }
  speed_m_s {
    String ioos_category "Currents";
    String long_name "Speed M S";
  }
  speed_result_value_type {
    String ioos_category "Currents";
    String long_name "Speed Result Value Type";
  }
  direction_degrees {
    Float32 actual_range 0.0, 359.99;
    Float64 colorBarMaximum 360.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Currents";
    String long_name "Direction Degrees";
  }
  direction_result_value_type {
    String ioos_category "Currents";
    String long_name "Direction Result Value Type";
  }
  fix {
    Byte actual_range 0, 1;
    String ioos_category "Unknown";
    String long_name "Fix";
  }
  sat {
    Byte actual_range 0, 16;
    String ioos_category "Unknown";
    String long_name "Sat";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_name "Barber David, Babb David, & Lukovich, Jennifer.";
    String creator_url "https://umanitoba.ca/environment-earth-resources/earth-observation-science";
    Float64 Easternmost_Easting 0.0;
    String featureType "Point";
    Float64 geospatial_lat_max 90.0;
    Float64 geospatial_lat_min 69.8373;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 0.0;
    Float64 geospatial_lon_min -172.5304;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-06-13T09:43:47Z (local files)
2024-06-13T09:43:47Z http://CanWINerddap.ad.umanitoba.ca/tabledap/IPY_CFL_IceBeacon_1077_840c_8814.das";
    String infoUrl "https://umanitoba.ca/environment-earth-resources/earth-observation-science";
    String institution "Centre for Earth Observation Science";
    String keywords "Beaufort Sea, Canadian Arctic Arctic, Climate change, Ice beacon, Sea ice";
    String keywords_vocabulary "Polar Data Catalogue";
    String license "Creative Commons Attribution 4.0 International";
    Float64 Northernmost_Northing 90.0;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 69.8373;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "project_name, platform_name, beacon_ID, altitude_result_value_type, speed_m_s, speed_result_value_type, direction_result_value_type, fix";
    String summary "Ice beacons are used to monitor sea ice motion, which is an important element in mass balance calculations, ice thermodynamic modeling, ice management and ecosystem studies. During the IPY-CFL project a total of 22 ice beacons were launched in Franklin Bay from November 2007 to May 2008. Measured parameters include latitude, longitude, speed and direction.";
    String time_coverage_end "2008-08-12";
    String time_coverage_start "2007-11-19";
    String title "IPY-CFL Ice Beacon Data";
    Float64 Westernmost_Easting -172.5304;
  }
}

 

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