Messages

16

General / Re: cheap CAD software for contours, creating drawing, etc.

« on: July 02, 2020, 09:20:34 AM »

Hi cronair,

Try QGIS. It's free & open-source.

www.qgis.org

FYI: You can also do (some) virtual surveying directly in Metashape. Just digitise lines / points on your computed DEM/mesh/point cloud and then export the vector files as DXF or SHP.

All the best.

Regards,
SAV

P.S. Regarding contours. You can either generate dem directly in Metashape or in QGIS with any DEM that comes out of Metashape. Use geotif format to export from Metashape.

17

General / Re: Best Laptop for Metashape?

« on: July 01, 2020, 10:20:47 AM »

Hi Govant,

For a workstation type laptop (such as the Lenovo P53) the best available graphics cards are the Quadro RTX4000, Quadro RTX5000 and Quadro RTX6000 (latter not available for the P53).

You might also want to check out high end gaming laptops from Razer (www.razer.com). They work very well with Metashape and RAM can be upgraded if needed (you can replace the RAM modules yourself). The Razer Blade 15 comes with the latest (10th) generation 8 core Intel i7-10875H CPU (16 threads) and a NVIDIA RTX 2080 Super graphics card. All very powerful / latest generation components. Big plus: it's all packed into a sleek/compact and portable machine at just over 2kg total weight (no heavy 'monster' gaming laptop).

All the best.

Regards,
SAV

18

General / Re: Best Macbook Pro for Metashape/photogrammetry?

« on: June 29, 2020, 10:45:41 AM »

Hi Matt,

Get the 16 inch Macbook Pro. The dedicated graphics card will make a big difference when it comes to processing, which is why I suggest to upgrade it to the 8GB version (standard is 4GB). Another advantage of the 16 inch Macbook Pro is that it comes with a 6 core CPU (or you can even upgrade to 8 cores) whereas the 13 inch Macbook Pro only has a max of 4 cores.

The 13 inch Macbook Pro + the eGPU would work too, but I think it's a cleaner/more streamlined setup if you just go for the 16 inch Macbook Pro. Plus you won't get into any issues with eGPU drivers etc.


All the best.

Regards,
SAV

19

Python and Java API / Re: How to import markers and use as bounding box in standalone python module

« on: May 12, 2020, 08:16:18 AM »

Hi adamjg,

As far as I can tell it also uses markers in the X / Y plane based on the floor mat.

Code: [Select]

#  Floormate marker definition 
#
#   py
#   
#   |
#   |
#   |
#   
#   p0 ------------ px

p0 = "target 3"   
px = "target 4"
py = "target 1"

distancepx = 0.7 # Change values is you are not using the A1 floormat posted
distancepy = 0.4 # on www.pi3dscan.com
Have a look at the provided AutoProcess_v2.py script and adjust it to your needs. Note that the script was written in 2016 by Richard Garsthagen, hence it might need some alterations to make it work with the latest version of Metashape.

Regards,
SAV

Hi SAV,

Yes I have seen this posted around a few times but it uses markers positioned in the z axis and my case is just x and y.

20

Python and Java API / Re: How to import markers and use as bounding box in standalone python module

« on: May 11, 2020, 01:44:37 PM »

Hi adamjg,

This might be helpful:
http://www.pi3dscan.com/index.php/instructions/item/agisoft-how-to-process-a-scan-with-projection

You can also download the python scripts from that website.

All the best.

Regards,
SAV

21

General / Re: Best collection method for 3D building

« on: May 11, 2020, 01:23:44 PM »

Hi cronair,

For such complex surveys you can also make use of Metashape's built in 'UAV survey tool'.
It's in TOOLS > PLAN MISSION.

Metashape introduces functionality for obtaining optimal sets of camera positions based on rough model and creating mission plans using these optimal sets.

Mission planning feature works as follows. At first, photos captured during a simple overhead flight are used to create a rough polygonal model. Then, a set of the viewpoints which are enough to cover the surface of the object with sufficient overlap is automatically generated. Finally, a round-trip passing through all the generated viewpoints is computed and can be exported in KML file format to be used for drone controlling application.

Such a KML can then be used in Litchi or DJI GS PRO. More info in HELP > CONTENTS.

Also have a look at this blog post:
https://www.agisoft.com/index.php?id=70

All the best.

Regards,
SAV

22

General / Re: Import transformation matrix from CloudCompare

