Release Notes - 23rd May 2023

New Features

External cloud storage locations

It is now possible for company administrators to configure a set of cloud storage locations (e.g. AWS S3, or Azure Blob storage) for your company. Storage locations can then be utilised by users/teams that have been granted access to the location, as an alternative to direct file downloads. If a storage location is selected, then files will be copied across to the preconfigured cloud storage location rather than downloading to the user's computer. The option to use a storage location is currently supported for:

• Point cloud and dataset file downloads
• Exporting
• LAS overrides
• Analytics result files

For more details and to enable this feature for your account, please contact your Pointerra account manager. You will require credentials to access your AWS and/or Azure cloud storage, so you may need to ensure you have IT support from your company.

Improvements/Changes

Pointerra3D Core

• Point cloud names with an ampersand character (&) in them are now handled and render correctly in the UI.
• Archive (zip, rar, etc) functionality has been updated to support unzipping of large archives (there was a 4GB limit for some dataset types) 
• Photo set uploads that include a CSV metadata file now better handles missing or mismatched columns.
• Photo set uploads now support Phase One IIQ image files.
• Photo set processing now supports Applanix external orientation files for photo locations.
• 360 photo processing now supports reading of Leica extended External Orientation CSV files (in addition to the non-extended format that was already supported).
• 360 photo processing checks that images are valid equirectangular (ie. width is exactly 2x height). It will skip images and report an error if the image is invalid.
• When reprocessing a 360 photo job, and images that have already been processed successfully are now skipped. This can substantially speed up the reprocessing.
• 360 photo processing now strips leading and trailing whitespace from image names in the metadata file - this allows previously failing jobs that were reporting missing images to process without an error.
• Various fixes to support 360 photos processed with geographic coordinates.
• Mouse panning now works when the cursor if over a graphics object such as a vector element, 360 photo marker, or measurement.
• Vector dataset labels are now clipped by the rectangle clip tool.
• Drawing elements are now properly clipped by the horizontal and vertical cropping tools.
• Added split line segment functionality to the polyline drawing tool. Right click on a line segment and select "Split Line" from the context menu.
• Added a new report to include all point clouds - not just active. This report includes a status column that indicates whether the point cloud is active/archived/vault.
• Point cloud files downloaded to an external cloud storage location now include a metadata file as part of the file package.
• Audit data now includes transfers to/from external cloud storage locations.
• Improved detection of browsers that don't fully support the streaming point cloud rendering. Automatically drop back to legacy mode when detected. Fixed rendering not working on some Safari browsers.
• User signups that use an email from a previously deleted account will now succeed - this would report an error and fail the signup previously.

Analytics

• Some of the graphical elements in the viewer (poles, labels, etc) would interfere with panning if the mouse cursor was over the element.

Utility Explorer

• All reports now use the measurement unit preferences when writing out length values (eg. pole heights)

Bug Fixes

• Fixed an issue where the photo viewer would only allow viewing 1 of the photos when a set of photos all had the same location.
• Use DEM as terrain setting was not being applied when loading a bookmark or saved defaults.
• Fixed a bug with photo set processing failing when the set only contained a single photo.
• Creating a photoset that included a calibration CSV file would fail if uploading from an external cloud storage location.
• Point of Interest CSVs exported from Utility Explorer had incorrect formatting if the data contained newline characters.
• LAS override could sometimes create invalid files when generating LAZ.
• Poles and wires analytics now fail if ground model data cannot be determined (would previously try to continue and produce empty results).
• P&W processing could fail if encroachment analysis was enabled in data with no wires.