Page History

...

https://api.bimplus.net/v2/bimplus/disciplines/

Default HTTP method is get, so we mustn't specify it explicitly in the request. Server responses with a string, which automatically will be converted into JSON object:

...

threejs: {
	elementcount: 14312,
	viewbox: {
		x: 827364,
		y: 23765,
		z: 2974652,
		with: 827346,
		height: 2873456,
		depth: 1726354
	},
	colors: [123414, 9817413, ....],
	geometries: [ {<ThreeJS_JSON_format>}, {...}, ... ]
}

Object services and resulting object collections structures.

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, f.e. if we have service getTopology(), that means that HTTP request will look like (see BIM+ Services):

GET https://api.bimplus.net/v2/bimplus/objects/<object_id>/topology

As a resulting set following JSON object should be created:

{

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>}

}, 
{...},
...

Class diagram (v2, draft)

...