The US Ocean Observatories Initiative (OOI) now hosts EK80 echosounders on the Regional Cabled Array. Some users do not use netCDF files to analyze data and rely on reading .raw files into Echoview or other software, and would like the .raw files to only contain one type of transmission signals, either "CW" (narrowband) or "FM" (broadband) transmissions.
This issue is to track this need. While echopype's philosophy is to create and operate on standardized datasets to increase accessibility and scalability (i.e., we do not operate based on the .raw files once we parse and convert all the content to zarr or nc files following a netCDF data model), this functionality may be useful for the community.
We can potentially add a function in the echopype.utils subpackage to split the .raw files into 2 .raw files: one contain only CW pings and the other contains only FM pings.
We can close this now since this is likely not the path taken by the OOI team. We can stay on track with our approach to create and operate on standardized datasets.
The US Ocean Observatories Initiative (OOI) now hosts EK80 echosounders on the Regional Cabled Array. Some users do not use netCDF files to analyze data and rely on reading
.raw
files into Echoview or other software, and would like the.raw
files to only contain one type of transmission signals, either "CW" (narrowband) or "FM" (broadband) transmissions.This issue is to track this need. While echopype's philosophy is to create and operate on standardized datasets to increase accessibility and scalability (i.e., we do not operate based on the
.raw
files once we parse and convert all the content tozarr
ornc
files following a netCDF data model), this functionality may be useful for the community.We can potentially add a function in the
echopype.utils
subpackage to split the.raw
files into 2.raw
files: one contain only CW pings and the other contains only FM pings.