-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creation of acoustic sample files using OG-1.0 format #176
Comments
There is a treasure trove of various examples that are used for the test suite for ERDDAP. It would be quite an exercise to walk a lot of these examples (a handful) for use in OG-1.0. REF: https://github.com/ERDDAP/erddapTest. |
The closest example that fits what was proposed is https://github.com/ERDDAP/erddapTest/blob/main/CFPointConventions/trajectoryProfile/trajectoryProfile-Multidimensional-SingleTrajectory-H.6.2/trajectoryProfile-Multidimensional-SingleTrajectory-H.6.2.cdl, which is looks identical to the proposed |
@emmerbodc Getting closer. Need to circle back on a few thing now that I have a path forward. Need to make sure it is truly CF-1.10 compliant and then we will kick it over to a PR.
Rendering in ERDDAP: |
A somewhat ugly solution has been found avoiding use of netCDF4 groups. This avoids causing the CTD like data to become very sparse when adding N_BINS to a shared depth variable. In this example, two sets of dimensions are created and seem to work well within ERDDAP. A similar principle can be applied to support OG-1.0 format. See: https://hoodfish.fish.washington.edu/erddap/files/unit_507_20240304T0000_CF2/ The typical CTD parameters continue to use time, lat, lon, depth as their shared dimensions. The echogram now has its own dimensions: echogram_sv(echogram_time, echogram_depth). To make the dimensions more generic for other related acoustic variable, the dimensions might be acoustic_time and acoustic_depth. The next attempt is to try and clean this up leveraging netCDF4 groups (#119). Keeping the typical CTD structured data in the [root] group and creating an [acoustics] group. |
Adding for reference to some sample files: |
The first sample is a simpler case. This has been described here and a suggested solution here.
Currently flattened versions are available from here: https://hoodfish.fish.washington.edu/erddap/files/unit_507_20240304T0000_acoustic/
A more complex case would be taking account of the nominal sensor orientation with respect to measured pitch and yaw of the glider. Instead bins simply varying by depth, each bin would have a 3D coordinate.
The end result is to build a pool of gold standard example datasets to test against a future OG-1.0 compliance tester.
The text was updated successfully, but these errors were encountered: