Batch Export Point Cloud Vertical Datum out of range error

[PKPK]

Hi,

Since upgrading to 2.20, I've had issues exporting point clouds through batch process where it would give the Vertical Datum out of Range error. However, when I manually export it through the workspace, the issue does not occur. I've made sure that I have the correct geoids that I'm using is in the respective geoid folder and I've checked that I'm using the same CRS when exporting as the one in the reference settings. I'm out of ideas on how or where to look next to try rectifying this issue.

Any help or ideas would really help me out. Thanks for taking the time to read.

Cheers!

[Alexey Pasumansky]

Hello PKPK,

Do you have the same geoid file on the working nodes in respective /geoids/ directory?

[macsurveyr]

Another oddity that I found with version 2.2 build 19890 regarding Vertical Datum out of range error.

The vertical datum with geoid us_noaa_g2018u0.tif in this case is honored for everything until I try to create an orthomosaic using the Model as the surface AND try to transfer model texture. I then get the Vertical datum out of range error.

As I said, everything else seems to be fine.

Tom

[Alexey Pasumansky]

Hello Tom,

Can you please check, if you are no longer observinh this problem in 2.2.1 pre-release?
https://download.agisoft.com/metashape-pro_2_2_1_x64.msi
https://download.agisoft.com/metashape-pro_2_2_1.dmg
https://download.agisoft.com/metashape-pro_2_2_1_amd64.tar.gz

[macsurveyr]

Hello Alexey,

The problem still exist with 2.2.1 pre-release

Tom

[dcsa]

Hello Alexey,

We have the same problem using a compound CRS and API since version 2.2.0.
We have added the geoids to our Metashape.Document, but we don't know if we are handling the new Metashape.Geoid object well with this type of CRS.
Thanks in advance

[PKPK]

Hello PKPK,

Do you have the same geoid file on the working nodes in respective /geoids/ directory?

Hi Alexey,

Yes the working nodes all use the same geoid files in their respective directories.

[PKPK]

Just posting an update for reference and others that might encounter this situation:

I sort of figured out the problem but not quite sure all the way, I found that if I turned off these options in the 'Export Point Cloud' options in Batch Process it will successfully export with the compound CRS.
I've attached a screenshot showing which ones I turned off to get it working. I'm assuming one of these options don't like compound CRS? I'm only taking a guess at this point.


EDIT: Never mind, didn't work after all, ignore sorry

[Alexey Pasumansky]

If anyone still have issues with vertical datum out of range error, please check updated 2.2.1 build 20221 pre-release.

https://download.agisoft.com/metashape-pro_2_2_1_x64.msi
https://download.agisoft.com/metashape-pro_2_2_1.dmg
https://download.agisoft.com/metashape-pro_2_2_1_amd64.tar.gz

In case the problem persists, please share the project to support@agisoft.com so that we can reproduce the issue.

[dcsa]

Please, can you share python module to check too?

Thank you again

If anyone still have issues with vertical datum out of range error, please check updated 2.2.1 build 20221 pre-release.

https://download.agisoft.com/metashape-pro_2_2_1_x64.msi
https://download.agisoft.com/metashape-pro_2_2_1.dmg
https://download.agisoft.com/metashape-pro_2_2_1_amd64.tar.gz

In case the problem persists, please share the project to support@agisoft.com so that we can reproduce the issue.