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

Pages: [1]
1
Hi Paulo, thanks, it's two flight lines but I'll see if I can get an improvement by adding a third. The alt accuracy is almost certainly better than 1000m (we just don't have access to any calibration info for it) so I'll play around with that as well. Thanks!

2
Here's the reference I used (metashape_metadata), along with the exported processed data (processed_metadata)

3
I've been using Metashape to build DEMs from historical imagery downloaded from USGS earth explorer. Much of it is fairly high resolution. The elevations that metashape returns are totally wild. Here's my process:

import photos (cropped w/ no film scan artifacts) -> import reference (wgs 84 w/ flight altitude in meters) -> align photos -> optimize cameras -> generate point cloud -> generate DEM

The elevations I'm getting are -10- -13 km? Any idea why this is or how I can improve it? I can do further alignment e.g. using asp but just confused about why this is happening.

Thanks!


4
General / Re: Metashape on Apple Silicon
« on: August 09, 2022, 10:39:23 PM »
This worked for me! Thank you.

Hello glacier,

Does it help, if you add the following line in the beginning of the script body?

Code: [Select]
Metashape.app.gpu_mask = 2 ** len(Metashape.app.enumGPUDevices()) - 1

5
General / Re: Metashape on Apple Silicon
« on: July 29, 2022, 01:07:48 AM »
Hey,

Reviving this thread -- I'm using the python api, and can't seem to get metashape to use my gpu. I've turned it on in metashape pro's preference (preferences --> gpu --> check boxes) but no dice when I'm running it in python. Any suggestions? Thanks ahead of time.

```
Found 1 GPUs in 0.000381 sec (OpenCL: 0.000314 sec)
Using device: CPU VirtualApple @ 2.50GHz (using 8/8)
[CPU 1] group 1/1: estimating depth map for 1/13 camera 0 (2 neighbs)...
```


Pages: [1]