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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [NCBI accession numbers for S. arcuata and S. meunieri] - NCBI accession
numbers from a study of two tintinnid ciliate species, Schmidingerella arcuata
and Schmidingerella meunieri (Collaborative Research: Combining single-cell and
community 'omics' to test hypotheses about diversity and function of planktonic
ciliates)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_924260_v1)
Range: longitude = -122.7 to -72.06°E, latitude = 41.31 to 48.5°N, depth = 0.0 to 0.0m
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: 
[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";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 41.31, 48.5;
    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 -122.7, -72.06;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 0, 0;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  date {
    String long_name "Date";
    String units "unitless";
  }
  NCBI_BioprojectProject_ID {
    String long_name "Ncbi_bioprojectproject_id";
    String units "unitless";
  }
  Sample_Accession {
    String long_name "Sample_accession";
    String units "unitless";
  }
  Sequence_Accession {
    String long_name "Sequence_accession";
    String units "unitless";
  }
  sample {
    String long_name "Sample";
    String units "unitless";
  }
  other_links {
    String long_name "Other_links";
    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.924260.1";
    Float64 Easternmost_Easting -72.06;
    Float64 geospatial_lat_max 48.5;
    Float64 geospatial_lat_min 41.31;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -72.06;
    Float64 geospatial_lon_min -122.7;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 0.0;
    Float64 geospatial_vertical_min 0.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2026-10-18T11:38:26Z (local files)
2026-10-18T11:38:26Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_924260_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/924260";
    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.5;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 41.31;
    String summary "Many ciliates express their genes only after \"unscrambling\" them from the genome (portions of the gene may be reversed in the genome or expressed in a different order from what is in the genome). Because the scrambling process would have to be unique to a given species, we can use genome/transcriptome comparisons of single cells to define species boundaries. We showed that two tintinnid ciliate species that look almost identical, Schmidingerella arcuata and S. meunieri, scramble and unscramble their genes differently in the step before transcription, verifying that they represent two distinct biological species. We are also using the single-cell -omics data to better understand the evolutionary relationships (phylogenomics) among tintinnids and related planktonic ciliates. The information in this dataset indicates how to access the sequence data from NCBI.";
    String title "[NCBI accession numbers for S. arcuata and S. meunieri] - NCBI accession numbers from a study of two tintinnid ciliate species, Schmidingerella arcuata and Schmidingerella meunieri (Collaborative Research: Combining single-cell and community 'omics' to test hypotheses about diversity and function of planktonic ciliates)";
    Float64 Westernmost_Easting -122.7;
  }
}

 

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