My $.02... Either way is probably fine, but a fundamental is that the Metrics be vehicle-independent, and with one metric for each item (meaning that we don't have separate metrics for the same item with different precision). Otherwise, the use of the metrics becomes more challenging, and prone to error.

Greg

Mark Webb-Johnson wrote:

> a) I'd love to get rid of those km→miles→km conversions in V3.
> 
> How about introducing a metric "v.units" instead to hold the units used
> by the vehicle, and make conversions at the user level if necessary?

I don’t have a good answer for this. I thought to just store all the metrics in ‘metric’ (celcius, kilometers, etc), and let the apps deal with it (as they do now). But, as you say, that does lead to the problem of km->miles->km, etc.

An alternative is to store a ‘units’ with the metric, and have the metric deal with presentation conversion upon retrieval. That reduces the number of conversions.

In general, having this done in the module seems to make more sense than doing it in the apps.