# Imperial/Metric conversion: Where do you put your single source of truth? **URL:** \ **Category:** Ignition\ **Created:** [January 15, 2026, 12:49pm UTC](https://forum.inductiveautomation.com/t/imperial-metric-conversion-where-do-you-put-your-single-source-of-truth/113313 "2026-01-15T12:49:17Z")\ **Posts on this page:** 1\ **Showing post:** 28
**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\ **Post date:** [January 17, 2026, 7:59pm UTC](https://forum.inductiveautomation.com/t/imperial-metric-conversion-where-do-you-put-your-single-source-of-truth/113313/28 "2026-01-17T19:59:30Z")
Linking a previous post: > [@Numeric entry with unit conversion (bidirectional) question](https://forum.inductiveautomation.com/t/numeric-entry-with-unit-conversion-bidirectional-question/113027/9): > > Regarding "bind a custom property to engUnit on the tag" above, the goal would be to allow conversion from any unit to another of the operator's choosing. The conversion would be a two-step process, but straightforward. Ex: "R" --\> "degF" --\> "degC" (where 'degF' is selected as your 'standard' for temperature conversion). Consider building a table (as a tag and/or session prop?) which contains everything needed for any unit conversion to another. Something resembling: Units Type Factor Offs… The expression transform will be more performant. The dataset should be very maintainable, straightforward to update and maintain….no scripting required. --- _[View the full topic](https://forum.inductiveautomation.com/t/imperial-metric-conversion-where-do-you-put-your-single-source-of-truth/113313)._