PML PML's ERDDAP
Easier access to scientific data at PML
log in | ?    
Brought to you by PML NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  EQUIFy - Kincardine Lander CTD - M3 - Level 3 Subscribe RSS
Institution:  Plymouth Marine Laboratory   (Dataset ID: M3_RBR80234_e41e_b5f2_6c8e)
Range: time = 2025-08-14T16:48:30Z to 2025-09-03T09:22:30Z
Information:  Summary ? | License ? | Metadata | Background (external link) | 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: 
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 ? )
   
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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.75519011e+9, 1.75689135e+9;
    String axis "T";
    String calendar "gregorian";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  temp_cal {
    Float32 _FillValue 9.96921e+36;
    Float32 actual_range 12.90173, 13.56619;
    Float64 calibration_a 0.7977057898829553;
    String calibration_applied "true";
    Float64 calibration_b 2.6989416564380715;
    String calibration_equation "y = a * x + b";
    String calibration_method "linear";
    String calibration_source "CTD011 & CTD197 (DY197)";
    Float64 colorBarMaximum 32.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Temperature";
    String long_name "Calibrated temperature";
    String standard_name "sea_water_temperature";
    String units "degree_Celsius";
  }
 }
  NC_GLOBAL {
    String abstract 
"This dataset contains time series observations of seawater temperature and pressure recorded with an RBRconcerto CTD+ sensor (S/N 80234). The instrument measured conductivity, temperature, pressure and dissolved oxygen; however, the conductivity, salinity and oxygen data were not recoverable to a usable standard and are not included.
The sensor was deployed on the same M3 seabed mounted instrument frame as a 500kHz acoustic Doppler current profiler in the northern North Sea, near the Kincardine Floating Offshore Wind Farm. The dataset spans 14 August 2025 to 3 September 2025 and was collected during the DY197 research expedition (RRS Discovery), during which the instrument was deployed and recovered. The deployment site is located at 56.989897° N, â^'1.882947°E, and the instrument remained fixed for the duration of the deployment.
These observations were collected as part of the NERC and Crown Estate funded ECOFlow programme, EQUIFy, Establishing a Framework for Quantifiable Evidence and Impact of Ecosystem Change Throughout the Lifecycle of UK Floating Offshore Wind Farms, grant number NE/Z504099/1. EQUIFy aims to co deliver a transferable monitoring and evidence framework that quantifies ecological impacts from future floating offshore wind development across spatial and temporal scales. The temperature measurements provide environmental context for co-located observations and support EQUIFy objectives to quantify physical drivers of ecosystem change associated with floating offshore wind development.";
    String acknowledgement "EQUIFy is part of the NERC and Crown Estate funded ECOFlow programme, grant number NE/Z504099/1. The authors wish to thank the officers and crew of RRS Discovery, the NMF staff and the eSWEETS3 project for their assistance in collecting these data.";
    String analytical_protocol 
"Raw RBR concerto CTD+ data files were downloaded and processed using RBR software. Conductivity, temperature, and pressure measurements were converted to standard engineering units and salinity derived following the manufacturer’s processing routines. 
These data were then calibrated against CTD observations from casts CTD011 and CTD197. Following further assessment of data quality, the conductivity, derived salinity and oxygen channels were found to be noisy and showed indications of drift. These variables were therefore excluded from the final dataset due to insufficient confidence in their accuracy.";
    String cdm_data_type "Other";
    String contributor_institution "Scottish Government's Marine Directorate; Environmental Research Institute - University of the Highlands and Islands; Plymouth Marine Laboratory";
    String contributor_name "Rory O'Hara Murray, Benjamin Williamson, Matthew Palmer";
    String contributor_role "Data collection/processing, Data collection; Funding";
    String Conventions "CF-1.8, ACDD-1.3, COARDS";
    String CreationDate "2026/04/01 16:20:59";
    String creator_email "jwi@pml.ac.uk";
    String creator_name "Juliane Wihsgott";
    String creator_type "person";
    String creator_url "https://www.ecoflow.org.uk/about-1";
    String cruise "DY197";
    String data_quality_comments "Data quality assessment indicated that conductivity, derived salinity, and dissolved oxygen measurements were noisy and showed evidence of drift, and these variables were therefore excluded from the final dataset. Temperature data were stable throughout the deployment and provide a reliable near seabed time series";
    String date_range_human "14-Aug-2025 16:48 to 03-Sep-2025 09:22";
    String history 
"2026-07-23T22:36:20Z (local files)
2026-07-23T22:36:20Z https://erddap.eofrom.space/tabledap/M3_RBR80234_e41e_b5f2_6c8e.das";
    String infoUrl "https://www.ecoflow.org.uk/about-1";
    String institution "Plymouth Marine Laboratory";
    String keywords "bedframe, calibrated, data, deployment, earth, Earth Science > Oceans > Ocean Temperature > Water Temperature, laboratory, marine, meastro, moored, ocean, oceans, plymouth, rb80234, rbr, science, sea, sea_water_temperature, seawater, series, temp_cal, temperature, time, time series, water";
    String keywords_vocabulary "GCMD Science Keywords";
    Float64 Latitude 56.989897;
    String license "Permission is granted to EQUIFy project partner institutes and interested parties to use this dataset for research and analytical purposes only. Redistribution, republication, or any form of data sharing with unauthorized third parties is strictly prohibited without prior written consent from the data owner. All users must acknowledge the source of the dataset in any publications or outputs.";
    Float64 Longitude -1.882947;
    String metadata_version "0.1.0";
    String processing_level "3";
    String project "EQUIFy";
    String sampling_protocol 
"An RBR concerto CTD+ sensor (S/N 80234) was deployed on a stable seabed mounted frame at at site M3 (56.989897° N, â^'1.882947°E) in the northern North Sea near the Kincardine Floating Offshore Wind Farm. The instrument was deployed and recovered during the DY197 research expedition (RRS Discovery).
The CTD recorded a continuous time series of conductivity, temperature, and pressure near the seabed at a 30 s sampling interval. Dissolved oxygen was also measured by the instrument. Following later processing and quality assessment, only temperature is retained in the final dataset.
The dataset spans the full deployment period from 14 August 2025 to 3 September 2025.";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "Moored RBR Meastro (RB80234) calibrated time series from bedframe deployment";
    String time_coverage_end "2025-09-03T09:22:30Z";
    String time_coverage_start "2025-08-14T16:48:30Z";
    String title "EQUIFy - Kincardine Lander CTD - M3 - Level 3";
  }
}

 

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