Add support for IFC4 export with textures as entities IfcBlobTexture, IfcPixelTexture or IfcImageTexture. This would allow to deliver results in IFC even if yet not all IFC viewers/editors can handle textures.
See how these examples work with latest free FZKViewer.
| How frequently will feature be used? | Once a month or longer |
| How much time will you save? | N/A |
| Other Industry | BIM |
If you are waiting for votes then you will have wait for one eternity.
This is very specific request of which users are yet unaware because of previous IFC issues.
The IFC2x3 version of the schema contains a notable flaw, which is addressed in version IFC4. The main attribute IfcBlobTexture.RasterCode had been wrongfully declared to be of type boolean, rather than binary, rendering it unable to comprehend any meaningful bitmap data.
If Bentley waits for BIM industry to correct such mistakes then it will be behind industry. Also if i-model allows to embed textures then need option to keep them exporting to IFC.
Hi Oto, Thank you for your valuable idea. We are waiting for more votes on this issue.