ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Hydrobios-CTD data collected by the CCGS Amundsen in the Canadian Arctic Subscribe RSS
Institution:  Amundsen Science   (Dataset ID: amundsen12717)
Range: longitude = -155.8006 to -48.5738°E, latitude = 53.9213 to 81.7721°N, time = 2003-10-23T17:47:00Z to (now?)
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 {
  platform_name {
    String actual_range 
"Amundsen
Amundsen";
    String long_name "Platform Name";
    String standard_name "platform_name";
  }
  platform_id {
    Int32 _FillValue 2147483647;
    Int32 actual_range 7510846, 7510846;
    String long_name "Platform WMO ID";
    String standard_name "platform_id";
  }
  filename {
    String cf_role "profile_id";
    Float64 colorBarMaximum 1050.0;
    Float64 colorBarMinimum 950.0;
    String long_name "Source File Name";
  }
  original_filename {
    String long_name "Original Filename";
  }
  section_number {
    String long_name "Section Number";
  }
  cruise_number {
    String long_name "Cruise Number";
  }
  cast_number {
    Int32 _FillValue 2147483647;
    Int32 actual_range 1, 26;
    String long_name "Cast Number";
  }
  station {
    String long_name "Station";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.06693122e+9, NaN;
    String axis "T";
    String ioos_category "Time";
    String long_name "Initial Start Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 53.9213, 81.7721;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Initial Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -155.8006, -48.5738;
    String axis "X";
    String ioos_category "Location";
    String long_name "Initial Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Pres {
    String _CoordinateAxisType "Height";
    Float64 _FillValue NaN;
    String axis "Z";
    String long_name "Sea Pressure (Sea Surface - 0)";
    String standard_name "sea_water_pressure_due_to_sea_water";
    String units "decibars";
  }
  Temp {
    Float64 _FillValue NaN;
    Float64 colorBarMaximum 32.0;
    Float64 colorBarMinimum 0.0;
    String long_name "Temperature (ITS-90)";
    String standard_name "sea_water_temperature";
    String units "degree_C";
  }
  Sal {
    Float64 _FillValue NaN;
    Float64 colorBarMaximum 37.0;
    Float64 colorBarMinimum 32.0;
    String long_name "Practical Salinity (PSS-78)";
    String standard_name "sea_water_practical_salinity";
    String units "PSU";
  }
  Net {
    Float64 _FillValue 9223372036854775807;
    Float64 actual_range 0, 9;
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String long_name "Net Number";
  }
 }
  NC_GLOBAL {
    String ccin "12717";
    String cdm_altitude_proxy "Pres";
    String cdm_data_type "Profile";
    String cdm_profile_variables "filename,platform_name,platform_id,cruise_number,cast_number,station,time,latitude,longitude";
    String comment 
"##Limitations:
Purpose: Provide core physical oceanographic data for all arctic research teams onboard the CCGS Amundsen and other interested scientists.
The Hydrobios is equipped with Conductivity, Temperature, Depth (CTD) sensors recording temperature, salinity, and pressure data in the water column. This dataset is composed of CTD profiles and specific data for the volume of water going through the nets during their operation. CTD data constitute ancillary data for all other data recorded during the CCGS Amundsen scientific expeditions by providing information on the prevailing physical oceanic conditions in which biological, chemical and physical samplings were conducted. They also provide long-term records of the basic parameters central to the study of physical oceanographic processes, more specifically water column structure, water masses characteristics and oceanic circulation, in the Canadian Arctic Ocean. For some years, the data collection surpasses the Canadian Arctic border, however, the main goal of this project is to collect data from the Canadian Arctic Ocean.

 Supplemental Information: Summary: Not Applicable Research Program(s): DFO,GreenEdge,IPY,NETCARE,IPY,ArcticNet,BREA,CASES. For further information: http://doi.org/10.5884/12717";
    String contributor_name "Forest, Alexandre;Morisset, Simon;Lévesque, Keith;Linkowski, Thomas;Zier, Juergen;ArcticNet;Amundsen Science;Amundsen Science";
    String contributor_role "principalInvestigator;originator;collaborator;collaborator;collaborator;pointOfContact,owner,distributor;owner,distributor;pointOfContact,custodian";
    String Conventions "COARDS,ACDD-1.3,CF-1.6,CF-1.7,CF-1.8,CF-1.9";
    String creator_city "Québec";
    String creator_country "Canada";
    String creator_email "pdc@arcticnet.ulaval.ca";
    String creator_institution "ArcticNet";
    String creator_name "ArcticNet";
    String creator_role "Amundsen Science Core Data Collection DATA Coordinator";
    String creator_type "institution";
    String creator_url "amundsenscience.com";
    String date_created "2024-07-17";
    String date_modified "2024-07-17T00:00:00Z";
    String doi "https://doi.org/10.5884/12717";
    Float64 Easternmost_Easting -48.5738;
    String featureType "Profile";
    Float64 geospatial_lat_max 81.7721;
    Float64 geospatial_lat_min 53.9213;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -48.5738;
    Float64 geospatial_lon_min -155.8006;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-12-14T18:01:28Z (local files)
2025-12-14T18:01:28Z https://erddap.amundsenscience.com/tabledap/amundsen12717.das";
    String id "ccin-12717";
    String infoUrl "https://www.polardata.ca/pdcsearch/PDCSearchDOI.jsp?doi_id=12717";
    String institution "Amundsen Science";
    String keywords "Arctic Ocean, Baffin Bay, Beaufort Sea, Canadian, Canadian Arctic Archipelago, Conductivity, CTD (Conductivity, CTD profiles, Depth), Greenlandic and USA Arctic Seas, Oceanography, Salinity, Temperature";
    String keywords_vocabulary "CIOOS: CIOOS Essential Ocean Variables Vocabulary";
    String license "https://creativecommons.org/licenses/by/4.0";
    Float64 max_depth_m 709.34;
    String metadata_form "https://cioos-siooc.github.io/metadata-entry-form#/en/amundsen/c8GqCtwH6sZnf3HtZhCgkOsmtoh1/ccin-12717";
    String metadata_link "https://doi.org/10.5884/12717";
    Float64 min_depth_m 1.98;
    String naming_authority "ca.cioos";
    Float64 Northernmost_Northing 81.7721;
    String pdc_ccin "12717";
    String platform "ship";
    String platform_vocabulary "https://vocab.nerc.ac.uk/collection/L06/current/";
    String product_version "1.0";
    String progress "completed";
    String project "ArcticNet,BREA,CASES,Fisheries and Oceans Canada,GreenEdge,IPY-CFL,IPY-GEOTRACES,NETCARE-Network on Climate and Aerosols";
    String publisher_city "Quebec City";
    String publisher_country "Canada";
    String publisher_email "amundsen.data@as.ulaval.ca";
    String publisher_institution "Amundsen Science";
    String publisher_name "Amundsen Science";
    String publisher_ror "https://ror.org/02s3xv195";
    String publisher_type "institution";
    String publisher_url "https://amundsenscience.com";
    String reference "http://doi.org/10.5884/12717";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 53.9213;
    String standard_name_vocabulary "CF Standard Name Table v79";
    String subsetVariables "platform_name,platform_id,section_number,cruise_number,cast_number,station";
    String summary 
"The Canadian research icebreaker CCGS Amundsen is equipped with multi-plankton sampler system called Hydrobios. The MultiNet Type Maxi, part of the system, is used for vertical collections. An integrated CTD unit is also integrated to the system and allows recording of the sampled water characteristics. This dataset is composed of CTD profiles and specific data for the volume of water going through the nets during their operation. The Hydrobios was deployed during the Amundsen scientific expeditions in the summer and fall between 2003 and 2023 with the exception of 2004, 2005, 2009, 2011 and 2012, where no data is available. The integrated CTD sensors are from the Hydrobios company itself. In-situ data belong to and are under the responsibility of the leading Nets scientists while physical and chemical data from the sensors are part of the Amundsen core data collection.

The Hydrobios-CTD data were corrected and controlled by comparing them to CTD-Rosette data when available.  Outliers and suspicious measurements were removed from the dataset. Variables are provided for every 2 decibars (dbar) between the maximum and minimum pressure recorded for each cast.";
    String time_coverage_start "2003-10-23T17:47:00Z";
    String title "Hydrobios-CTD data collected by the CCGS Amundsen in the Canadian Arctic";
    Float64 Westernmost_Easting -155.8006;
  }
}

 

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