BCO-DMO ERDDAP
Accessing BCO-DMO data
log in    
Brought to you by BCO-DMO    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [Temperature Data] - Temperature data collected in the bottoms of intertidal
rock tide pools at Bodega Marine Reserve intertidal zone, between October 2017
and August 2019 (Collaborative Research: Context-dependency of top-down vs.
bottom-up effects of herbivores on marine primary producers)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_851437_v1)
Information:  Summary ? | License ? | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 time (Datetimeutc, UTC) ?          2017-10-08T02:00:00Z    2019-08-19T13:30:00Z
  < slider >
 Site (unitless) ?          "BML"    "BML"
 Pool (unitless) ?          "01A"    "18A"
 Latitude (degrees_north) ?          38.31634    38.31933
 longitude (degrees_east) ?          -123.0743    -123.0716
  < slider >
 TempC (degrees Celsius (°C)) ?          3.089    40.631
 TidBitID (unitless) ?          "LM01"    "LM22"
 Block (unitless) ?          "A"    "B"
 TrtGroup (unitless) ?          1    8
 HerbivoreTreat (unitless) ?          "High"    "Low"
 TempTreat (unitless) ?          "Ambient"    "Warmed"
 NutrientTreat (unitless) ?          "Control"    "Increased"
 
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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.507428e+9, 1.5662214e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Datetimeutc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Site {
    String long_name "Site";
    String units "unitless";
  }
  Pool {
    String long_name "Pool";
    String units "unitless";
  }
  Latitude {
    Float32 actual_range 38.31634, 38.31933;
    String long_name "Latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -123.0743, -123.0716;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  TempC {
    Float32 actual_range 3.089, 40.631;
    String long_name "Tempc";
    String units "degrees Celsius (°C)";
  }
  TidBitID {
    String long_name "Tidbitid";
    String units "unitless";
  }
  Block {
    String long_name "Block";
    String units "unitless";
  }
  TrtGroup {
    Int32 actual_range 1, 8;
    String long_name "Trtgroup";
    String units "unitless";
  }
  HerbivoreTreat {
    String long_name "Herbivoretreat";
    String units "unitless";
  }
  TempTreat {
    String long_name "Temptreat";
    String units "unitless";
  }
  NutrientTreat {
    String long_name "Nutrienttreat";
    String units "unitless";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_url "https://www.bco-dmo.org/";
    String doi "10.26008/1912/bco-dmo.851437.1";
    Float64 Easternmost_Easting -123.0716;
    Float64 geospatial_lon_max -123.0716;
    Float64 geospatial_lon_min -123.0743;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-09-19T15:09:29Z (local files)
2024-09-19T15:09:29Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_851437_v1.html";
    String infoUrl "https://www.bco-dmo.org/dataset/851437";
    String institution "BCO-DMO";
    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 "(local files)";
    String summary "Temperature data collected in the bottoms of intertidal rock tide pools at Bodega Marine Reserve intertidal zone, between October 2017 and August 2019.";
    String time_coverage_end "2019-08-19T13:30:00Z";
    String time_coverage_start "2017-10-08T02:00:00Z";
    String title "[Temperature Data] - Temperature data collected in the bottoms of intertidal rock tide pools at Bodega Marine Reserve intertidal zone, between October 2017 and August 2019 (Collaborative Research: Context-dependency of top-down vs. bottom-up effects of herbivores on marine primary producers)";
    Float64 Westernmost_Easting -123.0743;
  }
}

 

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