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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Neocalanus flemingeri oocyte production] - Oocytes formation in post-diapause
Neocalanus flemingeri females from the R/V Sikuliaq and the R/V Tiglax in the
Northern Gulf of Alaska from 2019-06-30 to 2019-09-13 (Collaborative Proposal:
Optimizing Recruitment of Neocalanus copepods through Strategic Timing of
Reproduction and Growth in the Gulf of Alaska)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_908514_v1)
Range: longitude = -147.987 to -147.803°E, latitude = 60.278 to 60.535°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 {
  Station {
    String long_name "Station";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 60.278, 60.535;
    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 -147.987, -147.803;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Date_collected {
    String long_name "Date_collected";
    String units "unitless";
  }
  Collection_month {
    String long_name "Collection_month";
    String units "unitless";
  }
  Species {
    String long_name "Species";
    String units "unitless";
  }
  Sex {
    String long_name "Sex";
    String units "unitless";
  }
  EdU_sample_ID_number {
    String long_name "Edu_sample_id_number";
    String units "unitless";
  }
  Amount_of_EdU {
    Float32 actual_range 0.06, 0.5;
    String long_name "Amount_of_edu";
    String units "milligrams (mg)";
  }
  Incubation_date_at_start {
    String long_name "Incubation_date_at_start";
    String units "unitless";
  }
  Length_of_EdU_incubation_in_hours {
    Int32 actual_range 3, 24;
    String long_name "Length_of_edu_incubation_in_hours";
    String units "hours";
  }
  Time_point_in_days {
    Float32 actual_range 0.125, 32.0;
    String long_name "Time_point_in_days";
    String units "days";
  }
  Number_of_cells_replicating {
    Int32 actual_range 0, 295;
    String long_name "Number_of_cells_replicating";
    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.908514.1";
    Float64 Easternmost_Easting -147.803;
    Float64 geospatial_lat_max 60.535;
    Float64 geospatial_lat_min 60.278;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -147.803;
    Float64 geospatial_lon_min -147.987;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-12-03T17:13:08Z (local files)
2024-12-03T17:13:08Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_908514_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/908514";
    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 60.535;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 60.278;
    String summary "These data are from a study on the formation of oocytes in post-diapause Neocalanus flemingeri females collected from depth in Prince William Sound in the Gulf of Alaska. Collections were made during two NGA LTER cruises. After sorting, females were incubated in flasks and removed for experimental incubations and imaging. Oocyte production by post-diapause females that involved DNA replication in the ovary and oviducts was examined using incubation in 5-Ethynyl-2'-deoxyuridine (EdU). Both oogonia and oocytes incorporated EdU, with the number of EdU labeled cells peaking at 72 hours following diapause termination. Cells labeling with EdU remained high for two weeks, decreasing thereafter with no labeling detected by four weeks post diapause, and three to four weeks before spawning of the first clutch of eggs. By limiting DNA replication to the initial phase, the females effectively separate oocyte production from oocyte provisioning.";
    String title "[Neocalanus flemingeri oocyte production] - Oocytes formation in post-diapause Neocalanus flemingeri females from the R/V Sikuliaq and the R/V Tiglax in the Northern Gulf of Alaska from 2019-06-30 to 2019-09-13 (Collaborative Proposal: Optimizing Recruitment of Neocalanus copepods through Strategic Timing of Reproduction and Growth in the Gulf of Alaska)";
    Float64 Westernmost_Easting -147.987;
  }
}

 

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