NOAA ERDDAP
Easier access to scientific data
| ?    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  EMPA Logger Data Pressure Depth Correction Subscribe RSS
Institution:  SCCWRP   (Dataset ID: empa_logger_depth_pressure_correction)
Information:  Summary ? | License ? | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 projectid ?          "EMPA"    "EMPA"
 siteid ?          "CC-ADLC"    "SC-VEN"
 estuaryname ?          "Arroyo de la Cruz"    "Ventura River"
 stationno (unitless) ?          -88    23
 sensortype ?          "CTD"    "troll"
 sensorid ?          "04-X1704 317"    "X5994"
 buoyid ?          "9410230"    "9416841"
 samplecollectiontimestamp ?          "1/1/2022 00:00:00"    "9/9/2024 23:45:00"
 raw_pressure ?          -20.40849    2150.0
 raw_barometric_pressure ?          986.4    1034.9
 corrected_pressure ?          -1047.344    1126.855
 corrected_depth ?          -10.48055    11.27619
 last_edited_date ?          "26/3/2025 23:02:10..."    "7/3/2025 22:52:44...."
 
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 {
  projectid {
    String comment "The name of the project for data submission";
    String ioos_category "Unknown";
    String long_name "projectid";
  }
  siteid {
    String comment "Enter your 5 or 6 character site code (XX-YYYY)";
    String ioos_category "Unknown";
    String long_name "siteid";
  }
  estuaryname {
    String comment "The name of the specific estuary where the sample was collected";
    String ioos_category "Unknown";
    String long_name "estuaryname";
  }
  stationno {
    Int32 actual_range -88, 23;
    String comment "The specific station number (1, 2, or 3) where the sample was collected";
    String ioos_category "Unknown";
    String long_name "stationno";
    String units "unitless";
  }
  sensortype {
    String comment "The type of sensor (CTD, MiniDot, rugged troll, tidbit)";
    String ioos_category "Unknown";
    String long_name "sensortype";
  }
  sensorid {
    String comment "The serial number of the sensor.";
    String ioos_category "Unknown";
    String long_name "sensorid";
  }
  buoyid {
    String comment "BuoyID associated with the sensorID";
    String ioos_category "Unknown";
    String long_name "buoyid";
  }
  samplecollectiontimestamp {
    String comment "Timestamp of logger data";
    String ioos_category "Time";
    String long_name "samplecollectiontimestamp";
  }
  raw_pressure {
    Float32 actual_range -20.40849, 2150.0;
    String comment "Unadjusted pressure reading";
    String ioos_category "Pressure";
    String long_name "raw_pressure";
  }
  raw_barometric_pressure {
    Float32 actual_range 986.4, 1034.9;
    String comment "Unadjusted barometric pressure reading from buoy";
    String ioos_category "Pressure";
    String long_name "raw_barometric_pressure";
  }
  corrected_pressure {
    Float32 actual_range -1047.344, 1126.855;
    String comment "Pressure reading with corrections applied";
    String ioos_category "Pressure";
    String long_name "corrected_pressure";
  }
  corrected_depth {
    Float32 actual_range -10.48055, 11.27619;
    String comment "Depth reading based on corrected pressure";
    String ioos_category "Location";
    String long_name "corrected_depth";
  }
  last_edited_date {
    String comment "Last modified timestamp";
    String ioos_category "Time";
    String long_name "last_edited_date";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.10, ACDD-1.3";
    String creator_email "janw@sccwrp.org";
    String creator_name "Jan Walker";
    String creator_type "Institution";
    String geospatial_lat_max "39.5495";
    String geospatial_lat_min "33.0335";
    String geospatial_lon_max "-117.2925";
    String geospatial_lon_min "-123.7832";
    String history 
"2026-04-16T12:33:03Z http://erddap.sccwrp.org/erddap/files/empa_logger_depth_pressure_correction/logger-raw-depth-correction-publish.csv
2026-04-16T12:33:03Z https://erddap.sccwrp.org/erddap/tabledap/empa_logger_depth_pressure_correction.html";
    String infoUrl "https://empa.sccwrp.org";
    String institution "SCCWRP";
    String keywords "Baseline MPA monitoring, EMPA, Estuary, Sensor, Southern California Coastal Water Research Project, Water quality, Wetland";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    String sourceUrl "http://erddap.sccwrp.org/erddap/files/empa_logger_depth_pressure_correction/logger-raw-depth-correction-publish.csv";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "The overall goal of the Estuary Marine Protected Area (EMPA) Monitoring Program is to establish a monitoring framework, including data collection, analysis, synthesis, and reporting to determine the health of estuaries in California and the efficacy of MPA designation in estuaries. As part of the initial phases of the program, we developed standard protocols to assess key estuarine features across different estuaries, coupled with standard data templates and guidance on analysis, synthesis, and reporting, focused on four guiding principles: flexibility, comparability, interpretability, and practicality. We developed 14 SOPs and piloted the framework at 15 estuaries in 2021. For more details on the EMPA program and framework, see https://empa.sccwrp.org. This dataset includes the continuous water logger data collected from 2015, as illustrated in SOP 1. In estuaries without continuous logger deployment, CTD Divers, PME MiniDots, Rugged Trolls, and Hobo Tidbits were deployed to collect temperature, conductivity, dissolved oxygen, and pressure (depth). Replication and length of deployment varied with estuary. In a select number of estuaries, other logger types were used due to existing monitoring; in those locations, that logger data has been included as well. For more details, see SOP 1 on https://empa.sccwrp.org. To simplify data usability, fields from both data and metadata tables have been combined to provide the user with a merged dataset. The metadata table is also included in standalone format.";
    String time_coverage_end "2023-12-31";
    String time_coverage_start "2015-05-27";
    String title "EMPA Logger Data Pressure Depth Correction";
  }
}

 

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