Pix4Dmapper 2.2 Preview Technical Release Notes

This is the release of Pix4Dmapper 2.2 Preview. Get a preview of the new features and help us improve the product by reporting any issues to support@pix4d.com

Disclaimer: the documentation is not yet ready for 2.2 Preview, and we do not recommend using the Preview for production work. No support is provided for the Preview.

Download

VersionRelease dateRelease type
2.2.22 August 11, 2016 New release
2.2.19 July 27, 2016 Preview
2.2.15 July 5, 2016 Preview

 

Version 2.2.22

Bug fixes

  • Project management
    • Fix bug where p4d files created by merging projects could not be opened.
    • Fix bug where the software crashed when creating a new project after having merged a project.
  • Merge projects
    • Fix bug where MTPs disappeared when merging projects.
    • Fix bug where when merging projects fails with error e0401f, the projects to be merged cannot be opened any more.
  • Various UI bug fixes
  • Index calculator
    • Fix bug where wrong sensitivity of the Sequoia's sunshine sensor was used in version 2.2.19 to compute the reflectance map.
    • Fix bug where Sequoia's images without sunshine sensor information were used for the reflectance map.
  • Command line
    • Fix bug where the degree symbol was not correctly printed out on stdout.

 

Version 2.2.19

What is new

  • 360° cameras processing
    • A new spherical model has been introduced, which allows processing of images and videos acquired with a 360° camera. Only equirectangular images and videos are supported.
  • Automatic detection of the Airinov calibration targets
    • When an image with an Airinov calibration target is imported at project creation the target is automatically detected and the target region and albedo values are automatically extracted.

Improvements

  • Quality report
    • Display all the processing options used for processing.
  • CLI
    • Pix4Dmapper outputs are now split between stdout (Info, UI, Processing) and stderr (Error, Warning) when using the command line.

Bug fixes

  • Project management
    • Fix bug where a .p4d file created with version 2.1 could not be opened in version 2.2.15.
  • Processing options
    • Fix bug where processing options for step 3 were set to the 3D Maps template options when loading a template created in version 2.1.
  • Quality report
    • Fix display issues appearing in the quality report generated after merging processed projects.
  • Processing
    • Fix bug where processing failed at step 2 when annotating images for masking before step 2 is run.
  • rayCloud
    • Fix bug where in some cases the software crashed when generating the orthoplane and some images were annotated for masking. When this happens the project cannot be opened anymore.
  • Index calculator
    • Fix bug where for some projects the grayscale used to display the reflectance map was not correct. The reflectance map appeared almost black.
  • Various UI bug fixes

Known issues

  • Project management
    • When merging processed projects failed with error e0401f, the individual projects cannot be opened anymore.
  • Processing
    • Cannot reprocess step 3 when the Index Calculator View is open.
  • Outputs
    • The 3D PDF can only be visualized with a texture up to 8192x8192.
  • Maps View
    • Importing a Processing Area using a DXF file does not place it at the project location as there is no coordinate system.
  • rayCloud
    • The adding an orientation constraint for the X and Y axis is not working when following this workflow:
      1. On the menu click rayCloud > New Orientation Constraint.
      2. On the right sidebar, under Axis, select the X axis.
      3. Draw the Orientation Constraint. It disappears.
      Workaround: Draw first the constraint and then change the axis.
  • Index Calculator
    • In some cases the reflectance map displays wrong band information values.
  • Volumes view
    • Volumes export from Pix4Dmapper and re-imported into another project do not have the same number of vertices.

 

Version 2.2.15

What is new

  • New Volumes view
    • The Volumes view allows to easily measure volumes as well as to import and export them.
  • Manually improve the 3D textured mesh
    • Use surfaces drawn in the rayCloud to improve the 3D textured mesh. This new tool helps to flatten surfaces or to fill holes on flat surfaces.
  • Automatic sky masking for Parrot Bebop images
    • New processing option that allows to automatically mask sky in Parrot Bebop images during step 1. When running step 2 Point Cloud Densification masked areas will not be used to reconstruct 3D Points. Therefore sky will not be reconstructed at step 2.
  • Manually remove orthoplane background
    • Annotate images in the rayCloud in order to remove the background for orthoplane generation.
  • Optimized camera position uncertainties
    • The optimized camera position uncertainties are displayed in the quality report. The absolute position uncertainty is displayed in Figure 3 and the relative position uncertainty is displayed in Figure 5.

Improvements

  • Processing options
    • 3D textured mesh: remove zipped OBJ option as it is not compatible anymore with Sketchfab. By default the 3D textured mesh is generated in OBJ and FBX format.
  • Processing
    • Faster processing for multi-spectral rigs (e.g. Sequoia, etc.).
    • Easier and faster processing for images acquired by senseFly's albris.
    • Automatically remove foreground objects when generating the 3D Textured Mesh.
  • Outputs
    • The 3D Textured Mesh can be exported directly from the rayCloud layers by right clicking on a mesh layer.
    • Save the DSM and orthomosaic generated with the SGM add-on.
  • Image annotation
    • Annotate images globally to remove objects that are visible in each image at the same location. E.g: Remove the feet of the drone.
  • send to eMotion
    • The two options Send Map to eMotion and Send DSM to eMotion can now also be used when only step 1 is done or when only step 1 and step 3 are done.

 

Bug fixes

  • Project management
    • Fix bug where the radiometric calibration image path was not updated when moving a project.
  • Processing
    • Fix bug where processing was failing when importing an external point cloud to generate the DSM using the menu Process > Import Point Cloud for DSM Generation...
  • Outputs
    • Fix bug where contour lines shapefiles were not compatible with AutoCAD Civil 3D. The file name for the contour lines was changed such that it does not contain a ".". File names without a "." can be directly imported in AutoCAD Civil 3D.
  • Command line
    • Fix bug where it was not possible to logout with --logout when the user logged in with another version. E.g. When the software was logged in with version 2.0, it is not possible to log out with version 2.1.

Other changes

  • Processing options
    • Discontinue the orthomosaic in Mapbox tiles format. The GeoTIFF orthomosaic can be directly uploaded to Mapbox.
  • Quality Report
    • Figure 7. Georeference Verification will not be shown in the quality report anymore. The Ground Control Table can be used to assess the accuracy of the GCPs. The rayCloud gives a better indication about the GCP marks and reprojection.

 

Known issues

  • Processing
    • Wrong matches are computed when using the Reoptimize or Rematch and Optimize options in version 2.2 for projects that have been processed in version 2.1.
    • In some cases the optimized camera position uncertainty is not computed.
    • For some projects with multiple blocks, the densfied point cloud contains holes.
      Workaround: If possible, disable the images in small blocks and run step 2 again.
  • rayCloud
    • Annotate images for Global Mask. Run step 2 and select again the annotated images. The areas annotated for Global Mask are not highlighted with a color. However, the mask was correctly applied when step 2 was run.
    • When using the spherical point cloud shader, the point cloud does not get correctly displayed on systems with AMD graphic cards.
  • Index calculator
    • When scrolling the mouse wheel while inserting a region, the reflectance map disappears.
  • Command line
    • When applying a template file that was created with version 2.1, all the processing options for step 3 are reset to the 3D Maps processing template options.
      Workaround: re-export the template file using version 2.2.
Was this article helpful?
0 out of 0 found this helpful


Powered by Zendesk