CODEWITHSUNDEEP
autodesk-forgeautodesk-model-derivative
Robin999
Robin999

Reputation: 11

IFC less object properties in model derivative translation compared to when translated in ACC

If I use my own Forge Viewer program which takes an IFC file as input and displays it in Viewer, I get properties like this for an object.

However, if I instead download the same model to our Autodesk Construction Cloud hub, I get properties like this.

So in other words, by using the viewer in ACC, I get much more properties which is exactly what I want. Would it be possible to get these same properties when using the model derivative API? How would I do this?

Upvotes: 1

Views: 148

Answers (1)

Eason Kang
Eason Kang

Reputation: 7070

It looks like you used the legacy IFC conversion method.

To get the same result as Autodesk Docs(a.k.a. ACC Docs), you must specify the conversion method to either modern or v3.

curl --location --request POST 'https://developer.api.autodesk.com/modelderivative/v2/designdata/job' \
--header 'Authorization: Bearer ' \
--header 'Content-Type: application/json' \
--header 'x-ads-force: true' \
--data-raw '{
    "input": {
        "urn": ""
    },
    "output": {
        "formats": [
            {
                "type": "svf",
                "views": [
                    "3d"
                ],
                "advanced": {
                    "conversionMethod": "v3" // or change it to modern
                }
            }
        ]
    }
}'

The main difference between modern and v3, as I know, is that the modern one uses feet as the length unit always. But on the other hand, the v3 method uses IFC file native length unit. So, choosing either of them depends on your use case.

ref: https://forge.autodesk.com/en/docs/model-derivative/v2/reference/http/job-POST/#body-structure

Upvotes: 1

Related Questions