Discussions on golf courses

this is no longer called 'golf facility' as i have changed it to 'golf club.'

Because golfers in different countries use different units of measurement.

You might want to consider the "User defined length" type in my Summary Statistics base (or something like it) for this property. In your case, where there are only two options(?) it might not be that big a deal. However, you will need to convert values AND consolidate columns if you ever want to make comparisons among groups of golf courses with instances that are described differently. That kind of query would be simpler if all the values were in the same column.

Clarification: by "column" I meant "property".

In most properties that use a measurement unit, and that can reasonably expect values to exist in different units, the convention is to use the metric unit, and expect users to be able to do the conversion at input.  With two properties, users will have to do a lot of math in order to, say, create a list of courses over (or under) a certain length. Whereas, with a single property, all they have to do is sort one column.

since there are only two real world units (meters and yards) for golf courses, i think this base will be significantly more usable if we do not ask users to convert yards to meters.  i agree that this will limit the abilty to make comparisons (or at least it will make performing them more complex), but i think this is a small price to pay for the enhanced usability of offering both units of measurement.