externalId Navisworks 文件的持久性 [英] persistence of externalId Navisworks files

问题描述

我一直在使用 externalId 来唯一地引用伪造查看器中的对象，并将它们与有关这些对象的外部数据连接起来.这对于具有一种 GUID 86715290-fa28-4ff5-aef9-8c75d7c81e77-0012917b 的 revit 文件很有效.现在我正在处理一个 Navisworks 文件，它们的 externalId 使用看起来与 a、0 或 0/0/0/.这些有多持久，我可以想象不是全局唯一的，但是更改/删除/添加是否使它们在文件中保持唯一?在 Navisworks 文件中全局引用实体的建议策略是什么?

I've been using the externalId to uniquely refer to objects in the forge viewer and connect them with outside data about these objects. This has worked well for revit files, which have a kind of GUID 86715290-fa28-4ff5-aef9-8c75d7c81e77-0012917b. Now I'm working with a Navisworks file, and their externalId use looks very different with values like a, 0 or 0/0/0/. How persistent are these, I can imagine not globally unique, but do changes/removals/additions keep them unique within the file? What is the suggested strategy to globally refer to solids in Navisworks files?

推荐答案

通过模型选择树到该元素的路径的外部 id 从 0 开始，请参见下面的快照:

The external id of the path through the model selection tree to that element started from 0, see the snapshot below:

据我所知:

在 Revit 案例中，它使用元素的唯一 ID(即 Revit API 的 Element.UniqueId)作为 externalId.但是，Navisworks 没有概念唯一 ID，因为它必须处理不同的格式，而且某些源模型也没有唯一 ID.因此，它使用选择树路径作为 externalId.

In Revit case, it uses a unique id of the element (saying Element.UniqueId of the Revit API) as the externalId. However, the Navisworks doesn't have a concept unique id since it will have to handle different formats and some source models don't have unique id either. Therefore, it uses the selection tree path as the externalId instead.

因此，

为了保留Revit元素的标识信息，我建议你添加一个Revit共享参数来存储Element.UniqueId的值，并通过这个参数来标识元素.

To preserve the identity information of the Revit elements, I would like to advise you to add a Revit shared parameter to store the value of the Element.UniqueId, and identify the element by this parameter.

这篇关于externalId Navisworks 文件的持久性的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！