Editing BCF - BIM Collaboration Format
From Wiki.OSArch
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
{{stub}} | {{stub}} | ||
{{buildingSMART International}} | {{buildingSMART International}} | ||
| − | |||
| − | The BIM Collaboration Format (BCF) is a technology by [[buildingSMART | + | The BIM Collaboration Format (BCF) is a technology by [[buildingSMART international]] to allow different BIM applications to communicate model-based issues with each other. Examples of issues may be model coordination problems, RFIs, or model clashes. As an open format, it allows many users to identify model problems in a variety of tools, bypassing proprietary formats and workflows. BCF specifies the metadata to be stored with each issue, as well as the rules on how the metadata may be edited and transferred. It is similar to a standardisation on how "bugtrackers" work in the software industry. The official terminology used for a model issue in BCF is called a "topic". A collection of BCF topics are stored in a BCF project. |
BCF is may be used together with [[Industry Foundation Classes (IFC)]] models that have been previously shared among project collaborators. However, although BCF contains metadata to aid in linking to aspects of an IFC model, BCF may be used with any model, including proprietary ones. Each BCF topic may include camera viewpoints of the relevant model problem, to allow the user to investigate the issue. It is also possible to use BCF without any 3D model at all, simply sharing topics with only image snapshots. | BCF is may be used together with [[Industry Foundation Classes (IFC)]] models that have been previously shared among project collaborators. However, although BCF contains metadata to aid in linking to aspects of an IFC model, BCF may be used with any model, including proprietary ones. Each BCF topic may include camera viewpoints of the relevant model problem, to allow the user to investigate the issue. It is also possible to use BCF without any 3D model at all, simply sharing topics with only image snapshots. | ||
| Line 17: | Line 16: | ||
BCF information may be transferred to other users in two ways. The BCF-XML specification allows users to transfer files with the <code>.bcf</code> extension to import and export a BCF project from different software. The BCF-API specification instead allows users software to connect directly to a BCF server to retrieve and update data in the BCF project. | BCF information may be transferred to other users in two ways. The BCF-XML specification allows users to transfer files with the <code>.bcf</code> extension to import and export a BCF project from different software. The BCF-API specification instead allows users software to connect directly to a BCF server to retrieve and update data in the BCF project. | ||
| − | + | Free Software with support for BIM Collaboration Format includes [[BCFier]], [[OpenProject]], [[BIMData]], [[BlenderBIM Add-on]] and the [[BCF-Plugin-FreeCAD]] to [[FreeCAD]]. For developers, [[IfcOpenShell]] contains a BCF module in Python, intended to supersede [[bcfplugin]], which was originally a fork of the FreeCAD BCF implementation with FreeCAD's GUI code removed. There is also a variety of commercial products with multi user server integration, some of them with free limited versions. | |
| − | Free Software with support for BIM Collaboration Format includes [[ | ||
==BCF Specification== | ==BCF Specification== | ||
| Line 35: | Line 33: | ||
The BCF-API specification describes how to transfer BCF project data by making REST HTTP calls to a central server. The BCF-API specification only describes client behaviour, and does not describe how the server implementation works. However, it does cover user authorisation. | The BCF-API specification describes how to transfer BCF project data by making REST HTTP calls to a central server. The BCF-API specification only describes client behaviour, and does not describe how the server implementation works. However, it does cover user authorisation. | ||
| − | |||
| − | |||
| − | |||
=See also= | =See also= | ||
* OSArch forum discussion: [https://community.osarch.org/discussion/485/adding-the-ability-to-the-bcf-libraries-to-connect-with-the-api Adding the ability to the BCF Libraries to connect with the API] | * OSArch forum discussion: [https://community.osarch.org/discussion/485/adding-the-ability-to-the-bcf-libraries-to-connect-with-the-api Adding the ability to the BCF Libraries to connect with the API] | ||
| − | |||
=External Resources= | =External Resources= | ||
| Line 47: | Line 41: | ||
[[Category:buildingSMART International]] | [[Category:buildingSMART International]] | ||
| − | |||
