Recent Posts

Pages: 1 ... 7 8 [9] 10
Bug Reports / Re: Importing 16bit texture converted to 8bit internally
« Last post by wojtek on June 21, 2019, 11:57:51 AM »

I overlooked your reply sorry.

It does not require any specific data set but I sent you a package for convenience

There is a project file with a model and a texture to import/export.

Hello andyroo,

Glad to hear that the workaround worked, but anyway we are going to release the hotfix update in a few days.

The tweak could have disabled value, if Metashape has been installed over older PhotoScan version where the corresponding advanced option of photo view loading has been disabled. The option has been removed from the interface, but we have kept the corresponding tweak just for case.
Python Scripting / Re: Exported cameras not scaled
« Last post by willfig on June 21, 2019, 09:23:22 AM »
Hi Alexey,

The files produced by the script allow this external software to show the camera points and also have their orientation so that images can be projected back onto the dense cloud. What we've realised is that if we have a dense cloud that we've scaled in MS (using markers and/or scale bars...but no camera GPS data...we're underwater), and we export the dense cloud and run this script to get the two output files, the cameras are not in the correct position in this external software.  If we copy the chunk, turn off all scale features, update scaling and reset transformation and then do the same process, the cameras are in the correct position.  When I compare the script output files from the scaled and unscaled models they appear exactly the same...which is odd.  And importantly, I can see in the .json that even in the file exported from the scaled model, the camera centers at least are not correct.  I say that by comparing them with the estimated x,y,z values in the reference pane.  Any idea if we're doing something wrong in the script such that we're not getting the scaled values out of it?   I've attached the two .json files that come from the script from one of our projects.
 I exported it from both a scaled and unscaled version of the model. Thanks.

Feature Requests / Manual Camera alignment to Model
« Last post by aaronfhd on June 21, 2019, 02:08:03 AM »
Would be great when some pictures do not align that well or not at all we can manually align them with XYZ controls.
Setting that value to true solved the problem. Interestingly the tweak was populated (and set to false) in two of our workstations, but was not populated in the third.
still hoping for some insight on this...
Hello mkol,

If you need to get the 2D coordinates of the marker's projection on the image and the 3D location of the marker in the space (geographic system), use the following code as a reference:
Code: [Select]
x_img, y_img = marker.projections[camera].coord
x_geog, y_geog, z_geog =

The second line gives you the estimated position of the marker in geographic coordinates, like you see it in the Reference pane -> Estimated values tab.
General / Depth Filtering Level (Micasense RedEdge MX)?
« Last post by ihb on June 20, 2019, 08:43:45 PM »
Hello everybody!

I am working on a project involving monitoring grain sorghum height throughout the early growing stages. To do this, I captured a DEM (bare soil, before any growth) and will then capture data when the sorghum is growing to generate a DSM; the DSM will be subtracted from the DEM to get vegetation height.

My question is this: What depth filtering should I use? I need as much detail as possible since my plants are really small. As I understand it, the higher the level of depth filtering, the less detail will be shown in the DEM/DSM.

Here are the parameters/equipment I am currently working with:

DJI Matrice 200
Camera: Micasense RedEdge MX
Flight altitude: 30m (I desire to eventually take this down to an altitude of 15-20 m)
Alighment quality: High
Key point limit: 40,000
Tie point limit: 4,000
Dense point cloud accuracy: High
Depth Filtering: Mild

Any help would be appreciated! Thanks everyone!

Hello tpubben,

When working with the scripts run in headless mode, we usually recommend the following way of project creation:

Code: [Select]
doc = Metashape.Document() = "D:\Projects\new_empty_project.psx") #new empty project is created
So do not use in case of stand-alone module and scripts run in the headless mode.
Python Scripting / Re: Saving multiple chunks to separate psx files
« Last post by Alexey Pasumansky on June 20, 2019, 08:27:23 PM »
Hello danderson4,

Document class element has optional chunks parameter that allows to path the list of chunks to be saved, for example:

Code: [Select]
doc =
#... some processing

for i in range(len(doc.chunks)):"D\chunks\" + doc.chunks[i].label + ".psx", chunks = [doc.chunk[i]])
As you see the original project is re-opened, since the doc variable is re-assigned, if the project is saved in PSX format.
Pages: 1 ... 7 8 [9] 10