Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Potential AR feature - point clouds #71

Open
bialpio opened this issue Oct 12, 2021 · 3 comments
Open

Potential AR feature - point clouds #71

bialpio opened this issue Oct 12, 2021 · 3 comments

Comments

@bialpio
Copy link

bialpio commented Oct 12, 2021

Creating an issue to gauge interest for a new feature, I expect it to be mostly relevant for AR. Both ARCore and ARKit expose such APIs (unsure about other platforms). Do we think this is something worth pursuing, or is that a too-low-level API?

/tpac to see what people think, probably would not take more than 15 (no API shape to talk about)

@DRx3D
Copy link

DRx3D commented Oct 12, 2021

Several 3D organizations are currently working on various aspects of point clouds. OGC has active work in the field. MPEG is working with some proposals. Khronos is investigating the delivery and rendering of point cloud data. JPEG also is pursuing Point Clouds in some manner. Not all of the work is for AR, and some (especially MPEG) is done with streaming in mind (live active).

I am interested in this discussion if it can be on Friday.

@AdaRoseCannon AdaRoseCannon transferred this issue from immersive-web/administrivia Oct 13, 2021
@probot-label probot-label bot added the TPAC label Oct 13, 2021
@AdaRoseCannon
Copy link
Member

I've moved this over to Proposals as it is new work :)

@bialpio
Copy link
Author

bialpio commented Oct 18, 2021

Summary of the TPAC discussions:

  • scope of work would be exposing an API that allows access to the point clouds used by the underlying XR system within the XR session
  • example APIs that this could be implemented on top of: ARCore, ARKit, no corresponding API in OpenXR.
  • some interest from 8thWall, could save them work in having to detect feature points JS-side (pros: ease of implementation, potentially better perf since they won't need to do the work that the XR system is already doing anyway)
  • backwards compatibility is a potential risk: exposing point clouds API means that the implementations will need to commit themselves to a specific behavior
  • cross compatibility is a potential risk: XR experiences that would otherwise work well across most / all systems could take a dependency on this and would not work in some cases, depending on the hardware and the framework being used

Please let me know if I messed something up or misunderstood. @thetuvix, @nbutko, @DRx3D, @fordacious - FYI as you've been involved in the discussion.

@Yonet Yonet removed the TPAC label Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants