You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, filip is closely to the UNECE unit model. However, depending on the system requirements one want to add other unit standard,e.g., QUDT or BACNET.
Integrate diffrent unit models depending on QUDT or BACnet and parse them based on their type definition, e.g. qudt:unit, bacnet:unit, unece:unit. We can make the default unit-type configurable via filip settings. I would stick to the unece as default as this is what the fiware community proposes. @SBlechmann is this correct?
Prepare a way to define CustomUnits, e.g. by defining an import path using filip settings
Describe alternatives you've considered
Stay with the current
@tstorek Sorry for the late response. I think it's a good idea to support another unit's standards. However, I'm skeptical about integrating the unit framework pint. In my opinion, we should at most provide an example of how to use this library.
Is your feature request related to a problem? Please describe.
Currently, filip is closely to the UNECE unit model. However, depending on the system requirements one want to add other unit standard,e.g., QUDT or BACNET.
Describe the solution you'd like
qudt:unit
,bacnet:unit
,unece:unit
. We can make the defaultunit
-type configurable via filip settings. I would stick to theunece
as default as this is what the fiware community proposes. @SBlechmann is this correct?Describe alternatives you've considered
Stay with the current
Additional context
For future work this might be kind of relevant, e.g. when integrating with frameworks as https://pint.readthedocs.io/en/stable/
Also related to #186
The text was updated successfully, but these errors were encountered: