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

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [Fish collection locations] - Collection locations, dates, and weight and
length measurements of individuals of three fish species from the Matagorda Bay
region of Texas in the northwestern Gulf of Mexico from 2021 to
2023 (Collaborative Research: Shifting the Hypoxia Paradigm – New Directions to
Explore the Spread and Impacts of Ocean/Great Lakes Deoxygenation)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_916418_v1)
Information:  Summary ? | License ? | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 FishID (unitless) ?          "MB002"    "PB_455"
 Station_Name (unitless) ?          "5D Steakhouse"    "The Jetties"
 Station_Latitude (degrees_north) ?          27.67968    28.70121
 longitude (Station_longitude, degrees_east) ?          -97.32014    -96.22841
  < slider >
 Date_Collected (unitless) ?          "2021-07-16"    "2023-07-01"
 Species (unitless) ?          "Micropogonias undu..."    "Sciaenops ocellatus"
 Weight_g (grams (g)) ?          15.9    38.9
 Length_mm (millimeters (mm)) ?          116    1050
 
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.Hover here to see a list of options. Click on an option to select it.")

File type: (more information)

(Documentation / Bypass this form ? )
 
(Please be patient. It may take a while to get the data.)


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  FishID {
    String long_name "Fishid";
    String units "unitless";
  }
  Station_Name {
    String long_name "Station_name";
    String units "unitless";
  }
  Station_Latitude {
    Float32 actual_range 27.67968, 28.70121;
    String long_name "Station_latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -97.32014, -96.22841;
    String axis "X";
    String ioos_category "Location";
    String long_name "Station_longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Date_Collected {
    String long_name "Date_collected";
    String units "unitless";
  }
  Species {
    String long_name "Species";
    String units "unitless";
  }
  Weight_g {
    Float32 actual_range 15.9, 38.9;
    String long_name "Weight_g";
    String units "grams (g)";
  }
  Length_mm {
    Int32 actual_range 116, 1050;
    String long_name "Length_mm";
    String units "millimeters (mm)";
  }
 }
  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.916418.1";
    Float64 Easternmost_Easting -96.22841;
    Float64 geospatial_lon_max -96.22841;
    Float64 geospatial_lon_min -97.32014;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-15T20:57:27Z (local files)
2024-11-15T20:57:27Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_916418_v1.html";
    String infoUrl "https://www.bco-dmo.org/dataset/916418";
    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 dataset describes the collection locations of individuals of three fish species (Red Drum Sciaenops ocellatus, Southern Flounder Paralichthys lethostigma, and Atlantic Croaker Micropogonias undulatus) in the Matagorda Bay region of Texas in the northwestern Gulf of Mexico. Fish carcasses were obtained from anglers at boat docks, fish cleaning stations, or other locations in the region. Fish were also obtained from bait shops where the proprietors verified the fish were sourced from the Matagorda Bay study region. These fish will be dissected to subsample muscle tissue, eye lenses, and otoliths for chemical analysis to reconstruct environmental histories (trace element proxies for hypoxia, salinity, and other parameters), mercury concentrations, and stable isotopes to reconstruct food web interactions.";
    String title "[Fish collection locations] - Collection locations, dates, and weight and length measurements of individuals of three fish species from the Matagorda Bay region of Texas in the northwestern Gulf of Mexico from 2021 to 2023 (Collaborative Research: Shifting the Hypoxia Paradigm – New Directions to Explore the Spread and Impacts of Ocean/Great Lakes Deoxygenation)";
    Float64 Westernmost_Easting -97.32014;
  }
}

 

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