« on: December 15, 2019, 06:36:09 AM »

Hi jnb,

This should be possible with a custom python script.

See this example code which aligns/rotates the coordinate system to match the bounding box.
https://github.com/agisoft-llc/metashape-scripts/blob/master/src/coordinate_system_to_bounding_box.py

In a similar way you could rotate your coordinate system based on the transformation matrix values you get out of CloudCompare.

Regards,
SAV

23

General / Re: Hardware test thread

« on: December 15, 2019, 06:25:56 AM »

Hi Kjellis85,

Check out Pugetsystems who have published comprehensive hardware comparisons & recommendations for Metashape online:
https://www.pugetsystems.com/recommended/Recommended-Systems-for-Agisoft-Metashape-145/Hardware-Recommendations

Currently one of the best value for money CPU/GPU packages is a i9-9900K with an NVIDIA RTX 2080 Ti.

Best regards,
SAV

24

General / Re: Desert Area

« on: December 05, 2019, 02:49:45 PM »

Hi ahmed,

For flat areas a strong imaging geometry is recommended (besides good reference information).

Therefore you should acquire images with a slightly inclined camera instead of nadir ( =pointing straight down). Additionally, add perpendicular tie lines to your survey so that you fly a 'cross hatch' pattern. This will help to improve the error.

And make sure to have sharp and high quality imagery. Motion blur caused by a too high horizontal flight speed will overall increase the error of your 3D reconstruction.

And last but not least, don't forget to run OPTIMISE in Metashape to minimize the reprojection error and improve accuracy. 

All the best.

Regards,
SAV

25

General / Re: Exporting Orthomosiac

« on: December 02, 2019, 03:19:12 AM »

I'm pretty sure I optimised cameras, though I can't recall what stage in the process this was done.

Right click on the chunk in the Workspace pane and choose SHOW INFO. If you optimized your cameras, then it would be shown in the list.

Regards,
SAV

26

General / Re: Exporting Orthomosiac

« on: December 01, 2019, 07:11:27 AM »

Hi Brett,

There are a few things that could lead to this issue.

1) Make sure to have each GCP (accurately) linked/marked in at least 4 pictures (check PROJECTIONS column for cameras within the reference pane)
2) In the Reference pane, make sure that the markers you want to use are checked
3) Make sure that the marker coordinate reference system is set to MGA Z55 (should be EPSG::28355)
4) Before computing the dense point cloud, mesh, DEM or orthophoto make sure to run OPTIMIZE CAMERAS.
5) Make sure to choose MGA Z55 as coordinate reference system when finally exporting your orthomosaic.

All the best.

Regards,
SAV

27

Feature Requests / Re: Oriented scale bars

« on: November 04, 2019, 08:07:35 AM »

sounds interesting! But I would call them vectors rather than scale bars, because they would be also very useful without length value. And they could lead to a new chunk status added to [R] and , which could be labeled as [r]?

You could simply use a very large length accuracy value for the scale bar in case the length is unknown.

This would help to keep it simple; you wouldn't need to introduce a new type of reference information called vector but instead incorporate it into an already existing one.

Regards,
SAV

28

General / Re: Volumes on tilted grounds where it is not possible to position ground vertices.

« on: October 13, 2019, 11:51:53 AM »

Hi Isaac,

Indeed, it shouldn't be too tricky to implement this feature into Metashape. The SET DRAWING PLANE function is already the first step into the right direction. But as you mentioned in your initial post, at the moment the Z coordinates are inherited from the mesh/DEM even when you are digitising on a manually set drawing plane.

In case you have a 3D model of the bench before and after blasting/ground work, then you could export both point clouds and use CloudCompare to calculate the cut-and-fill volume. 

https://www.cloudcompare.org/doc/wiki/index.php?title=2.5D_Volume

All the best.

Regards,
SAV

29

General / Re: Optimal size non-coded targets

« on: October 11, 2019, 04:37:37 PM »

Hi Helge,

Around 10 to 20 times the GSD has worked for me.
But please note that the marker detection algorithm that is used in Agisoft is a 'mixed bag'. It commonly picks up false positives or struggles to identify markers that are not 'optimally' sized (even when using coded markers).

All the best.

Regards,
SAV

30

General / Re: Problem with texture

« on: October 11, 2019, 04:26:45 PM »

Strange behavior. Maybe you can share the dataset so the community can help to fix your problems.

Regards,
SAV