CIOOS Atlantic ERDDAP
Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Coastal Monitoring Program Data: Digby County Subscribe RSS
Institution:  Centre for Marine Applied Research (CMAR)   (Dataset ID: wpsu-7fer)
Range: longitude = -66.22486 to -65.92824°E, latitude = 44.32015 to 44.53912°N, depth = 0.0 to 32.0m, time = 2019-01-17T14:10:00Z to 2021-11-08T17:47:19Z
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_station {
    String cf_role "timeseries_id";
    String ioos_category "Unknown";
    String long_name "Waterbody";
  }
  lease {
    String ioos_category "Unknown";
    String long_name "Lease";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 44.32015, 44.53912;
    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 -66.22486, -65.92824;
    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_start_date {
    String ioos_category "Unknown";
    String long_name "Deployment Start Date";
  }
  deployment_end_date {
    String ioos_category "Unknown";
    String long_name "Deployment End Date";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.5477342e+9, 1.636393639e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Timestamp";
    String source_name "timestamp";
    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";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    String _Unsigned "false";
    Byte actual_range 0, 32;
    String axis "Z";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  sensor {
    String ioos_category "Unknown";
    String long_name "Sensor";
  }
  Dissolved_Oxygen {
    Float32 _FillValue NaN;
    Float64 colorBarMaximum 1.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Dissolved O2";
    String long_name "Volume Fraction Of Oxygen In Sea Water";
    String standard_name "volume_fraction_of_oxygen_in_sea_water";
    String units "% saturation";
  }
  sea_water_temperature {
    Float32 _FillValue NaN;
    String ioos_category "Temperature";
    String long_name "Sea Water Temperature";
    String standard_name "sea_water_temperature";
    String units "degree_Celsius";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "waterbody_station, lease, sensor";
    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-01-19T19:29:25Z";
    Float64 Easternmost_Easting -65.92824;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 44.53912;
    Float64 geospatial_lat_min 44.32015;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -65.92824;
    Float64 geospatial_lon_min -66.22486;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 32.0;
    Float64 geospatial_vertical_min 0.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2022-11-28T20:51:55Z (local files)
2022-11-28T20:51:55Z https://cioosatlantic.ca/tabledap/wpsu-7fer.das";
    String infoUrl "https://cmar.ca/coastal-monitoring-program/";
    String institution "Centre for Marine Applied Research (CMAR)";
    String instrument "HOBO-20330419,HOBO-20495211,HOBO-20495227,VR2AR-548044,aquaMeasure-670355,aquaMeasure-670376,VR2AR-548043,HOBO-20495234,aquaMeasure-670380,HOBO-10817501,HOBO-20330414,HOBO-20495203,HOBO-20495204,HOBO-20495209,HOBO-20495220,VR2AR-548589,HOBO-20820322,HOBO-20820334,HOBO-20820490,HOBO-20820501,aquaMeasure-675014,VR2AR-548038,HOBO-20031664,HOBO-20308041,HOBO-20495210,VR2AR-548042,HOBO-20820378,HOBO-20820488,HOBO-20820489,HOBO-20820502,aquaMeasure-670351,VR2AR-549340,HOBO-20820324,HOBO-20820327,HOBO-20820329,HOBO-20820381,aquaMeasure-670375,VR2AR-549341,HOBO-10817410,HOBO-20820351,HOBO-20820379,VR2AR-549342,aquaMeasure-675015";
    String keywords "aquaculture, climate change, coast, coastal monitoring program, digby county, dissolved oxygen, downloadable data, ecosystem, environment, environmental monitoring, fisheries, fishing, nova scotia, oceanography, salinity, temperature, water quality";
    String license "Nova Scotia Open Government Licence";
    Float64 Northernmost_Northing 44.53912;
    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 44.32015;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "waterbody_station, lease, sensor";
    String summary "The Centre for Marine Applied Research (CMAR) measures environmental data throughout Nova Scotia’s coastal waters as part of the Coastal Monitoring Program. This program was initiated by the Nova Scotia Department of Fisheries and Aquaculture in 2012 and CMAR became involved in 2017. CMAR collects temperature (degrees Celsius), dissolved oxygen (% saturation), and intermittent salinity (practical salinity units) data using autonomous sensors attached to moored lines, called ‘sensor strings’. Each string is attached to the seafloor by an anchored acoustic release and suspended by a sub-surface buoy, with sensors attached at various depths. Sensor strings are typically deployed for several months, and data are measured every 1 minute to 1 hour depending on the sensor. Data are retrieved by triggering the acoustic release, enabling the sensor string to float to the surface for data download. Some data are excluded from the final dataset during quality control processes.   The Coastal Monitoring Program data is organized by county. These datasets are very large, typically exceeding the number of rows that can be viewed in Excel. We recommend using the filter options of the Open Data Portal to filter to the WATERBODY, STATION, DEPTH, VARIABLE, and/or TIMESTAMP of interest before exporting. A chart derived from the dataset also allows for interactive filtering and export (https://data.novascotia.ca/Nature-and-Environment/Coastal-Monitoring-Program-Data-Digby-County-Daily/yeii-vbir).   Coastal Monitoring Program data for other Nova Scotia counties is also available through the Open Data Portal. The \"Coastal Monitoring Program: Station Locations\" dataset on the Portal shows locations with available data (https://data.novascotia.ca/Nature-and-Environment/Coastal-Monitoring-Program-Station-Locations/cjfb-f4d4). Summary reports by county are available on the CMAR website (https://cmar.ca/2020/07/14/coastal-monitoring-program/). Data collection and retrieval are ongoing. The datasets and reports may be revised pending ongoing data collection and analyses.";
    String time_coverage_end "2021-11-08T17:47:19Z";
    String time_coverage_start "2019-01-17T14:10:00Z";
    String title "Coastal Monitoring Program Data: Digby County";
    Float64 Westernmost_Easting -66.22486;
  }
}

 

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