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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Discrete NCP and GPP on AR29, RB1904 and TN368] - Discrete Net Community and
Gross Primary Production Rates data on the US Northeastern Shelf in the SPIROPA
project during spring and summer 2018 and 2019 (Collaborative Research:
Shelfbreak Frontal Dynamics: Mechanisms of Upwelling, Net Community Production,
and Ecological Implications)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_985985_v1)
Range: longitude = -71.3372 to -69.9988°E, latitude = 39.2495 to 40.724°N, time = 2018-04-17T13:15:00Z to 2019-07-18T05:45: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 {
  Cruise {
    String long_name "Cruise";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.5239709e+9, 1.5634287e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Date_time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 39.2495, 40.724;
    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 -71.3372, -69.9988;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  GOP {
    Float32 actual_range 8.592, 366.1;
    String long_name "Gop";
    String units "mmol O2/m2/day";
  }
  NCP {
    Float32 actual_range -55.3, 200.1;
    String long_name "Ncp";
    String units "mmol O2/m2/day";
  }
  NCP_GOP {
    Float32 actual_range -0.3728928, 1.239746;
    String long_name "Ncp_gop";
    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.985985.1";
    Float64 Easternmost_Easting -69.9988;
    Float64 geospatial_lat_max 40.724;
    Float64 geospatial_lat_min 39.2495;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -69.9988;
    Float64 geospatial_lon_min -71.3372;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-10-15T16:03:37Z (local files)
2025-10-15T16:03:37Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_985985_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/985985";
    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 40.724;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 39.2495;
    String summary "Triple oxygen isotopes and O2/Ar ratios were were measured on discrete bottle samples which were collected from surface Niskins from the CTD. The samples were collected at sea into poisoned, pre-evacuated bottles and then measured on an isotope ratio mass spectrometer. The gas data was then used to calculate mixed layer depth integrated rates of gross primary production (in oxygen units = gross oxygen production) and net community production. The gas data itself is posted on BCO-DMO in the bottle CTD tables associated with this cruise. This data set contains the rates of production calculated from the gas data for those who simply want the rates rather than the gas data.  This data set has rates calculated from samples collected from cruises on the US Northeastern Shelf taking place in Spring 2018 (Ar29), spring 2019 (RB1904) and summer 2019 (TN368). There is no depth associated with each rate since the exact depth the water came from does not matter - the rate represents the production integrated over the mixed layer in all cases and the depth of collection is not the same as the mixed layer depth. CTD data posted on BCO-DMO can be used to determine depths if desired and/or mixed layer depths.";
    String time_coverage_end "2019-07-18T05:45:00Z";
    String time_coverage_start "2018-04-17T13:15:00Z";
    String title "[Discrete NCP and GPP on AR29, RB1904 and TN368] - Discrete Net Community and Gross Primary Production Rates data on the US Northeastern Shelf in the SPIROPA project during spring and summer 2018 and 2019 (Collaborative Research:  Shelfbreak Frontal Dynamics: Mechanisms of Upwelling, Net Community Production, and Ecological Implications)";
    Float64 Westernmost_Easting -71.3372;
  }
}

 

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