CIOOS Atlantic ERDDAP
Easier access to scientific data
| ?    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Inverness County Wave Data Subscribe RSS
Institution:  Centre for Marine Applied Research (CMAR)   (Dataset ID: 3szy-egwz)
Range: longitude = -61.1272 to -60.9649°E, latitude = 45.94275 to 46.0002°N, time = 2015-11-25T16:30:00Z to 2023-07-24T18:40:45Z
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 {
  waterbody {
    String ioos_category "Unknown";
    String long_name "Waterbody";
  }
  station {
    String cf_role "timeseries_id";
    String ioos_category "Identifier";
    String long_name "Station";
  }
  deployment_id {
    String ioos_category "Identifier";
    String long_name "deployment id";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 45.94275, 46.0002;
    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";
    Float32 actual_range -61.1272, -60.9649;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -190.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  deployment_date {
    Float64 actual_range 1.4484096e+9, 1.6823808e+9;
    String ioos_category "Time";
    String long_name "Deployment Date";
    String source_name "deployment_date";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  retrieval_date {
    Float64 actual_range 1.4504832e+9, 1.6901568e+9;
    String ioos_category "Time";
    String long_name "Retrieval Date";
    String source_name "retrieval_date";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  sensor_model {
    String ioos_category "Identifier";
    String long_name "Sensor Model";
  }
  sensor_serial_number {
    String ioos_category "Identifier";
    String long_name "Sensor Serial Number";
  }
  deployment_sounding {
    Float32 actual_range 13.7, 24.0;
    String ioos_category "Location";
    String long_name "Deployment sounding depth";
    String standard_name "depth";
    String units "m";
  }
  wave_ensemble_interval {
    Float32 actual_range 3600.0, 7200.0;
    String ioos_category "Sea Level";
    String long_name "Wave ensemble interval";
    String units "s";
  }
  wave_pings_per_ensemble {
    Float32 actual_range 2400.0, 2400.0;
    String ioos_category "Sea Level";
    String long_name "Wave pings per ensemble";
    String units "1";
  }
  wave_averaging_interval {
    Float32 actual_range 1200.0, 1200.0;
    String ioos_category "Sea Level";
    String long_name "Wave averaging interval";
    String units "s";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.448469e+9, 1.690224045e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Timestamp";
    String source_name "timestamp_utc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  sea_surface_wave_significant_height {
    Float32 actual_range 0.0, 1.23;
    String ioos_category "Sea Level";
    String long_name "Sea Surface Wave Significant Height";
    String standard_name "sea_surface_wave_significant_height";
    String units "m";
  }
  sea_surface_wave_peak_period {
    Float32 actual_range -0.1, 25.6;
    String ioos_category "Sea Level";
    String long_name "Sea Surface Wave Peak Period";
    String standard_name "sea_surface_wave_period_of_highest_wave";
    String units "s";
  }
  sea_surface_wave_from_direction {
    Float32 actual_range -1.0, 360.0;
    String ioos_category "Sea Level";
    String long_name "Sea Surface Wave from Direction";
    String standard_name "sea_surface_wave_from_direction";
    String units "degree";
  }
  sea_water_speed {
    Float32 actual_range 0.0, 0.522;
    String ioos_category "Currents";
    String long_name "Sea Water Speed";
    String standard_name "sea_water_speed";
    String units "m s-1";
  }
  sea_water_to_direction {
    Float32 actual_range 0.0, 359.0;
    String ioos_category "Currents";
    String long_name "Sea Water to Direction";
    String standarad_name "sea_water_to_direction";
    String units "degree";
  }
  sensor_depth_below_surface {
    Float32 actual_range 7.995, 27.073;
    String ioos_category "Location";
    String long_name "Sensor depth below surface";
    String standard_name "depth";
    String units "m";
  }
  grossrange_flag_sea_surface_wave_significant_height {
    String ioos_category "Quality";
    String long_name "Gross Range Quality Flag for Sea Surface Significant Height";
  }
  grossrange_flag_sea_surface_wave_peak_period {
    String ioos_category "Quality";
    String long_name "Gross Range Quality Flag for Sea Surface Wave Peak Period";
  }
  grossrange_flag_sea_surface_wave_from_direction {
    String ioos_category "Quality";
    String long_name "Gross Range Quality flag for Sea Surface Wave From Direction";
  }
  grossrange_flag_sea_water_speed {
    String ioos_category "Quality";
    String long_name "Gross Range Quality Flag for Sea Water Speed";
  }
  grossrange_flag_sea_water_to_direction {
    String ioos_category "Quality";
    String long_name "Gross Range Quality Flag for Sea Water Direction";
  }
  grossrange_flag_sensor_depth_below_surface {
    String ioos_category "Quality";
    String long_name "Gross range Quality Flag for Sensor Depth Below Surface";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "waterbody,station,deployment_id,sensor_model,sensor_serial_number";
    String contributor_name "Centre for Marine Applied Research (CMAR)";
    String contributor_role "owner";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info(at)cmar.ca";
    String creator_name "CMAR";
    String creator_type "person";
    String date_created "2021-09-22T15:59:27Z";
    Float64 Easternmost_Easting -60.9649;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 46.0002;
    Float64 geospatial_lat_min 45.94275;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -60.9649;
    Float64 geospatial_lon_min -61.1272;
    String geospatial_lon_units "degrees_east";
    String geospatial_vertical_max "27.073";
    String geospatial_vertical_min "7.995";
    String history 
"2025-08-13T20:07:29Z (local files)
2025-08-13T20:07:29Z https://dev.cioosatlantic.ca/tabledap/3szy-egwz.das";
    String infoUrl "https://cmar.ca/coastal-monitoring-program/";
    String institution "Centre for Marine Applied Research (CMAR)";
    String instrument "Workhorse Sentinel 600kHz-8891,Sentinel_V100-24349,Sentinel_V100-24349,Sentinel_V50-254,Sentinel_V20-253";
    String keywords "adcp, aquaculture, centre for marine applied research, climate change, cmar, coast, coastal monitoring program, downloadable data, ecosystem, environment, environmental monitoring, essential ocean variables, fisheries, fishing, inverness county, nova scotia, ocean, oceanography, wave, wave data, wave direction, wave height";
    String license "Nova Scotia Open Government Licence";
    Float64 Northernmost_Northing 46.0002;
    String publisher_email "info(at)cmar.ca";
    String publisher_institution "Centre for Marine Applied Research (CMAR)";
    String publisher_name "Centre for Marine Applied Research (CMAR)";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 45.94275;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "waterbody, station, deployment_id, sensor_model, sensor_serial_number, grossrange_flag_sea_water_to_direction, grossrange_flag_sea_water_speed, grossrange_flag_sea_surface_wave_peak_period, grossrange_flag_sea_surface_wave_significant_height, grossrange_flag_sea_surface_wave_from_direction, grossrange_flag_sensor_depth_below_surface";
    String summary "The Centre for Marine Applied Research (CMAR) provides high resolution data on ocean variables from around the coast of Nova Scotia through their Coastal Monitoring Program. The program was initiated by the Nova Scotia Department of Fisheries and Aquaculture (NSDFA) in 2015. In 2019, CMAR assumed responsibility for the program and expanded its scope and mandate. Through the Wave Branch of the program, CMAR processes and publishes Wave data collected by NSDFA. The data are measured by upward facing Acoustic Doppler Current Profilers (ADCPs) that are mounted on the sea floor for 1 - 3 months. An ADCP uses sound to measure wave variables including height, period, and direction. NSDFA uses several ADCP instrument models, including the Sentinel V20, Sentinel V50, Sentinel V100, and Workhorse Sentinel 600kHz. The data is processed using Velocity and WavesMon4 Software, and then compiled and formatted for publication with CMAR’s waves R package. An automated “Gross Range” test was applied to the data to identify statistical outliers. Each data point was assigned a flag value of “Pass”, “Suspect/Of Interest”, or “Fail”. Observations flagged as “Pass” passed the test (i.e., were not considered outliers) and can be included in analyses. Observations flagged as “Fail” were considered outliers and should be excluded from most analyses. Observations flagged as “Suspect/Of Interest” were either poor quality or highlight an unusual event, and should be carefully reviewed before being included in analyses. Flags should be used as a guide only, and data users are responsible for evaluating the quality of the data prior to use in any analysis.  The \"Nova Scotia Current and Wave Data: Deployment Information\" dataset on this Portal shows all locations with available Wave data collected through CMAR’s Coastal Monitoring Program (https://data.novascotia.ca/Fishing-and-Aquaculture/Nova-Scotia-Current-and-Wave-Data-Deployment-Infor/uban-q9i2/about_data). Summary reports for each county are available on the CMAR website (https://cmar.ca/coastal-monitoring-program/). Data collection and retrieval are ongoing. The datasets and reports may be revised pending ongoing data collection and analyses.  If you have accessed any Coastal Monitoring Program data, CMAR would appreciate your anonymous feedback: https://docs.google.com/forms/d/e/1FAIpQLSe3TD6umrsVVKnQL13VVMJIpckCi2ctONJsgN7_g-4c-tKTuw/viewform. Please acknowledge the Centre for Marine Applied Research in any published material that uses this data. Contact info@cmar.ca for more information.";
    String time_coverage_end "2023-07-24T18:40:45Z";
    String time_coverage_start "2015-11-25T16:30:00Z";
    String title "Inverness County Wave Data";
    Float64 Westernmost_Easting -61.1272;
  }
}

 

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