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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Winter temperature data from northeast Pacific embayments] - Winter
temperature data from loggers placed in shallow subtidal areas in the northeast
Pacific from Oct 2019 to Jul 2024 (Collaborative Research: Tracking fine-scale
selection to temperature at the invasion front of a highly dispersive marine
predator)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_949897_v1)
Range: longitude = -124.675 to -122.6679°E, latitude = 37.90789 to 48.96176°N, time = 2019-10-01T06:59:00Z to 2024-07-16T17:30:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
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.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.")
 
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:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.56991314e+9, 1.721151e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Iso_datetime_utc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Local_DateTime {
    String long_name "Local_datetime";
    String units "unitless";
  }
  Temperature {
    Float32 actual_range -5.0, 40.92;
    String long_name "Temperature";
    String units "degrees Celsius";
  }
  File_Name {
    String long_name "File_name";
    String units "unitless";
  }
  SiteNumber {
    Int32 actual_range 138, 604;
    String long_name "Sitenumber";
    String units "unitless";
  }
  SiteName {
    String long_name "Sitename";
    String units "unitless";
  }
  HabType {
    String long_name "Habtype";
    String units "unitless";
  }
  Type {
    String long_name "Type";
    String units "unitless";
  }
  Model {
    String long_name "Model";
    String units "unitless";
  }
  SerialNumber {
    String long_name "Serialnumber";
    String units "unitless";
  }
  LoggerStartDate {
    String long_name "Loggerstartdate";
    String units "unitless";
  }
  DeploymentDate {
    String long_name "Deploymentdate";
    String units "unitless";
  }
  DeploymentTime {
    String long_name "Deploymenttime";
    String units "unitless";
  }
  DeploymentDateTime {
    String long_name "Deploymentdatetime";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 37.90789, 48.96176;
    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 -124.675, -122.6679;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  DeployedBy {
    String long_name "Deployedby";
    String units "unitless";
  }
  RetrievalDate {
    String long_name "Retrievaldate";
    String units "unitless";
  }
  AnchorType {
    String long_name "Anchortype";
    String units "unitless";
  }
  TimeVar {
    Int32 actual_range 2, 123529;
    String long_name "Timevar";
    String units "seconds";
  }
  Notes {
    String long_name "Notes";
    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 defaultDataQuery "&amp;time&lt;now";
    String doi "10.26008/1912/bco-dmo.949897.1";
    Float64 Easternmost_Easting -122.6679;
    Float64 geospatial_lat_max 48.96176;
    Float64 geospatial_lat_min 37.90789;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -122.6679;
    Float64 geospatial_lon_min -124.675;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-08-03T04:40:07Z (local files)
2025-08-03T04:40:07Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_949897_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/949897";
    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.";
    Float64 Northernmost_Northing 48.96176;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 37.90789;
    String summary "Dataset includes winter temperature logger data for a suite of embayments in the northeast Pacific. Data were collected as part of an NSF-funded project on invasive European green crab adaptation; loggers were placed in the shallow subtidal in areas determined by Washington Sea Grant's Crab Team to be good environments for green crabs. Loggers were placed by multiple collaborators without a fully standardized approach; metadata are incomplete but include all available information. Loggers used were iButtons and HOBO pendant loggers. Two loggers were placed at each site in the shallow subtidal with the goal that they were always submerged in water while deployed (i.e., not emersed). Logging frequency depended on the monitor type; iButtons captured water temperatures every 2.15 hours, and HOBO loggers recorded water temperature every 30 minutes over the winter. Deployment duration varied between years and sites, but typically ran from October - April.";
    String time_coverage_end "2024-07-16T17:30:00Z";
    String time_coverage_start "2019-10-01T06:59:00Z";
    String title "[Winter temperature data from northeast Pacific embayments] - Winter temperature data from loggers placed in shallow subtidal areas in the northeast Pacific from Oct 2019 to Jul 2024 (Collaborative Research: Tracking fine-scale selection to temperature at the invasion front of a highly dispersive marine predator)";
    Float64 Westernmost_Easting -124.675;
  }
}

 

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