Unit of pset/qset values out of scope for Reference View, why?

We posted this thread on b-Cert:
https://b-cert.org/Discussion/Sections/29670a46-a1e8-426f-542c-08d4c87c74c1/Forums/9edb9460-d7bd-4c0d-090e-08d4c87cb4b9/Threads/98e14aa1-af7c-4db9-ee86-08d74bec36e7
But we should rather take the case here.

As I see it, if it should be up to software to present whatever unit it sees fit, regardless of what unit is set in the ifc file, then why use units at all in Reference View ifc files? Then we might as well just say that all RV files must be in default SI units.

The problem is that when we export a cable with a cross sectional area of 1.5 mm², and the file’s area unit is m², then the value becomes 0.0000015 m². This shows as 0 m² in most software, including Solibri.

One of the points with RV is that viewers should be able to present the contents without too much specific expertise into each discipline. Is it really meant that each software has to know about all attributes of all psets/qset in order to present them with reasonable units?

2 Likes