Agisoft PhotoScan 1.1.0 pre-release

[Alexey Pasumansky]

Hello Steven,

Thanks for reporting, however, we haven't been able to reproduce the problem with crashes.

But as for the creating duplicated copies of chunks and adding them to the existing document, we will try to implement this functionality in Python API.

Hi Alexey,
It could be my install. I'm working with the 64-bit Linux version which fails on the chunk.copy() command. I just downloaded the Windows 64-bit version and it worked fine. I load in a project and execute the following at the console:
import PhotoScan
doc = PhotoScan.app.document
chunk = doc.chunk
chunk2 = chunk.copy()

Hello Steven,

Please check latest build 1995.

You can use doc.addChunk(chunk.copy()) for duplicating.

[StevenF]

Hi Alexey,
Copying chunks appears to work in the new build for Linux 64 bit Pro. Thank you.

[andyroo]

We suggest to reset camera alignment for all the cameras that have <5 projections prior to optimization.

Please also provide the console pane output related to the optimization that doesn't do anything in 1.1.

Hi Alexey,

If I try to optimize without resetting alignment for the cameras with no value in the  [Projections] column, I get this in the console:

Optimizing point cloud...
adjusting: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 17.9803 -> 17.9803
coordinates applied in 0 sec
Finished processing in 50.109 sec (exit code 1)

I removed the single camera with one projection and got the same thing. Then I removed all of the cameras with blank projection values and successfully optimized in 1.1:

Optimizing point cloud...
adjusting: xxxxxxxxxxxxx- 17.9803 -> 1.14188
coordinates applied in 0 sec
Finished processing in 23.031 sec (exit code 1)

[ppkong]

Hello ppkong,

Maybe you can provide the project file for the further problem studying?

I think this problem is caused because I used the distortion corrected image with black edges, by the way the black edge because when I distortion correction chose "Center principal point" caused.

[eriks]

This time I tried to build in batch using the default projection (although I really hope you add the option to set projection for the ortho and dem generation in batch).

Build 1985 now allows to choose export coordinate system in the Batch export orthophoto/DEM.

Can you please also allow us to choose coordinate system projection for exporting point clouds like we now can do for exporting orthophotos?

[Alexey Pasumansky]

Hello eriks,

We'll try to include this option in the final 1.1 release.
Meanwhile build 1998 has region selection option in the Batch Process -> Export DEM/Orthophoto. And split in blocks option for batch point cloud export has been added.

[eriks]

Thanks Alexey!

[Kjellis85]

all of a sudden I can't import markers! I haven't done anything except from trying to detect some old markers, then after that failed I manually registered the markers, but when I try to import nothing happens in the marker section and the model is still not georeferenced. I tried the latest version 1998 but to no avail.

To be sure of the problem I tried an old job that I georeferenced yesterday, in the same version as the first try that failed, and now that won't get georeferenced with new data. I tried removing a marker and adding it from the same file but nothing happens.

[Alexey Pasumansky]

Hello Kjellis85,

Are you using Export/Import markers options in the Tools menu?

Are there any error messages in the console pane?

[augeaz]

Hello Martin,

We'll check if it could be easily implemented for the next update.

Thank you, looking forward it.

[andyroo]

Version 1998 still has the same issue/feature - I have to reset alignment on cameras with no projections before optimizing, or the optimization will fail.

[Kjellis85]

Hello Kjellis85,

Are you using Export/Import markers options in the Tools menu?

Are there any error messages in the console pane?

I am using my regular workflow, import "button" in reference section. My GCPs are stored as plain text, like this:

6654,7742522.307,659135.905,14.606,target 43
6655,7742524.167,659137.788,14.861,target 45
6656,7742522.920,659140.087,14.950,target 47

I set column values to label: 5 easting: 3 northing: 2 altitude: 4

This has always worked, but after going up to version 1.1 it fails to import anything.

[Alexey Pasumansky]

Hello Erik,

I've tried to create sample text file with your data and got no problems with the coordinate information import to the Reference pane.

Do you see proper column segregation in the Import CSV dialog? Do you have already GCPs with the corresponding labels?

[Kjellis85]

Ok... there must be something severely wrong with my computer. It suddenly worked! I did not change anything other that rebooting the computer. I will see if I can recreate the problem, but so far everything works fine.

[Kjellis85]

Don't know if it is a bug or if it is a change, but photoscan won't detect any markers from pre 1.1 versions, or at least not any I have tried. Is this due to a change in markes? If so, would it be possible to include an option for compatibility with previous version markers? Otherwise it will make a lot of our previous work hard to reproduce from scratch.