[Feature Request] Ping Sonar device log data
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
The issue names no repository files, tests, or entry points. Start by reviewing the linked Ping Viewer binary structure and defining the scope for Ping360 logs, telemetry alignment, speed-of-sound handling, and result storage; done should include an agreed, testable subset rather than the full wishlist.
Written by the indexing model from the issue text.
Description
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.
-
Ping Sonar data is simplest to implement (has a#6distanceoutput), and most critical - 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
distancevalues 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
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ES-Alexander/data-alignment
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
ES-Alexander/data-alignment#3 · 1 comment ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in ES-Alexander/data-alignment
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100