BCO-DMO ERDDAP
Accessing BCO-DMO data

Make A Graph

Dataset Title:	[Molecular identification of genetic variants of Neocalanus flemingeri] - Molecular identification of genetic variants of Neocalanus flemingeri in the Gulf of Alaska from samples collected from 2015 to 2023 (Collaborative Research: Zooplankton restarts in a high-latitude marine ecosystem: species- specific recruitment and development in early spring)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_954181_v1)
Information:	Summary \| License \| Metadata \| Background \| Data Access Form \| Files

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:

X Axis:

Y Axis:

Color:

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.

Graph Settings

Marker Type:

Size:

Color:

Color Bar:

Continuity:

Scale:

Minimum:

Maximum:

N Sections:

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

)

[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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Year {
    String long_name "Year";
    String units "unitless";
  }
  Stage {
    String long_name "Stage";
    String units "unitless";
  }
  SRX {
    String long_name "Srx";
    String units "unitless";
  }
  Nf_Small {
    Int32 actual_range 0, 1384700;
    String long_name "Nf_small";
    String units "count";
  }
  Nf_Large {
    Int32 actual_range 0, 611047;
    String long_name "Nf_large";
    String units "count";
  }
  Np {
    Int32 actual_range 0, 685926;
    String long_name "Np";
    String units "count";
  }
  Nc {
    Int32 actual_range 0, 248;
    String long_name "Nc";
    String units "count";
  }
  Cg {
    Int32 actual_range 0, 235087;
    String long_name "Cg";
    String units "count";
  }
  Eb {
    Int32 actual_range 0, 6;
    String long_name "Eb";
    String units "count";
  }
  Mp {
    Int32 actual_range 0, 4;
    String long_name "Mp";
    String units "count";
  }
  BioProject {
    String long_name "Bioproject";
    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.954181.1";
    String history 
"2025-05-12T09:29:08Z (local files)
2025-05-12T09:29:08Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_954181_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/954181";
    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 "The subarctic Pacific is inhabit by three copepod congeners in the genus Neocalanus with an overlapping biogeographic range that includes the open ocean, marginal seas and fjord systems. Two distinct genetic variants of Neocalanus flemingeri have been reported from the western Pacific: the “small form” with an annual life cycle is found throughout the region, while the “large form” population with a 2-year life cycle is centered in the Sea of Okhotsk. Using a molecular approach, this study examined the genetic composition of N. flemingeri populations in the Gulf of Alaska from multiple stations over an eight-year period using existing nucleotide sequence data from RNA-Seq, Sanger sequencing and metabarcoding data. This is the first report for the occurrence of the large form in the eastern Pacific with a significant presence in fjord systems.";
    String title "[Molecular identification of genetic variants of Neocalanus flemingeri] - Molecular identification of genetic variants of Neocalanus flemingeri in the Gulf of Alaska from samples collected from 2015 to 2023 (Collaborative Research: Zooplankton restarts in a high-latitude marine ecosystem: species-specific recruitment and development in early spring)";
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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