Enable IFC Export from Updated Fragments

[MiguelG97]

Description 📝

As requested by users, the library should support exporting updated fragments as IFC, so that changes made to properties, property sets, or element edits can be saved back to an IFC file for interoperability with other tools.

Constraints:

• The IFC export should support basic schemas and Model View Definitions (MVDs):
  IFC Schema:
  IFC4x3
  MVD:
  Reference View
  Alignment Based View

Suggested solution 💡

No response

Alternative ⛕

No response

Additional context ☝️

No response

Validations ✅

• Read the docs.
• Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.

[agviegas]

I've looked into this. We are already able to export IFC files using web-ifc.

What people expect (a one-liner function that prevents roundtripping from fragments to IFC) would be next to impossible, because I'm anticipating people won't just want any IFC; they'll want an IFC with the flavour that their BIM application of choice can read. So as soon as we decide our "IFC flavour", there will be many issues complaining about "our IFC" not being compatible with "X app", even if it follows the schema.

Given the huge amount of work, the specifity of the export each dev can expect and our limited resources, we won't pursue this for now. Here's an answer taht should throw some light on exporting IFC files. Anyone should be able to write their own exporter with our libraries already.

Cheers!