QK for IfcCompoundPlaneAngleMeasure - plane angle measured in degrees, minutes and seconds?

[fkleedorfer]

I am considering mapping a IfcCompoundPlaneAngleMeasure to QUDT.

So far, mapping QUDT quantityKinds to IFC measures has worked pretty well, but in this case, the IFC measure is about the representation of the measurement rather than about how it is obtained (IFC has a IfcPlaneAngleMeasure).

The IFC specification is a 4-tuple of integer numbers (degrees, minutes, seconds, millionths of second).

I would like to know how one would represent such a value in QUDT (lesser priority though), and whether it would be permissible to add this quantitykind (qk:CompoundPlaneAngleMeasure)- if not for any other use than making a 1:1 mapping between QUDT and IFC a bit more feasible. (higher priority)

BTW, I have no ideas yet on how to integrate this with the conversionFactor/offset system. Interested in opinions as well.

[jhodgesatmb]

Measurements, sensors, and actuators are best handled by SOSA. In our EPIC project we build bridges between QUDT and SOSA and SOSA to IFC. I may be mistaken as I have constructed many bridge ontologies. I’ll look them up and send a diagram.The long and short of it is that if an ontology is purely about units and quantities we have suggested a mapping/harmonization, if it is a taxonomy we have suggested a cross reference, and if it is a domain we have suggested a bridge. Perhaps it is just my recommendation but I am a believer that ontologies should stand on their own and be integrated pairwise with other ontologies to increase and simplify interoperability

[fkleedorfer]

I think am trying to see if/how such a composite quantity is inherently implied by QUDT. unit:DEG, unit:ARCMIN, unit:ARCSEC are already in QUDT. A number of units/quantitykinds seem to have complex numbers as their range of values. These would be two-dimensional (right?). So, maybe we are already - without making it explicit in the model. In that case, we could think about how to specify the value range of this composite angle and even its conversion to other plane angle units - without having to resort to other ontologies.

[jhodgesatmb]

The QUDT data types model already supports tuples and, as a specialization, complex numbers (real part and imaginary part). I do not believe that quantity values are allowed to be complex but I haven’t checked.