Messages

1

General / Re: Wrong camera calibration - adjusted focal lenght too off

« on: Today at 01:48:58 AM »

Hello, michaldolnik
I suggest you to carefully inspect geotags.
I have seen some cases where really bad geotags are wrongly qualified as accurate as a few centimetres while just watching the coordinates one can see they are wrong.
When you load pictures in a new project you will see the blue balls representing camera locations. watch and see if there is any obvious blunder or misplaced ball.
if you see something suspicious, just uncheck the box for the suspicious photos. If they are tagged as accurate, they can potentially causing a strong bias in both exterior orientation and interior params.

Best regards
José

2

General / Re: GUI in Spanish

« on: February 01, 2023, 02:16:02 AM »

Thank you! That SP GUI typo is likely my fault, I'm sorry!
by the way, don't you think Omega Phi Kappa is the "right", the same fashion as XYZ is the right way for me whereas YXZ... is like driving on the left lane. Very much of an annoyance like nowadays is the entire English System of measurement. (personally: I think the whole world would benefit from banning non IS units whose survival in the globalized world only produces headaches and often catastrophic errors... even some English people privately agree)
Regards

José Martínez Rufio... ups, sorry, it's Rubio

3

Feature Requests / Allow saving bounding region

« on: January 23, 2023, 03:01:53 PM »

I know we can use script to copy region from one chunk to another, but it would be useful to save it so it can be recalled easier.
Regards

4

General / Re: Fill holes in pointcloud?

« on: January 19, 2023, 02:55:40 PM »

Build a watertight mesh from depth maps, and then build a point cloud from the mesh (by sampling) with the desired point spacing... this workflow tends to deliver a much cleaner dense cloud.
Best regards,

José Martínez CTO
Geobit & Accupixel

Metashape training endorsed by Agisoft:

https://accupixel.co.uk/courses/metashape-standard-edition/

https://accupixel.co.uk/courses/metashape-professional-edition-for-forensics-surveying/

5

Bug Reports / Re: ... error reading pixel

« on: January 13, 2023, 06:58:19 PM »

Hi, Alexey, it happens consistently. New computer, 64gb ram. Sorage is ssd, Ryzen9, dual Gtx 1070ti, up to date Nvidia drivers... and occurs after depth maps are finished while mesh is being built. Will try same proj in my older computer.
regards

6

Bug Reports / ... error reading pixel

« on: January 13, 2023, 04:06:54 PM »

What can I do?

[...]
2023-01-13 13:55:52   2.83981/4~71% avg groups per camera
2023-01-13 13:55:52   146.25/206~70% avg cameras per group
2023-01-13 13:55:52   0% leaves avg camera intersects in group
2023-01-13 13:55:52   1% big leaves avg camera intersects in group
2023-01-13 13:55:52   29% of leaves are big
2023-01-13 13:55:52   100% of voxels in group are from big leaves
2023-01-13 13:55:52 saved 4 groups (0.03125 KB) for 344 leaves
2023-01-13 13:55:52 saved 2.28516 KB of affected cameras and 0.804688 KB of exclusive cameras for all leaves
2023-01-13 13:55:52 Scheduling octree 344 leaves hist initing in 4 groups (86 avg leaves per group)
2023-01-13 13:55:52 Initing hists in leaves group #1/4: [0; 60)...
2023-01-13 13:56:02 total cubes: 105221949 cubes, 1605.56 MB, 163.966 MB/s
2023-01-13 13:56:02 Data: 2408.34 MB hists + 0 MB codes, 117.297 MB pyramid
2023-01-13 13:56:02 Found 2 GPUs in 0 sec (CUDA: 0 sec, OpenCL: 0 sec)
2023-01-13 13:56:03 [GPU 1] Using device: NVIDIA GeForce GTX 1070 Ti, 19 compute units, free memory: 7104/8191 MB, compute capability 6.1
2023-01-13 13:56:03   driver/runtime CUDA: 12000/10010
2023-01-13 13:56:03   max work group size 1024
2023-01-13 13:56:03   max work item sizes [1024, 1024, 64]
2023-01-13 13:56:03 [GPU 2] Using device: NVIDIA GeForce GTX 1070 Ti, 19 compute units, free memory: 7197/8191 MB, compute capability 6.1
2023-01-13 13:56:03   driver/runtime CUDA: 12000/10010
2023-01-13 13:56:03   max work group size 1024
2023-01-13 13:56:03   max work item sizes [1024, 1024, 64]
2023-01-13 13:56:08 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:08 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:08 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:09 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:09 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:09 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:09 [GPU 1] Exception
2023-01-13 13:56:09 [GPU 2] Exception
2023-01-13 13:56:09 Peak memory used: 8.44 GB at 2023-01-13 13:56:06
2023-01-13 13:56:09 deleting all temporary files...
2023-01-13 13:56:10 done in 0.734 s
2023-01-13 13:56:10 Finished processing in 2280.18 sec (exit code 0)
2023-01-13 13:56:10 Error: Can't decompress depth

