ERDDAP > tabledap > Data Access Form

Dataset Title:	Temperature (TEMP) and salinity (PSAL) in ES033 Campaign MO M1 - in situ data - TimeSeries Observation
Institution:	Geophysical Institute, University of Bergen   (Dataset ID: TS_TEMP_PSAL_ES033_M1_MO)
Information:	Summary | License | FGDC | ISO 19115 | Metadata | Background | Subset | Files | Make a graph

 

Variable	Optional Constraint #1		Optional Constraint #2		Minimum    or a List of Values	Maximum
PLATFORMCODE	!= =~ <= >= = < >		!= =~ <= >= = < >		"M1-1" "M1-2" "M1-3" "M1-4" "M1-5" "M1-6" "M1-7"
ID	!= =~ <= >= = < >		!= =~ <= >= = < >		1 2 3 4 5 6 7
time (UTC)	!= =~ <= >= = < >		!= =~ <= >= = < >		2009-02-10T18:05Z	2010-02-10T21:55Z
latitude (degrees_north)	!= =~ <= >= = < >		!= =~ <= >= = < >		-74.228	-74.228
longitude (degrees_east)	!= =~ <= >= = < >		!= =~ <= >= = < >		-32.3199	-32.3199
depth (m)	!= =~ <= >= = < >		!= =~ <= >= = < >		831.0	957.0
TEMP (degrees_Celsius)	!= =~ <= >= = < >		!= =~ <= >= = < >		-1.9909	0.66
PSAL (psu)	!= =~ <= >= = < >		!= =~ <= >= = < >		34.375	34.68
CURR_U (Current u component, m/s)	!= =~ <= >= = < >		!= =~ <= >= = < >
CURR_V (Current v component, m/s)	!= =~ <= >= = < >		!= =~ <= >= = < >

 

Server-side Functions

distinct()

orderBy orderByDescending orderByClosest orderByCount orderByLimit orderByMax orderByMin orderByMinMax orderByMean orderBySum (" PLATFORMCODE ID time latitude longitude depth TEMP PSAL CURR_U CURR_V PLATFORMCODE ID time latitude longitude depth TEMP PSAL CURR_U CURR_V PLATFORMCODE ID time latitude longitude depth TEMP PSAL CURR_U CURR_V PLATFORMCODE ID time latitude longitude depth TEMP PSAL CURR_U CURR_V PLATFORMCODE ID time latitude longitude depth TEMP PSAL CURR_U CURR_V ")

