...
As described above different types of JSON object collections can be obtained, depending on which object service will be used. It doesn't alter single object structure, but resulting object collections can have slightly different structure. Since we're working with object collections, we can have a set of objects which contain topology tree without geometry, or object collections with geometry. In the case we've requested a collection of objects with geometry, we need some additional information f.e. like view box size (3D model dimensions which should be rendered). So these properties will be added to the set of objects. Thus generally we can consider objects collection like a set of objects with additional properties. Object collection type defined by additional element in the resource path.
...
Services getTopology() and getProjectTree()
HTTP request: (see BIM+ Services):
...
| Code Block |
|---|
{
objects: {
id: "54dd1d25-4c58-4af2-96a1-1d26fa440177",
name: "Element",
type: "10074EEF-9418-4D64-9C6D-23932835A7F1",
division,
parent: null,
attributes: {
general: {
name: "<PP>Wall layer",
valid: true
},
quantity: {
length: 8523.27,
width: 300,
height: 2500,
volume: 6392448992.508584,
area: 21308163.308361948
},
<...>,
},
children: <child_objects>}
},
{...},
...
}
|
For the project topology the depth of the tree will be filtered till the node type "subproject".
Alternative Geometry Services getMesh(),
...
getThreejs()
HTTP request: (see BIM+ Services):
...