ERDDAP
Easier access to scientific data

Brought to you by ICATMAR

Make A Graph

Dataset Title:	BUOY TORDERA ADCP
Institution:	ICATMAR (Dataset ID: BUOY_TORD_ADCP)
Range:	longitude = 2.7698 to 2.7698°E, latitude = 41.5997 to 41.5997°N, time = 2025-12-17T03:01:00Z to 2026-06-08T06:31:00Z
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Subset \| 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 {
  station_id {
    String actual_range 
"BOIA_TORDERA
BOIA_TORDERA";
    String cf_role "timeseries_id";
    String ioos_category "Identifier";
    String long_name "Station Identifier";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 41.5997, 41.5997;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range 2.7698, 2.7698;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.76594046e+9, 1.78090026e+9;
    String axis "T";
    String calendar "gregorian";
    String cf_role "profile_id";
    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";
  }
  bin_index {
    String _CoordinateAxisType "Height";
    Float32 actual_range 1.0, 18.0;
    String axis "Z";
    Float64 colorBarMaximum 30.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Location";
    String long_name "ADCP cell index (vertical geometry pending)";
    String units "1";
  }
  NSCT_ADCP {
    Float32 _FillValue 9.96921e+36;
    Float32 actual_range -1.69, 1.43;
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String icatmar_name "NSCT";
    String ioos_category "Currents";
    String long_name "Northward sea water velocity";
    String standard_name "northward_sea_water_velocity";
    String units "m s-1";
  }
  VCSP_ADCP {
    Float32 _FillValue 9.96921e+36;
    Float32 actual_range -2.29, 0.23;
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String icatmar_name "VCSP";
    String ioos_category "Currents";
    String long_name "Upward sea water velocity";
    String standard_name "upward_sea_water_velocity";
    String units "m s-1";
  }
  EWCT_ADCP {
    Float32 _FillValue 9.96921e+36;
    Float32 actual_range -1.29, 0.82;
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String icatmar_name "EWCT";
    String ioos_category "Currents";
    String long_name "Eastward sea water velocity";
    String standard_name "eastward_sea_water_velocity";
    String units "m s-1";
  }
 }
  NC_GLOBAL {
    String access_constraint "otherRestrictions";
    String acknowledgement "Deployed and maintained by ICATMAR and ICM-CSIC. If used, please cite: ICATMAR (year), Boia Tordera, https://www.icatmar.cat";
    String cdm_altitude_proxy "bin_index";
    String cdm_data_type "TimeSeriesProfile";
    String cdm_profile_variables "time";
    String cdm_timeseries_variables "station_id, latitude, longitude";
    String Conventions "CF-1.10, ACDD-1.3, COARDS";
    String creator_email "observacions@icatmar.cat";
    String creator_name "ICATMAR";
    String creator_type "institution";
    String creator_url "https://www.icatmar.cat";
    String data_mode "R";
    Float64 Easternmost_Easting 2.7698;
    String featureType "TimeSeriesProfile";
    Float64 geospatial_lat_max 41.5997;
    Float64 geospatial_lat_min 41.5997;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 2.7698;
    Float64 geospatial_lon_min 2.7698;
    String geospatial_lon_units "degrees_east";
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"Created/updated: 2026-08-04T08:00:42Z by icatmar-buoys (ICATMAR)
2026-08-05T18:25:05Z (local files)
2026-08-05T18:25:05Z https://hebe.icm.csic.es/tabledap/BUOY_TORD_ADCP.das";
    String id "ICATMAR-BOIA-TORD-NRT-ADCP";
    String infoUrl "https://www.icatmar.cat";
    String institution "ICATMAR";
    String institution_edmo_code "5801, 280";
    String instrument "Nortek Aquadopp Profiler 400 kHz";
    String instrument_vocabulary "NERC SeaVoX Device Catalogue";
    String keywords "acoustic, adcp, boia, buoy, catal\\u00e0, circulation, ci\\u00e8ncies, csic, current, currents, data, del, depth, depth2, doppler, earth, Earth Science > Oceans > Ocean Circulation > Ocean Currents, eastward, eastward_sea_water_velocity, EWCT, governan\\u00e7a, icatmar, icm, icm-csic, institut, northward, northward_sea_water_velocity, NSCT, ocean, oceans, odas, per, profiler, recerca, science, sea, seawater, time, tordera, upward, upward_sea_water_velocity, VCSP, velocity, water";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "CC-BY-4.0";
    Float64 mooring_depth 86.0;
    String naming_authority "cat.icatmar";
    Float64 nominal_latitude 41.5997;
    Float64 nominal_longitude 2.7698;
    Float64 Northernmost_Northing 41.5997;
    String platform "moored surface buoy";
    String platform_name "Boia Tordera";
    String platform_vocabulary "GCMD Platforms";
    String processing_level "1A";
    String processing_level_meaning "Level 1 data without QC";
    String product_version "1.0";
    String project "ICATMAR Xarxa de Boies Fixes";
    String publisher_email "info@icatmar.cat";
    String publisher_name "ICATMAR";
    String publisher_type "institution";
    String publisher_url "https://www.icatmar.cat";
    String quality_control "No QC applied (NRT)";
    String sensor_depth_units "m (positive down)";
    String source "moored surface buoy";
    String source_files "oS82Messages (MSM GraphQL API)";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 41.5997;
    String standard_name_vocabulary "CF Standard Name Table v85";
    String station_name "Boia Tordera";
    String subsetVariables "station_id";
    String summary "ODAS Boia Tordera - Acoustic Doppler Current Profiler (ADCP). Real-time current profiles from Nortek Aquadopp Profiler 400 kHz at Boia Tordera (Catalan Sea).";
    String testOutOfDate "now-1day";
    String time_coverage_duration "173 days, 3:30:00";
    String time_coverage_end "2026-06-08T06:31:00Z";
    String time_coverage_resolution "PT60M";
    String time_coverage_start "2025-12-17T03:01:00Z";
    String title "BUOY TORDERA ADCP";
    Float64 Westernmost_Easting 2.7698;
  }
}

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