File type: (more information) .asc - View OPeNDAP-style ISO-8859-1 comma-separated text. .csv - Download a ISO-8859-1 comma-separated text table (line 1: names; line 2: units; ISO 8601 times). .csvp - Download a ISO-8859-1 .csv file with line 1: name (units). Times are ISO 8601 strings. .csv0 - Download a ISO-8859-1 .csv file without column names or units. Times are ISO 8601 strings. .dataTable - A JSON file formatted for use with the Google Visualization client library (Google Charts). .das - View the dataset's metadata via an ISO-8859-1 OPeNDAP Dataset Attribute Structure (DAS). .dds - View the dataset's structure via an ISO-8859-1 OPeNDAP Dataset Descriptor Structure (DDS). .dods - OPeNDAP clients use this to download the data in the DODS binary format. .esriCsv - Download a ISO_8859_1 .csv file for ESRI's ArcGIS 9.x and below (separate date and time columns). .fgdc - View the dataset's UTF-8 FGDC .xml metadata. .geoJson - Download longitude,latitude,otherColumns data as a UTF-8 GeoJSON .json file. .graph - View a Make A Graph web page. .help - View a web page with a description of tabledap. .html - View an OPeNDAP-style HTML Data Access Form. .htmlTable - View a UTF-8 .html web page with the data in a table. Times are ISO 8601 strings. .iso19115 - View the dataset's ISO 19115-2/19139 UTF-8 .xml metadata. .itx - Download an ISO-8859-1 Igor Text File. Each response column becomes a wave. .json - View a table-like UTF-8 JSON file (missing value = 'null'; times are ISO 8601 strings). .jsonlCSV1 - View a UTF-8 JSON Lines CSV file with column names on line 1 (mv = 'null'; times are ISO 8601 strings). .jsonlCSV - View a UTF-8 JSON Lines CSV file without column names (mv = 'null'; times are ISO 8601 strings). .jsonlKVP - View a UTF-8 JSON Lines file with Key:Value pairs (missing value = 'null'; times are ISO 8601 strings). .mat - Download a MATLAB binary file. .nc - Download a flat, table-like, NetCDF-3 binary file with COARDS/CF/ACDD metadata. .ncHeader - View the UTF-8 header (the metadata) for the NetCDF-3 .nc file. .ncCF - Download a NetCDF-3 CF Discrete Sampling Geometries file (Contiguous Ragged Array). .ncCFHeader - View the UTF-8 header (the metadata) for the .ncCF file. .ncCFMA - Download a NetCDF-3 CF Discrete Sampling Geometries file (Multidimensional Array). .ncCFMAHeader - View the UTF-8 header (the metadata) for the .ncCFMA file. .nccsv - Download a NetCDF-3-like 7-bit ASCII NCCSV .csv file with COARDS/CF/ACDD metadata. .nccsvMetadata - View the dataset's metadata as the top half of a 7-bit ASCII NCCSV .csv file. .ncoJson - Download a UTF-8 NCO lvl=2 JSON file with COARDS/CF/ACDD metadata. .odvTxt - Download longitude,latitude,time,otherColumns as an ISO-8859-1 ODV Generic Spreadsheet File (.txt). .subset - View an HTML form which uses faceted search to simplify picking subsets of the data. .tsv - Download a ISO-8859-1 tab-separated text table (line 1: names; line 2: units; ISO 8601 times). .tsvp - Download a ISO-8859-1 .tsv file with line 1: name (units). Times are ISO 8601 strings. .tsv0 - Download a ISO-8859-1 .tsv file without column names or units. Times are ISO 8601 strings. .wav - Download a .wav audio file. All columns must be numeric and of the same type. .xhtml - View a UTF-8 XHTML (XML) file with the data in a table. Times are ISO 8601 strings. .kml - View a .kml file, suitable for Google Earth. .smallPdf - View a small .pdf image file with a graph or map. .pdf - View a standard, medium-sized .pdf image file with a graph or map. .largePdf - View a large .pdf image file with a graph or map. .smallPng - View a small .png image file with a graph or map. .png - View a standard, medium-sized .png image file with a graph or map. .largePng - View a large .png image file with a graph or map. .transparentPng - View a .png image file (just the data, without axes, landmask, or legend).

(Documentation / Bypass this form )
 
Submit (Please be patient. It may take a while to get the data.)

 

---

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, 7;
    String long_name "ID";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.2342891e+9, 1.2658389e+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 -74.228, -74.228;
    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.3199, -32.3199;
    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 831.0, 957.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 {
    Float32 actual_range -1.9909, 0.66;
    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;
    Float32 actual_range 34.375, 34.68;
    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;
    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;
    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.869781";
    Float64 Easternmost_Easting -32.3199;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max -74.228;
    Float64 geospatial_lat_min -74.228;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -32.3199;
    Float64 geospatial_lon_min -32.3199;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 957.0;
    Float64 geospatial_vertical_min 831.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-05-20T10:53:25Z (local files)
2024-05-20T10:53:25Z https://erddap.sochic-h2020.eu/erddap/tabledap/TS_TEMP_PSAL_ES033_M1_MO.html";
    String infoUrl "https://doi.pangaea.de/10.1594/PANGAEA.869781";
    String institution "Geophysical Institute, University of Bergen";
    String keywords "depth, direction, mooring, oceanography, physical, polar, salinity, temperature";
    String license "CC-BY 3.0";
    Float64 Northernmost_Northing -74.228;
    String owner_name "Geophysical Institute, University of Bergen";
    String owner_url "https://www.uib.no/";
    String sensros_specification "ID 1: microcat, SN 5397; ID 2: rcm7, SN 1586; ID 3: microcat, SN 5398; ID 4: sbe39, SN 3566; ID 5: microcat, SN 5449; ID 6: sbe39, SN 3251; ID 7: aquadopp, SN 06459";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -74.228;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "PLATFORMCODE,ID";
    String summary "ES033 - Mooring M1 Time Series - Moored measurements of temperature and salinity in the southern Weddell Sea, January 2009-January 2010";
    String time_coverage_end "2010-02-10T21:55Z";
    String time_coverage_start "2009-02-10T18:05Z";
    String title "Temperature (TEMP) and salinity (PSAL) in ES033 Campaign MO M1 - in situ data - TimeSeries Observation";
    Float64 Westernmost_Easting -32.3199;
  }
}

 

---

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 Data Access Protocol (DAP) and its selection constraints.

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