Two weeks ago, Model Properties API was released. Based on SVF2 data, it provides the ability to build indexing with rich properties and the query supports sophisticated conditions in granular control (SQL-liked expression). It can also compare model versions and tells added/removed/changed objects & different properties/geometry hash(plus bounding box data).
As you may have experience with Model Derivative API of Forge which can also provide model properties, the table below describes the differences of the two APIs only in this perspective. We hope it would help when you evaluate which one is more suitable to you scenarios.
| Comparison | Model Derivative API | Model Properties API |
|---|---|---|
| Environment | general service for any models | models in BIM360/ACC only |
| Token | 2-legged or 3-legged | 3 legged token only |
| Trigger Translation | Yes | No |
| Model Hierarchy | Yes | No |
| Object Properties | Yes | Yes |
| Properties Indexed | No | Yes |
| Models Difference | No | Yes |
| Model Formats | formats in Supported Translation |
|
| Properties Format |
|
|
| Search |
|
|
| Properties Fields (keys) info | No | Yes |
| dbId | dbId for SVF/SVF2 | dbId for SVF/SVF2/OTG |
| External Id | Yes | Yes |
| Bounding-box data | No | Yes |
| Geometry Hash | No | Yes |
| Properties Hash | No | Yes |
| Views the object locates in | No | Yes |
Xiaodong Liang has been with Autodesk since 2007, focusing on providing programming support, consulting, training and evangelism to external developers. He started his career China and now lives in Beijing, China. Xiaodong is currently a developer consultant in the team Developer Technical Services (DevTech), the worldwide team of API gurus providing technical services through the Autodesk Developer Network. He...