[Feature Request] Video frame extraction
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- computer-vision, data
Research direction
Start by reviewing the linked VideoReader project and the upstream src/pcv/examples/stitching_advanced.py example to understand the referenced video-processing and stitching work. The issue lists several independent goals, so a contributor would first need a maintainer to select and define one scope; done criteria are not specified.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Video data is often a useful source of images, but can be difficult to get synchronised with corresponding telemetry and other data. It is also frequently challenging to efficiently get "good" frames, by frame quality, by physical spacing, etc
Describe the solution you'd like
- extract timestamped frames from QGroundControl-saved video (and other formats?)
- a method for aligning video frames with corresponding telemetry and other data
- a method of extracting the best (sharpest?) frame within a small time or area region
- intelligent frame extraction that avoids large vibrations/acceleration
- a method of extracting frames by distance travelled since last frame
- a method of extracting frames in specific regions (waypoints)
- a way of stitching frames together into a composite image
- a way of aligning frames or composite images onto/into a map
Describe alternatives you've considered
| alternative | reason(s) why unsuitable |
|---|---|
| manual frame extraction | slow, time-consuming, impractical |
| direct time-based extraction (e.g. ffmpeg, every nth second) | imprecise, may get a bad frame even if the next one was great, doesn't make intelligent use of other available data |
Additional context
VideoReader- nice setup, efficient processing- initial stitching work (upstream, in
pythonic-cv)
- 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
ES-Alexander/data-alignment#1 · 1 comment ·
All issues in ES-Alexander/data-alignment
Similar issues
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100