EMODnet Physics ERDDAP Installation EMODnet Physics ERDDAP
Easier access to scientific data
log in|?   
Brought to you by EMODnet Physics    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  TCM - Physiochemical water column parameters and hydrographic time series from
river, lagoon, and open ocean sites along the Alaska Beaufort Sea coast.
Subscribe RSS
Institution:  Beaufort Lagoon Ecosystems LTER   (Dataset ID: COINS_Arctic_TCM_LTER)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
   or a List of Values ?
   Maximum ?
 
 station (Station_ID) ?          "EELD1"    "KALD2"
 time (Date Time, UTC) ?          2018-08-08T01:00Z    2019-08-13T00:00Z
  < slider >
 station_name ?          "Elson East Lagoon ..."    "Kaktovik Lagoon De..."
 latitude (degrees_north) ?          70.089    71.3379
  < slider >
 longitude (degrees_east) ?          -156.4165    -143.4434667
  < slider >
 temperature (°C) ?          -2.1672    12.3424
 speed (Speed Cm S, cm/s) ?          0.04    116.11
 heading_degree (degree) ?          0.04    359.99
 vel_N_cm_s (cm/s) ?          -113.02    32.14
 vel_E_cm_s ?          -97.41    32.65
 flags ?          "BAD"    "VALID"
 habitat_type ?      
   - +  ?
 
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.Hover here to see a list of options. Click on an option to select it.")

File type: (more information)

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


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  station {
    String long_name "Station_ID";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.53369e+9, 1.5656544e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Date Time";
    String source_name "date_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";
  }
  station_name {
    String long_name "Station Name";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 70.089, 71.3379;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -156.4165, -143.4434667;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  temperature {
    Float32 actual_range -2.1672, 12.3424;
    String long_name "Temperature";
    String units "°C";
  }
  speed {
    Float32 actual_range 0.04, 116.11;
    String long_name "Speed Cm S";
    String units "cm/s";
  }
  heading_degree {
    Float32 actual_range 0.04, 359.99;
    String long_name "Heading Degree";
    String units "degree";
  }
  vel_N_cm_s {
    Float32 actual_range -113.02, 32.14;
    String long_name "Vel N Cm S";
    String units "cm/s";
  }
  vel_E_cm_s {
    Float32 actual_range -97.41, 32.65;
    String long_name "Vel E Cm S";
  }
  flags {
    String long_name "Flags";
  }
  habitat_type {
    String long_name "Habitat Type";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String DOI "10.6073/pasta/e0e71c2d59bf7b08928061f546be6a9a";
    Float64 Easternmost_Easting -143.4434667;
    String featureType "Point";
    Float64 geospatial_lat_max 71.3379;
    Float64 geospatial_lat_min 70.089;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -143.4434667;
    Float64 geospatial_lon_min -156.4165;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-04-19T12:59:02Z (local files)
2024-04-19T12:59:02Z https://erddap.emodnet-physics.eu/erddap/tabledap/COINS_Arctic_TCM_LTER.html";
    String infoUrl "https://portal.edirepository.org/nis/metadataviewer?packageid=knb-lter-ble.3.1";
    String institution "Beaufort Lagoon Ecosystems LTER";
    String institution_url "https://ble.lternet.edu/";
    String keywords "habitat, habitat_type, heading, heading_degree, latitude, local, longitude, name, source, speed, speed_cm_s, station, station_name, temperature, temperature_C, time, type, vel, vel_E_cm_s, vel_N_cm_s";
    String license "CC-BY4.0";
    Float64 Northernmost_Northing 71.3379;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 70.089;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "habitat_type";
    String summary "To understand circulation and seasonality as part of the Beaufort Lagoon Ecosystem Long Term Ecological Research program, temperature, conductivity, salinity, pressure, depth, and current velocity are recorded hourly in situ, starting August 2018 in lagoons across the Beaufort Sea coast (Elson Lagoon, Kaktovik Lagoon, and Jago Lagoon). Moorings include combinations of 1) RBR Concerto CTDs with temperature, conductivity, and pressure sensors; 2) StarOddi CTs with temperature and conductivity sensors; and 3) Lowell TCM-1 Tilt Current meters with MAT-1 Data Loggers for velocity and bearing. In addition, during BLE LTER's annual sampling, water column physiochemical parameters (chlorophyll a, dissolved oxygen, phycoerythrin concentration, pH, temperature, conductivity, salinity) are measured by hand with a YSI data sonde at river, lagoon, and open ocean sites along the Beaufort Sea coast. Here we provide both raw and quality controlled in situ mooring data, the R scripts used for processing, and all YSI sonde data plus a subset used to calibrate and validate the in situ mooring data.";
    String time_coverage_end "2019-08-13T00:00Z";
    String time_coverage_start "2018-08-08T01:00Z";
    String title "TCM - Physiochemical water column parameters and hydrographic time series from river, lagoon, and open ocean sites along the Alaska Beaufort Sea coast.";
    String vocaboularies "SDN-P01";
    Float64 Westernmost_Easting -156.4165;
  }
}

 

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