Release notes¶
pix4dvortex releases follow semantic versioning.
Release 2023.09 - semantic version 2.2.0¶
What’s new¶
New geoid models:
FIN2000 (EPSG:4258+5717) “N60 height”.
FIN2005N00 (EPSG:4258+3900) “N2000 height”.
LV14 (EPSG:4661+7700) “Latvia 2000 height”.
TWGEOID2018h (EPSG:8904) “TWVD 2001 height”.
Support for new camera models:
MicaSense Altum-PT.
MicaSense RedEdge-P.
Corrected and improved API documentation for
cameras.GeoTag
and related classes.Improved DSM generation performance and quality.
cameras.make_input_cameras()
reads GPS time for following camera models:Parrot Sequoia.
SenseFly S.O.D.A.
SenseFly AeriaX.
Sony DSCWX220.
Wingtra RGB61.
Xacti CX GB100.
Improved densification performance up to 5% when using perspective cameras.
Improved mesh texturing by reducing seams visibility and improving texture segmentation.
cameras.GeoTag
can be initialized from optionaldmodel.GeoLocation
anddmodel.YawPitchRoll
OPF objects.Added OPF Yaw-Pitch-Roll Orientation as
dmodel.YawPitchRoll
.
Bug fixes¶
Sporadic tiled orthomosaic generation failures due to incompatible DSM and ortho tile sizes.
Various minor quality and performance issues in
ortho.gen_tiled_orthomosaic()
.cameras.make_input_cameras()
raisesValueError
and logs DUPLICATE_IMAGE as failure reason. Previously the failure was erroneously logged as rig related.Fix very long processing times on some cases of planar meshes in mesh texturing.
Exception resulting from
ortho.gen_tiled_orthomosaic()
failure due to a color balance error had incorrect message “Unknown error”. This has been replaced by “Color balance error”.Loading OPF objects with CRS user input description fields such as
"EPSG:2056+5773"
instead of full WKT strings was leading to run time errors in some situations.Removed erroneously exposed and problematic option
coordsys.WktExportOptions.BIND_TO_WGS84
.
Internal release 2.1.1¶
What’s new¶
Improvements in documentation.
Bug fixes¶
Fixed a regression in LAS 1.2 serialization of site localized point clouds (i.e. with CRS
DERIVEDPROJCRS
), which resulted in an exception being raised. The previous behaviour of generating the LAS file with inconsistent CRS information has been restored. Strictly speaking this is not a bug fix, since the regression was simply applying stricter correctness criteria.
Release 2023.06 - semantic version 2.1.0¶
What’s new¶
Improvements in documentation.
Windows GPU support upgraded to CUDA 11.7 compatible drivers.
Camera Support: ShareUAV 202S Pro.
Camera Support: WINGTRA RGB61_FE24mmF2.8G_24.0_9504x6336.
Camera Support: DJI M3M_4.3_2592x1944.
Slovenian geoid model SLO-VRP2016/Koper.
German geoid model GCG2016.
Support for NADCON5 grid files for USA. This may slightly change transformations in the USA.
Stability and performance improvements in GPU enhanced orthomosaic generation.
API changes¶
Type of mask paths in the mask map parameters of
mesh.gen_mesh_geometry()
anddense.densification()
changed fromstr
toos.PathLike
. This change is backwards compatible.Type of mask paths in the mask map returned by
skyseg.gen_segment_masks()
changed fromstr
topathlib.Path
.Type of output directory parameter of
skyseg.gen_segment_masks()
changed fromstr
toos.PathLike
. This change is backwards compatible.pix4dvortex.io
function parameters representing paths changed fromstr
toos.PathLike
. This change is backwards compatible.pix4dvortex.proc.Resources.work_dir
property is now represented asos.PathLike
instead ofstr
on set, which is backward compatible, and aspathlib.Path
instead ofstr
on get.pix4dvortex.dmodel.io
function parameters representing paths changed fromstr
toos.PathLike
. This change is backwards compatible.
Bug fixes¶
Fixed a bug in site calibration by which calibrations with big coordinates could end up with the site system up-side down.
Failure to run
pix4dvortex.transform.transform()
for point clouds when the supplied working directory does not exist.
Release 2023.05 - semantic version 2.0.0¶
What’s new¶
This is the initial release of the 2nd generation PIX4Dengine SDK. For the feature content refer to the latest feature list on the PIX4Dengine product page or contact the PIX4D sales team.