Messages

1

Python and Java API / Re: Orthomosaic export after raster calculation formula

« on: April 30, 2024, 03:34:56 AM »

I used the script you send and it worked great! I think it may have been enabling 'big tiff' that caused the differences but I'm not sure either.

2

Python and Java API / Re: Orthomosaic export after raster calculation formula

« on: April 23, 2024, 09:30:55 AM »

I was using this thread as a reference for my task and I am running into problems. I'm trying to export orthomosaics using raster transform 'B4' values using a script  but when I compare it to the orthomosaic  exported from the GUI, I get different values and different tif file sizes as well. What could be the problem? I've posted the script below along with the export settings that I used in the GUI. I'm currently using Metashape 2.0.1.

Code: [Select]

import Metashape

app = Metashape.app
doc = app.document

chunk = doc.chunk

proj = Metashape.OrthoProjection()
proj.crs = Metashape.CoordinateSystem("EPSG::4326")

chunk.raster_transform.formula = ["B4"]
chunk.raster_transform.calibrateRange()
chunk.raster_transform.enabled = True

exportPath = "[i]path[/i]"

compression = Metashape.ImageCompression()
compression.tiff_compression = Metashape.ImageCompression.TiffCompressionLZW
compression.tiff_big = True

chunk.exportRaster(path=exportPath, source_data = Metashape.OrthomosaicData, raster_transform = Metashape.RasterTransformValue, image_format = Metashape.ImageFormat.ImageFormatTIFF, image_compression = compression, save_world = True, save_alpha = False, global_profile = True, white_background = False)


3

General / Re: close range accuracy settings

« on: February 28, 2024, 07:26:37 AM »

As far as I know, camera accuracy in the reference settings only matters if your camera has GPS so that number doesn't really matter without coordinates in the image metadata.

4

General / Re: GPU GTX 3060 is low on memory at 12 GB

« on: February 28, 2024, 07:14:53 AM »

Other than the obvious solutions of buying a GPU with more memory or lowering the resolution, maybe you can try reducing the work area if some parts aren't necessary which could reduce the amount of memory needed to process the mesh.

5

General / Re: Taking 5 days to create a point cloud?!

« on: February 07, 2024, 03:43:18 AM »

As you're probably aware, your graphics card is a huge bottleneck for your system and point cloud generation is a GPU heavy process. I would say probably try checking the box to use CPU when performing GPU accelerated processing in Preferences -> GPU tab if you haven't already.

My recommendation would be sticking with 'Medium' for point cloud generation with your setup unless you get a more powerful graphics card.

Still 5 days seems to be a bit long for 390 images and it could be a bug. What resolution are the drone images?

6

Feature Requests / Re: Improving Calculate Profile tool

« on: June 19, 2023, 05:48:14 AM »

+1

Also would be nice to be able to calculate profile from the Python API.

7

Feature Requests / Re: Cloth Simulation method for DTM point classification

« on: June 07, 2023, 04:10:54 AM »

+1 for cleaner DTMs

8

General / Re: build DEM

« on: June 02, 2023, 08:05:56 AM »

Hi Angieu,

I think the problem might be that your images aren't geotagged.
Metashape requires GNSS data either on the image metadata or with GCPs added in the project to create DEMs and Orthomosaics.

Go to the reference tab and see if your images have GNSS metadata.

If not, you might be able to add them if your drone saves the geotagging data.
Which drone and camera were you using?

9

General / Re: Orthomosaic has distorted areas

« on: March 20, 2023, 07:43:31 AM »

Hey MP7,

Not sure if you found a solution yet but I would try processing again with General Preselection turned off during alignment.
The repetitive roof patterns might be causing the problems with General Preselection turned on.

Hope that helps!

10

General / Re: Laptop recomendations

« on: March 13, 2023, 08:04:17 AM »

Hello,

I'm not sure exactly how prices are in your region but I would definitely recommend going with the newer MSI Raider GE78HX models. You'll get a big performance boost from the 13th gen Intel CPU and also upgraded performance from the 4000 RTX series at the same price point.

Buying two less powerful laptops mean you have to buy another copy of Metashape, and would probably be a hassle to set up a network server on the move. I personally would prefer one powerful one with plenty of storage.

Hope that helps!

11

General / Re: reset region using shapefile

« on: March 09, 2023, 07:52:23 AM »

Hi bisenberger,
The script I modified below should work in Metashape 2.0.

Hope it helps!

12

General / Re: Using RTK and Ground control Points

« on: March 09, 2023, 06:54:30 AM »

As Olihar said, if the GCP measurements from the Trimble R6 are geoid altitudes make sure it is properly designated in Metashape as well. Otherwise Metashape defaults to using the GCP as if ellipsoid altitudes are used resulting in an increased error. You can use this link as reference for applying geoid altitudes : https://agisoft.freshdesk.com/support/solutions/articles/31000148332-how-to-use-height-above-geoid-for-the-coordinate-system

However, I found it easier to get the WGS84 readings with ellipsoid altitude from the Trimble device (which is the same CRS as the M3E), process the data, and then convert to my local adjusted geoid CRS only when exporting my results.

Hope that helps!

13

General / Re: Optimizing Processing Time?

« on: March 09, 2023, 06:12:41 AM »

So with your budget of under $1000, I would recommend the following upgrades.

CPU: AMD 5800X - $220 MSRP   #Extremely cost-efficient cpu but uses an AM4 motherboard which means you won't be able to upgrade to an AM5 CPU in the future, also might be hard to find
Motherboard: Any AM4 MB - $100
GPU: AMD 6800 XT - $560 MSRP   #Huge performance boost from the 1070
RAM: Use your old 64GB - $0
PSU: ~800W at least - $100

Total : $980

Pretty sure this setup is the most cost-effective Metashape performance you'll get under $1000

14

General / Re: Metashape Pro Local Network Licencing

« on: March 08, 2023, 09:04:55 AM »

"processing nodes [...] require activation" means that to add processing power, you have to purchase another license per node.

The answer to your question is any computer that adds processing power requires a separate license regardless of whether it uses the GUI.
Hope that helps.

15

Python and Java API / Re: Export profile of shapes using script

« on: February 20, 2023, 03:47:29 AM »

I was looking into this so that Metashape could be used to generate and export cross-section profiles.

If scripting this is currently not possible, could this be added as a feature request?