Metadata altitude is totally off - Help!

[bostonkiter]

For some reason, our exif files now show bizarre altitude readings. They're now "below sea level". Does anyone know what gives?!

THANK YOU!


This is what it looks like...

 

[southerndoug]

I noticed this when I was using Map Pilot for survey work. The exif data does not use the barometric altitude, but might be using the GPS altitude, which is notoriously bad. The Maps Made Easy guys said DJI was aware of the problem as was going to address it. They probably haven't....

 

[The Editor]

For some reason, our exif files now show bizarre altitude readings. They're now "below sea level". Does anyone know what gives?!

THANK YOU!


This is what it looks like...
View attachment 8223

Not unusual for GPS altitude data to be out by +/-400 feet.
Depending on the DOP error at the time this can easily average 75 feet in either direction.
GPS height data should not be relied upon as nearly all manufacturers base their altitude measurements on the elipsoid from centre orbit. Since the Earth is nowhere near round this model is flawed and so you will always get height/altitude errors in the data.

 

[bostonkiter]

Not unusual for GPS altitude data to be out by +/-400 feet.
Depending on the DOP error at the time this can easily average 75 feet in either direction.
GPS height data should not be relied upon as nearly all manufacturers base their altitude measurements on the elipsoid from centre orbit. Since the Earth is nowhere near round this model is flawed and so you will always get height/altitude errors in the data.

Thanks for the response.

Point taken regarding the GPS vs Alt accuracy with HDOP in mind. However, the metadata was never incorrect until now. It's as if the inspire stopped using the alt to populate the altitude and started using GPS in its place. This is very troublesome as we depend on this for industrial application. Please post if you have any further info.

THANKS!

 

[NickOfLeeds]

Thanks for the response.

Point taken regarding the GPS vs Alt accuracy with HDOP in mind. However, the metadata was never incorrect until now. It's as if the inspire stopped using the alt to populate the altitude and started using GPS in its place. This is very troublesome as we depend on this for industrial application. Please post if you have any further info.

THANKS!

Did you get to the bottom of this by any chance?
I have just started to realise that this may be causing me a problem.

 

[Mogmen]

Does anyone have a solution for fixing in incorrect altitude data in the exif?

I tried my i1 with my x3 today and took 300+ images and they we all off by 160'. It consistently showed 280' in the exif when i was at 120' AGL. Is there a fix?

Is there a program that i can use on my PC to change this data without changing each individual photo.

Last year on my aircraft i was not having this problem. Does anyone know which FW update caused this issue and is it possible to go back and change the FW. I read where you can but now sure how many versions i can go back to.

Thank you
Ed

 

[bluelight.support]

Is there a program that i can use on my PC to change this data without changing each individual photo.

I use EXIF Editor on the mac and batch process my I1 images - just change from below to above sea level and it works fine. If I need anything more accurate, I just add GCP and go from there.

 

[KyleIRYS]

I still have the exact same issue on both an I1 w/ X5 and I2 w/ X5S.

Property devleopers want to look a their photos and know which levels they are looking from and it's an absolute mess of information. I'm not on absolutely latest firmware, but this has been an issue for well over a year for myself and none of the firmware updates I have done in that period of time have fixed it. I can confirm it DID work at some point prior, I'll see if I can pick a photo with correct metadata and backtrack which firmware I was on.

The question remains - why does DJI move from Baro to GPS Altitude data when it was working perfectly fine on the former?