ARCore – 超过 24 小时的云锚点或超过 7 天的特征点 [英] ARCore – Cloud Anchors for more than 24 hours or Feature Points for more than 7 days

问题描述

是否可以在 24 小时后访问 Cloud Anchors 和/或重新激活功能点?

Is it possible to have Cloud Anchors be accessed after 24 hours and/or the feature points re-activated?

推荐答案

根据 Google 文档:

According to Google documentation:

在 ARCore 1.20 及更高版本中，云锚点可以在托管后 365 天得到解决.在 1.20 之前的 ARCore 版本中，云锚点只能在托管后 24 小时内解析.

In ARCore 1.20 and later, Cloud Anchors can be resolved for 365 days after they are hosted. In versions of ARCore earlier than 1.20, Cloud Anchors could be resolved only for 24 hours after they were hosted.

如果您使用的是 ARCore 1.12 ... ARCore 1.19 – 24 小时后仍然无法访问云锚点.点云也会在 7 天后丢弃.有可能将您自己的托管服务用于 Cloud Anchor，但在这种情况下，您将无法使用 ARCore Cloud Anchor API.

If you're using ARCore 1.12 ... ARCore 1.19 – it's still impossible to access Cloud Anchors after 24 hours. Also Point Cloud is discarded after 7 days. It's potentially possible to use your own hosting service for Cloud Anchors, but in that case you'll be unable to use an ARCore Cloud Anchor API.

一旦成功托管了一个锚点，该锚点就会成为一个云锚点并被分配一个唯一的云锚点 ID.在此之后，它会存活二十四小时.使用 Firebase 实时数据库交换锚 ID.

Once an Anchor is hosted successfully, the anchor becomes a Cloud Anchor and is assigned a unique Cloud Anchor ID. After this it lives twenty-four hours. Anchor IDs are exchanged using Firebase Realtime Database.

在服务器端根据存储的稀疏点图解析锚点.

Anchors are resolved on the server side against the stored sparse point map.

这篇关于ARCore – 超过 24 小时的云锚点或超过 7 天的特征点的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！