I'm unable to accurately map imagery being collected with an M300 / P1 / DRTK-2. The screenshot attached shows example metadata from one of the images. The "Absolute Altitude" in the image references above sea level, and the Relative Altitude is referencing above ground level.
This mission was set to run at 100m altitude AGL relative to take-off point so the Relative Altitude of 99.984m appears to be correct.

I'm unsure where the 96.257m Absolute Altitude ASL in the metadata is coming from or how it could be possible and that is what is being imported into my processing software. It wouldn't make sense that the ASL is 96m and the AGL was 100m, that would put the ground 4m below sea level which it is not (actual ASL elevation on the ground is around 12m).

When I import the data into my processing software, I'm using EGM96 as a vertical reference and the ortho ends up being drawn about 12m above ground level.

Any help sorting these numbers out would be greatly appreciated.

I'm unable to accurately map imagery being collected with an M300 / P1 / DRTK-2. The screenshot attached shows example metadata from one of the images. The "Absolute Altitude" in the image references above sea level, and the Relative Altitude is referencing above ground level.
This mission was set to run at 100m altitude AGL relative to take-off point so the Relative Altitude of 99.984m appears to be correct.

I'm unsure where the 96.257m Absolute Altitude ASL in the metadata is coming from or how it could be possible and that is what is being imported into my processing software. It wouldn't make sense that the ASL is 96m and the AGL was 100m, that would put the ground 4m below sea level which it is not (actual ASL elevation on the ground is around 12m).

When I import the data into my processing software, I'm using EGM96 as a vertical reference and the ortho ends up being drawn about 12m above ground level.

Any help sorting these numbers out would be greatly appreciated.