Forum

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 - jnb

Pages: 1 2 [3] 4
31
General / Re: Import transformation matrix from CloudCompare
« on: December 17, 2019, 03:50:03 PM »
By the way here is the kind of 4x4 matrix I get from CC.

0.9989238771179371 -0.0313060372092998 0.0342201659539925 -8403.3011118634076411
0.0083067630845548 0.8466571728972258 0.5320738945566998 -10010.7389053153965506
-0.0456298741037703 -0.5312170588525252 0.8460061175744220 -6650.4709921952662626
0.0000000000000000 0.0000000000000000 0.0000000000000000 1.0000000000000000


I guess I have to use "chunk.transform.matrix" but I don't get how...

32
General / Re: Import transformation matrix from CloudCompare
« on: December 15, 2019, 06:27:00 PM »
Hello,

Thank you for your answer. Python is indeed the way but my skills are alas too limited in this matter...

33
General / Import transformation matrix from CloudCompare
« on: December 10, 2019, 09:19:00 PM »
Hello,

I am looking for a way to import a transformation matrix from CloudCompare (or Geomagic / 3dReshaper) into Metashape for an entire chunk.

Somebody have an idea ?

Thank you

34
General / Shapes missing on orthomosaic
« on: November 28, 2019, 08:14:41 PM »
Hello,

I still have issues with the shapes.
I made several orthomosaics within the same project, with different projection planes. I drew shapes on the first one, then on the second one with a different projection plane.
Now, when I go back to the first one, the shapes are no longer in the good projection. Making a new shape or actualising the orthomosaic makes no difference.  Worse, I now have lost the shapes on the second one as well.

It is really confusing since I don't get the logic behind it. Basically, I just lost a huge part of my work.

Thank you for your help.


35
I have nerver tried this export mesh - import points workaround, thank you for the suggestion.
I have seen the new option in 1.6, looking forward to test it in new projects.

If I can find some time, I'll test this two options on my (very) noisy project and let you know.

36
Hello Alexey,

I completely understand that for most projects this limit is enough and why this setting is not in the GUI.
My point was that it would have been better to let us known about this change since it is not a trivial one.

By the way, I indeed work a lot with dense cloud (for profil extraction etc) and also because it allows me to correct imperfections on complex projects before generating the mesh. On simpler cases, the depth maps generated mesh is enough.


37
Hello,

Working lately on a drone acquisition, I have been stroke by the poor quality of dense cloud noise filtering. I eventually found a topic talking about the same issue : https://www.agisoft.com/forum/index.php?topic=10362.15

The last post from Dieter give me the answer :
Hello

I had the same problems and was amazed at the poor quality of the point cloud in the latest version. Starting with one of the last versions, the dense_cloud_max_neighbors parameter was set to 100 by default.

Experience has shown that this value was too low for me. Especially with objects that were photographed against the sky, extreme deviations formed.

I set this value to -1 and the calculation time was much longer. Now the point clouds are in the quality of the past again.

I hope I could help.

Greeting
Dieter


The default number of depth maps used for the dense cloud filtering stage have indeed been changed  - in June if I am not mistaken - shifting from no limit to 100, without any mention in the change log. To get back to the previous behaviour, you now must use the well known tweak main/dense_cloud_max_neighbors and set it to -1.

This is a major issue for me, as this undocumented change vastly impact the quality of dense cloud on at least some kind of projects. It would have saved me a lot of time and headaches if I have been aware of this change. I understand that this new threshold probably works in most cases but a change so sensitive should have been clearly explained.

You can find attached exemples of how the number of depth maps used impacts this project (default 100, 350 and 850) and the position of the cameras (heavy overlap)

It would be great if in the futur this kind of changes could be more documented.

Regards.

38
General / Unwanted dense cloud or mesh cuttings at export (solved)
« on: November 22, 2019, 03:33:13 PM »
Hello,

On some projects I have unwanted random cuttings when exporting dense cloud or mesh. (v 1.5.5)
Any idea of what could cause this issue ?

Thank you for your help.

Edit : OK I found it. The issue was caused by shapes (boundaries) drawn on the orthomosaic. This shapes impact also the dense cloud and model.

39
General / Re: Adjusting camera extrinsic giving initial cameras config
« on: November 20, 2019, 03:23:28 AM »
Hello,

Maybe you can check the new alignment options in 1.6 beta. You could tried the estimated preselection after importing your camera configuration (xml)

Sequential pre-selection is trying to match the images with a bunch of their neighbors according to the camera labels.

Estimated preselection is based on the estimated camera locations after initial alignment (for example, performed using rough accuracy settings).

One of the possible scenarios of use - when aligning the video sequence frames run Sequential preselection at first and then Estimated preselection, if there are intersecting parts of the image acquisition path.

40
General / Re: Export import Shapes on orthomosaic
« on: November 17, 2019, 02:19:41 PM »
Hello Alexey,

The shapes are indeed drawn on the orthomosaic generated in a custom projection in the first project.
On the duplicated project, I generated the same orthomosaic with the same plane (same 3 markers) but different size (I needed only a small part of the orthomosaic).

I need the shapes to be drawn on the orthomosaic because I use them as boundaries.

41
General / Export import Shapes on orthomosaic
« on: November 15, 2019, 07:59:52 PM »
Hello,

I'm working on a duplicated project and I need to export shapes drawn on an orthomosaic of a wall from the source project and import them into the copy, on the same orthomosaic generated with the same projection plane (3 markers).

Unfortunately, I can't find a way to do it. I think the issue is related to the coordinates system, so I tried to remove the shape layer in both projects and draw the shapes again, with no success.

The chunk is in EPSG 3944 and the orthomosaic and shapes in EPSG 4964

Thank you for your help

Edit: tried to solved my problem using othomosaic import in Metashape 1.6 but didn't work either, apparently EPSG 4964 is not present.

42
General / Re: Agisoft Metashape 1.6.0 pre-release
« on: October 03, 2019, 02:12:31 PM »
Hello,

I was wondering about the new options in the align photos stage : source - estimated - sequential.
I think sequential speaks for itself but what do the others ?

Thank you

43
General / Estimation of orthomosaic resolution for imported dense cloud
« on: September 16, 2019, 06:27:14 PM »
Hello,

I noticed a difference in the orthomosaic resolution estimation between original and imported dense cloud. I only exported the dense cloud generated by Metashape for cleaning purposes on another software and then imported it again in the same project (in ply).

Is there a way to preserve the original resolution estimation ?

Thank you



44
Bug Reports / Inconsistant window size
« on: June 11, 2019, 09:13:41 PM »
Hello,

I noticed some time ago a minor ui issue, but still quite annoying a least for me : when editing an ortho using the draw patch tool, the assign images window don't keep the same size and emplacement from a modification to another. It therefore needs to be resize manually every time, especially since it is often beyond the limits of the screen.

Not a big deal but a fix would be much welcome !

Regards

45
Hello Alexey,

No, no change in the hardware at all.
Right now I don't have the time to run Memtest, but I'll give it a try as soon as I can.

Voltage, fans speed, temperature, everything is fine. The only change I can think of is the installed version of nvidia drivers. I have updated them today, and I'll try to run the new mesh generation again when I'm done with the current project.

Others ressources demanding tasks perform well (depth maps, dense cloud)

Pages: 1 2 [3] 4