Difference between revisions of "VSLMSM"
| Line 29: | Line 29: | ||
|- | |- | ||
|} | |} | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
Remarks: | Remarks: | ||
Revision as of 11:15, 20 June 2011
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 vessels. (http://en.wikipedia.org; 24 July 2010)
| Sub-attribute | Camel Code Identifier | Multiplicity | Sequential |
|---|---|---|---|
| VSLCAR | vesselsCharacteristics | 1 | n/a |
| VSLVAL | vesselsCharacteristicsValue | 1 | n/a |
| VSLUNT | vesselsCharacteristicsUnit | 1 | n/a |
| COMPOP | ComparisonOperator | 1 | n/a |
Remarks:
Distinction:
Justification:
to be completed
Comments:
VSLVAL has been set to REAL assuming 3 decimal places, i.e.: 10.000 m.
That would give the result:
1. VSLMSM [VSLCAR=4 (draught); VSLVAL=10.5; VSLUNT=1 (m); COMPOP=2 (>=) ] the regulation applies for vsl of 10.5 m draught and above
2. VSLMSM [VSLCAR=9 (deadweight); VSLVAL=2000; VSLUNT=4 (ton); COMPOP=5 (=) ] the regulation applies for vsl of exactly 2000 DWT
3. VSLMSM [VSLCAR=1 (L.O.A.); VSLVAL=150; VSLUNT=1 (m); COMPOP=3 (<)] the regulation applies for vsl of less than 150 m length
Using a further example:
4. [VSLMSM [VSLCAR=1 (L.O.A.); VSLVAL=50; VSLUNT=1 (m); COMPOP=1 (>)]], CATVSL=3 (tanker), LOGCON=1 (and), LIMTYP=2 (required); associated to a PILBOP object: tankers with LOA > 50.0 m must use the PILBOP
In an example for tankers between 50 and 100 m in length, the coding is like this:
5. [VSLMSM [VSLCAR=1 (L.O.A.); VSLVAL=50; VSLUNT=1 (m); COMPOP=1 (>)], [VSLCAR=1 (L.O.A.); VSLVAL=100; VSLUNT=1 (m); COMPOP=3 (<)]], 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 |
|---|---|---|---|
| Y | RMM Y/N | others Y/N | Y |