ERDDAP
Easier access to scientific data

Brought to you by SO-CHIC

Make A Graph

Dataset Title:	Current in ES033 Campaign MO M2 - in situ data - TimeSeries Observation
Institution:	Geophysical Institute, University of Bergen (Dataset ID: TS_CURR_ES033_M2_MO)
Range:	longitude = -32.278 to -32.278°E, latitude = -73.978 to -73.978°N, depth = 1748.0 to 1879.0m, time = 2009-02-11T19:20Z to 2010-02-10T08:39Z
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 {
  PLATFORMCODE {
    String cf_role "timeseries_id";
  }
  ID {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 1, 2;
    String long_name "ID";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.23438e+9, 1.26579114e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -73.978, -73.978;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -32.278, -32.278;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 1748.0, 1879.0;
    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";
  }
  TEMP {
    String long_name "Temperature of the water column";
    String units "degrees_Celsius";
    String vocabulary "SDN:P02::TEMP";
    String vocabulary_url "https://vocab.nerc.ac.uk/collection/P02/current/TEMP/";
  }
  PSAL {
    Float32 _FillValue NaN;
    String long_name "Salinity of the water column";
    String units "psu";
    String vocabulary "SDN:P02::PSAL";
    String vocabulary_url "https://vocab.nerc.ac.uk/collection/P02/current/PSAL/";
  }
  CURR_U {
    Float64 _FillValue NaN;
    Float64 actual_range -0.1562, 0.1344;
    String long_name "Current u component";
    String units "m/s";
    String vocabulary "SDN:P02::RFVL";
    String vocabulary_url "https://vocab.nerc.ac.uk/collection/P02/current/RFVL/";
  }
  CURR_V {
    Float64 _FillValue NaN;
    Float64 actual_range -0.1968, 0.182;
    String long_name "Current v component";
    String units "m/s";
    String vocabulary "SDN:P02::RFVL";
    String vocabulary_url "https://vocab.nerc.ac.uk/collection/P02/current/RFVL/";
  }
 }
  NC_GLOBAL {
    String campaign "ES033";
    String campaign_DOI "https://doi.org/10.1594/PANGAEA.869799";
    String campaign_infoUrl "https://www.pangaea.de/expeditions/events/ES033";
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "PLATFORMCODE,ID,time";
    String citation "Fer, Ilker (2016): Current measurements in the southern Weddell Sea at mooring site M1. Geophysical Institute, University of Bergen, PANGAEA, https://doi.org/10.1594/PANGAEA.869787, In: Fer, I (2016): Moored measurements of current, temperature and salinity in the southern Weddell Sea, January 2009-January 2010. Geophysical Institute, University of Bergen, PANGAEA, https://doi.org/10.1594/PANGAEA.869799";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String DOI "https://doi.org/10.1594/PANGAEA.869788";
    Float64 Easternmost_Easting -32.278;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max -73.978;
    Float64 geospatial_lat_min -73.978;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -32.278;
    Float64 geospatial_lon_min -32.278;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 1879.0;
    Float64 geospatial_vertical_min 1748.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-05-20T11:11:31Z (local files)
2024-05-20T11:11:31Z https://erddap.sochic-h2020.eu/tabledap/TS_CURR_ES033_M2_MO.das";
    String infoUrl "https://doi.pangaea.de/10.1594/PANGAEA.869788";
    String institution "Geophysical Institute, University of Bergen";
    String keywords "current, depth, direction, mooring, oceanography, physical, polar";
    String license "CC-BY 3.0";
    Float64 Northernmost_Northing -73.978;
    String owner_name "Geophysical Institute, University of Bergen";
    String owner_url "https://www.uib.no/";
    String sensros_specification "ID 1: rcm7, SN 12313; ID 2: rdi_down, SN 11434";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -73.978;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "PLATFORMCODE,ID";
    String summary "ES033 - Mooring M2 Time Series - Moored measurements of current in the southern Weddell Sea, January 2009-January 2010.";
    String time_coverage_end "2010-02-10T08:39Z";
    String time_coverage_start "2009-02-11T19:20Z";
    String title "Current in ES033 Campaign MO M2 - in situ data - TimeSeries Observation";
    Float64 Westernmost_Easting -32.278;
  }
}

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