MicroMVDs for exchange requirements/Geometric detail MicroMVD

From Wiki.OSArch
< MicroMVDs for exchange requirements
Revision as of 21:52, 8 September 2020 by Moult (talk | contribs) (Created page with "The following MicroMVD vocabulary can be used to ensure classification system standards are correctly applied. <pre> Feature: Ge...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The following MicroMVD vocabulary can be used to ensure classification system standards are correctly applied.

Feature: Geometric detail

To allow for the efficient transfer of geometry
For any stakeholder using 3D geometry
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
 * All elements must be under {number} polygons

You can fill out the variables using the guide below.

Variable Example Description
{file} project.ifc The filename or path to any IFC file.
{schema} IFC4 The schema version. At the moment, these are likely to be either IFC4 or IFC2X3.
{number} 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.