Make A Graph

Dataset Title:	EQUIFy - Kincardine ADCP current velocity - M3 - Level 3 - V1.0
Institution:	Plymouth Marine Laboratory (Dataset ID: M3_25_6a46_cc53_f998)
Range:	depth = -3.9550383 to 65.86108m, time = 2025-08-13T16:31:00Z to 2025-09-02T08:31:00Z
Information:	Summary \| License \| 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:

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:

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 {
  mab {
    Float64 _FillValue -9999.0;
    Float64 actual_range 3.5, 69.5;
    String ioos_category "Unknown";
    String long_name "Bin centre positions in metres above the bed (relative to the instrument)";
    String short_name "Metres above bed (relative to instrument)";
    String units "m";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.755102660001e+9, 1.756801860001e+9;
    String axis "T";
    String calendar "Gregorian";
    String ioos_category "Time";
    String long_name "Time replicated across bins for plotting";
    String short_name "time_matrix";
    String source_name "ddm";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 _FillValue -9999.0;
    Float64 actual_range -3.9550383083889784, 65.86107257023775;
    String axis "Z";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String ioos_category "Location";
    String long_name "Depth of bin centres (relative to sea bed)";
    String positive "down";
    String short_name "dpt";
    String standard_name "depth";
    String units "m";
  }
  ve {
    Float64 _FillValue -9999.0;
    Float64 actual_range -0.31503810726866127, 0.3582151986381775;
    String ioos_category "Currents";
    String long_name "E-W horizontal velocities";
    String units "m s-1";
  }
  vn {
    Float64 _FillValue -9999.0;
    Float64 actual_range -0.8609384972799612, 0.7630591314677946;
    String ioos_category "Currents";
    String long_name "N-S horizontal velocities";
    String units "m s-1";
  }
  vv {
    Float64 _FillValue -9999.0;
    Float64 actual_range -0.02354145940288921, 0.025742084463466503;
    String ioos_category "Currents";
    String long_name "Vertical 5th beam velocities";
    String units "m s-1";
  }
 }
  NC_GLOBAL {
    String abstract 
"This dataset contains full depth observations of horizontal velocities recorded with a Nortek Signature 500 acoustic Doppler current profiler (500 kHz, 5 beam configuration, S/N100680) deployed upward facing on a seabed mounted frame at site M3 in the northern North Sea, near the Kincardine Floating Offshore Wind Farm. The instrument collected 20 minute bursts at 4 Hz every hour, beginning at 21 minutes past the hour, and was deployed and recovered during the DY197 research expedition (RRS Discovery). The dataset spans 14 August 2025 at 16:31 UTC to 3 September 2025 at 08:31 UTC. 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 the ecological impacts from potential future FLOW farms. It will assess the compound and cumulative ecological, social and economic effects of FLOW at a range of scales using historical and contemporary data to underpin predictions of likely future pressures including changing marine use and within the context of a changing climate";
    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 Nortek Signature 500 files (.ad2cp) were converted to MATLAB format using Nortek Signature software. During conversion, the along beam velocities were transformed into Earth coordinate horizontal velocities (east and north) and vertical velocity, expressed in metres per second. All 4 Hz pings within each 20 minute burst were averaged to produce one hourly velocity profile. Final timestamps represent the midpoint of the 20 minute sampling window. The native bin structure of 23 depth cells at 3 m vertical resolution was retained.
        Velocity samples affected by strong sea surface echoes were removed to eliminate side lobe contamination in the upper part of the profile. The nearest bin to the transducer head also showed consistently high, comparatively elevated levels of vertical shear of the horizontal velocities squared, S2 (s 2), and relatively low beam correlations, so this bin was blanked. Compass corrections were applied using independently recorded VMADCP data from DY197.
        All variables are provided in Earth coordinates and expressed in standard SI units.";
    String averaging "20-minute burst-averaged data";
    String cdm_data_type "Other";
    String contact "jwi@pml.ac.uk";
    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 "COARDS, CF-1.6, ACDD-1.3";
    String CreatedBy "Juliane Wihsgott";
    String CreationDate "2025/12/22 12:41:30";
    String creator_email "jwi@pml.ac.uk";
    String creator_name "JWI";
    String creator_type "institution";
    String creator_url "https://www.pml.ac.uk";
    String cruise "DY197";
    String data_quality_comments "The instrument remained stable throughout the deployment due to the gimbal mounted frame, and no significant tilt or heading issues were observed. Beam correlations across most of the water column were consistent with expected performance for a 500 kHz Signature instrument, and the hourly averaged profiles provide a reliable representation of the flow field. Minor data loss occurred in the near surface and near the instrument head, which is typical for upward facing ADCPs, but these effects were handled during processing.";
    String date_range_human "14-Aug-2025 16:31 to 03-Sep-2025 08:31";
    Float64 geospatial_vertical_max 65.86107257023775;
    Float64 geospatial_vertical_min -3.9550383083889784;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2026-07-23T22:35:45Z (local files)
2026-07-23T22:35:45Z https://erddap.eofrom.space/tabledap/M3_25_6a46_cc53_f998.das";
    String infoUrl "https://www.ecoflow.org.uk/ecoflow-about";
    String institution "Plymouth Marine Laboratory";
    String keywords "acoustic, adcp, bedframe, current, currents, depth, Doppler, e-w, Kincardine, moored, n-s, North Sea, observations, profiler, velocities, velocity";
    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.";
    String long_title "Quality controlled observations of full-depth horizontal and vertical current velocities collected by a bottom mounted, upward facing Nortek Signature 500 acoustic Doppler current profiler";
    Float64 Longitude -1.882947;
    String metadata_version "0.1.0";
    String processing_level "3";
    String project "EQUIFy";
    String sampling_protocol 
"A Nortek Signature 500 ADCP (500 kHz, 5 beam configuration, S/N 100680) was deployed upward facing on a stable seabed mounted frame 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 ADCP operated in burst mode to avoid interference with the alongside echosounder and passive acoustics. Each burst consisted of 4800 samples collected at 4 Hz over a 20 minute period. The ADCP sampled every 60 minutes and began at 21 minutes past each hour. Velocities were resolved across 23 bins with a 3 m bin size, providing depth resolved coverage from above the transducer head to the near surface, with standard blanking in the near field and occasional upper bin loss under energetic sea states.
The dataset covers the full observation period from 14 August 2025 at 16:31 UTC to 3 September 2025 at 08:31 UTC.";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "Moored (bedframe) 5-beam 500kHz Acoustic Doppler Current Profiler (ADCP) velocity observations, North Sea, 14-Aug-25 - 03-Sep-25. Data are 20-minute burst-averaged. Test ADCP data. Plymouth Marine Laboratory data from a local source.";
    String time_coverage_end "2025-09-02T08:31:00Z";
    String time_coverage_start "2025-08-13T16:31:00Z";
    String title "EQUIFy - Kincardine ADCP current velocity - M3 - Level 3 - V1.0";
  }
}

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