Talk:VSLCAR

jens 13:02, 24 July 2010 (UTC) I'm really sure, that this list can be extended due to several reasons.

It is to be considered if we should add the units here. Only a given value makes no sense. (think about tons and long tons, metre vs foot etc.)

DavidAcland 15:50, 13 August 2010 (UTC)

I am tempted. Without units somewhere, we cannot use a flexible model like this when VSLCAR is an integer but for very different characteristics.

However we will get into trouble with draught and feet and metres; probably some others.

Could we have a unit attribute with values like:

metres, feet, tonnes, gross tonnage, net tonnage?

raphael 20:16, 13 August 2010 (UTC): I assume the dataset will have parameters that specify the units it uses for depths, etc., like HUNITS, DUNITS, and PUNITS in S-57. Maybe S-100 has something to say about this? In general I am somewhat reluctant to allow a dataset to specify units at a fine-grained level, I think it increases the chances of an encoding or programming error. But it is indeed tempting, especially in connection with long tons and gross tons and converting feet to metres. Let's think about this for a few days and see if there are compelling arguments for either alternative.