Why to use GimbalYawDegree instead of FlightYawDegree in opposite to what ODM do?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 899
- PR merge metrics
- No merged PRs in 30d
Description
While I am looking the file photo.py from ODM, exactly here:
https://github.com/OpenDroneMap/ODM/blob/12e5b63b6f5423383892d325467b64ce295e3a9c/opendm/photo.py#L463
I see using of gimbal's roll and pitch BUT flight's yaw instead of gimbal's yaw.
On the other side when looking into file exif.py from opensfm, exactly here:
https://github.com/mapillary/OpenSfM/blob/537275b730d7a6417fce68c3645f69c834bddca3/opensfm/exif.py#L494
then I see what I expect or claim to be, is there any explanation for that?
My regards.
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
Compare the referenced ODM photo.py line with OpenSfM's exif.py line and trace how each yaw value is interpreted. Confirm the intended behavior with maintainers before selecting a code or documentation location; done would be a maintainer-approved explanation of the difference, with tests only if a behavior change is requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100