A number of new functionality related to the processing of aerial lidars has been added to the program in Agisoft Metashape 2.2, as well as the ability to improve the quality of orthomosaic based on data with a more detailed resolution and additional tools that will be described in the article below:



Download Agisoft Metashape 2.2.0 pre-release


Currently Agisoft Metashape 2.2.0 is available as pre-release and can be downloaded from Agisoft Forum:

https://www.agisoft.com/forum/index.php?topic=16745.0

In case of any problems related to the pre-release version please report either in the related forum thread of create a helpdesk support ticket with the detailed description of the issue.


Aerial LiDAR boresight calibration support

It is now possible to perform boresight calibration for aerial lidars. This process allows for better alignment between aerolidars. A detailed workflow is described in our article - Aerial laser scans data processing in the "Aerial LiDAR boresight calibration" section.




Pansharpening 

Starting from Agisoft Metashape 2.2, it is possible to improve the quality of orthomosaic based on higher resolution data. Below is an example of orthomosaic before and after pansharpening (image on the left before, on the right after):




We have described the detailed workflow and processing parameters in our article - Pansharpening.


AprilTags coded-targets

In Agisoft Metashape 2.2, it is possible to automatically detect AprilTags. To start tag detection, select Tools > Markers > Detect Markers... and select the appropriate label type in the dialog box:



You can view information on the types of AprilTags on the following pages:
https://april.eecs.umich.edu/software/apriltag
https://github.com/AprilRobotics/apriltag


Build texture from orthomosaic

Starting from version 2.2, it is possible to build textures using orthomosaic rather than the original images. You need to select Orthomosaic as the Source data in the Build Texture dialog window:



Build orthomosaic from textured model

It is also possible to build an orthomosaic from a textured model.  In this case it is important to select the Model as the Source data and to use the model not only as a surface and texture, you need to enable the Transfer model texture option:



Multiple masks instances support

It is now possible to store several masks in different layers and choose whether to use masks during building depth maps, orthomosaic, texture or not. 


Layers with masks are displayed in the Workspace pane. In order for masks to be used during processing, you need to make the mask layer active. To do this, double-click on the layer with masks or select Set an active command from the layer context menu on the Workspace pane:




Only one mask layer can be made active, if you need to use all masks, then the layers with masks need to be merged. Select masks on the Workspace pane and choose Merge... command from the mask context menu.




Restart processing after power failure

The construction algorithms include subtasks during processing. If there is a problem during processing problem is related to
unexpected Metashape termination (crash, shut down, ect) now it is possible to continue the processing process from the moment when the problem occurred. That is, after the problem occurred when reopening the project, processing will automatically continue from the previous saved task on which the failure occurred.


In order for this algorithm to be available, it is important that the processing of each stage is saved. For this, the Save project after each step parameter was added to the processing dialog boxes. It should be enabled when selecting the parameters to build, as in the example below of the Align Photos dialog box:



If this option was not enabled before processing, then the failed processing operation has to be started from scratch.



Changes in network processing


All information related to the network batches is now stored in database on the server side, therefore the failover (slave) server feature is no longer needed and has been removed from 2.2.0 version. 

Starting from 2.2.0 version working nodes are started by default in paused state, if it is necessary to override this setting, use --resume-workers key when starting the server instance.