Agisoft Metashape 2.1.0 pre-release

[bassistas]

With this release, if I export the model and import it back it comes up in a different position, so its impossible to do any editing on the mesh on another program and then re-import it back for re-texturing. It seems that during the export the model is shifted by a few meters.
Also sometimes the model rotates by itself inside metashape if I decimate it through the decimate model command.

[renevg]

when exporting model + textures it doesn't export the displacement map. The other textures are fine. Exporting displacement map manually  is sometimes fine, sometimes it exports a black jpg.
Would be nice to build all textures in batch.
regards
René

[spader]

Ive been trying out the geometric matching with good results. Heres a few features which might improve it. I assume youre working on many of them already. Considering were treating the clouds as images in a sense (extract tie points for bundle adjust), they should be treated in a similar manner in the gui, for great simplicity when were used to Metashape with images.

- Allow multi-scanner rigs similar to multi-camera setups. Use case is for throwing together a few lidars for a poor mans laser scanner and joint optimizing their internal relation at the same time as were optimizing the large scene.
- Have some symbol for a laser scan, similar to cameras that shows up in model space.
- Allow us to use the matching graph to see the scan relations.
- Allow editing of the matching graph. Right click on link > Remove factor. Right click two or more selected scans > Add factor.
- Choose cloud markers. Right click in a scan and add marker, simple as that.
- View laser scan orientation data in reference.
- Distinguishing the optimization results from photograph tie points when right clicking tie points - show info. Right  now, its reported in same units/manner as photos.
- Allow estimated prior positions in reference, just as with images, with known offset.
- The number of strong points extracted seem fixed regardless of point cloud size or quality or number of allowed tie points. Allow more!

[Alexey Pasumansky]

With this release, if I export the model and import it back it comes up in a different position, so its impossible to do any editing on the mesh on another program and then re-import it back for re-texturing. It seems that during the export the model is shifted by a few meters.
Also sometimes the model rotates by itself inside metashape if I decimate it through the decimate model command.

Can you please check, if the issue is resolved in the newly released 2.1.0 update (build 17343)?

[Alexey Pasumansky]

when exporting model + textures it doesn't export the displacement map. The other textures are fine. Exporting displacement map manually  is sometimes fine, sometimes it exports a black jpg.
Would be nice to build all textures in batch.

Hello René,

See the comment about the displacement map here:
https://www.agisoft.com/forum/index.php?topic=15691.msg68012#msg68012
The suggested export format for it is .TIF, as it allows 32-bit Floating point values.

[bassistas]

With this release, if I export the model and import it back it comes up in a different position, so its impossible to do any editing on the mesh on another program and then re-import it back for re-texturing. It seems that during the export the model is shifted by a few meters.
Also sometimes the model rotates by itself inside metashape if I decimate it through the decimate model command.

Can you please check, if the issue is resolved in the newly released 2.1.0 update (build 17343)?

Hello, I just tried this build, the issue still exists when I export an FBX file but when I  export an obj file and then import it back again it comes in the same position. So it is partially solved, at least for the obj format and I can continue working with my projects now, thank you!

[Alexey Pasumansky]

Hello bassistas,

Can you provide more detailed description of the steps followed starting from model generation (also specify the coordinate system of the chunk, model and CS options in export/import dialog)? I was not able to reproduce any problem with export-import workflow for FBX model in the latest pre-release version.

[Dsenovilla]

Hello!
I have been doing some tests with version 2.1 (17343) and I have noticed that when creating a DEM from a laser scanner the option to deactivate interpolation has disappeared, while in version 2.0.3 when creating the DEM from a point cloud it does exist.

[rowild]

A somewhat cheeky question: do the pre release version reset the trial period, if I have 2.0.3 Standard (Trial) installed?

[Raitis]

