英文:
Model Derivatives API: translate to svf2 error 406 "SVF2 is not supported for this design."
问题
我们正在将文件上传到BIM 360，并尝试使用SVF2格式，但似乎我们的派生仅生成SVF格式。我们尝试手动启动翻译作业，使用以下端点：
https://developer.api.autodesk.com/modelderivative/v2/designdata/job
并使用以下参数：
{
"input": {
"urn": [REDACTED],
"compressedUrn": true,
"rootFilename": "testModel.nwc"
},
"output": {
"destination": {
"region": "us"
},
"formats": [
{
"type": "svf2",
"views": [
"2d",
"3d"
]
}
]
}
}
我们收到了一个错误响应 '406'
{"diagnostic":"此设计不支持SVF2。"}
有什么想法？
英文:
We are uploading files to BIM 360 and trying to utilize the SVF2 format but it appears our derivatives are only generating SVF formats. We tried manually starting a translation job using this endpoint:
https://developer.api.autodesk.com/modelderivative/v2/designdata/job
with these parameters:
{
"input": {
"urn": [REDACTED],
"compressedUrn": true,
"rootFilename": "testModel.nwc"
},
"output": {
"destination": {
"region": "us"
},
"formats": [
{
"type": "svf2",
"views": [
"2d",
"3d"
]
}
]
}
}
We are receiving an error response '406'
> {"diagnostic":"SVF2 is not supported for this design."}
Any Ideas?
答案1
得分: 0
根据Eason的反馈，我们意识到翻译是自动进行的，无需手动触发。
我们之前认为翻译不会自动进行，因为model.IsSVF2()返回false，但当我们尝试model.isOTG()时，它实际上返回true。
英文:
Based on the feedback from Eason, we realized the translation was happening automatically and there is no need to trigger it manually.
We didn't think it was happening because model.IsSVF2() was returning false, but when we tried model.isOTG() it was in fact returning true.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论