Reputation: 156
This question is connected another issue which I've posted before here: Inconsistent data.
When models are uploaded with SVF2
format, Model Derivative brings wrong data like (IfcGUID on externalId field or names on externalId field instead of real external id)
or msising data like (names without [Revit ID], missing properties)
. But from viewer with SELECTION_CHANGED_EVENT
right data and structure can be seen without any issue.
When the models are uploaded with older version SVF
format there are no problems.
What could be the real issue here, should we not use SVF2
yet ?
Upvotes: 0
Views: 231
Reputation: 439
Actually I don't think it's "wrong datas". With SVF2, the metadata endpoint will provide SVF2 data according to this SVF2 Metadata
So I guess it's normal you have some differences between your SVF and SVF2 data.
For the viewer part, I know you can change some parameters to specify whether you're working with SVF or SVF2 : Viewer initializer options
Hope it will help
Upvotes: 1