Messages

1

General / Re: Unsupported datum transformation when exporting pointcloud

« on: March 09, 2026, 04:55:00 PM »

Hi Alexey,

In the reference settings, I see "WGS 84 (ESPG::4326)" for crs, camera reference and marker referrence (screenshot: https://freeimage.host/i/1.quWnaef). I do not see any separate entry for the pointcloud.
I also don't see anything noteworthy in the point cloud info in the workspace tab (https://freeimage.host/i/2.quWnRgn).

In the console, I can verify there is no specific crs set for the pointcloud:

Metashape.app.document.chunk.point_cloud.crs is None
Out[4]: 2026-03-09 14:50:11 True

I also just noticed that the model view turns completely white/blank when I select the pointcloud to be rendered, while the tiepoints and mesh render properly. Even the map, markers and shape are not rendered. (Screenshot: https://freeimage.host/i/quhwx9t). Again, in Metashape 2.1.1 the pointcloud is rendered for this project.

2

General / Unsupported datum transformation when exporting pointcloud

« on: February 26, 2026, 02:00:19 PM »

I am running Metashape 2.1.1 and Metashape 2.3 side-by-side on my machine. I have various projects for which I'd like to export a pointcloud using the export pointcloud dialog from the Metashape UI. All projects have a single chunk in WGS 84 (EPSG::4326), are located within the Netherlands, and I am using the following export settings:

ExportPointCloud: path = C:/Users/jolle/Desktop/test.las, save_point_classification = off, save_point_confidence = off, colors_rgb_8bit = off, save_comment = off, format = PointCloudFormatLAS, crs = WGS 84

For most projects, the pointcloud export works in both Metashape 2.1.1 and in Metashape 2.3. However, on two projects I get the error "Unsupported datum transformation" when using version 2.3. In 2.1, the export works fine. The Geoids dialog shows that the egm-96-15.tif is used. How can I further troubleshoot this error?

3

Python and Java API / Re: Exception on PointCloud.compactPoints()

« on: February 09, 2026, 02:02:55 PM »

Hi Alexey,

The workaround works like a charm. Thanks a lot!

4

Python and Java API / Exception on PointCloud.compactPoints()

« on: February 02, 2026, 04:58:04 PM »

I installed Metashape 2.3.0 (build 21954) on a Windows 11 machine.

When I open an a Metashape project with a single chunk with a pointcloud, calling .compactPoints() on the pointcloud gives an exception. Is this function broken in version 2.3?

Code: [Select]

Metashape.app.document.chunk.point_cloud
Out[3]: 2026-02-02 14:51:08 <PointCloud '56220811 points'>

Metashape.app.document.chunk.point_cloud.compactPoints()
2026-02-02 14:51:09 CompactPointCloud: point_cloud = 0
2026-02-02 14:51:09 Finished processing in 0 sec (exit code 0)
---------------------------------------------------------------------------
Exception                                 Traceback (most recent call last)
Cell In[4], line 1
----> 1 Metashape.app.document.chunk.point_cloud.compactPoints()

Exception: Null point cloud

5

Bug Reports / Run script task does not start when network processing

« on: February 01, 2024, 07:31:49 PM »

I have a small processing cluster with a server and 4 worker nodes, all on the same version - 2.1.0.17532.

When starting any task except for running a script (eg. Align Photo's), and choosing 'Yes' when asked to run as a network task:
 - The task shows up in the network monitor.
 - The full version number is shown for the task (2.1.0.17532).
 - The task is completed without errors and as expected.

When running any script and choosing 'Yes' when asked to run as a network task:
 - The task shows up in the network monitor.
 - The version number is shown as {major.minor} for the task (2.1).
 - The task is not picked up by a processing node.

My expectation is that RunScript tasks can be run over network like any other tasks. In previous versions, this was supported. Is this a bug, or am I overlooking something?

6

Bug Reports / Re: Convert images drops xmp metadata

« on: May 12, 2022, 02:46:11 PM »

Hi Alexey,

I just did a test with version 1.8.3 (the application is listing build 14431), and I am observing the same behaviour with that version.

7

Bug Reports / Convert images drops xmp metadata

« on: May 11, 2022, 04:36:06 PM »

On metashape 1.8.1 - build 13915 on Windows, when using the convert images functionality, the converted images have no xmp metadata.

Steps to reproduce:
 - Create a new metashape project with 1 chunk.
 - Add a number of .jpg files to the chunk
 - Right click the chunk, choose export --> convert images
 - In the convert images dialog, keep the default settings and click OK.
 - Select a folder for exporting.

We observe that the exported .jpg's have no xmp metadata (by running exiftool -b -xmp on the exported files).
Our expectation is, that the exported .jpg's have the same xmp metadata as their counterparts in the metashape project camera groups.

Is this a bug, or are we missing a setting/toggle/etc. in metashape? Or is this by design?