Skip to Main Content
Need Support? Let’s guide you to the right answer or agent.
Status Needs review
Created by Guest
Created on Jun 25, 2023

DSM & DTM from Point Cloud for Orthorectification

Importing a point cloud for generation of DSM or DTM for orthomosaic workflows would allow a significant reduction in processing time. If the point cloud is LiDAR based, the DSM would also improve DSM based orthorectification in vegetated areas. Currently the 2.5D workflow takes a significant amount of time as the reference model is generated before a DSM and orthomosaic are produced.

  • Guest
    Reply
    |
    Oct 27, 2024

    While the option to import a point cloud and exclude the photo tie points from being used in the reconstruction geometry, this workflow is cumbersome and has limitations.

    1. Currently the density of the point cloud dictates the final resolution that can be created in ortho outputs in both the 3D and 2.5D construction workflows. Ideally the full resolution of the images should be used to texture a mesh, even if the mesh is of a lower resolution.

    2. The importation of large dense point clouds if very slow during the conversion to .POD

    3. The point cloud is then used to build a 3D mesh or DTM/DSM in 2.5D workflow which are both time consuming.

    As many software packages allow the importation of a point cloud (or raster directly) I think it would be a good feature to allow direct ortho rectification onto a surface - much in a similar way to correlator 3D allows - even if this is only inside the 2.5D ortho DSM workflow.

    1 reply
  • Guest
    Reply
    |
    Aug 22, 2024

    There is such option so seems it is alreade available.

    Processing settings->Photos used for geometry

    This advanced option allows you to choose the input data used for reconstructing geometry.

    • None: geometry will use only point clouds (available only if input block has point clouds).