# Proposal to make IfcMaterialProfileSetUsage IfcCardinalPointReference an enum

**URL:** <https://forums.buildingsmart.org/t/proposal-to-make-ifcmaterialprofilesetusage-ifccardinalpointreference-an-enum/3717>\
**Category:** Developers\
**Created:** [June 9, 2021, 2:23am UTC](https://forums.buildingsmart.org/t/proposal-to-make-ifcmaterialprofilesetusage-ifccardinalpointreference-an-enum/3717 "2021-06-09T02:23:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Moult](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.buildingsmart.org/moult/32/196_2.png) [@Moult](https://forums.buildingsmart.org/u/Moult)\
**Post date:** [June 9, 2021, 2:23am UTC](https://forums.buildingsmart.org/t/proposal-to-make-ifcmaterialprofilesetusage-ifccardinalpointreference-an-enum/3717/1 "2021-06-09T02:23:26Z")

</div>

Currently `IfcMaterialProfileSetUsage` has a `CardinalPoint` attribute with a data type of `IfcCardinalPointReference`. This data type serves only to define a positive integer, and the only definitions are recorded in the documentation.

I propose to change this to an enumeration, which makes more sense than 1-19 “magic” numbers which need to be recorded by implementers which have a risk of creating errors.

---

<div class="post-metadata">

**Author:** ![Jesusbill](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.buildingsmart.org/jesusbill/32/1122_2.png) [@Jesusbill](https://forums.buildingsmart.org/u/Jesusbill)\
**Post date:** [June 9, 2021, 2:25am UTC](https://forums.buildingsmart.org/t/proposal-to-make-ifcmaterialprofilesetusage-ifccardinalpointreference-an-enum/3717/2 "2021-06-09T02:25:13Z")

</div>

Definitely agree with this proposal