Difference between revisions of "VSLMSM"

From IHO Nautical Information Processing Working Group
Jump to navigation Jump to search
m
(One intermediate revision by the same user not shown)
Line 1: Line 1:
EATURE OBJECT ATTRIBUTES
+
FEATURE OBJECT ATTRIBUTES
  
  
Line 27: Line 27:
 
|-
 
|-
 
|}
 
|}
 +
 +
 +
 +
 +
  
  

Revision as of 05:59, 16 August 2010

FEATURE OBJECT ATTRIBUTES


Attribute: vessel's measurements

Acronym: VSLMSM Code:

Camel case: vesselsMeasurements

Attribute type: Complex


Definition:

Multitude of terms and definitions specifically related to ships. (http://en.wikipedia.org; 24 July 2010)


Sub-attribute Camel Code Identifier Multiplicity Sequential
VSLCAR vesselsCharacteristics 0..* True
VSLVAL vesselsCharacteristicsValue 0..* True
COMPOP ComparisonOperator 0..* True










VSLVAL was been set to INTEGER assuming using 3 decimal like 10.000 m.

That would give the result:
1. VSLCAR=draught; VSLVAL=10500; COMPOP=(>=) the regulation applies for vsl of 10.5 m draught and above
2. VSLCAR=DWT; VSLVAL=200000; COMPOP=(=) the regulation applies for vsl of exactly 2000 DWT
3. VSLCAR=length; VSLVAL=15000; COMPOP=(<) the regulation applies for vsl of less than 150 m length

Using a further example
[VSLMSM [VSLCAR=length; VSLVAL=50000; COMPOP=(>)]], CATVSL=3 (tanker), LOGCON=1 (and), LIMTYP=2 (required); associated to a PILBOP object: tankers with LOA > 50.0 m must use the PILBOP

If the example should work for tanker between 50 and 100 m length the coding is like this
[VSLMSM [VSLCAR=length; VSLVAL=50000; COMPOP=(>)], [VSLCAR=length; VSLVAL=100000; COMPOP=(<)]], CATVSL=3 (tanker), LOGCON=1 (and), LIMTYP=2 (required); associated to a PILBOP object: tankers with LOA > 50.0 m and < 100.0 m must use the PILBOP




David Raphael others Jens
DA Y/N RMM Y/N others Y/N JSF Y/N