7

General / Re: Weird decimation

« on: January 13, 2023, 03:00:56 PM »

Model   
Faces   452,844
Vertices   229,662
Vertex colors   3 bands, uint8
Depth maps generation parameters   
Quality   Medium
Filtering mode   Mild
Max neighbors   16
Processing time   7 minutes 24 seconds
Reconstruction parameters   
Surface type   Arbitrary
Source data   Depth maps
Interpolation   Enabled
Strict volumetric masks   No
Processing time   9 minutes 9 seconds
Memory usage   8.29 GB
Date created   2023:01:13 10:01:27
Software version   2.0.0.15597
File size   10.41 MB

8

General / Weird decimation

« on: January 13, 2023, 01:27:37 PM »

I've recently observed that during decimation metashape divides the whole mesh into regions and it looks it decimates diferently. It gives the impression that it sets triangle count per cluster as target rather than a global volumetric parameter for cutting the iterative reduction process, so it leads to very noticeable diferences in mesh resolution thus exactness between clusters.
I think there's room for improvement here.
Regards

9

General / Re: Dense Cloud to PTS (or e57, las etc) to RCS Problems

« on: January 09, 2023, 01:55:29 AM »

it shows just a long straight line of points

Very likely you are exporting geographic coordinates: lat/lon/elev and they are read in Recap as if they were X/Y/Z.
If you think a bit, you will surely understand why all your points look like a single line, or better, like a tall stack of points. They vary some metres in Z and barely move sub-microns in X/Y
Regards

José Martínez
Agisoft training

10

General / Re: how to add an elevation offset to Point Cloud and to DEM based Point cloud?

« on: October 25, 2022, 10:16:37 PM »

Export the cloud with the offset (you can enter shift during export) and then import again.
Cheers,

José Martínez

Geobit & Accupixel
Agisoft endorsed training providers.

11

General / Re: How to solve strange images aligment

« on: October 23, 2022, 11:08:12 AM »

Precalibrate your camera could be the best solution.

12

General / Re: Agisoft Metashape 2.0.0 pre-release

« on: October 16, 2022, 04:21:27 PM »

It is rather difficult to understand for me why steps towards the integration of lidar/laser scans and photogrammetry requires the removal of  the terms "laser scans", or "LiDAR" from all menus. Apparently import scans sounds too much explicit or specific, so it is better to call them depth images.
Why not "structured laser scans" versus "unstructured point cloud? Also why drag and drop scans over the chunk is still impossible?
Thanks for the update!!!! I'm eager to test it further.

Best for good russians.

13

General / Re: How to display 3D side by side in fullscreen ?

« on: October 14, 2022, 12:38:28 AM »

Are you trying to adapt some stereoscope? I do not recommend it: I did it some time ago and the stereo view was deformed and uncomfortable... I spent many days working this way and finally gave up. Later I purchased a true stereoscpic diplay based on dual monitors and a splitting mirror... and OMG, this is glory! I love it. I'm an absolute fan of stereo plotting it feels like diving into the reality. Seriously, forget split view. Aspect ratio gets wrong, Agisoft has done something wrong with the split view and I have already told them but they don't seem to care enough about old school stereo photogrammetrists. Get a stereo ready card and just let me know if you want a proper stereo display.
Cheers

14

Feature Requests / back face color tint

« on: October 13, 2022, 02:45:50 PM »

Dear Agisoft devs.
I know there is an option for back face culling that works during orthomosaic creation hiding triangles with normals pointing towards the projection plane. It works well in some cases, but not-so-well for complex geometry where it often creates confusion when triangles in the hidden areas have normals towards the viewer.
I would like to have also an option for using a distinctive tint overlay for inverted triangles as alternative to culling.

The mesh is rendered darker for inverted faces, but it is not so much different to the positive face when texture or colour is also dark. It would be nice to have the color tint option also in the model viewport when looking at textured or shaded mesh.

Best regards.
José Martínez

15

Feature Requests / Re: Use Drawing plane as reference plane for exporting orthomosaic

« on: October 13, 2022, 02:20:15 PM »

It is already available. Select the same three markers used for drawing plane definition also for building the planar orthomosaic... or am I missing something?