Generating Occlusion texture on Orthomosaic

[jinjamu]

Hi
I am currently involved a large seabed mapping project using a AUV (Automated Underwater Vehicle) mounted Voyis camera, which we use to scan areas of archaeological importance.  The ultimate objective of the process is to obtain hi res orthos, and my workflow typically goes Tie Points -> DEM -> Orthomosaic. 
Apart from the DEM and the Ortho, an Orthomosaic using Occlusion Map would a very valuable deliverable.  This is possible using QGis, however the way that Metashape generates this is far more visually appealing then any QGis method I have used (I am no expert in QGis so maybe I am missing a trick!). 
The only way I have managed to do this in Metashape involves the creation of a mesh, then texturing that using Occlusion, exporting and reimporting that texture, then running an Ortho on the mesh using the "Transfer Model Texture" option.  This adds an excessive amount of time to the process.
So my suggestion, if this is possible, is to consider adding a feature to generate an Ortho with Occluded texture, directly from the DEM.
Thanks
John

[JMR]

+1 Occlusion ortho sounds just great to me too!
José Martínez
Geobit &
Accupixel

[Alexey Pasumansky]

Hello all,

Please check the latest 2.2.2 pre-release version:
https://download.agisoft.com/metashape-pro_2_2_2_x64.msi
https://download.agisoft.com/metashape-pro_2_2_2.dmg
https://download.agisoft.com/metashape-pro_2_2_2_amd64.tar.gz

There in Build Orthomsaic dialog you can find Color Source option in the Build Orthomosaic dialog. If you are using Model as a surface, then you can select Texture (diffuse map) for regular texture transfer, or Occlusion map to use this type of texture for orthomosaic rendering.

If you have any problems with this new feature, please comment.

[jinjamu]

Thanks Alexey I will try that.
However if I understand your message correctly this new method depends on a model being built already.  My original request was more about the possibility of an occlusion map being build off a DEM, just like it is currently possible to build a normal textured ortho.  This will allow a process that completely bypasses the building of a model in workflows where this is not needed.
Thanks