Page History

...

Anchor

	revisionService
	revisionService

...

Deck of Cards

id	bimCreateRevision

Card

label	URL / Resource / JSON Structure

Resource: revisions

URL: https://api-stage.bimplus.net/v2/<team_slug>/divisions/<id>/revisions

Example: https://api-stage.bimplus.net/v2/bimplus/divisions/00b54edd-c84c-4bd2-a08c-c93d1f28907a/revisions

JSON Structure:

Name	Mandatory / Optional	Type	Description
name	mandatory	string	Name of the revision
description	optional	string	Short description of the revision
projectId	will be ignored	string (guid)	Creation date of the revision
divisionId	will be ignored	string (guid)	Id of the model
revisionNr	will be ignored	int	Revision number
created	will be ignored	string (date)	Creation date
createdBy	will be ignored	user object	The user who created it
changed	will be ignored	string (date)	Modification date
changedby	will be ignored	user object	The user who did the modification
applicationId	will be ignored	string (guid)	The id of the application
inputType	optional	string	Type of upload (eg: "IFC_IMPORT")

Note: The import/upload is always done only for the latest revision.

Card

label	HTTP Method

POST

Card

default	true
label	Description

Use this API for creating a new revision. Please, note that import/upload is always done only for the latest revision. i.e if there are no revisions, & if we use import API the always the model is updated/overwritten. If a model has revisions & if we use the import API then always the latest import/upload is linked with the latest revision.

Card

label	Request

Code Block

borderColor	Green
lang	xml
title	Headers

Authorization: BimPlus 9c1874a62c974dcfa75e0132c423a088
Content-Type: application/json

Code Block

borderColor	Red
lang	xml
title	JSON

{
    "name": "Ballo.ifc"
}

Card

label	Response

Code Block

borderColor	Green
lang	xml
title	Status

Status: 201 Created

Code Block

borderColor	Red
lang	xml
title	JSON

{
    "id": "d2d39bca-051e-48fa-ba23-4845087a071c",
    "name": "Ballo.ifc",
    "description": "",
    "projectId": "e31c3480-5633-4506-b717-8dd97c0f0ab3",
    "divisionId": "00b54edd-c84c-4bd2-a08c-c93d1f28907a",
    "revisionNr": 6,
    "created": "2015-11-03T11:13:27.2",
    "createdby": {
        "id": "71e0ac3b-fa49-e540-ac2f-8caff3dd72ed",
        "email": "jayaraj.purushothaman@gmail.com"
    },
    "changed": "2015-11-03T11:13:27.2",
    "changedby": {
        "id": "71e0ac3b-fa49-e540-ac2f-8caff3dd72ed",
        "email": "jayaraj.purushothaman@gmail.com"
    },
    "applicationId": "0106c8ba-ad46-7c08-e26f-026852cb7525",
    "inputType": "IFC_IMPORT"
}

...

Deck of Cards

id	bimUpdateModelRevision

Card

default	true
label	URL / Resource / JSON Structure

Resource: projects/<project_id>

URL: https://api-stage.bimplus.net/v2/<team_slug>/projects/<project_id>

Example: https://api-stage.bimplus.net/v2/bimplus/projects/0d2ce2cc-3588-45d6-a59a-f6b89ebed34e

JSON Structure:

Name	Mandatory / Optional	Type	Description
name	mandatory	string	Name of the revision
description	optional	string	Short description of the revision
projectId	will be ignored	string (guid)	Creation date of the revision
divisionId	will be ignored	string (guid)	Id of the model
revisionNr	will be ignored	int	Revision number
created	will be ignored	string (date)	Creation date
createdBy	will be ignored	user object	The user who created it
applicationId	optional	string (guid)	The id of the application
inputType	optional	string	Type of upload (eg: "IFC_IMPORT")

Card

label	HTTP Method

PUT

Card

label	Description

Update the revision info of a model.

Card

label	Request

Code Block

borderColor	Green
lang	xml
title	Headers

Authorization: BimPlus 9c1874a62c974dcfa75e0132c423a088
Content-Type: application/json

