Feature Inquiry: Extra EXIF Parameters (Heading and Orientation)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 899
- PR merge metrics
- No merged PRs in 30d
Description
Does OpenSFM take advantage of extra EXIF information such as GPS Img Direction, GPS Image Direction Ref, and User Comment (Yaw, Pitch, Roll) to help with the processing and reconstruction?
OpenCamera, for instance, can optionally write these parameters, which in addition to normal GPS EXIF for lat/long/elevation, you get heading and orientation as Yaw/Pitch/Roll.
Let's say you get those orientation values from the flight log of a sUAS, and join them to the images in pre-processing. Wouldn't that help with matching and reconstruction?
To me, this seems like a great bit of extra data to use.
Example attached:
Thanks!
Contributor guide
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.
Research direction
The issue names no files, tests, or entry points. Start by locating where OpenSfM reads image EXIF and where camera orientation enters matching or reconstruction, then determine how the listed GPS direction and Yaw/Pitch/Roll values could be represented and validated. Done would require an agreed scope and evidence that the extra parameters improve processing or reconstruction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100