[Feature Request] Ping Sonar device log data

[ES-Alexander]

Is your feature request related to a problem? Please describe. Sonar data from Ping Viewer is helpful for navigation, but difficult to use in post-processing and analysis.

Describe the solution you'd like Create a way for Ping Viewer log files to have their data aligned with telemetry, for saving and further analysis.

• [x] ~Ping Sonar data is simplest to implement (has a distance output), and most critical~ #6
• [ ] Ping360 would also be helpful, including ways to analyse each scan, and account for whole-sensor rotation/motion
• [ ] Ideally would support/incorporate speed of sound estimation from telemetry and water properties - may be used to estimate distance values from sonar scan data, or as correction scaling on existing estimates
• [ ] Saving processing results (in a database?) could be useful for efficiency of further analysis (in case later steps use the results of this initial extraction stage multiple times)

Describe alternatives you've considered	approach	reason(s) why unsuitable
Doing alignment and extraction by hand	impractical, time-consuming, and messy
Not having sonar data in results	results are less useful

Additional context

• sonar rangefinder distances are relevant for bathymetry, surface measurements, and providing context for images, among other things
  • cave scanning/mapping
  • biodiversity / bathymetry / video context
  • bathymetric surveying (beware short distances)
• scanning/imaging sonar can be relevant for inspections, SAR, and more
  • mapping / rendering
  • pipe profiling

[ES-Alexander]

A potential approach to improve mapping data resolution.

It may also be relevant/valuable to consider direction to source for each ping, but not sure if that could be worked in.