Code Block

borderColor	Red
lang	xml
title	JSON

{
"name": "updated name"
}

Card

label	Response

Code Block

borderColor	Green
lang	xml
title	Status

Status: 200 OK

Code Block

borderColor	Red
lang	xml
title	JSON

{
    "id": "d2d39bca-051e-48fa-ba23-4845087a071c",
    "name": "updated name",
    "divisionId": "00b54edd-c84c-4bd2-a08c-c93d1f28907a",
    "revisionNr": 6,
    "created": "2015-11-03T11:13:27",
    "createdby": {
        "id": "71e0ac3b-fa49-e540-ac2f-8caff3dd72ed",
        "email": "jayaraj.purushothaman@gmail.com"
    },
    "changed": "0001-01-01T00:00:00",
    "changedby": {
        "id": "71e0ac3b-fa49-e540-ac2f-8caff3dd72ed",
        "email": "jayaraj.purushothaman@gmail.com"
    },
    "applicationId": "0106c8ba-ad46-7c08-e26f-026852cb7525"
}

...

GET /<TeamSlug>/objects/<ObjectID>/attachments?revision=2

Anchor

revisionComparison

	calculateModelRevisionsComparison

revisionComparison

...

	calculateModelRevisionsComparison

Calculate revisions comparison of the model

Deck of Cards

id	bimGetRevisionListOfModelbimCalculateModelRevisionsComparison

Card

default	true
label	URL / Resource / JSON Structure

Resource: divisions/{divisionId}/revisions/{latest divisions/<division_id>/revisionscomparison/<higher_revision_no}/compare/{any_previous_revision_no}number>/<lower_revision_number>

URL: https://api-stage.bimplus.net/v2/ <team_slug>/divisions/{divisionId}/revisions/{latest<division_id>/revisionscomparison/<higher_revision_no}/compare/{any_previousnumber>/<lower_revision_no}number>

Example: https://api-stage.bimplus.net/v2/bimplus/divisions/00b54edd-c84c-4bd2-a08c-c93d1f28907a/revisionscomparison/revisions5/2/compare/1

Card

label	HTTP Method

GET POST

Card

label	Description

Compare

This API call will calculate comparison between two revisions of the same model

& get the differences. There are three sets of data returned (i.e Newly created objects, Modified objects & Deleted objects) The unaffected & hidden objects are not returned in the response. The modified objects contains both the new part & the old part

to provide revisions differences. The revisions numbers does not have to be consecutive, meaning you can compare revisions e.g. 5 vs 2. But revision numbers must be in correct order, revisions number higher_revision_number must be higher then lower_revision_number. The higher revision number maybe be also the latest revision.

Card

label	Request

Code Block

borderColor	Green
lang	xml
title	Headers

Authorization: BimPlus 9c1874a62c974dcfa75e0132c423a088
Content-Type: application/json

Card

label	Response

The response is similar to the /v2/{slug}/objects/{id}/geometries/threejs/properties/8

Code Block

borderColor	Green
lang	xml
title	Status

Status: 200 OK

Code Block

borderColor	Red
lang	xml
title	JSON

 - when succeeded calculation of comparison of revisions of the model

Status : 400 BadRequest - if revision numbers are incorrect, or first revision is not greater than second
Status : 400 NotFound - if any of the revisions does not exist

Code Block

borderColor	Red
lang	xml
title	JSON

The response is similar to the GET <Url>/<TeamSlug>/divisions/<division_id>/revisionscomparison/<higher_revision_number>/<lower_revision_number>. 
For details see "Get calculated comparison of revisions of the model" below.

Anchor

	getModelRevisionsComparison
	getModelRevisionsComparison

Get calculated comparison of revisions of the model

Deck of Cards

id	bimModelRevisionsComparision

Card

default	true
label	URL / Resource / JSON Structure

Resource: divisions/<division_id>/revisionscomparison/<higher_revision_number>/<lower_revision_number>

URL: https://api-stage.bimplus.net/v2/<team_slug>/divisions/<division_id>/revisionscomparison/<higher_revision_number>/<lower_revision_number>

