ERDDAP
Easier access to scientific data |
log in |
Brought to you by NOAA NMFS SWFSC ERD |
Dataset Title: | NOAA-Navy Sanctuary Soundscape Monitoring Project, Blue Whale Sound Production, Monterey Bay, SanctSound_MB03_01_bluewhale_disk2 |
Institution: | NOAA (Dataset ID: noaaSanctSound_MB03_01_disk2_bluewhale) |
Information: | Summary | License | ISO 19115 | Metadata | Background | Files | Make a graph |
Attributes { time { String _CoordinateAxisType "Time"; Float64 actual_range 1.5473019353600001e+9, 1.54730221696e+9; String axis "T"; String ioos_category "Time"; String long_name "Time"; String standard_name "time"; String time_origin "01-JAN-1970 00:00:00"; String time_precision "1970-01-01T00:00:00.000Z"; String units "seconds since 1970-01-01T00:00:00Z"; } bluewhale_presence { String cell_methods "time: sum (comment: presence (1) or absence (0) over time interval)"; String comment "Presence of Blue Whale (0 = not present; 1 = present)"; String ioos_category "Statistics"; String long_name "blue whale presence"; String standard_name "bluewhale_presence"; String units "boolean"; } NC_GLOBAL { String abstract "This record represents blue whale sound production detected from raw passive acoustic data. Blue whale B calls were detected using Triton's Blue Whale B Call Detector Remora. The detector uses spectrogram correlation (Mellinger and Clark, 2000) to detect calls with a kernel (an average B call) that is generated from a subset of calls. The kernel was calculated from 30 excellent quality B calls that were at least 24 hours apart. A kernel was generated per sanctuary for every six months of data. Kernel quality and optimal threshold settings were tested by running the detector through a subsample of data in which 200-400 calls were manually detected. The comparison between manual and automatic detections was used to calculate precision and recall of the detector, in percentages. Settings were considered optimal when precision and recall were both 85% or higher. These settings were then used to run the detector through the entire dataset for that deployment. Wav files were first decimated to 2 kHz sampling rate. Detector results were manually verified during time periods in which few detections were expected.These data were recorded at SanctSound Site MB03_01 between November 15, 2018 and June 10, 2019."; String acknowledgement "This project received funding from the U.S. Navy."; String cdm_data_type "TimeSeries"; String citation "Cite as: NOAA Office of National Marine Sanctuaries and U.S Navy. 2022. Blue Whale Sound Production Recorded at SanctSound Site MB03_01, SanctSound Data Products. NOAA National Centers for Environmental Information. Accessed [date]. DOI: https://doi.org/http://doi.org/10.25921/ryy8-4224"; String comment "Data quality: Quality data were recorded for the duration of the deployment."; String contributor_name "Simone Baumann-Pickering, Scripps Institution of Oceanography; Leila Hatch, NOAA Stellwagen Bank National Marine Sanctuary; John Joseph, U.S. Naval Postgraduate School; Anke Kuegler, Hawai'i Institute of Marine Biology, University of Hawai'i at Manoa; Marc Lammers, NOAA Hawaiian Islands Humpback Whale National Marine Sanctuary; Tetyana Margolina, U.S. Naval Postgraduate School; Karlina Merkens, NOAA Pacific Islands Fisheries Science Center; Lindsey Peavey Reeves, NOAA Channel Islands National Marine Sanctuary; Timothy Rowell, NOAA Northeast Fisheries Science Center; Jenni Stanley, Woods Hole Oceanographic Institution; Alison Stimpert, Moss Landing Marine Laboratories; Sofie Van Parijs, NOAA Northeast Fisheries Science Center; Eden Zang,NOAA Hawaiian Islands Humpback Whale National Marine Sanctuary"; String contributor_role "Principal Investigator"; String Conventions "COARDS, CF-1.6, ACDD-1.3"; String creator_email "ncei.info@noaa.gov"; String creator_name "NOAA NCEI"; String creator_url "https://www.ncei.noaa.gov/"; String date_created "2022-08-22"; String date_issued "2022-08-22"; String featureType "TimeSeries"; String geospatial_bounds "POINT (36.3703 -122.3148)"; String history "Blue whale B calls were detected using Triton's Blue Whale B Call Detector Remora. The detector uses spectrogram correlation (Mellinger and Clark, 2000, JASA 107:3518-3529) to detect calls with a kernel (an average B call) that is generated from a subset of calls. The kernel was calculated from 30 excellent quality B calls that were at least 24 hours apart. A kernel was generated per sanctuary for every six months of data. Kernel quality and optimal threshold settings were tested by running the detector through a subsample of data in which 200-400 calls were manually detected. The comparison between manual and automatic detections was used to calculate precision and recall of the detector, in percentages. Settings were considered optimal when precision and recall were both 85% or higher. These settings were then used to run the detector through the entire dataset for that deployment. For higher performance speed, wav files were decimated to 2 kHz sampling rate. A final evaluation of the detector results consisted of manual verification of the automatic detections in time periods in which few detections were expected. Data were processed with Triton Blue Whale B Call Detector Remora (v 1.93.20160524) and Matlab (2016b and newer; statistics toolbox). 2024-11-23T08:01:55Z (local files) 2024-11-23T08:01:55Z https://coastwatch.pfeg.noaa.gov/erddap/griddap/noaaSanctSound_MB03_01_disk2_bluewhale.das"; String id "http://doi.org/10.25921/ryy8-4224"; String infoUrl "https://ncei.noaa.gov"; String institution "NOAA"; String instrument "HARP"; String keywords "acoustic attenuation/transmission, acoustics, ambient noise, aquatic ecosystems, cetacean, environmental, fish, frequency, intensity, marine environment monitoring, marine habitat, national centers for environmental information, Navy, NOAA, ocean acoustics, oceans, office of national marine sanctuaries, passive acoustic recorder, pressure, sound_intensity_level_in_water, soundscapes"; String keywords_vocabulary "GCMD Science Keywords"; String license "The data may be used and redistributed for free but are not intended for legal use, since it may contain inaccuracies. Neither the data creator, 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 naming_authority "NOAA-Navy"; String project "NOAA-Navy Sanctuary Soundscape Monitoring Project"; String publisher_email "erd.data@noaa.gov"; String publisher_name "NOAA NMFS SWFSC ERD"; String publisher_type "institution"; String publisher_url "https://www.pfeg.noaa.gov"; String sourceUrl "(local files)"; String standard_name_vocabulary "CF Standard Name Table v55"; String summary "NOAA and the U.S. Navy are working to better understand underwater sound within the U.S. National Marine Sanctuary System. From 2018 to 2021, these agencies will work with numerous scientific partners to study sound within seven national marine sanctuaries and one marine national monument, which includes waters off Hawai'i and the east and west coasts. Standardized measurements will assess sounds produced by marine animals, physical processes (e.g., wind and waves), and human activities. Collectively, this information will help NOAA and the Navy measure sound levels and baseline acoustic conditions in sanctuaries. This work is a continuation of ongoing Navy and NOAA research, including efforts by NOAA's Office of National Marine Sanctuaries This dataset represents the derived products from the raw acoustic data that are archived at NOAA National Centers for Environmental Information."; String time_coverage_end "2019-01-12T14:10:16.960Z"; String time_coverage_start "2019-01-12T14:05:35.360Z"; String title "NOAA-Navy Sanctuary Soundscape Monitoring Project, Blue Whale Sound Production, Monterey Bay, SanctSound_MB03_01_bluewhale_disk2"; } }
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.
griddap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/griddap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/griddap/jplMURSST41.htmlTable?analysed_sst[(2002-06-01T09:00:00Z)][(-89.99):1000:(89.99)][(-179.99):1000:(180.0)]
Thus, the query is often a data variable name (e.g., analysed_sst),
followed by [(start):stride:(stop)]
(or a shorter variation of that) for each of the variable's dimensions
(for example, [time][latitude][longitude]).
For details, see the griddap Documentation.