Recent Posts

Pages: 1 2 3 [4] 5 6 ... 10
Bug Reports / Help with a heavy project
« Last post by OZDF on June 15, 2021, 12:54:31 PM »
Hi everyone,
I am writing on Metashape forum because I need some advice for a huge work.
My machine is an Intel i9 18 core, 128 GB RAM, GeForce 3060 RTX 12GB, 4TB SSD, Motherboard Asus Prime X299-A2.

I am working with Metashape to reconstruct a big wooden church choir, it has a lot of details and I took 1620 pictures of this object.
Since it is the first time I use Metashape for a big project, I tried to work with all the 1620 uncompressed pictures (25mb each photo). The alignment worked but once I tried to do the dense cloud the computer wasn't able to process the action. My SSD and RAM jumped to 99-100% of activity and the completion rate did not advance once 4% was reached (even if I left my computer working for days).
So I decided to create the dense cloud dividing the church choir into smaller parts, but the results of the alignment weren't as good as the alignment of the whole object with 1620 pictures. Indeed I would say that the results obtained were full of errors. So I just tried to reduce the size of the pictures to 4-6 mb each. This time I reached about 70% of completion with a normal use of memory, CPU, etc, after 70% everything goes to 100% and the completion rate doesn't advance.

Is there a "right way" to go for this kind of big projects? What would be the steps you would take to get a good result?
Furthermore, from my experiments, I noticed that it is more difficult to obtain a good result by dividing the project into smaller parts rather than processing big objects as a whole, but in this case obviously we have to contend with the limits of computer performance. Is there a way to subdivide a big the project without losing quality in the result? Maybe doing the alignment of all the 1600 photos, and after that dividing it in 4 chunks and creating smaller dense clouds (I am now trying to proceed in this way, but it is just an experiment).

Thank you so much for your patience and information.
Feature Requests / Re: Zoom to marker/shape
« Last post by c-r-o-n-o-s on June 15, 2021, 12:48:38 PM »
That is no problem. Mark your point and zoom in. Then go along the markers with the keys Page up / Page down.
General / Re: Should I build dence point cloud at all now?
« Last post by c-r-o-n-o-s on June 15, 2021, 12:41:45 PM »
I found the depth maps to be far more accurate and the whole process is quicker.

That's what I always thought until now. But even if I reuse the depth images, DEM creation with the point cloud is much faster than from the depth images.
Python and Java API / Re: Question about sensor and camera coordinates from api
« Last post by Phogi on June 15, 2021, 09:07:12 AM »
Hi Paul,

Thank you so much, I actually found that the marker position I used was wrong! In GUI GCP002 is the first marker but then in the chunk.markers it is the third, so I was using another marker position that's why it was off a lot!

May I ask if you know how can we get the projection matrix? As camera.project() can project world coordinates into image coordinates, from my understanding the marker.position it should be meaning the u,v,w coordinates, but it can't directly change from homogenious coordinates by divide the w, so I'm confusing about which internal coordinate system does this marker.position actually refer to?

Thanks a lot!

Jose and myself have recently added two topics dealing merging photogrammetry with laser scan data into the Professional online training course:

Access to new material for all existing students is included.
General / Re: Metashape Professional and Coral Reef Measurement
« Last post by SimonBrown on June 14, 2021, 06:01:29 PM »
What's the cost of a  UWIS GPS system?

It really depends what your needs/requirements are, but for single diver tracking then this:

Would get you started. This would also enable merging of camera positions with GPS data via our App (Accupixel are the UK dealer for UWIS and customers get the app).

Tablet for bidirectional comms and navigation is extra, as is additional tracker units.

Hope this helps?
We wanted to process RGBI geotiffs with 16 bit to get point clouds and DEMs. The RGB bands were properly defined and recognized by Agisoft Metashape. The 4th band was not recognized as NIR by Metashape (Set Primary Channel: Channel 4 was empty). We need the 4th band to be defined as infrared band, because only in that case the exported point clouds are saved in version .las 1.4 with point cloud format 8 which can store the infrared band and additional attributes properly.
Unfortunately the python script to redefine the 4th band fail, but we found out that if you redefine ALL of the 4 bands at the same time, it sets also the 4th band to NIR.

We hope somebody will profit from our findings.
Python and Java API / Re: Exported Model does not have RGB color values
« Last post by danimlk on June 14, 2021, 03:02:36 PM »
Hello danimlk,

For buildModel operation which uses depth maps data as a source, I suggest to add the following lines for the vertex colors calculation:

Code: [Select]
colorizeModel = Metashape.Tasks.ColorizeModel()
colorizeModel.source_data =Metashape.DataSource.ImagesData

Hi Alexey,

Thank for replying, I've added this to my script and it works now. The final output now has the color information.

Thanks for the help!  :)
Python and Java API / Re: Console output and stdout
« Last post by marg on June 14, 2021, 12:07:47 PM »
Thanks for the reply.
Yes, this is the way I am currently doing it, redirect everything to some file. But this gives me no flexibility. Since the metashape workflow is just part of a bigger processing chain (of which I also want a couple of lines of comprehensive output), I cannot selectively decide which part of the metashape output I want, and which I don't. The workaround I have now is redirect everything to some temporary file, and log the parts I want from metashape (x/x cameras aligned, ortho written etc) manually. I was just hoping there would be a more elegant way to deal with the metashape console output.
General / Re: Should I build dence point cloud at all now?
« Last post by dpitman on June 14, 2021, 04:16:14 AM »
So good to see @Paulo & @JMR's comments. For use cases where classification is needed (drone photogrammetry in my case) I think the dense point cloud workflow is the only option.
Pages: 1 2 3 [4] 5 6 ... 10