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

Pages: [1] 2 3 ... 15
General / Re: Systematic Z Error in Proportion to Altitude (Phantom 4 RTK)
« on: February 24, 2019, 12:59:07 AM »
Hello Domingo,

yes please send the dat, and would certainly have a look at it… If you measures a few GCPs from the base station, then we can have an independant check on the quality of airborne RTK positions….

General / Re: Identification and removal of redundant photos
« on: February 13, 2019, 07:37:57 AM »
Hi Will,

in latest version, there is Plan Motion Tool (previously Optimize Coverage in 1.4) that  lets you select Optimize Coverage step so that program disables any unecesary photos and thus you can process only with a reduced set of enabled photos….

You must first have a crude 3D mesh (from sparse cloud) to run tool….

In attached screen shots you can see that tool reduced number of photos by more than 50% after running tool….


General / Re: Modify camera coordinates
« on: February 13, 2019, 12:04:16 AM »

I think that your camera CSV coordinate file should have each camera IDed with its extension (.jpg or .tif) so it corresponds to the project imported images….

General / Planning Motion tool
« on: February 04, 2019, 04:22:34 PM »
Hello Agisoft support,

I am curious to know what exactly does the new tool Planning motion (replacing Optimize coverage) do in MS 1.51....

Im trying it on a 118 UAV 16 Mpix image set at 4.8 cm GSD with double grid coverage and it is taking an enormous time ( 17 hours and counting...)

Attached Screen captures....

More insight on this tool and its various input parameters (which I left at default value) will be appreciated!

Python Scripting / Re: requests Module fails to import in Metashape 1.5
« on: February 02, 2019, 08:27:39 PM »
Hi Alexey,

yes after installing requests in command mode, I can run the script with no problem!


Python Scripting / requests Module fails to import in Metashape 1.5
« on: February 02, 2019, 01:38:16 AM »
Hi all,

I am trying to run a python script that ran correctly on PS1.4...

the script contains following code:

import requests

and get following error in Metashape

2019-02-01 07:21:23   File "C:/Users/paul.pelletier/Documents/Pi3d/AutoProcess_v1/", line 14, in <module>
2019-02-01 07:21:23     import requests
2019-02-01 07:21:23 ImportError: No module named 'requests'
2019-02-01 07:21:23 Error: No module named 'requests'

How can I get request module to work in Metashape?

I found solution to this problem consulting the Agisoft solutions page

and using following system command:

"%programfiles%\Agisoft\Metashape Pro\python\python.exe" -m pip install requests

Feature Requests / Re: GPS position alignment
« on: December 17, 2018, 10:06:00 PM »
I think you may inversed latitude and longitude when importing camera GPS positions into PhotoScan...

General / Re: Systematic Z Error in Proportion to Altitude (Phantom 4 RTK)
« on: December 17, 2018, 04:27:30 AM »
Hello Paulo,

I have had a busy few days! However I got a chance to collect another dataset yesterday. It includes obliques. This seems to have fixed most of the problem, however there is still some error there. The error seems to be just a vertical shift though. I'm not quite sure where this is coming from yet. I will PM you a link to the data for you to take a look at.

The control points are in EPSG: 26734. I just use the Agisoft coordinate calculator to convert the photo locations to this system.


I was wondering if you sent me a PM regarding your last data set... Would like to have a look if possible,,,,

General / Re: Agisoft Metashape 1.5.0 pre-release
« on: December 11, 2018, 07:53:36 PM »
Hi Alexey,

thank you for the clarification.....

So For Photo-invariant parameters option would it not be better to use instead Photo-variant parameters as in this case a different parameter will be estimated for each photo?

Using this option, where can we find  the adjusted Photo Invariant (Variant) parameter for each image?

General / Re: Agisoft Metashape 1.5.0 pre-release
« on: December 11, 2018, 07:24:23 PM »
What is exactly "Added an option to fix a subset of calibration parameters.".

I would like to reiterate that more clarity, explanation will be appreciated on the use and difference in Fixed parameters and photo invariant parameters in latest release…

I can understand that you may have a calibrated lens where you want to fix f, cx and cy and leave other parameters free to be adjusted by software...

But what would using photo invariant parameters do?

General / Re: Systematic Z Error in Proportion to Altitude (Phantom 4 RTK)
« on: December 08, 2018, 11:50:18 PM »

to decorrelate the calibration parameters as well as to eliminate bowl effect, I would suggest capturing additional obliques photos to the traditional grid pattern coverage, maybe a few going up to the block and a few after terminating the grid collection....

General / Re: Systematic Z Error in Proportion to Altitude (Phantom 4 RTK)
« on: December 08, 2018, 09:40:33 PM »

it would be very interesting to have some data set to test it... Using RTK to just fix the camera perspective centers can often bring a problem in elevation as focal is directly correlated to flight altitude... So the higher you are from ground, the Z error will increase relative to some error in focal…..

General / Re: KMZ grayed out
« on: December 04, 2018, 07:02:59 AM »
Hello Graca,

I would suggest, after setting your reference settings to WGS84 to  re generate your DEM and  orthomosaic so that it is now produced in WGS84... Should work….

Remember changing your reference settings to WGS84 (with Covert Reference button - 4 th button from left in Reference pane), will change your camera coordinates but original Ortho will remain in original CS (NAD83) if it is nor regenerated...

General / Re: Workflow to process the Photography of "PHANTOM 4 RTK"
« on: November 29, 2018, 01:14:01 AM »
BobvdMeij ,

thanks for the update… makes more sense now...

Yes I did a new calibration in PS without entering Dewarp Data parameters...

However the big difference between fx and fy (affinity) is not reflected in the PS adjustment as b1 is very small.....

By the way in PS calibration f = fy and b1 = fx-fy

My only doubt is p1, p2 parameters as in Pix4D they are inverted wrt PS... so maybe support can confirm how to treat p1, p2 from DJI Dewarp parameters for use in PS ….

General / Re: Workflow to process the Photography of "PHANTOM 4 RTK"
« on: November 28, 2018, 08:32:27 PM »

yes I think you are right, the last 5 correspond to k1,k2,k3 and p1, p2 distorsion parameters... the 3rd and 4 th parameters seem to correspond to Principal point position in pixels. In screen capture, I show calibration done on P4RTK set corresponding to first example. In this case no dewarp parameters were applied and camera exhibits high radial distorsion… In this calibration, I have also a r4 radial parameter estimated....The first 2 parameters are more difficult to explain, they seem to correspond to something like focal length in pixels ( 2 values for affinity^?) but are far from 3663 value estimated in PS.... DJI should give more information on this especially since it puts in EXIF calibrated focal and PP at:
Calibrated Focal Length         : 3666.666504
Calibrated Optical Center X     : 2736.000000
Calibrated Optical Center Y     : 1824.000000

Pages: [1] 2 3 ... 15