Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
Hi,
We are looking into contextualizing our data models with 3D info, based on the relevant concepts/types from the Cognite Core Model. However, we ran into a limitation that as far as we can see severely limits the usability of the functionality as is.
The CogniteCADNode has a direct relation to a Cognite3DObject, that can be made up of multiple CogniteCADNodes, reflecting that an asset may correspond to multiple nodes in the 3D model. That makes sense.
However since the link from CogniteCADNode to Cognite3DObject is a single direct relation, the current model does not allow a CogniteCADNode to be part of more than one Cognite3DObject, which typically is meant to correspond to an asset. That is unfortunately in direct contrast to reality. One CAD node belonging to many different assets/objects is not an edge case, rather, it is the norm, at least for Aker Solutions.
Have we correctly understood the current functionality? If so, are there any plans to amend this limitation? Do you have a timeline for when we can expect an update to this?
Best regards,
Arnfinn Aamodt
AKSO DataOps