import of google pixel depth maps not working

[ferengi]

When I try to import the depth map from images taken with my Google Pixel 7 Pro, Metashape does recognize that depth data is present, but it only generates a second image and no actual depth information.
Unfortunately, the example image is too large to attach here, but I can send it via email if needed.

Pro Version 2.2.2 build 20848 from https://www.agisoft.com/forum/index.php?topic=17289.0

[vineg]

Hi!

I just tried to check a picture from Google Pixel 7 Pro from an internet.

When imported it in Metashape - there is a message in a log:
"Android embedded depth has unsupported units: Diopters"

So it looks like there is no proper depth sensor...
Do you have similar message?

[ferengi]

hi,

no im only getting

2025-08-05 21:02:40 Failed to load android embedded depth data.

and the depth data is loaded as own grayscale image

[vineg]

Hi!

The picture you've attached doesn't looks like a depth. Depth is usually brighter or darker based on the distance to an object.
There is often some other data embedded to the photos, which may be recognized, but it is not necessarily depth.

You can send a sample to support@agisoft.com with a link to this thread, but it is very unlikely that there is some data that we can use.

[ferengi]

You're right, I should have described it better.
When you open the photo with, for example, https://www.photopea.com, you can see that there are three additional data sets stored next to the main image. One of them looks like a correct depth map. It appears as if Metashape is loading the bottle plane from the image.
I will send the photo by email for closer inspection.

[vineg]

Hi!

I've received a photo. It does contain visualization of depth information, but it is uncalibrated.

There is such notable values in the image metadata:

Cameras Depth Map Format      : RangeLinear
Cameras Depth Map Units         : None
Cameras Depth Map Near          : -0.251632
Cameras Depth Map Far            : 1.147961

Whereas we expect some metric units and Near value should never be negative. I've tried substituting different near and far values just in case (attached visualization), but it looks like depth data has some non standard transform.

As of Android phones, I've only seen photos from Nokia 9 PureView with suitable depth data so far.

[ferengi]

thanks for investigating, it was worth a try.
maybe you could update the Helpdesk artikle?

https://agisoft.freshdesk.com/support/solutions/articles/31000162212-smart-cameras-with-depth-sensor-data-processing

[vineg]

Sure, we've added a note.

Thanks for pointing!