Raw Depth API vs Full Depth API
At Google I/O 2021, the Raw Depth API for ARCore 1.24 version was announced in addition to the existing Full Depth API, working since ARCore 1.18. This second-Gen depth API gives you the ability to merge Raw Depth data coming from iToF sensor with data coming from Depth-from-Motion
ML-algorithm. The resulted data can be retrieved through 16-bit buffer stream, where 13-bit is reserved for depth map
and 3-bit is reserved for confidence map
.
At Google I/O 2022, Full Depth API
was updated for users running ARCore 1.31. Now, all 16 bits per pixel are used, allowing app to represent the depth within a distance of 65,535 millimeters.
Today ARCore developers can use Raw Depth API for Precise Measurements and for ops on Reconstructed Mesh. On the other hand, Full Depth API is ideally suitable for People/Objects Occlusion and Scene Relighting purposes.
The following table represents three important parameters:
|
Full Depth API (v1.31+) |
Raw Depth API (v1.24+) |
Full Depth API (v1.18+) |
Accuracy |
Bad |
Awesome |
Bad |
Coverage |
All pixels |
Not all pixels |
All pixels |
Distance |
0 to 65.5 m |
0.5 to 5.0 m |
0 to 8.2 m |
Raw Depth is available on all devices that support the Depth API. The Raw Depth API, like the Full Depth API, does not require a supported hardware depth sensor, such as a time-of-flight (iToF) sensor. However, both the Raw Depth API and the Full Depth API make use of any supported hardware sensors that a device may have.
The list of ARCore Depth API supported devices is growing. Pay attention to the last column called Comments
- info about Depth API support is there.