Geoid no longer workds with latest 2.2.1 release

[Paulo]

hello support,

I used to work with a compound CS including the GGM2010 geoide (Geoide Gravimétrico Mexicano 2010) without any problem. But now when I load a Compound CS WGS84 / UTM14 + Altura GGM2010, I get Vertical datum missing Error.

Clearly, the GGM2010.tif geoid is present in geoids list...see following

I think something is broken in the geoids treatment

Please advise,

The weirdest is the geoids list, shows the AusGeoid2010 as the one used....

[Paulo]

Update...

i was able to make it work by renaming the vertical cs name to same as to entry in description of relevant file of geoids list...

previously, this was not the case at it looked at Vertical datum name....

However, when I convert coordinates from wgs84 to this compound CS , I still get Verttical datum out of ramnge error...

And even if my geoid file is correct, when I try to click on world to placa a market I get multiple vertical datum out of range....

Still does not work

[wojtas]

Hi, I noticed the same issue affects all of my user-definied coordinate systems with imported geoids. I had to downgrade Metashape to 2.2.0 version to keep working on my projects.

[Paulo]

Thanks wojtas for info1

Yes from latest release with the horizontal shift grid support for compound coordinate systems, this has somehow affected the original normal geoid file procedure. Hope this will be fixed soon!

[Dmitry Semyonov]

Hello Paulo,

Thank you for reporting the problem.

Indeed there was a problem with custom geoids without EPSG codes in the original Metashape 2.2.1 release.

We fixed the problem and updated Metashape 2.2.1 installers on our website.

Please download the latest Metashape 2.2.1 build 20547 from our website with a fix included:
https://www.agisoft.com/downloads/installer/

We are very sorry for inconvenience.

[Paulo]

hello Dmitry,

thanks a lot it works, now!

I guess you can close the tickets I had raised concerning the Italian and Indonesian geoids....