ARCore –超过24小时的Cloud Anchors或超过7天的Feature Points [英] 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 ARCore Cloud Anchor Service 中的"nofollow noreferrer> Cloud Anchors 会在24小时后失效.

Cloud Anchors stored at Google ARCore Cloud Anchor Service expire after 24 hours.

目前，仍无法在24小时后访问Cloud Anchors. 7天后，点云也将被丢弃.可以将自己的托管服务用于Cloud Anchors，但是在这种情况下，您将无法使用ARCore Cloud Anchor API.

At this time 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.

成功托管锚点后，该锚点将成为Cloud Anchor，并被分配一个唯一的Cloud Anchor 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.

• 稀疏点图在生成后的24小时内可用于Cloud Anchor解析请求.
• 以前上传的地图数据永远不会发送到用户的设备.

而且，正如您所说的:

在托管锚点时上传到云的原始视觉映射数据将在7天后被丢弃.

Raw visual mapping data uploaded to the cloud when hosting an anchor is discarded after 7 days.

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