Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - sfmdd

Pages: [1] 2
If you cancel Dense Cloud oder Build Mesh process after the depth maps are completed the depth maps will preserve and you can save the project and continue the process later.
Maybe you can write a script for overnight projects doing that as a workaround.


Feature Requests / Re: Orthomosaic of Face
« on: December 16, 2021, 02:11:32 PM »
You can build an orthomosaic from view point by changing Projection Typ to Planar and choose what you want in Projection plane menu in the Build Orthomosaic dialog.
Or do i miss something?


Feature Requests / Re: DHHN2016 Geoid
« on: December 15, 2021, 11:11:52 AM »
Yes, exactly.

Feature Requests / Re: DHHN2016 Geoid
« on: December 15, 2021, 09:39:39 AM »
I guess for a country wide you have to pay. But at least for some states you can get the geoid in different file formats, mostly not tiff, but that doesn't matter due to metashape can read most of the files. I'm using the GCG2016 from saxony in gsf-format, just because it's readable and not binary like for example the Trimble-Format, but you can use that as well.
Just search for GCG2016 at your states survey agency.


General / Re: Mesh from Dense Point Cloud vs. Depth Maps
« on: October 18, 2021, 09:26:24 AM »
You could delete the polygons and fill the voids with the "close holes"-command. This command is sometimes sketchy and not working as supposed but you could also try to fix the holes with 3rd-party software like Blender.

General / Re: Import German Geoid Model into Metashape
« on: September 15, 2021, 08:23:15 AM »

not a solution for your problem, but what i am doing is using the already integrated DHHN92 heights in metashape and set an offset when exporting the final products, which for my region is usually 2 cm.

I wasn't able to use the GCG2016 from saxony in metashape neither.


Feature Requests / Re: Close Holes - Within Selection
« on: September 07, 2021, 02:13:18 PM »

Bug Reports / Re: Help with a heavy project
« on: September 07, 2021, 09:22:08 AM »
What quality settings are you using?
1600 images on ultra high settings are a quite large project, try medium or high quality in dense point cloud and mesh stage, it should run through easily with a much lower processing time.

Just to show the difference on a project with 303 20 Mpx images:

High Quality
Depth Maps      2h38min    6 GB Memory usage
Dense Cloud    1h27min    20,5 GB Memory usage

Ultra High Quality
Depth Maps      10h26min    21,8 GB Memory usage
Dense Cloud    8h34min      44,4 GB Memory usage

Both on Metashape Pro 1.6.5


Bug Reports / Re: 1.7.3 - Sample Points Bug
« on: August 19, 2021, 07:54:15 AM »
The point cloud doesn't matter if you're doing depth map based reconstruction. As the general results are much better than point cloud based meshes most of the time.

General / Re: DEM file
« on: August 18, 2021, 12:19:50 PM »
It's a Professional Edition Feature only i guess.

General / Re: Clean up work flow? What's yours?
« on: May 05, 2021, 09:06:55 AM »
Have you tried building the mesh from depth maps?
The resulting mesh is always much better in my experience.


General / Re: Problem with phantom 4 pro and samsung S20 matching
« on: March 29, 2021, 12:27:09 PM »

had the same issue today. Deleting the GPS-Tags from the Samsung images solved the problem for me.

General / Re: Adding height to DEM in Agisoft
« on: February 15, 2021, 11:56:35 AM »
Hi toffersan,

Export your DEM as a geoTIFF and use QGIS (free and open-source) to perform a shift along the z-axis.
Use RASTER > RASTER CALCULATOR to do so (Z=Z+[enter_value]).


It's actually the same for ArcGIS.
But a simple +/- option in the export DEM dialog in Metashape would be very nice. A Z-Shift for Point Cloud and Mesh-Export is already available, so i don't see why it shouldn't be there for the DEM.


Hi, i'm not sure if this helps with your problem:

1. Looks like if you're using way to much images for this kind of an object, around 50 would do the job. Maybe the software is also messing around with the different focal lenghts in close ranges but i'm not sure about that.
2. Don't adjust images at all. I'm also a bit confused about the anti aliasing filter in the RAW images, there shouldn't be any filter. If so: Canon, what are you doing?


I'm still using Metashape 1.6.2, so maybe it's fixed in a newer version already?

When importing a TLS pointcloud in las-format, Metashape seems to shift the points in a random direction for a very small value. Some attributes are also modified, classification is lost, intensity changed big time and the "point record"-value is totally different. RGB, Number of returns or Return numbers on the other hand stays the same.

Whats going on here?

In the attached 2D-ArcMap-Screenshot you can see the horizontal shift, brown points are the original las-points and the red points was imported and directly reexported again from Metashape. The grey squares have an edge length of 2 cm.


Pages: [1] 2