Forum

Recent Posts

Pages: [1] 2 3 ... 10
1
General / Re: Texture problems with large project
« Last post by Bzuco on July 04, 2022, 07:09:31 PM »
I wrote two posts in this topic https://www.agisoft.com/forum/index.php?topic=14145.0

If your workflow is only in metashape, the fastest way how to guess the size and count is simply do one texture 4k or 8k size which does not take so much time and then compare the result with original photos. If the result looks like 4 times less sharper, then increase 4x the count or 4x the resolution...so one quick test, one quick visual guess/comparisson and then one final texture calculation :)
2
General / Re: Texture problems with large project
« Last post by Daniele on July 04, 2022, 06:42:55 PM »
Hello Bzuco,
many many thanks for your reply and solution. As you suggested, I used  8192 for the size of texture and 4 as count and now the texture is properly applied to the entire model. THANK YOU AGAIN for your valuable help!
Do you have a rule of thumb to understand how I should set such parameters according to the size of the model?

All the best,
Daniele
3
Hello Sydney,

Can you send the project saved after the script run to support@agisoft.com?
4
Python and Java API / alignCameras not working with film camera w/fiducials
« Last post by sydneyg on July 04, 2022, 05:40:19 PM »
Hi all,

I am trying to work with some historical aerial imagery (from a film camera with fiducials).  I cannot seem to get the images to align with the script I have.

My script detects the fiducials automatically, calibrates them, and masks out the background, and matches the photos. All of that seems to work fine, but the final alignment produces 0 tie points. When I run this script without the flag "film camera with fiducials", the images align and a sparse cloud is made. However, when the film camera comes into the question it seems to find 0 tie points. 

PS: I also slammed the same images into the GUI and processed with the same setup as I have here in this script (film camera w/ fiducials auto detected and auto calibrated) and the images aligned just fine. 

PPS: I also tested it with a different set of historical aerial film images, same issue again. So I don't think the images are the issue.

Does anyone have any insights on this? Maybe I'm overlooking something in this script. Script attached as is the console output. Thx for the help.

Sydney
5
Python and Java API / Marker Detection - Image Scale
« Last post by FabianN on July 04, 2022, 12:14:45 PM »
Hi Alexey,

I sometimes have problems in detecting coded markers when they are too small in an image. However, when I upsample the images (f.e. by a factor of 2), the detection works well an accurately (visually).
Is it an option for you to implement a user-parameter for internal up- or downsampling of the images prior to marker detection? This would allow to handle coded targets with a larger size difference than what is currently possible.

Or is there another way of dealing with this?

Thank you,
Fabian
6
Python and Java API / Re: Shape.vertices attribute removed
« Last post by Paulo on July 04, 2022, 08:13:44 AM »
Hello Raj,

since 1.8 the following attributes were removed from Shape class:
Quote
Removed has_z, type, vertex_ids and vertices attributes from Shape class

So you should look at Geometry class for the correct attributes in API reference. For example a shape's vertices would be accessed thru shape,geometry.coordinates in case of point or linestring. For Polygon, the outer boundary vertices are accessed thru shape,geometry.coordinates[0]....
7
Python and Java API / Shape.vertices attribute removed
« Last post by Raj Calisa on July 04, 2022, 07:46:30 AM »
Hi all,

When I upgraded to Metashape 1.8.x, I noticed that my python code had errors. In particular, the vertices attribute of a shape object is not supported any more.

What is the alternative?

Regards,

Raj.
8
@gateway
I can only give you idea of my workflow, but it is outside of MS:
-create pointcloud in MS, export it to cloudcompare and apply poisson surface reconstruction, then export mesh to meshlab and apply "Simplification: Quadric edge collapse decimation" filter(this gives you overlap/dark triangles free mesh)

I totally forgot about meshlab.. thanks for the reminder.. do you run any other options in meshlab or just that one?
9
The thing that annoys me the most is that MS and Blender have their X-axis at 90 degrees to each other. I always have to do a rotation of -90 in Blender to get the model to the correct orientation.

when you import to blender select z up and it should work
10
The thing that annoys me the most is that MS and Blender have their X-axis at 90 degrees to each other. I always have to do a rotation of -90 in Blender to get the model to the correct orientation.
Pages: [1] 2 3 ... 10