FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Volume report is always based on DSM, even when DTM is selected. · Issue #1992 · WebODM/WebODM · GitHub

/ WebODM Public

Volume report is always based on DSM, even when DTM is selected. #1992

Description

How did you install WebODM (docker, installer, etc.)?

Docker

What's your browser and operating system? (Copy/paste the output of https://www.whatismybrowser.com/)

Safari 26.5 on macOS

What is the problem?

Volume report always uses the Digital Terrain Model for calculating the volume, even when the Digital Surface Model is generated and visible. Volume should be calculated from the currently visible model.

How can we reproduce this? (What steps trigger the problem? What parameters are you using for processing? Does it work with the default settings? Include screenshots. If you are having issues processing a dataset, you must include a copy of your dataset uploaded on Dropbox, Google Drive or https://dronedb.app)

Any task with a distinctly different DSM and DTM will demonstrate this issue by producing an identical volume measurement, regardless of which layer is currently visible.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL