OpenDroneMap / OpenDroneMap/ODM
GLB quantization computed incorrectly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 1.3k
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 4
Description
Depending on the size of the scene, GLB assets generated via ODM (--gltf) are quantized improperly due to the quantization in draco using per-mesh bounds rather than per-scene bounds https://github.com/google/draco/issues/713
Approach used by gltf-transform and that should be ported to draco_transcoder: https://github.com/donmccurdy/glTF-Transform/commit/977995c5fda719bb8a2da377055757436dd46165
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
Start with the linked Draco issue and the glTF-Transform commit, then trace the GLB generation path invoked by ODM's --gltf option into draco_transcoder. Done means quantization uses per-scene bounds rather than per-mesh bounds and generated GLB assets have correct quantization across scene sizes.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100