Messages

1

Python and Java API / Re: How to run a script

« on: Today at 06:30:11 PM »

Hello gmeinero,

Were you able to get it working?

2

Python and Java API / Re: The argument 'pairs' in chunk.matchPhotos is lost (version 1.6.2)

« on: Today at 06:29:21 PM »

Hello kot,

OK, thank you for additional information.

It seems that it really got broken, but we'll fix it in the next version update. Meanwhile you can use Tasks concept:

Code: [Select]

task = Metashape.Tasks.MatchPhotos()
task.pairs = pairs_keys
task.apply(chunk)


3

Python and Java API / Re: How to run a script

« on: Today at 06:07:08 PM »

Hello gmeinero,

This script adds custom menu item, please check it in the Main Menu and use to open the custom dialog and run the script.

4

Python and Java API / Re: camera.photo.meta --> Exposure Compensation or value missing

« on: Today at 06:05:41 PM »

Ok, thank you. I think we'll add support for most of them in the next update.

5

General / Re: loading TLS file

« on: May 29, 2020, 08:44:29 PM »

Hello ssv76,

Please send the message to support@agisoft.com requesting TLS format specification. Also please include some brief description of the solution where TLS will be used.

Note that you can also consider other Tiled Model export formats, supported by Metashape, as most of them are documented.

6

General / Re: Rolling Shutter bug?

« on: May 29, 2020, 08:41:42 PM »

Hello RHenriques,

Yes, it seems to be an issue with 1.6.2 version only, which has been already fixed in the 1.6.3 pre-release.

7

General / Re: Markers eroors before and after selection

« on: May 28, 2020, 05:57:31 PM »

Hello Damian,

Please see my post regarding the difference of the error estimation for Control and Check points in another thread:
https://www.agisoft.com/forum/index.php?topic=11329.msg50857#msg50857

In Metashape Pro (and PhotoScan Pro) versions prior to 1.5.4 estimated control point coordinates displayed in the Reference pane (and the error values as well) were calculated based on minimization of the reprojection error only, without taking into account measured control point coordinates in space. So they did not correspond to adjusted coordinates from the bundle adjustment step, and were recalculated from weighted image measurements alone.
 
Starting from Metashape Pro version 1.5.4 estimated control point coordinates correspond to the adjusted values, that is, they are calculated taking into account both reprojection error and measured object space coordinates. Similar behavior is common for other software packages and also allows for better detection of the measurement errors.

If you are interested in the difference between measured and triangulated control point coordinates, you can temporary uncheck the corresponding entry in the reference pane (thus making it a check point). Please note that check point error calculation is not affected by the change mentioned above. Upon unchecking the control points you do not have to click on Update button.

8

General / Re: Rolling Shutter bug?

« on: May 28, 2020, 04:45:39 PM »

OK, thank you for reporting. We'll try to fix that as soon as possible.

9

General / Re: Agisoft Metashape 1.6.3 pre-release

« on: May 28, 2020, 04:23:09 PM »

Hello Shadow,

The reported issues should be fixed in the next update.

Hello RHenriques,

There seems to be a bug in coordinate import from EXIF data in pictures coming from DJi UAV's. The longitude column has all zeros. Version 1.6.2 works fine.

It will be also fixed in the next version update. It seems that DJI has finally fixed the typo in GPSLongtitute tag and it is correct now.

Hello ruyi7952,

Is it possible to add the ability to read Angle elements?

Please clarify your request.

10

Bug Reports / Re: Vertice merging too aggressive in Out of Core meshing

« on: May 28, 2020, 04:20:10 PM »

Have you checked, if the problematic areas exist if the custom face count is used, but it is below the 'undecimated' polygon count?

11

General / Re: Micasense Altum Thermal: conversion, resolution questions

« on: May 28, 2020, 01:42:00 AM »

Hello aggieair,

When you are generating a multi-band orthomosaic, it would have the same resolution for all the layers, therefore the thermal band orthorectified images will have large scale compared to thermal band only processing. Visually the individually orthorectified images for both approaches should be similar, but due to the larger resolution for the multi-band approach the blending of those orthorectified images would likely give more detailed result.

12

General / Re: Problem with Alignment Result

« on: May 28, 2020, 01:34:41 AM »

Hello evonflo,

It would be helpful to get the processing reports from both Medium and High runs, as well as the screenshots of the tie point and dense clouds for the problematic areas.

13

General / Re: Alignment Problem in Z

« on: May 28, 2020, 01:30:31 AM »

Hello Broken Arm,

If it would be easier for you to follow, I can suggest the following steps:
- add each flight images to the separate chunks,
- merge chunks (without processing anything),
- switch to the merged chunk and process the data there.

In this case all the calibration groups will be already separated according to each flight.

14

General / Re: Mesh from depth maps gives worse results in newer versions

« on: May 28, 2020, 01:27:32 AM »

Hello Alex,

If there's a possibility to provide the project with the alignment results only (saved in PSZ format) and the original images, we will generate the models in different 1.6.x versions and check the difference. You can send the download link to support@agisoft.com.

15

General / Re: Rolling Shutter bug?

« on: May 28, 2020, 01:19:42 AM »

Hello RHenriques,

Please provide the complete log related to the failed operation and specify the GPU models that you are using for the processing.

Also please specify if there are no GPU-related issues when the depth maps run is based on the alignment without rolling shutter compensation?