Topics

1

Python and Java API / Overloading PointClass to have custom values

« on: February 17, 2023, 09:56:05 PM »

@Alexey and @paulo is there a way to add custom classes to Metashape.PointClass though the Python API? Is there a definition of these classes in a Python script somewhere within the Metashape applications folder?

2

Python and Java API / Importing a Dense Cloud as .ply with Confidence Values?

« on: January 11, 2023, 08:21:35 PM »

How could one import a dense cloud as a .ply (or other file format) into metashape using the python api with confidence values included? Essentially a custom dense cloud is being made and I would like to tack on "confidence values" so they can be filtered using the Metashape GUI.

Jordan

3

Python and Java API / Changing the Python Interpreter

« on: January 06, 2023, 01:08:42 AM »

Hello,

Is it possible to change the python interpreter being used in the Metashape GUI to a custom one (i.e., anaconda)? I have some scripts running from the Metashape GUI that require additional dependencies, and I would rather not install them on the same python interpreter that Metashape uses by default, and instead switch to another one, but still have everything run within the Metashape GUI.

Jordan

4

Python and Java API / List of points within dense point cloud

« on: December 19, 2022, 08:55:53 PM »

How can one obtain a list (or np array) of points within the dense point cloud using the Metashape API? I can see that points within the sparse point cloud can be accessed, as well as the vertices of the mesh. From the dense point cloud you can get the point count, and select using a filter, but how would you get access to the points to change an attribute like the color?

Jordan

5

General / Colorizing Dense and Mesh using Export Ortho - Unexpected Results

« on: November 20, 2022, 03:39:06 AM »

Hello!

I saw that Metashape allows for colorizing the dense cloud and mesh using an orthomosaic, very handy! However, I'm running into unexpected results in specific scenarios and would like to know why. If an ortho is made and the dense cloud and mesh are colorized using said ortho, everything is fine and you can see that the mesh does indeed change (turns black) where there are no data values. However, if that ortho is exported using default parameters and re-imported (no changes to the file) and the same process is performed, the dense cloud and mesh appear to be smeared (see mesh_after_export.png).

The scene is not geo-referenced, the ortho was made using Planar (Current View). Ortho re-imported in Local Coordinates (m) with the No Data value set to 0.

Thanks!

6

General / Textures from 2D atlas being re-used on 3D model?

« on: September 27, 2021, 05:42:24 PM »

I just have a quick question regarding the 2D texture atlas output for a textured model: is there a 1-to-1 ratio with the pixels (RGB values) in the 2D texture atlas to the 3D model, or are some of the RGB values reused?

For example, if I were to go one-by-one through a single texture atlas and project the RGB values within each pixel index to the 3D model, each RGB value would only be mapped from the 2D texture atlas to the 3D model once, correct?

Thanks for any clarification!

@Alexey Pasumansky