Vertical Datum out of range 1.7.1

[flyzk]

Maybe the problem come from another source: I've changed both my Marker and project that was in the old custom GEOID by the new one. Maybe I should only change the project coordinate system without changing the marker and then create DEM?

[Paulo]

The difference in geoid height at these 4 points is maximum 4 mm. So 10 cm error does not come from this expanded geoid

Code: [Select]

ID X Y Z RAR07 fr ign RAR07 Geoid_Diff
1 321294.397 7681606.334 11.304 3.501 3.502 -0.001
2 321372.135 7683392.457 8.955 3.246 3.250 -0.004
3 321179.878 7682426.914 2.417 3.369 3.373 -0.004
4 321360.926 7683811.359 3.321 3.181 3.184 -0.003


[Alexandre Demers-Potvin]

Hi, everyone,

I've encountered similar challenges when I tried to export a 3D model from Metashape 1.7 in .kmz format. No matter which geographical and vertical CS I used, the vertical datum was always out of range. I made sure I always used the same CS for markers and cameras at every attempt, but it just didn't work. I followed Alexei's advice and got the following results.

1. Disable interpolation for mesh building: didn't work
2. Expand geoid: didn't work. I noticed that it is possible to edit the No Data area in the 'import geoid' pane, but this edit doesn't appear to get saved, no matter which geoid I import. I tried to edit that in the 'ToWGS84' pane too, but it didn't work either. I tried the EGM 96, NAVD88 and CGVD2013 to no avail.

Disclaimer: the only reference data for my model consists in a single georeferenced camera plus 2 control points I placed manually by estimating their position from Google Earth. Maybe my reference data just isn't precise or accurate enough for now.

Here are the coordinates of my reference data just in case:

Type               Longitude            Latitude           Altitude(m)         Altitude error(m)
Camera          -111.394094         50.759816        695.059504          1.399042
Marker           -111.394115         50.760669         668.559534          0.000001
Marker           -111.393617         50.760367         670.559513          -0.000001

Thanks,
Alexandre Demers-Potvin

[Alexey Pasumansky]

Hello Alexandre,

Do you observe the problem in 1.7.2 version as well?

[wizprod]

I am also having this problem a lot! Usually happens at some point after converting Cameras to another datum. And especially prone to happen if Markers and Cameras are not converted at the same time, or you use the Update from Exif, resulting in a Datum mismatch between Markers and Cameras.

And the real mess is that there seem to be no remedy other than do the project again from scratch

Also occuring in 1.7.2.

[gismoe]

Same Problem here with Version 1.8.1

Loaded pics that worked in older versions but now after trying to change the coordinate system with undulation modell, results in "vertical datum out of range"

[Alexey Pasumansky]

Hello!

If the problem is also observed in 1.8.3, please share the original project file (re-saved in PSZ format) to support@agisoft.com together with the target coordinate system definition in WKT format (saved to PRJ file) and geoid file used, so that we could reproduce the issue on our side and analyse the problem.

[andyroo]

working on 1.8.4 with both old and new geoid installed:

egm96-15.tif  navd88-12b.tif  us_noaa_g2012b.tif

I'm getting the "vertical datum out of range" error in 1.8.4 when trying to build a DEM in NAD83UTM17N (EPSG:6346)+NAVD88 from a point cloud in NAD83(2011) (EPSG:6318) ellipsoid height. Working in SW Florida:

2022-10-19 13:39:12 BuildDem.buildRawTiles (64/99): source_data = Dense cloud, subtask = buildRawTiles, interpolation = Disabled, projection = NAD83(2011) / UTM zone 17N + NAVD88, classes = Created (never classified), resolution = 0
2022-10-19 13:39:13 loaded elevation data in 0.000698 sec
2022-10-19 13:39:13 Error: Vertical datum out of range
2022-10-19 13:39:13 processing failed in 1.09217 sec

Dense cloud was built in NAD83(2011), and a workaround is to build the DEM in UTM17N/ellipsoid height, and export in UTM17N+NAVD88, but it breaks some of my scripts and is irritating.

Should I only have the new Geoid file installed? Seems like it might be related to the issue discussed earlier re 1.7.1?