Unable to Process Transformation to INAGEOID even after providing Datum

[Aakash Parsi]

Hello,

We use Metashape Python SDK 2.x , we recently have added INAGEOID 2020 Vertical Datum to our system and tried to export the report using that datum but we have been constantly facing the same issue "Unsupported Datum Transformation WGS84 to INAGEOID 2020", we have tried all the possible ways and I could not find any way to enforce metashape to use this particular vertical datum for processing, please help us , this is of highest priority for us


Unable to attach the Vertical Datum file as its 92 MB

[Alexey Pasumansky]

Hello Aakash Parsi,

Please send to support@agisoft.com the GeoTIFF file that you are using in /geoids/ folder, PRJ file with the WKT definition of the compound coordinate system used in the project and list of several 3D points (XYZ) that we can test with the geoid.

If you also have the undulation grid in external format that you have used to create Metashape-supported GeoTIFF, please send it to us as well.

[Paulo]

Hello Alexey,

I found the iNAGEOID2020 version 2 at https://zenodo.org/records/8404628 in txt (lon,lat,alt) format. However, on my side trying all possible avenues (custom datum or already ESPG defined vertical datums), I always get undefined datum transformation or vertical datum out of range...Strange

update. I was able to configure a SRGI2013 + INAGEOID2020 height compound CS. THE transformation using crs.transform method works well in both directions but when i try to Convert Reference from wgs84 to SRGI2013 + INAGEOID2010 height, after setting all datum tranformation parameters to Custom (all 0), it does do the conversion but still prints vertical datum out of range error.
See following:

[Alexey Pasumansky]

Hello Paul,

I think we have managed to create proper geoid based on data provided by Aakash to support email.

Assuming that the undulation grid in the shared file has been defined on WGS84 ellipsoid, we have customized the required UTM projection by adding "INAGeoid2020 v2 height" (EPSG::20036) to it via coordinate system editing dialog and then loading the geoid file through Datum Transformation Settings dialog -> Add Geoid button.
The resulting WKT line for the compound coordinate system was the following:

Code: [Select]

COMPD_CS["WGS 84 / UTM zone 50S + INAGEOID2020 height",
PROJCS["WGS 84 / UTM zone 50S",
GEOGCS["WGS 84",
DATUM["World Geodetic System 1984 ensemble",
SPHEROID["WGS 84",6378137,298.257223563,AUTHORITY["EPSG","7030"]],
TOWGS84[0,0,0,0,0,0,0],AUTHORITY["EPSG","6326"]],
PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],
UNIT["degree",0.01745329251994328,AUTHORITY["EPSG","9102"]],
AUTHORITY["EPSG","4326"]],
PROJECTION["Transverse_Mercator",AUTHORITY["EPSG","9807"]],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",117],
PARAMETER["scale_factor",0.9996],
PARAMETER["false_easting",500000],
PARAMETER["false_northing",10000000],
UNIT["metre",1,AUTHORITY["EPSG","9001"]],
AUTHORITY["EPSG","32750"]],
VERT_CS["INAGeoid2020 v2 height",
VERT_DATUM["Indonesian Geoid 2020 version 2",2005,AUTHORITY["EPSG","1328"]],
UNIT["metre",1,AUTHORITY["EPSG","9001"]],
AUTHORITY["EPSG","20036"]]]

[Paulo]

Alexey,

thanks for the update. But I still get Vertical datum out of range when I define the chunk crs according to your supplied wkt.

See attachment..

Is it my version or the geoid file created?

[Paulo]

Hello,

We use Metashape Python SDK 2.x , we recently have added INAGEOID 2020 Vertical Datum to our system and tried to export the report using that datum but we have been constantly facing the same issue "Unsupported Datum Transformation WGS84 to INAGEOID 2020", we have tried all the possible ways and I could not find any way to enforce metashape to use this particular vertical datum for processing, please help us , this is of highest priority for us


Unable to attach the Vertical Datum file as its 92 MB

Hi Aakash,

please download latest release of v.2.2.1 and it should solve your issue with INAGEOID 2020