Difference between revisions of "Talk:BRGINF"
| Line 8: | Line 8: | ||
[[User:Jens|jens]] 18:45, 20 February 2012 (UTC) started to develop a coplex attribute; SECTR1 and SECTR2 are S57 attributes. It is to check whether they can replace the direction attribute proposal at the table | [[User:Jens|jens]] 18:45, 20 February 2012 (UTC) started to develop a coplex attribute; SECTR1 and SECTR2 are S57 attributes. It is to check whether they can replace the direction attribute proposal at the table | ||
| + | |||
| + | [[User:Rmm|raphael]] 01:50, 21 February 2012 (UTC): The S57 attribute ORIENT is an additional possibility. | ||
Revision as of 01:50, 21 February 2012
jens 11:32, 28 July 2011 (UTC)
However it will look, it should be a string. Although it is very tempting to say it can be numeric like 256 (degrees), I checked several image title saying "in xx bearing" others say "from xx". Both is opposite. It seems to be also impossible to specify what kind of bearing it will be; in SW or from SW or something else. So, string is fine, I guess.
jens 15:39, 19 February 2012 (UTC)Folllowing dicussion came up at SNPWG14. Bearing information stored ar string can not sufficiently accessed by software. Better would be to provide more options; e.g. degrees, cardinal directions, sector and strings. The cardinal directions should be coded in 16 values.
Is it feasable to replace the current string by a complex attribute which allows access to several options if applicable?
Meantime I have developed an attribute for the cardinal directions CARDIR.
It was further agreed that the direction should be given from the observer's point.
jens 18:45, 20 February 2012 (UTC) started to develop a coplex attribute; SECTR1 and SECTR2 are S57 attributes. It is to check whether they can replace the direction attribute proposal at the table
raphael 01:50, 21 February 2012 (UTC): The S57 attribute ORIENT is an additional possibility.