Editing MicroMVDs for exchange requirements/Classification MicroMVD

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 9: Line 9:
 
As someone who needs to catalogue BIM data in a structured and organised manner
 
As someone who needs to catalogue BIM data in a structured and organised manner
 
Classification systems data must be assigned to each relevant element
 
Classification systems data must be assigned to each relevant element
 +
 +
Scenario: Receiving a file
 +
* The IFC file "{file}" must be provided
 +
* IFC data must use the {schema} schema
  
 
Scenario: The appropriate classification systems are referenced in the model
 
Scenario: The appropriate classification systems are referenced in the model
  * The classification "{name}" must be used
+
  * The classification {guid} specifies the system {name}
  * The classification "{name}" is published by "{source}"
+
  * The classification {guid} is published by {source}
  * The classification "{name}" is the edition "{edition}" on "{edition_date}"
+
  * The classification {guid} is the edition {edition} on {edition_date}
  * The classification "{name}" has the description "{description}"
+
  * The classification {guid} has the description "{description}"
  * The classification "{name}" is referenced by the website "{location}"
+
  * The classification {guid} is referenced by the website {location}
  * The classification "{name}" has a hierarchy denoted by the tokens "{tokens}"
+
  * The classification {guid} has a hierarchy denoted by the tokens {tokens}
  
 
Scenario: The relevant elements are assigned to the classification system
 
Scenario: The relevant elements are assigned to the classification system
  * The element "{guid}" is classified as a "{identification}" with name "{reference_name}"
+
  * The element {guid} is classified as a "{identification}" with name "{reference_name}"
</pre>
 
 
 
Note that for IFC2X3, the following rules will not apply, as the data cannot be stored in IFC2X3.
 
 
 
<pre>
 
* The classification "{name}" has the description "{description}"
 
* The classification "{name}" is referenced by the website "{location}"
 
* The classification "{name}" has a hierarchy denoted by the tokens "{tokens}"
 
 
</pre>
 
</pre>
  
Line 36: Line 32:
 
! Example
 
! Example
 
! Description
 
! Description
 +
|-
 +
| <code>{file}</code>
 +
| project.ifc
 +
| The filename or path to any IFC file.
 +
|-
 +
| <code>{schema}</code>
 +
| IFC4
 +
| The schema version. At the moment, these are likely to be either IFC4 or IFC2X3.
 
|-
 
|-
 
| <code>{guid}</code>
 
| <code>{guid}</code>
Line 66: Line 70:
 
|-
 
|-
 
| <code>{tokens}</code>
 
| <code>{tokens}</code>
| ["_"]
+
| '_'
| A JSON list of of all of the separating tokens which denote hierarchy in the classification system, taken from the standard list if it exists.
+
| A comma separated, single quoted list of all of the separating tokens which denote hierarchy in the classification system, taken from the standard list if it exists.
 
|-
 
|-
 
| <code>{identification}</code>
 
| <code>{identification}</code>
Line 77: Line 81:
 
| A single classification reference name for the particular classification system, taken from the standard list if it exists.
 
| A single classification reference name for the particular classification system, taken from the standard list if it exists.
 
|}
 
|}
 
 
=Software guides=
 
 
{| class="wikitable"
 
!rowspan="2"|Icon
 
!rowspan="2"|Software
 
!colspan="2"|Certified Version
 
!rowspan="2"|Notes
 
!rowspan="2"|Guides
 
|-
 
! Import
 
! Export
 
|-
 
| [[File:Icon ArchiCAD.jpg|64x64px]]
 
| ArchiCAD
 
|
 
| style="background-color: #ffd37f;" | ArchiCAD 23
 
| Some work is required to set up the export, but it is possible. However, the description, location, and reference tokens for the <code>IfcClassification</code> cannot be exported. It should also be noted that the Graphisoft classification XMLs tend to store the location data in the source field, which is incorrect.
 
|
 
|-
 
| [[File:BlenderBIM_Addon_logo.png|64x64px]]
 
| [[BlenderBIM Add-on]]
 
| style="background-color: #b6cca1;" | v0.0.200829
 
| style="background-color: #b6cca1;" | v0.0.200829
 
|
 
|
 
|-
 
| [[File:icon_FreeCAD.png]]
 
| [[FreeCAD]]
 
|
 
|
 
|
 
|
 
|-
 
| [[File:Icon Revit.png|64x64px]]
 
| [[Autodesk Revit|Revit]]
 
|
 
|
 
|
 
|
 
|-
 
| [[File:Tekla-logo.png|64x64px]]
 
| [[Tekla]]
 
|
 
|
 
|
 
|
 
|}
 
 
[[Category:BIMTester]] [[Category:Model View Definitions (MVD)]] [[Category:MicroMVD]]
 

Please note that all contributions to Wiki.OSArch are considered to be released under the Creative Commons Attribution-ShareAlike (see Wiki.OSArch:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)