# Various issues in Type Enums (IfcDistributionFlowElement and below)

**URL:** <https://forums.buildingsmart.org/t/various-issues-in-type-enums-ifcdistributionflowelement-and-below/1528>\
**Category:** Uncategorized\
**Tags:** ifc4, ifc4-errata\
**Created:** [June 21, 2019, 7:59am UTC](https://forums.buildingsmart.org/t/various-issues-in-type-enums-ifcdistributionflowelement-and-below/1528 "2019-06-21T07:59:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![B.Huijskes](https://avatars.discourse-cdn.com/v4/letter/b/8baadc/32.png) [@B.Huijskes](https://forums.buildingsmart.org/u/B.Huijskes)\
**Post date:** [June 21, 2019, 7:59am UTC](https://forums.buildingsmart.org/t/various-issues-in-type-enums-ifcdistributionflowelement-and-below/1528/1 "2019-06-21T07:59:50Z")

</div>

Hi there,

When going over the Type Enums for MEP components, I found the following issue:

The description for TUBEAXIAL (in IfcFanTypeEnum) underwent changes from [IFC4](http://www.buildingsmart-tech.org/ifc/IFC4/final/html/schema/ifchvacdomain/lexical/ifcfantypeenum.htm) to [IFC4ADD1](http://www.buildingsmart-tech.org/ifc/IFC4/Add1/html/schema/ifchvacdomain/lexical/ifcfantypeenum.htm), now being exactly equal to VANEAXIAL. This has been unchanged in [IFC4.2](https://standards.buildingsmart.org/IFC/DEV/IFC4_2/FINAL/HTML/schema/ifchvacdomain/lexical/ifcfantypeenum.htm).

Its description currently reads: “Air flows through the impeller axially with guide vanes and reduced running blade tip clearance.”. I believe this to be a simple copy mistake coming from VANEAXIAL.  
Could this be corrected in the coming IFC update?

PS: I’ll be going over many more Type Enums the coming weeks. Is the way I am currently reporting these issues correct, or can I report them elsewhere?

Kind regards,

Ben

---

<div class="post-metadata">

**Author:** ![sergej](https://avatars.discourse-cdn.com/v4/letter/s/bcef8e/32.png) [@sergej](https://forums.buildingsmart.org/u/sergej)\
**Post date:** [June 21, 2019, 9:26am UTC](https://forums.buildingsmart.org/t/various-issues-in-type-enums-ifcdistributionflowelement-and-below/1528/2 "2019-06-21T09:26:12Z")

</div>

Another option would be Github. But I think if you stick to one thread and just leave short replies to your original post, it should work out fine.

In Github you would have to comb over the IfcKit/Schemas folder and leave Pull requests on the XTypeEnum.cs files in the [Description] part. it is a bit more complicated if you have not used Github before.

---

<div class="post-metadata">

**Author:** ![B.Huijskes](https://avatars.discourse-cdn.com/v4/letter/b/8baadc/32.png) [@B.Huijskes](https://forums.buildingsmart.org/u/B.Huijskes)\
**Post date:** [June 21, 2019, 11:23am UTC](https://forums.buildingsmart.org/t/various-issues-in-type-enums-ifcdistributionflowelement-and-below/1528/3 "2019-06-21T11:23:44Z")

</div>

@sergej: Thank you for your advice. I’ll stick to the forum then, since I have posted similar issues here before. Will change the name of the post and continue to update as I find things.

Issues in descriptions:

- [IfcFireSuppressionTerminalTypeEnum](https://standards.buildingsmart.org/IFC/DEV/IFC4_2/FINAL/HTML/schema/ifcplumbingfireprotectiondomain/lexical/ifcfiresuppressionterminaltypeenum.htm) \>\>\> NOTDEFINED: **Underined** type. Typo present since [IFC4](http://www.buildingsmart-tech.org/ifc/IFC4/final/html/index.htm), not fixed yet.
- [IfcElectricFlowStorageDeviceTypeEnum](https://standards.buildingsmart.org/IFC/DEV/IFC4_2/FINAL/HTML/schema/ifcelectricaldomain/lexical/ifcelectricflowstoragedevicetypeenum.htm) \>\>\> INDUCTORBANK: no description whatsoever. Issue present since [IFC4Add1](http://www.buildingsmart-tech.org/ifc/IFC4/Add1/html/schema/ifcelectricaldomain/lexical/ifcelectricflowstoragedevicetypeenum.htm).
