Menu Close

Can you access design metadata in Autodesk forge?

Can you access design metadata in Autodesk forge?

Sometimes, developers need to be able to access the metadata of their designs in Autodesk Forge without necessarily using the viewer. In this post we will take a look at some of the options the platform offers in this regard.

Where are the properties stored in Forge viewer?

Forge Viewer uses a different representation of the property database (mainly for performance reasons), stored in several *.json.gz files with similar naming as the tables in the sqlite database, for example, objects_attrs.json.gz , objects_avs.json.gz , objects_ids.json.gz, or objects_vals.json.gz.

Is it easy to parse JSON in Autodesk forge?

The JSON responses are easy to parse, and the endpoint can also be configured to only return properties of a single object with specific ID, making the requests faster and more efficient. However, before deciding to use this option in your application, consider the following characteristics of this endpoint:

How to get all DBID array in Autodesk?

One typical way to get all DbId array is to iterate model hierarchy by instanceTree.enumNodeChildren in the event when geometry are all ready ( Autodesk.Viewing.GEOMETRY_LOADED_EVENT ) The two blogs below tell more. For simple model, this workflow works well, but for a complicated huge model, it will take much time to complete the iteration.

Sometimes, developers need to be able to access the metadata of their designs in Autodesk Forge without necessarily using the viewer. In this post we will take a look at some of the options the platform offers in this regard.

When do we need to get the DBID of a model?

In most cases, we would need to get all DbId of the model when working with the web application of Forge Viewer. This is because most API methods of manipulating entities require the argument DbId (or array), such as isolate, hide, highlight etc. By the DbId array, we build a map with the the node of model hierarchy, or a kind of unique Id.

Forge Viewer uses a different representation of the property database (mainly for performance reasons), stored in several *.json.gz files with similar naming as the tables in the sqlite database, for example, objects_attrs.json.gz , objects_avs.json.gz , objects_ids.json.gz, or objects_vals.json.gz.

How to extract bubble files from Autodesk server?

The extract.autodesk.io server exercises and demonstrates the Autodesk Forge API authorization, translation, viewing processes mentioned in the Quick Start guide. It also demonstrates how to extract the ‘bubbles’ files from the Autodesk server for storing and viewing them locally.

What is model derivative API in Autodesk forge?

Model Derivative API enables users to represent and share their designs in different formats, as well as to extract valuable metadata Viewer (formerly part of the “View and Data API”) is a WebGL-based, JavaScript library for 3D and 2D model rendering

The JSON responses are easy to parse, and the endpoint can also be configured to only return properties of a single object with specific ID, making the requests faster and more efficient. However, before deciding to use this option in your application, consider the following characteristics of this endpoint:

How to render a model in Forge viewer?

Many industries use this viewer to render the model data in the browser but that needs the model data to be converted into SVF format (a generic format used by forge viewer to render the model data). 1. Create an App in Forge (Use this link to SignIn/Register https://forge.autodesk.com)

Where does the data for Forge viewer come from?

These 3D and 2D data may come from a wide variety of applications such as AutoCAD, Fusion 360, Revit or any other CAD application. Many industries use this viewer to render the model data in the browser but that needs the model data to be converted into SVF format (a generic format used by forge viewer to render the model data).

How to get model hierarchy from Forge cloud?

After the translating, the model hierarchy, DbId, and object properties are all managed in a specific database on Forge cloud. We can just request to get them in the Json format: 1. request to get metadata by https://developer.api.autodesk.com/modelderivative/v2/designdata/:urn/metadata.