Difference between revisions of "BRGINF"

From IHO Nautical Information Processing Working Group
Jump to navigation Jump to search
Line 29: Line 29:
 
|-  
 
|-  
 
|Cardinal Directions ||[[CARDIR]]||cardinalDirections||0..1||n/a
 
|Cardinal Directions ||[[CARDIR]]||cardinalDirections||0..1||n/a
|-
 
|Direction||[[??????]]||Direction||0..1||n/a
 
 
|-
 
|-
 
|Sector limit one||[[SECTR1]]||sectorLimitOne||0..1||n/a
 
|Sector limit one||[[SECTR1]]||sectorLimitOne||0..1||n/a
Line 41: Line 39:
 
|-
 
|-
 
|Information||[[INFORM]]||information||0..1||n/a
 
|Information||[[INFORM]]||information||0..1||n/a
|-
 
|Information of extension if fuzzy?????||[[???????]]||??????????||0..1||n/a
 
 
|}
 
|}
  

Revision as of 12:08, 9 April 2014

FEATURE OBJECT ATTRIBUTES


Attribute: Bearing Information

Acronym: BRGINF Code: ?

Camel case: bearingInformation

Attribute type: S


Definition:

A bearing is the direction one object is from another object.


Attribute type: Complex


SubAttributes:

Proposal ((((to be discussed and to be completed))))

Name AlphaCode CamelCase Multiplicity Sequential
Cardinal Directions CARDIR cardinalDirections 0..1 n/a
Sector limit one SECTR1 sectorLimitOne 0..1 n/a
Sector limit two SECTR2 sectorLimitTwo 0..1 n/a
Orientation ORIENT orientation 0..1 n/a
Distance TBD distance 0..1 n/a
Information INFORM information 0..1 n/a


Reference:



Remarks: INFORM should be used to specify "unknown directions"

Distinction:


Justification:
to be completed

Comments:

No comments.


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