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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [SRA archive of Magallana gigas] - NCBI accession numbers and related metadata
for an SRA archive of the Pacific oyster, Magallana gigas (The genetic legacy
of an Asian oyster introduction and its disease-causing parasite)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_958631_v1)
Range: longitude = -124.0237 to 175.11°E, latitude = -40.5394 to 58.8684°N
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 {
  sample_name {
    String long_name "Sample_name";
    String units "unitless";
  }
  accession {
    String long_name "Accession";
    String units "unitless";
  }
  bioproject_accession {
    String long_name "Bioproject_accession";
    String units "unitless";
  }
  biosample_accession {
    String long_name "Biosample_accession";
    String units "unitless";
  }
  pop {
    String long_name "Pop";
    String units "unitless";
  }
  Population {
    String long_name "Population";
    String units "unitless";
  }
  Region {
    String long_name "Region";
    String units "unitless";
  }
  Region2 {
    String long_name "Region2";
    String units "unitless";
  }
  NatNon {
    String long_name "Natnon";
    String units "unitless";
  }
  Collection_Date {
    String long_name "Collection_date";
    String units "unitless";
  }
  CollectionMonth {
    String long_name "Collectionmonth";
    String units "unitless";
  }
  CollectionYear {
    String long_name "Collectionyear";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -40.5394, 58.8684;
    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.0237, 175.11;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Collector {
    String long_name "Collector";
    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.958631.1";
    Float64 Easternmost_Easting 175.11;
    Float64 geospatial_lat_max 58.8684;
    Float64 geospatial_lat_min -40.5394;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 175.11;
    Float64 geospatial_lon_min -124.0237;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-04-20T13:40:37Z (local files)
2025-04-20T13:40:37Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_958631_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/958631";
    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 58.8684;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -40.5394;
    String summary "The massive geographic expansion of terrestrial plant crops, livestock, and marine aquacultured species during the 19th and 20th centuries provided local economic benefits, stabilized food demands, and altered local ecosystems. The invasion history of these translocations remains uncertain for most species, limiting our understanding of their future adaptive potential and historical roles as vectors for co-invaded species. We provide a framework for filling this gap in invasion biology using the widely transplanted Pacific oyster (Magallana gigas) as a case study. A two-dimensional summary of population-level variation in single nucleotide polymorphisms (SNPs) in native Japan reflected the geographical map of Japan and allowed identification of the source regions for the worldwide expansion. Pacific oysters proliferate in non-native areas with environmental temperatures similar to those areas where native lineages evolved.";
    String title "[SRA archive of Magallana gigas] - NCBI accession numbers and related metadata for an SRA archive of the Pacific oyster, Magallana gigas (The genetic legacy of an Asian oyster introduction and its disease-causing parasite)";
    Float64 Westernmost_Easting -124.0237;
  }
}

 

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