Editing MicroMVDs for exchange requirements/Geometric detail 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 7: Line 7:
 
For any stakeholder using 3D geometry
 
For any stakeholder using 3D geometry
 
Geometry shall use the appropriate modeling techniques
 
Geometry shall use the appropriate modeling techniques
 +
 +
Scenario: Receiving a file
 +
* The IFC file "{file}" must be provided
 +
* IFC data must use the {schema} schema
  
 
Scenario: Geometry must be efficiently modeled
 
Scenario: Geometry must be efficiently modeled
  * All elements must be under "{number}" polygons
+
  * All elements must be under {number} polygons
 
</pre>
 
</pre>
  
Line 18: Line 22:
 
! 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>{number}</code>
 
| <code>{number}</code>
 
| 500
 
| 500
 
| Given that the vast majority of objects in AEC are box-like or cylindrical, most objects should not be above 500 polygons. For context, a single box is 6 polygons, and a cylinder, depending on its size, may be faceted into 18 polygons. However, many proprietary AEC applications have poor mesh support and may inefficiently translate geometry into a large number of polygons without the users intention.
 
| Given that the vast majority of objects in AEC are box-like or cylindrical, most objects should not be above 500 polygons. For context, a single box is 6 polygons, and a cylinder, depending on its size, may be faceted into 18 polygons. However, many proprietary AEC applications have poor mesh support and may inefficiently translate geometry into a large number of polygons without the users intention.
|}
 
 
=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
 
| N/A
 
| style="background-color: #b6cca1;" | ArchiCAD 23
 
|
 
|
 
|-
 
| [[File:BlenderBIM_Addon_logo.png|64x64px]]
 
| [[BlenderBIM Add-on]]
 
| N/A
 
| style="background-color: #b6cca1;" | v0.0.200829
 
|
 
|
 
|-
 
| [[File:icon_FreeCAD.png]]
 
| [[FreeCAD]]
 
| N/A
 
| style="background-color: #b6cca1;" | 0.19pre
 
|
 
|
 
|-
 
| [[File:Icon Revit.png|64x64px]]
 
| [[Autodesk Revit|Revit]]
 
| N/A
 
| style="background-color: #fbb4a8;" | Revit 2020.2 IFC 8/5/2020
 
| Due to the lack of control in geometry export in Revit, and due to the serious bugs resulting in extreme filesize bloat during export, Revit is considered to have failed this MicroMVD in practice.
 
| Refer to [[Revit and IFC Geometry]]
 
|-
 
| [[File:Tekla-logo.png|64x64px]]
 
| [[Tekla]]
 
|
 
|
 
|
 
|
 
 
|}
 
|}
  
 
[[Category:BIMTester]] [[Category:Model View Definitions (MVD)]] [[Category:MicroMVD]]
 
[[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)