Easier access to scientific data
Brought to you by NOAA NMFS SWFSC ERD
|
The NOAA GEO-IDE UAF ERDDAP
Easier access to scientific data |
log in |
Brought to you by NOAA NMFS SWFSC ERD |
| Dataset Title: | National Marine Fisheries Service (NMFS) West Coast Region (WCR) Whale Entanglement Data, 1982-2022 
|
| Institution: | NOAA/NMFS/WCR/PRD (Dataset ID: WCRWhaleEntanglements) |
| Information: | Summary
| License
| FGDC
| ISO 19115
| Metadata
| Background
| Subset
| Files
| Make a graph
|
Attributes {
s {
time {
String _CoordinateAxisType "Time";
Float64 actual_range 3.837888e+8, 1.7013888e+9;
String axis "T";
String description "The year and month of the first reported observation of the entangled whale. Any subsequent sightings or dates that actions took place (e.g., a disentanglement response) are also included in the database and listed by corresponding date. All information is recorded, but linked to the original date of the first observation";
String ioos_category "Time";
String long_name "Time";
String standard_name "time";
String time_origin "01-JAN-1970 00:00:00";
String units "seconds since 1970-01-01T00:00:00Z";
}
latitude {
String _CoordinateAxisType "Lat";
Float32 actual_range 20.61, 57.4999;
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 -134.5677, -105.27;
String axis "X";
String ioos_category "Location";
String long_name "Longitude";
String standard_name "longitude";
String units "degrees_east";
}
CaseID {
String description "The initial identification number assigned to the case. The Case ID Number should be assigned by a NMFS Regional Stranding Coordinator. The format is as follows YYYYMMDDGs. Four digit year, two digit month, two digit day, followed by a two letter code for the scientific name, Genus species. Scientific name codes are: Ba=Minke, Bb=Sei, Bm=Blue, Bp=Fin, Er=Gray, Mn=Humpback, Oo=Killer, and Pm=Sperm and Uk=Unknown whale.";
String ioos_category "Other";
String long_name "Case ID";
}
Year {
Int32 _FillValue 2147483647;
Int32 actual_range 1982, 2023;
String description "The year of the first reported observation of the entangled whale. Any subsequent sightings or dates that actions took place (e.g., a disentanglement response) are also included in the database and listed by corresponding date. All information is recorded, but linked to the original date of the first observation";
String ioos_category "Time";
String long_name "Year";
}
Common_Name {
String description "Species identification (ID) initially relies on information provided by the reporting party. When the reporting party is able to provide photos or videos, this increases the Review Team's ability to confirm or later modify the initial species ID, as appropriate. For those reports where the entangled whale cannot be identified to species or the initial report is considered unreliable, it is recorded as unidentified in the database. In some cases, when the species ID was initially considered an \"unidentified\" whale by the reporting party, the Review Team was able to confirm the whale species from photos or videos associated with the report, or from a resight. The Review Team's decision-making process to confirm species ID is included in the record.";
String ioos_category "Other";
String long_name "Common Name";
String units "km";
}
Report_County {
String description "County nearest the position where the entangled animal was first sighted. If offshore the county is determined by nearest landfall due east";
String ioos_category "Other";
String long_name "Report County";
}
State {
String description "State nearest the position where the entangled animal was first sighted.";
String ioos_category "Other";
String long_name "State";
}
Alive_Dead {
String description "This records if the entangled whale is initially reported as being alive or dead.";
String ioos_category "Other";
String long_name "Alive or Dead";
}
Entanglement_Type {
String description "The identification of the entangling gear or the determination that the entangling gear came from a specific fishery relies on information and any documentation provided by the reporting party and/or responders to the NMFW WCR. This includes photographs, video, or the gear retrieved off the animal. Along the U.S. West Coast, certain fisheries have gear marking requirements that are put forth under State and Federal regulations, as well as other characteristics that may be identifiable (see Fixed Gear Guide; appendix in Saez et. al., 2013). NMFS works with State, Federal, tribal fishery managers, and other experts to identify and verify that the entangling gear is accurately assigned to a specific fishery. Because NMFS fishery observers are assigned to a specific fishery, any reports provided by them is assigned to that specific fishery. If a fisherman self-reports an entangled marine mammal, typically reported as bycatch, that report is assigned to the fisherman's specific fishery. Fishermen are required to self-report within 48 hours of returning to port, only if the marine mammal was injured or killed. If the entangling gear could not be identified or assigned to a specific fishery, it was assigned as unknown. For example, when the reporting party used only the term \"line\" to describe the entangling gear, the Review Team used a conservative approach and assigned the entangling gear as unknown, because it could be from a pot/trap, net, or other fishing source (e.g., mooring line). When netting was described/documented on a confirmed entanglement report, it was coded in general as a \"Net\" entanglement in the database. The Review Team determined that the likelihood for a reporting party to accurately identify netting as the correct entangling gear is higher due to its appearance than other types of gear. Reporting party gear type identification is often speculative (e.g. based solely on visible floats and/or line) and is categorized as unconfirmed unless there is additional conclusive information. All reports are ultimately categorized on a case-by-case basis when making these assessments.";
String ioos_category "Other";
String long_name "Entanglement Type";
}
Entanglement_Fishery {
String description "The entangling material has been identified or described with enough information to characterize as fishery origin. Can include general fishery type and/or more specific fishery ID. Examples include Oregon Dungeness crab pot, California lobster pot, gillnet or Unknown.";
String ioos_category "Other";
String long_name "Entanglement Fishery";
}
Entanglement_Fishery_Code {
String description "The entangling material has been identified or described with enough information to characterize as fishery origin. Fisheries were coded as: Dcc= Dungeness crab commercial, Dcr= Dungeness crab recreational, Dgn= Drift gillnet, Gn= Gillnet, Lb= Lobster, Nt= Netting, Rc=Rock crab, Sb= Sablefish pot, St= Salmon troll, Sp= Spot prawn, Spr= Spot prawn recreational, Un= Unknown, Ot= Other (e.g.., cables, weather buoys)";
String ioos_category "Other";
String long_name "Entanglement Fishery Code";
}
Entanglement_Response {
String description "Code for entanglement response are: Yes (Y), No (N), or Dead. Any attempt at intervention, including measures attempted by a trained disentanglement team1, and includes searching for the entangled whale, even if the whale is not found. Entanglement reports of live free-swimming and/or anchored entangled whales are classified by the level of entanglement response effort. Classifications include: a) whale not found after initial sighting; b) whale is re-sighted (no additional entanglement evaluation is possible, so disentanglement efforts are not initiated); c) stand-down (entanglement evaluated, but disentanglement efforts are not initiated for a variety of reasons); d) partial release from gear (disentanglement effort is conducted by a trained team, some gear is removed, but some gear remains on animal after team's release efforts; gear can be removed either directly by trained response team or by animal itself or a combination); e) full release from gear (disentanglement effort is conducted by trained team and all gear is removed from the animal); and whale self-release (entanglement response team is on-the-water and there is no intervention, but animal self-releases or trained observer reports the animal \"throwing\" the gear and self-releasing).";
String ioos_category "Other";
String long_name "Entanglement Response";
}
Entanglement_Removed {
String description "Codes for entanglement removed are: F, SR-F, P, SR-P, N, Dead: The intervention resulted in successful entanglement removal (F), partial removal (P), or removal was unsuccessful (N). This could also include self-release cases (SR-F, self-release full; SR-P, self-release partial). If the animal was reported as dead, entanglement response was not necessary and was coded as dead.";
String ioos_category "Other";
String long_name "Entanglement Removed";
}
}
NC_GLOBAL {
String cdm_data_type "Other";
String contributors "Whale entanglements reported to the NMFS WCR office from opportunistic sightings from a variety of sources including whale entanglement response network, whale watch vessels, sport fishing vessels, members of the public from on-water and shore, researchers, government organizations, and commercial fisheries observers.";
String Conventions "CF-1.6, ACDD-1.3, COARDS, NCCSV-1.1";
String coverage "California, Oregon, Washington, includes whale entanglements of US origin reported from Mexico and Canada";
String creator_email "lauren.saez@noaa.gov";
String creator_name "Lauren Saez";
String creator_url "https://www.fisheries.noaa.gov/region/west-coast";
String defaultGraphQuery "longitude,latitude,Year&.draw=markers&.marker=5|5&.color=0x000000&.colorBar=|||||";
Float64 Easternmost_Easting -105.27;
Float64 geospatial_lat_max 57.4999;
Float64 geospatial_lat_min 20.61;
String geospatial_lat_units "degrees_north";
Float64 geospatial_lon_max -105.27;
Float64 geospatial_lon_min -134.5677;
String geospatial_lon_units "degrees_east";
String history
"2024-05-03T22:08:51Z (local files)
2024-05-03T22:08:51Z http://upwell.pfeg.noaa.gov/erddap/tabledap/WCRWhaleEntanglements.html";
String infoUrl "https://www.fisheries.noaa.gov/resource/document/large-whale-entanglements-us-west-coast-1982-2017";
String institution "NOAA/NMFS/WCR/PRD";
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 57.4999;
String publisher_email "Lynn.Dewitt@noaa.gov";
String source "NMFS WCR Whale Entanglement Response (ERD) Database";
String sourceUrl "(local files)";
Float64 Southernmost_Northing 20.61;
String standard_name_vocabulary "CF Standard Name Table v70";
String subsetVariables "Common_Name,Report_County,State,Alive_Dead,Entanglement_Type,Entanglement_Fishery";
String summary "Publishing U.S. West Coast whale entanglement data from 1982-2019. Dataset included as an appendix to the NMFS Technical Memorandum Large whale entanglements off the U.S. West Coast, from 1982-2017 (Saez, et. al., 2020) and updated to include the published 2018 and 2019 whale entanglement report data. Updated to reflect an entanglement data review post-publication in 2020-2022.";
String time_coverage_end "2023-12-01T00:00:00Z";
String time_coverage_start "1982-03-01T00:00:00Z";
String title "National Marine Fisheries Service (NMFS) West Coast Region (WCR) Whale Entanglement Data, 1982-2022";
Float64 Westernmost_Easting -134.5677;
}
}
Data Access Protocol (DAP) and its
selection constraints.
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://upwell.pfeg.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
https://upwell.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.