# Wrong Orthometric Heights **URL:** https://community.pix4d.com/t/wrong-orthometric-heights/17437 **Category:** PIX4Dmatic Questions/Troubleshooting **Created:** [April 3, 2021, 11:49am UTC](https://community.pix4d.com/t/wrong-orthometric-heights/17437 "2021-04-03T11:49:02Z") **Posts on this page:** 1 **Showing post:** 7
### Author: ![Vertical\_Aspect\_Supp](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/vertical_aspect_supp/32/345_2.png) [@Vertical\_Aspect\_Supp](https://community.pix4d.com/u/Vertical_Aspect_Supp) #### Post date: [April 13, 2021, 11:52am UTC](https://community.pix4d.com/t/wrong-orthometric-heights/17437/7 "2021-04-13T11:52:52Z")
> [@Blaz](#): > > I had a look, and the vertical coordinate system is set to EGM96 when importing the DJI Zemnuse P1 images and not ellipsoidal height. I have to take your word for this since I have no control over the camera coordinate system as in Mapper. Matic is much more of a “Black Box Solution” than Mapper, and I am not sure that I like that as a Land Surveyor. > [@Blaz](#): > > In other words, Pix4Dmapper treats images as if they are in EGM96 and then transform them into Geoid18 that you selected in coordinate system dialog. Do you think this could explain the offset that you get? Since this is the behavior for other DJI drones in the past, this could definitely be the problem. I did check the elevation of one of the cameras in Matic vs. the same in Mapper and there was a 4.62-foot difference. I then computed the EGM96 and the Geoid 18 values and subtracted and came up with a distance of 4.61 feet. This would indicate that the EGM 96 value is being erroneously applied. I have never understood why you would apply a geoid value to the image. This was the first thing I advised clients to change in Mapper. --- _[View the full topic](https://community.pix4d.com/t/wrong-orthometric-heights/17437)._