Agisoft PhotoScan 1.4.0 pre-release

[rexsham]

Can I know what is this problem?
Build 5251

[GeoGecco]

I really need to know a fix for "invalid raster transform" when doing orthoimage!!!!!
Could you tell me some way of workaround or are you goin to fix it today?
My customer really needs a solution today....

[Alexey Pasumansky]

Hello GeoGecco,

I can share the link to the previous pre-release build for you to export the orthomosaic. The public pre-release update is expected by the end of this week.

[Alexey Pasumansky]

Hello rexsham,

libtiff warning is indicating that something is incorrect with the meta-data, but it seems that it doesn't affect the processing.

You can send the image example to support@agisoft.com, so that we can check which tag is causing the warning.

[GeoGecco]

Hello Alex

I installed the 1.3.4 now and I'm able to export the orthophotos.

[mirijovsky]

Hello,

I have question about raster transformation. I use EPSG 5514 for my project. If I want to export MBtiles there must be a conversion into EPSG 3857. But by default there is only 3-parameters transformation which has 6 m precesion in the 5514 prj file. Another transformation from 5514 is 7-parameters transformation which has 1 m precision. If I add a new coordinate system with this transformation nothing happend. I have again bad result with low precision at the end. Is it possible to change it somewhere? I know that I am able to define new projection in the "doc" file in the orthomosaic folder (project files folder).

Best regards,
Jakub

[rexsham]

I got problem in exporting using latest build.

[rexsham]

Please have a look at the log.
I processed a project till the DOM stage.
But when I try to export the DEM, it finishes within 1 second and nothing has been output.
If I create DSM using sparse cloud it can output, but when I used dense cloud to generate the DSM, it cannot output.
It cannot output even when I selected to cut the output into 10000x10000 size tiles.

[Alexey Pasumansky]

Hello rexsham,

"Invalid raster transform value" is a bug of the current pre-release build version. It has been already reported and will be fixed in the next update, by the end of the week.

[xabierr]

Hi Alexey,

Could you please share the link to the previous build? jleon@usc.edu.au

cheers,
Javier

[mirijovsky]

related to my topic for bad transformation:

Agisoft uses 3 parameters transformation by default (15965) - http://epsg.io/5514
Much better transformation is 7-parameters transformation (1623) - http://epsg.io/5514-1623

Best regards,
Jakub

[Alexey Pasumansky]

Hello Jakub,

When you select your reference coordinate system EPSG:5514 in the Reference settings dialog, there is a button to the right of the coordinate system selection field related to the Datum Transformation Settings.

Clicking on it allows to select one of the transformation to WGS84 or use custom values.

[Alexey Pasumansky]

Pre-release has been updated. Orthomosaic export issue should be fixed now.

[ruyi7952]

Hello Alexey Pasumansky

build 5251  export to Smart3D with tie points  have a problem

1、xml  miss child  tag <Name> in <SRS>
2、 Definition the coordinate system  (like epsg: 2383)，in Smart3D it‘s Wrong result。
       setp by setp :
       (1) AT worked with epsg 2383
     （2）Coordinate system changed to local（m）
     （3）Export to xml
       (4)  Change the xml file,add <Name>  and <Definition> tag, this case DOT NOT USE "local", you needed USE "epsg: 2383 ".
      like；
       <SRS>
       <Id>1</Id>
       <Name>Xian 1980 .......... </Name>
       <Definition>EPSG: 2383</Definition>
      </SRS>
       The result is correct With Smart3D 4.4.7。
3、Large Project（6400000 tie points /14000 images) memory overflow, export xml failure。

[spogna]

Hy Alexey
i'm trying the new usefull feature "import points"  in build 5310.
import points works well but when i try to create a mesh Agisoft crash.

I attached the log file
Best regards
Andrea