When testing using aerial lidar scans, I noticed, that confidence threshold at which lidar geometry takes over is pretty low, even if density is high (300p/m2). If I have high confidence in lidar scan (it's manually classified and cleaned) is it possible to increase its weight (via tweaks)?

Another issue, which is more general: glass facades and windows for city - are there some development works in direction of detecting and masking them?
https://www.sciencedirect.com/science/article/pii/S156984322300064X

Similarly with cars - it is better to have flattened surfaces, than broken wrecks. We made set of scripts, that creates masks in oblique images, but this almost doubles processing time, but if done internally, should be a lot faster.

[mrv2020]

Code: [Select]

import Metashape
import sys, os, time

chunk = Metashape.app.document.chunk
chunk.reduceOverlap(overlap = 5, use_selection = False)

Metashape.Model.clear(chunk.model)

This simple script does not work in batch process run over network, in local batch process it works fine. In 2.0.4 it works on local and network.

Laser and Images.

The import of the lasers, the workflow I imported the laser as listed at https://agisoft.freshdesk.com/support/solutions/articles/31000168474-terrestrial-laser-scans-processing-in-metashape-2-0- 0, pinned and locked the transformation in group only, aligned the photos. The laser has a precise position, and so do the photos. But before aligning we can see the error of 1.2 cm, and laser marks with 8 pixels with an error of 4 meters. Then I reset the laser alignment and realign. Now the images have an error of up to 5cm and the marks have 0.6pixels but with an error of 4 meters. Solution. It is necessary to deactivate the laser, align images and activate the laser, reset the laser alignment and align. The error now no longer exists, but the initial position of the laser, of course, I lost. Your import has the option to return without importing the laser.

So I worked with isolated processes, laser in one and the other, aligning images, applying laser to the images, merging, now checking the errors in the markers that I exported previously and the error no longer exists. But together it didn't work.

And, please, add option to remove orthophotos without script.

[bassistas]

Hello bassistas,

Can you provide more detailed description of the steps followed starting from model generation (also specify the coordinate system of the chunk, model and CS options in export/import dialog)? I was not able to reproduce any problem with export-import workflow for FBX model in the latest pre-release version.

The issue still exists in the latest stable release 2.1.0. The project contains photos from a DJI drone and laser scans imported as e57 files. The coordinate system is WGS 84, it doesn't matter which options I choose during the export or what file format, the exported model always comes up shifted by a few meters from the original position. I can send you an example project  (without the photos and laser scans) to investigate if you want.

[olihar]

Hello bassistas,

Can you provide more detailed description of the steps followed starting from model generation (also specify the coordinate system of the chunk, model and CS options in export/import dialog)? I was not able to reproduce any problem with export-import workflow for FBX model in the latest pre-release version.

The issue still exists in the latest stable release 2.1.0. The project contains photos from a DJI drone and laser scans imported as e57 files. The coordinate system is WGS 84, it doesn't matter which options I choose during the export or what file format, the exported model always comes up shifted by a few meters from the original position. I can send you an example project  (without the photos and laser scans) to investigate if you want.

Sounds like your problem is because you are using WGS84 as coordinate space, why not use a real coordinate space with accuracy and measurements, not something in degrees.

[bassistas]

Hello bassistas,

Can you provide more detailed description of the steps followed starting from model generation (also specify the coordinate system of the chunk, model and CS options in export/import dialog)? I was not able to reproduce any problem with export-import workflow for FBX model in the latest pre-release version.

The issue still exists in the latest stable release 2.1.0. The project contains photos from a DJI drone and laser scans imported as e57 files. The coordinate system is WGS 84, it doesn't matter which options I choose during the export or what file format, the exported model always comes up shifted by a few meters from the original position. I can send you an example project  (without the photos and laser scans) to investigate if you want.

Sounds like your problem is because you are using WGS84 as coordinate space, why not use a real coordinate space with accuracy and measurements, not something in degrees.

I don't care about the coordinate space as I don't georeference my model, I use the laser scans as reference which are in local coordinates and I just need to export the 3d model in local coordinates also. That is the workflow I always follow but now with the latest version of Metashape when I export the model it doesn't hold its original position and I cant re-import back to re-texture it after the cleanup in another program.

I just tested the previous 2.0.0 version and the bug does not exist there. I can export/import the model and it stays in the same position as it should