Community 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 - Alexey Pasumansky

Pages: [1] 2 3 ... 520
Model Menu is related to the operations available in the Model view mode (don't confuse it with mesh display option), in the Ortho Menu - the actions related to the Ortho view mode, and in the Photo Menu - the features related to the Photo view mode.

Edit menu now contains some general features that are applicable to any view (some features of the Edit menu may change depending on the active view mode).

Hello RnFstMapper,

In the version 1.4.0 the Gradual Selection function is available from the Model Menu:

Hello RnFstMapper,

Since this action is related to the Model view only, you can find the Gradual Selection in the Model Menu.

Hello Alice,

We are already working on the batch export/import issues, some parameters are ignored upon read/write. I think that the fix will be included in 1.4.1 release.

Hello ppant,

If the panel cannot be detected automatically, you need to move all the images with it to new camera group called "Calibration images" in the chunk contents, manually apply the mask for each band on every calibration image, then go to Calibrate Reflectance dialog and input the reflectance values for each each band related to the panel.

Python Scripting / Re: Build Dem error in Photoscan 1.4.0
« on: January 19, 2018, 05:51:15 PM »

now I have a question for Micasense  calibration will calling these to function helps or not 
Code: [Select]

So far I am able correct micasense Image via GUI interface I link to do that with python code too

Hello ppant,

.loadReference() function should be only used to load the coordinate information to the Reference pane.

Currently CSV import for the reflectance panel is not supported via Python, so you should input the reflectance values for each band manually (for every calibration image). For example:

Code: [Select]
albedo = {"Blue": "0.65952", "Green": "0.67788", "Red": "0.67718", "NIR": "0.66653", "Rededge": "0.6223266"} #reflectance values for the panel for each band
for camera in chunk.cameras:
    if != "Calibration images":
    for plane in camera.planes:
        plane.meta["ReflectancePanel/Calibration"] = albedo[plane.sensor.bands]

Hello jslyder,

How fast the gradual selection dialog shows up, if opened from GUI function?

And how many points are there in the sparse cloud for the cases when the Python-based function freezes?

Hello ppant,

If the panel cannot be detected automatically, you should apply the masks manually for each band on every calibration image of the reflectance panel.

Does the Spectralon Reflectance panel has any additional elements that can be used for automatic panel recognition?

General / Re: Incompatible dense cloud colors
« on: January 19, 2018, 08:14:35 AM »
Hello Mike,

Seems that the issue is related to the integrated graphic card, so I can suggest to disable Intel HD card in the GPU preferences of PhotoScan.

Python Scripting / Re: Build Dem error in Photoscan 1.4.0
« on: January 18, 2018, 08:48:36 PM »
Hello ppant,

You can send them to

General / Re: Camera Position for oblique aerial stereo pairs
« on: January 18, 2018, 05:38:25 PM »
Hello Paul,

Usually it is necessary to have at least three reference points for georeferencing, it includes camera locations and marker (GCPs) locations, providing that cameras are aligned and each marker has at least two projections on the images from aligned image subset.

The coordinates of the camera locations should represent the camera center at the moment the image were taken. As for the yaw, pitch, roll angles - currently PhotoScan assumes that camera is fixed under the aircraft in such way: when the aircraft is flying to the North and East is by the right wing (Yaw, pitch and roll are all zeros), the camera is pointing vertically down and the image axis bottom -> top direction is pointing to the North, whereas left -> right vector is pointing to the right wing.  In case the camera mount is different, but yaw, pitch, roll angles apply to the aircraft as described, it is necessary to use the GPS/INS offset values in the  Camera Calibration window.

Note that gimbal angles are not supported (varying angle offset for each camera position), so in such case pre-processing correction of the orientation angles should be used. Or angles should be ignored and not loaded to Reference pane.

As for the issue with the stereopair itself, there could be several reasons, for example, very short stereobase distance compared to the distance to the area of interest.
If you know the camera calibration parameters precisely, you can input them to the Camera Calibration window and use Fix Calibration flag to disable automatic distortion parameters refinement.

General / Re: Orthomosaik with cylindrial projection
« on: January 18, 2018, 03:54:13 PM »
Hello Dieter,

We'll try to reproduce the issue.

Can you please specify, if you have used "Interior Projection" option? It looks like the provided images are mirrored compared to each other.

General / Re: Orthomosaik with cylindrial projection
« on: January 18, 2018, 02:56:27 PM »
Hello Dieter,

Can you please also post the resulting orthomosaic overview? Do you mean that there's a lot of unused space in the final image?

Feature Requests / Re: Alembic export
« on: January 18, 2018, 01:56:52 PM »
Hello rodmac,

Currently Alembic format is available for mesh export/import operations, however, on export it may optionally include the camera positions.

"Zero resolution" usually means that either the bounding box is positioned incorrectly, or there are too few valid matching points inside the box for the overlapping images.

General / Re: How to choose which cameras to build texture from?
« on: January 18, 2018, 12:49:49 PM »
Hello kpk,

If you disable cameras in the activate chunk prior to the texture generation procedure, they wouldn't be utilized in the operation.

Pages: [1] 2 3 ... 520