HxMap 4.8 Release Notes
Main features
3D Advanced processing supports image only input for processing. Create mesh and true ortho from DMC-4, DMCIII and RCD30 images.
Beta Release of DEM Editor view to improve DEMs for ortho and 3D model product generation
Ingest and process datasets from TerrainMapper-3 outfitted with new MFC250 RGB camera
Provide a water mask for image radiometry to improve corrections with challenging specular reflection
Move the cross section in steps through loaded points in the point cloud viewer
Sample image color from images loaded in the Image Index View
Mosaic reference feature has been expanded with new block seamline generation for incremental mosaic production with fewer workflow dependencies
Re-project and rearrange band order of the input ortho images during mosaic tile cut
Performance report for cluster processing to evaluate processing time of different jobs
Building object vertex display can be toggled in 3D Editor perspective
Main fixes
Level of detail for point cloud display in cross section is more consistent
Vertical units other than meters handled incorrectly in Triangulation perspective
Handle GPS week rollover event within lidar takes and within lidar sessions
Mosaic seamline generation better handles large variations in image radiometry, reducing instances where seamlines were driven to the edge of individual take orthos
Edit Mesh tool did not recreate the corresponding true ortho tiles
Blockwide radiometry does not clear profiles assigned to strips or takes
Point cloud filter run after point cloud classification could cause lost points
Building objects not displayed in 3D Editor map view when exceeding height threshold
Building objects displayed incorrectly when reassigning to different layer
Upgrade Notes
HxMap 4.8 requires a new version of the Microsoft Visual C++ runtime libraries, these are included with the HxMap installer prereqs (VC_redist.x64.exe). Be sure to apply the update to all workstations and Cluster nodes where HxMap is run before using HxMap 4.8
HxMap 4.8 requires a new version of CLM Package, minimum version requirement is CLM 2.22. This is available for download from Leica myWorld, with a link included on the HxMap download page.
Starting in 2026, new versions of HxMap will only support the following Windows operating system versions. Please plan accordingly in case your current workstation or cluster nodes are running an earlier version.
Desktop: Windows 10, Windows 11
Server: Windows Server 2016, Windows Server 2019, Windows Server 2022
Processed sessions ingested with HxMap 4.8 are not compatible with earlier versions of HxMap
Point cloud filter and point cloud QC job processing on Infocloud only requires Core Image module license
Point information in the point cloud viewer now includes point coordinates and can be copied to the desktop clipboard
Mosaic scenario formatting has changed to reduce loading time of large projects in Mosaic perspective. A command line tool is available to upgrade existing mosaics from HxMap 4.7 to the new format
Feature based APM includes a new option to Refine Measurements, which can help to further reduce the sigma0 achieved during triangulation adjustment
Cluster job to collect tie point and histograms for image balancing correction is now parallelized on the cluster, improving throughput of the processing
Ingested session’s minifications can optionally be stored external to the 1 to 1 images, and tools are provided to remove them from a session for archival purposes and regenerate them later on
The point cloud decimation from product generation has been added to the iterative lidar workflow. Decimated points can be optionally discarded when necessary i.e. to reduce density over restricted AOIs
QC layers can be displayed in the Session and QC perspectives and are styled by defect type
HxMap GeoData
Added GSI Geoid 2024
Known Issues
Radiometric tie point collection on oblique systems creates 5x as many jobs during ingest as in blockwide radiometry, which could lead to longer run time depending on number of images.
Before running radiometric normalization at ingest reduce the HxMap.ini parameter [Multiframe] number_of_tie_points_collections_jobs accordingly.
After local run of point cloud classification on a Project the point cloud can no longer be displayed in the Lidar Viewer.
Close Workflow Manager and then launch again and reload the Project, the point cloud can be displayed with its classification results
Last used split scan direction setting in lidar matching is not remembered, its set to off by default
Verify the setting before running lidar matching
Apply autostretch with radiometric profile shows incorrect image radiometry
Autostretch is not required when setting product radiometry
License checking over a VPN may take several minutes