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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Quantification of ciliated band length per unit protein in early echinoderm
larvae: protein data] - Quantification of ciliated band length per unit protein
in early echinoderm larvae (protein data), collected between 2020 and 2022 in
the laboratory at California State University, Long Beach. (RUI: Effects of
large inedible particles on larval feeding, planktonic larval duration, and
juvenile quality in marine invertebrates)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_914146_v1)
Information:  Summary ? | License ? | 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: 
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:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Species {
    String long_name "Species";
    String units "unitless";
  }
  Age {
    Int32 actual_range 3, 10;
    String long_name "Age";
    String units "days";
  }
  Dev {
    String long_name "Dev";
    String units "unitless";
  }
  Beaker {
    String long_name "Beaker";
    String units "unitless";
  }
  Sample {
    Int32 actual_range 1, 4;
    String long_name "Sample";
    String units "unitless";
  }
  Average {
    Float32 actual_range 18.0763, 655.2599;
    String long_name "Average";
    String units "nanograms (ng)";
  }
  sd {
    Float32 actual_range 0.7741264, 112.9388;
    String long_name "Sd";
    String units "unitless";
  }
  geospatial_bound_N {
    Float32 actual_range 33.76659, 33.76659;
    String long_name "Geospatial_bound_n";
    String units "degrees_north";
  }
  geospatial_bound_S {
    Float32 actual_range 33.68083, 33.68083;
    String long_name "Geospatial_bound_s";
    String units "degrees_north";
  }
  geospatial_bound_E {
    Float32 actual_range -118.4271, -118.4271;
    String long_name "Geospatial_bound_e";
    String units "degrees_east";
  }
  geospatial_bound_W {
    Float32 actual_range -118.0907, -118.0907;
    String long_name "Geospatial_bound_w";
    String units "degrees_east";
  }
  experiment_location_lat {
    Float32 actual_range 33.77979, 33.77979;
    String long_name "Experiment_location_lat";
    String units "degrees_north";
  }
  experiment_location_long {
    Float32 actual_range -118.1121, -118.1121;
    String long_name "Experiment_location_long";
    String units "degrees_east";
  }
  experiment_start {
    String long_name "Experiment_start";
    String units "unitless";
  }
  experiment_end {
    String long_name "Experiment_end";
    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.914146.1";
    String history 
"2024-11-15T02:45:02Z (local files)
2024-11-15T02:45:02Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_914146_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/914146";
    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 "This experiment compares the ciliated band length to protein content of eight species and the protein content of the larvae. The data was collected between 2020 and 2022 in the laboratory at California State University, Long Beach.";
    String title "[Quantification of ciliated band length per unit protein in early echinoderm larvae: protein data] - Quantification of ciliated band length per unit protein in early echinoderm larvae (protein data), collected between 2020 and 2022 in the laboratory at California State University, Long Beach. (RUI: Effects of large inedible particles on larval feeding, planktonic larval duration, and juvenile quality in marine invertebrates)";
  }
}

 

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