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.

Make A Graph

Dataset Title:	Glider deployment #108 - EC 2019-11-05 (delayed)
Institution:	Ocean Frontier Institute (Dataset ID: EC_20191105_108_delayed)
Range:	longitude = -63.96564 to 356.045°E, latitude = 43.96402 to 156.76167°N, time = 2019-11-05T11:41:12Z to 2019-11-17T16:43:29Z
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Data Access Form \| Files

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:

X Axis:

Y Axis:

Color:

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.

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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  obs {
    Int16 actual_range 0, 1225;
    String long_name "Obs";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.572954072e+9, 1.574009009e+9;
    String axis "T";
    String calendar "gregorian";
    String comment "Measured or calculated time at each point in the time-series";
    String ioos_category "Time";
    String long_name "Time";
    String observation_type "measured";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue -9999.9;
    String accuracy "None";
    Float64 actual_range -63.96564, 356.045;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String instrument "instrument_telemetry";
    String ioos_category "Location";
    String long_name "Longitude";
    String precision "None";
    String sensor_name "EC-Telemetry_lon";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue -9999.9;
    String accuracy "None";
    Float64 actual_range 43.96402, 156.76167;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String instrument "instrument_telemetry";
    String ioos_category "Location";
    String long_name "Latitude";
    String precision "None";
    String sensor_name "EC-Telemetry_lat";
    String standard_name "latitude";
    String units "degrees_north";
  }
  gps_lat_quality_flag {
    Float64 _FillValue -9999;
    Float64 actual_range 2, 8;
    Float64 colorBarMaximum 10.0;
    Float64 colorBarMinimum 0.0;
    String flag_meanings "no_qc_performed good_data probably_good_data bad_data_that_are_potentially_correctable bad_data value_changed not_used not_used interpolated_value missing_value";
    Byte flag_values 0, 1, 2, 3, 4, 5, 6, 7, 8, 9;
    String ioos_category "Quality";
    String long_name "Gps lat quality flag";
    String standard_name "latitude";
    String units "degrees_north";
    Float64 valid_max 9;
    Float64 valid_min 0;
  }
  longitude_quality_flag {
    Float64 _FillValue -9999;
    Float64 actual_range 2, 8;
    Float64 colorBarMaximum 10;
    Float64 colorBarMinimum 0;
    String flag_meanings "no_qc_performed good_data probably_good_data bad_data_that_are_potentially_correctable bad_data value_changed not_used not_used interpolated_value missing_value";
    Byte flag_values 0, 1, 2, 3, 4, 5, 6, 7, 8, 9;
    String ioos_category "Quality";
    String long_name "Longitude quality flag";
    String standard_name "longitude";
    String units "degrees_north";
    Float64 valid_max 9;
    Float64 valid_min 0;
  }
  trajectory {
    String cf_role "trajectory_id";
    String long_name "trajectory identifier";
  }
  mose_g1000 {
    Int32 _FillValue -999;
    String comment "This is the serial number of the SV3-129 CCU Wave Glider 'EC'. Do not know the serial number for the instrument.";
    String identifier "EC-MOSE-Wave-Height";
    String long_name "MOSE-G1000";
    String platform "EC";
    String serial_number "006021";
    String short_name "mose";
    String type "instrument";
  }
  automatic_identification_system_receiver {
    Int32 _FillValue -999;
    String comment "This is the serial number of the SV3-129 Wave Glider 'EC' CCU.    Model:";
    String identifier "AIS-Records";
    String long_name "automatic identification system receiver";
    String platform "EC";
    String serial_number "006021";
    String short_name "ais";
    String type "instrument";
  }
  weather_station_200wx {
    Int32 _FillValue -999;
    String identifier "Weather-Report";
    String long_name "weather station 200WX";
    String platform "EC";
    String serial_number "60089280";
    String short_name "weather station";
    String type "instrument";
  }
  wave_glider_vehicle_status {
    Int32 _FillValue -999;
    String comment "Vehicle status reported by the wave glider command and control unit (CCU). The serial number listed is of the SV3 Wave Glider 'SV3-129' aka EC.";
    String identifier "EC-Vehicle-Status";
    String long_name "wave glider vehicle status";
    String platform "EC";
    String serial_number "006021";
    String short_name "vehicle_status";
    String type "instrument";
  }
  telemetry {
    Int32 _FillValue -999;
    String comment "Telemetry reported by wave glider command and control unit (CCU). CCU name 'SV3-129' aka EC, s/n 006021.";
    String identifier "EC-Telemetry";
    String long_name "telemetry";
    String platform "EC";
    String serial_number "006021";
    String short_name "telemetry";
    String type "instrument";
  }
  ec {
    Int32 _FillValue -999;
    String ioos_category "Identifier";
    String long_name "EC";
    String type "platform";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Trajectory";
    String cdm_trajectory_variables "trajectory";
    String comment "SV3-129 was deployed outside the Halifax harbour with a Nortek ADCP, weather station, wave height, water speed sensor and VMT.     An Air-Sea Interaction Profiler (ASIP) was deployed at the start and middle of the mission to provide additional data and validation of data measured by the ADCP mounted on the wave glider.    The goal of this mission is to collect ocean current data during storm events.";
    String contributor_name "Alex Hay, Anneke ten Doeschate, Richard Cheel, Adam Comeau, Sue L'Orsa, Tyler Byrne, Zach Viva, Kate Patterson, Xiang Ling";
    String Conventions "CF-1.6, COARDS, ACDD-1.3";
    String creator_email "ceotr@dal.ca";
    String creator_name "Coastal Environmental Observation Technology and Research (CEOTR)";
    String creator_type "institution";
    String creator_url "http://ceotr.ocean.dal.ca/gliders/";
    String date_created "2021-02-22T18:21:01Z";
    String date_issued "2021-02-22T18:21:01Z";
    String date_modified "2021-02-22T18:21:01Z";
    String deployment_number "108";
    String deployment_title "Scotian Shelf Storm Glider";
    Float64 Easternmost_Easting 356.045;
    String featureType "Trajectory";
    String format_version "IOOS_Glider_NetCDF_v3.0-noqartod.nc";
    Float64 geospatial_lat_max 156.76167;
    Float64 geospatial_lat_min 43.96402;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 356.045;
    Float64 geospatial_lon_min -63.96564;
    String geospatial_lon_units "degrees_east";
    String history 
"Observational data from a wave glider
2024-11-21T08:46:01Z (local files)
2024-11-21T08:46:01Z https://data.ceotr.ca/tabledap/EC_20191105_108_delayed.das";
    String id "EC-2019-11-05 12:39:00";
    String infoUrl "http://ceotr.ocean.dal.ca/gliders/";
    String institution "Ocean Frontier Institute";
    String keywords "200wx, 2019-11-05, automatic, automatic_identification_system_receiver, conductivity, data, delayed, density, deployment, Earth Science > Oceans > Ocean Pressure > Water Pressure, Earth Science > Oceans > Ocean Temperature > Water Temperature, Earth Science > Oceans > Salinity/Density > Conductivity, Earth Science > Oceans > Salinity/Density > Density, Earth Science > Oceans > Salinity/Density > Salinity, flag, frontier, glider, global, gps, gps_lat_quality_flag, identification, identifier, institute, latitude, longitude, longitude_quality_flag, mose_g1000, obs, observations, ocean, oceans, positioning, pressure, quality, receiver, salinity, station, status, system, telemetry, temperature, time, trajectory, vehicle, water, wave, wave_glider_vehicle_status, weather, weather_station_200wx";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "This data may be redistributed and used without restriction.";
    String Metadata_Conventions "CF-1.6, COARDS, ACDD-1.";
    String naming_authority "org.oceantrackingnetwork";
    Float64 Northernmost_Northing 156.76167;
    String platform_type "Wave Glider";
    String processing_level "Dataset taken from glider native file format and is provided as is with no expressed or implied assurance of quality assurance or quality control.";
    String project "Quantification of Ocean Turbulence in the Upper Ocean with Autonomous Vehicles";
    String publisher_email "ceotr@dal.ca";
    String publisher_name "Coastal Environmental Observation Technology and Research (CEOTR)";
    String publisher_type "institution";
    String publisher_url "http://ceotr.ocean.dal.ca/gliders/";
    String sea_name "Northwest Atlantic Ocean";
    String source "Observational data from a wave glider";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 43.96402;
    String standard_name_vocabulary "CF Standard Name Table v27";
    String summary "Glider deployment #108 - EC 2019-11-05 (delayed). Wave gliders are small solar powered platforms that harness wave energy to move horizontally on the sea surface. They can be deployed for days to several months collecting and transmitting ocean and atmospheric data. The Wave glider was designed and built by Liquid Robotics, Sunnyvale, CA, USA.";
    String testing_mission "False";
    String time_coverage_end "2019-11-17T16:43:29Z";
    String time_coverage_start "2019-11-05T11:41:12Z";
    String title "Glider deployment #108 - EC 2019-11-05 (delayed)";
    Float64 Westernmost_Easting -63.96564;
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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