Dimensions tables should handle ranges

[MattiasSealander]

Currently tables like "tbl_sample_dimensions" use numerical fields, which limits the values they can store. Dimension types includes both estimated and measured. However, due to the numerical field restriction it is not possible to store an estimated range (e.g. estimated tree height between 15-25 meters).

Should the way dimensions are stored be opened up to be more flexible? The dendro data for living trees includes tree height as metadata, and it is a type of dimension. But, these estimated ranges of values must currently be stored as tbl_sample_descriptions due to them not being possible to store in tbl_sample_dimensions.

One possible way to manage it would be to add dimension types to tbl_dimensions with upper and lower limit of estimated range values.

[visead]

Perhaps something for a new data type that Roger mentioned? Ranges type, or is there a type with built in function for error margins?