Autodesk / Autodesk/revit-ifc

Export with PsetMapping - Unwanted Unit Conversion Occurring

Open
#37 15 comments 0 reactions 0 assignees View on GitHub
parameters-properties Triage
Dominant language
C#
Stars
637
Forks
225
PR merge metrics
No merged PRs in 30d

Description

# Unwanted Unit Conversion Occurring
When exporting the type parameters using the property set mapping the NominalLength, NominalWidth and Nominal Height converts the values to feet, whilst the source attributes are written in millimeters as expected.
![settings](https://user-images.githubusercontent.com/26350009/45917716-9ed3d780-be73-11e8-9d38-d7a67155339c.PNG)

## Ifcxml
### Original Params in one part of the ifc (exporting the Revit Parameters as property sets)
![unitconvert2-mappedifcxml](https://user-images.githubusercontent.com/26350009/45917588-3d5f3900-be72-11e8-9ad9-5a7a301718b3.PNG)
### Mapped Params in another part of the ifc (exporting the Mapped Parameters using [ the IFC2x3 Extended FM HandOve View.txt ](https://github.com/Autodesk/revit-ifc/blob/master/Install/Program%20Files%20to%20Install/IFC2x3%20Extended%20FM%20HandOver%20View.txt#L14))
![unitconvertifcxml](https://user-images.githubusercontent.com/26350009/45917589-3d5f3900-be72-11e8-95b8-8e92e35d0c24.PNG)
## Ifc
At first I thought it was just ifcxml, but then checked the ifc output and the same appears there too.

### Original Params in one part of the ifc (exporting the Revit Parameters as property sets)
![unitconvert2-mappedifc](https://user-images.githubusercontent.com/26350009/45917590-3d5f3900-be72-11e8-846c-26b04df203c5.PNG)
### Mapped Params in another part of the ifc (exporting the Mapped Parameters using [ the IFC2x3 Extended FM HandOve View.txt ](https://github.com/Autodesk/revit-ifc/blob/master/Install/Program%20Files%20to%20Install/IFC2x3%20Extended%20FM%20HandOver%20View.txt#L14))
![unitconvertifc](https://user-images.githubusercontent.com/26350009/45917591-3d5f3900-be72-11e8-892a-40a53acec552.PNG)

Contributor guide

Open the contributing guide

Research direction

Start with the IFC2x3 Extended FM HandOver View mapping file linked in the issue and trace how its mapped NominalLength, NominalWidth, and NominalHeight values are exported compared with the source property-set values. Reproduce the issue in both IFC and IFCXML output; done means mapped values retain the expected millimeter units without unwanted conversion.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.