Example: https://api-stage.bimplus.net/v2/bimplus/divisions/00b54edd-c84c-4bd2-a08c-c93d1f28907a/revisionscomparison/5/2

Card

label	HTTP Method

GET

Card

label	Description

This api returns already calculated comparison of revisions of the model. In returned json is very important property "IsUpToDate" which provide information if revision comparison is actual or not.
In response are most important four sets of objects - inserted, deleted, changedGeometry, changed.
The unaffected & hidden objects are not returned in the response.

Card

label	Request

Code Block

borderColor	Green
lang	xml
title	Headers

Authorization: BimPlus 9c1874a62c974dcfa75e0132c423a088
Content-Type: application/json

Card

label	Response

Code Block

borderColor	Green
lang	xml
title	Status

Status: 200 OK

Code Block

borderColor	Red
lang	xml
title	JSON

{
  "divisionId": "958ee96f-12c6-4684-928c-7119ad7090ab",
  "firstRevision": 3,
  "secondRevision": 2,
  "status": "DONE",
  "isUpToDate": true,
  "calculatedAt": "2016-10-19T09:05:39.8138934",
  "calculatedBy": {
    "id": "7c555899-5a5f-44d1-930e-284930678bed",
    "email": "user@allplan.com"
  },
  "inserted": [ ... ],
  "deleted": [ ... ],
  "changedGeometry": [ ... ],
  "changed": [ ... ]
}
 
NOTE :  Properties "inserted", "deleted", "changedGeometry" and "changed", all returns array of objects, e.g. :
 
{                                                             
 "comparisonObjectId": "870c9ced-63fb-4fdf-beaf-ebd19507c072",
 "first": { 																									
 "id": "3a2d82dc-325c-4369-a083-02e3535d850d", 								
 "type": "Beam", 																							
 "name": "Beam_1-01" 																					
 },                                                           
 "second": { 																									
 "id": "3a2d82dc-325c-4369-a083-02e3535d850d",                
 "type": "Beam",                                              
 "name": "Beam_1-01"                                          
 }

JSON Structure:

Name	Type	Description
divisionId	string(guid)	The id of the model
firstRevision	int	higher revision number between whose the calculation was done
secondRevision	int	lower revision number between whose the calculation was done
status	string	Can be "DONE" => ok, or "PENDING" => calculation was not yet completed
isUpToDate	bool	Should be be true. False means that the model was changed after the revision comparison was calculated, so the revision comparison is not actual, and it will be better to recalculate again with POST (see api call above)
calculatedAt	string (date)	The date and time of the calculation
calculatedBy	string (user)	The user which performed the calculation
inserted	objects	Objects that exists only in in first (higher) revision but not in the second
deleted	objects	Objets that exist only in the second (lower) revision, but are already deleted in the first (higher) revision
changedGeometry	objects	Objects that exists in both revisions, but with different geometry
changed	objects	Objects that exist in both revisions, have identical geometry, but some other properties are changed, (objects identical in both revisions are not present in this response)
NOTE : Properties "inserted", "deleted", "changedGeometry" and "changed", all returns array of objects, e.g. : { "comparisonObjectId": "870c9ced-63fb-4fdf-beaf-ebd19507c072", "first": { "id": "3a2d82dc-325c-4369-a083-02e3535d850d", "type": "Beam", "name": "Beam_1-01" }, "second": { "id": "3a2d82dc-325c-4369-a083-02e3535d850d", "type": "Beam", "name": "Beam_1-01" } }
comparisonObjectId	string(guid)	id of the comparison object
first	object	Object from revision with higher revision number. This object is not present in the "deleted" list. Object has following properties: id of the compared element ("id") element type name ("type") element name ("name")
second	object	Object from revision with lower revision number. This object is not present in the "inserted" list. Object has following properties: element type name ("type") element name ("name")

Math Editor

Space shortcuts

Page tree

Versions Compared

Old Version 16

New Version 17

Key

Calculate revisions comparison of the model

Get calculated comparison of revisions of the model