Difference between revisions of "MicroMVDs for exchange requirements/Model federation MicroMVD"

From Wiki.OSArch
(Created page with "The following MicroMVD vocabulary can be used to ensure IFC elements belong to the correct IFC class. <pre> Feature: Model feder...")
(No difference)

Revision as of 07:55, 28 July 2020

The following MicroMVD vocabulary can be used to ensure IFC elements belong to the correct IFC class.

Feature: Model federation

In order to coordinate multiple models that are produced separately
For all model coordinators and recipients of the final built environment
The location of each model's origin point must be specifically set to a coordinated value

Scenario: Receiving a file
 * The IFC file "{file}" must be provided
 * IFC data must use the {schema} schema

Scenario: Ensure that an agreed datum for the project is in the right location
 * There is a datum element {guid} as an {ifc_class}
 * The element {guid} has a global easting, northing, and elevation of {number}, {number}, and {number} respectively
 * The element {guid} has a local X, Y, and Z coordinate of {number}, {number}, and {number} respectively

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.
{guid} 28q3AgmxP5cepIweO5Of$o This is a 22 character GlobalId for a particular IFC element.
{ifc_class} IfcSite This case insensitive text value must correspond to the full name of an IFC class. It is recommended for the purposes of this MicroMVD that this should be an IfcSite, or IfcBuilding, or other spatial element that all other objects are related to.
{number} 42 Any valid number. Note that eastings, northings, and elevations, are not angular measures, such as latitude and longitude, but are instead based on a coordinate reference system.