Hi. In our data models, we typically have a few attributes that contain only a sinlge float. Say, the “installedCapacity” of a power plant. It would be useful to have this float be a “float with unit” type - preferably connected to the unit catalog for simple conversion.
I assume that right now we’ll have to define the “float with unit” as our own custom type, but would be a good idea to have this value type come as a standard type?
Hi Kristian!
Thank you for suggesting this product idea. We will follow the traction this idea gets in the community. You can expect updates on this post if decide to include this in our future roadmap, or if we require more information.
- Marius
Hi Kristian,
I'm happy to inform you that you can already associate float properties with specific units from the unit catalog within CDF data models. This is achieved during the creation or update of a container. When you create a view that maps a unit-aware property from a container, it will inherit the unit. Consequently, once you populate the container with data, querying the view or container will yield unit-aware data.
For more information on how units work in time series and data models, you can refer to our developer documentation here: Unit Management in Data Models.
Feel free to reach out if you have any more questions on this topic.
Thanks
We’re currently using “neat” define and develop our data models. Do you know if neat supports configuring unit-aware properties?
Unfortunately, neat does not support this feature yet. I shared this limitation with the development team, and it was captured in their backlog.
Hi Kristian, we will look into this shortly.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.