- Recent changes [de-DE]

Talk:BRGINF

2012-05-16T08:24:20Z

←Older revision		Revision as of 08:24, 16 May 2012
Line 2:		Line 2:
	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.		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.

-	[[User:Jens\|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.	+	[[User:Jens\|jens]] 15:39, 19 February 2012 (UTC) Following dicussion came up at SNPWG14. Bearing information stored as string cannot be 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.
	<br>Is it feasable to replace the current string by a complex attribute which allows access to several options if applicable?		<br>Is it feasable to replace the current string by a complex attribute which allows access to several options if applicable?
	<br>Meantime I have developed an attribute for the cardinal directions [[CARDIR]].		<br>Meantime I have developed an attribute for the cardinal directions [[CARDIR]].
	<br>It was further agreed that the direction should be given from the observer's point.		<br>It was further agreed that the direction should be given from the observer's point.

-	[[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 complex 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.		[[User:Rmm\|raphael]] 01:50, 21 February 2012 (UTC): The S57 attribute ORIENT is an additional possibility.

	[[User:Jens\|jens]] 09:25, 22 February 2012 (UTC) Thanks Rapahel, ORIENT is incorporated.		[[User:Jens\|jens]] 09:25, 22 February 2012 (UTC) Thanks Rapahel, ORIENT is incorporated.

SNPWG

2012-05-16T08:13:18Z

←Older revision		Revision as of 08:13, 16 May 2012
Line 288:		Line 288:
	[[FIXDAT]] <span style="color:blue;">Fixed date</span>		[[FIXDAT]] <span style="color:blue;">Fixed date</span>

-	[[FIXTIM]] <span style="color:~~black~~;">Fixed time</span>	+	[[FIXTIM]] <span style="color:blue;">Fixed time</span>

	[[FRQRXV]] <span style="color:blue;">Frequency shore station receives</span>		[[FRQRXV]] <span style="color:blue;">Frequency shore station receives</span>

SLCONS

2012-05-16T07:52:10Z

←Older revision		Revision as of 07:52, 16 May 2012
Line 47:		Line 47:

	{\| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"		{\| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"
-	!David~~!!Ricardo!!Rolando~~!!Jens	+	!David!!Jens
	\|- style="background:white; color:black"		\|- style="background:white; color:black"
	\|Y		\|Y
-	~~\|RF Y/N~~
-	~~\|RR Y/N~~
	\|Y		\|Y
	\|}		\|}

SNPWG

2012-05-16T07:48:28Z

←Older revision		Revision as of 07:48, 16 May 2012
Line 166:		Line 166:
	==Simple attributes==		==Simple attributes==

-	[[ACTION]] <span style="color:~~black~~;">Action or activity</span>	+	[[ACTION]] <span style="color:blue;">Action or activity</span>

-	[[ACTXEP]] <span style="color:~~black~~;">Action or activty exception</span>	+	[[ACTXEP]] <span style="color:blue;">Action or activty exception</span>

	[[ADMDIV]] <span style="color:red;">Administrative division </span>		[[ADMDIV]] <span style="color:red;">Administrative division </span>
Line 236:		Line 236:
	[[CATROS]] <span style="color:black;">Category of radio station</span>		[[CATROS]] <span style="color:black;">Category of radio station</span>

-	[[CATRXN]] <span style="color:~~black~~;">Category of regulation / restriction / recommendation / nautical information</span>	+	[[CATRXN]] <span style="color:blue;">Category of regulation / restriction / recommendation / nautical information</span>

	[[CATSHA]] <span style="color:red;">Category of concentration of shipping hazard area</span>		[[CATSHA]] <span style="color:red;">Category of concentration of shipping hazard area</span>

SNPWG

2012-05-16T07:31:35Z

Complex Attributes:

←Older revision		Revision as of 07:31, 16 May 2012
Line 138:		Line 138:
	[[POPNBR]] <span style="color:blue;">Population in the vicinity of the Port</span>		[[POPNBR]] <span style="color:blue;">Population in the vicinity of the Port</span>

-	[[RXNCOD]] <span style="color:~~black~~;">Regulation / restriction / recommendation / nautical information code</span>	+	[[RXNCOD]] <span style="color:blue;">Regulation / restriction / recommendation / nautical information code</span>

	[[STTOFF]] <span style="color:blue;">Standard Time offset from UTC</span>		[[STTOFF]] <span style="color:blue;">Standard Time offset from UTC</span>
Line 163:		Line 163:

	[[TXTCON]] <span style="color:black;"> Text content</span>		[[TXTCON]] <span style="color:black;"> Text content</span>
-
-

	==Simple attributes==		==Simple attributes==

RXNCOD

2012-05-16T07:29:31Z

←Older revision		Revision as of 07:29, 16 May 2012
Line 85:		Line 85:
	\|Y		\|Y
	\|Y		\|Y
-	\|Y/N	+	\|Y
	\|}		\|}

RXNCOD

2012-05-16T04:58:26Z

←Older revision		Revision as of 04:58, 16 May 2012
Line 84:		Line 84:
	\|- style="background:white; color:black"		\|- style="background:white; color:black"
	\|Y		\|Y
-	\|Y/N	+	\|Y
	\|Y/N		\|Y/N
	\|}		\|}

RXNCOD

2012-05-15T10:13:05Z

←Older revision		Revision as of 10:13, 15 May 2012
(One intermediate revision not shown.)
Line 5:		Line 5:
	Attribute type: Complex		Attribute type: Complex

-	Camel Case: ~~RegRestRecNautInfCode~~	+	Camel Case: regRestRecNautInfCode


Line 21:		Line 21:
	\|[[SUBJCT]]\|\|subject\|\|0..1\|\|n/a		\|[[SUBJCT]]\|\|subject\|\|0..1\|\|n/a
	\|-		\|-
-	\|[[ACTION]]\|\|~~action~~\|\|0..1\|\|n/a	+	\|[[ACTION]]\|\|actionOrActivity\|\|0..1\|\|n/a
	\|-		\|-
	\|[[ACTXEP]]\|\|actionOrActivityException\|\|0..1\|\|n/a		\|[[ACTXEP]]\|\|actionOrActivityException\|\|0..1\|\|n/a
Line 83:		Line 83:
	!David!!Raphael!!Jens		!David!!Raphael!!Jens
	\|- style="background:white; color:black"		\|- style="background:white; color:black"
-	\|Y/N	+	\|Y
	\|Y/N		\|Y/N
	\|Y/N		\|Y/N
	\|}		\|}

CATREL

2012-05-15T10:08:50Z

←Older revision		Revision as of 10:08, 15 May 2012
Line 9:		Line 9:
	Data type: Enumeration		Data type: Enumeration

-	Definition: This attribute expresses the level of insistence for or against ~~a course of~~ action.	+	Definition: This attribute expresses the level of insistence for or against an action or activity.

SNPWG

2012-05-15T10:06:16Z

←Older revision		Revision as of 10:06, 15 May 2012
Line 138:		Line 138:
	[[POPNBR]] <span style="color:blue;">Population in the vicinity of the Port</span>		[[POPNBR]] <span style="color:blue;">Population in the vicinity of the Port</span>

-	[[RXNCOD]] <span style="color:black;">Regulation / restriction / recommendation ~~code~~ / nautical information</span>	+	[[RXNCOD]] <span style="color:black;">Regulation / restriction / recommendation / nautical information code</span>

	[[STTOFF]] <span style="color:blue;">Standard Time offset from UTC</span>		[[STTOFF]] <span style="color:blue;">Standard Time offset from UTC</span>

Talk:GRAPHC

2012-05-15T05:30:19Z

←Older revision		Revision as of 05:30, 15 May 2012
Line 88:		Line 88:
	Regarding item 3:<br>		Regarding item 3:<br>
	I think, if 1 and 2 are not available one can (hopefully) obtain from the picture where the location of the camera was. That can only be an approximate position but better than nothing. Means, the first two items can be positions and the third item can be a string if a psn can't be specified.		I think, if 1 and 2 are not available one can (hopefully) obtain from the picture where the location of the camera was. That can only be an approximate position but better than nothing. Means, the first two items can be positions and the third item can be a string if a psn can't be specified.
		+
		+	[[User:Rmm\|raphael]] 05:30, 15 May 2012 (UTC): OK

RXNCOD

2012-05-15T05:29:43Z

←Older revision		Revision as of 05:29, 15 May 2012
Line 70:		Line 70:
	Populate [[SUBJCT]] if [[CATRXN]] does not cover the type of regulation sufficiently accurately.		Populate [[SUBJCT]] if [[CATRXN]] does not cover the type of regulation sufficiently accurately.

-	Populate [[ACTXEP]] if [[ACTION]] does not describe the action or activity ~~sufficently~~ accurately.	+	Populate [[ACTXEP]] if [[ACTION]] does not describe the action or activity sufficiently accurately.

CATRXN

2012-05-15T05:21:42Z

←Older revision		Revision as of 05:21, 15 May 2012
Line 151:		Line 151:
	\|- style="background:white; color:black"		\|- style="background:white; color:black"
	\| Y		\| Y
-	\| Y/N	+	\| Y
	\| Y		\| Y
	\|}		\|}

Talk:SUBJCT

2012-05-15T05:06:09Z

←Older revision		Revision as of 05:06, 15 May 2012
Line 5:		Line 5:
	Can this be a string; or do we need to tighten it up with enumerations?		Can this be a string; or do we need to tighten it up with enumerations?

-	[[User:Jens\|jens]] 05:04, 15 May 2012 (UTC) That looks good to me now.	+	[[User:Jens\|jens]] 05:04, 15 May 2012 (UTC) That looks good to me now. Added distinction to the page.

SUBJCT

2012-05-15T05:05:35Z

←Older revision		Revision as of 05:05, 15 May 2012
(One intermediate revision not shown.)
Line 30:		Line 30:
	Distinction:		Distinction:

		+	categoryOfRegRestRecNautInf

Talk:SUBJCT

2012-05-15T05:04:26Z

←Older revision		Revision as of 05:04, 15 May 2012
Line 4:		Line 4:

	Can this be a string; or do we need to tighten it up with enumerations?		Can this be a string; or do we need to tighten it up with enumerations?
		+
		+	[[User:Jens\|jens]] 05:04, 15 May 2012 (UTC) That looks good to me now.

CATRXN

2012-05-15T05:01:56Z

←Older revision		Revision as of 05:01, 15 May 2012
Line 152:		Line 152:
	\| Y		\| Y
	\| Y/N		\| Y/N
-	\| Y/N	+	\| Y
	\|}		\|}

Talk:GRAPHC

2012-05-15T04:59:40Z

←Older revision		Revision as of 04:59, 15 May 2012
Line 84:		Line 84:

	I think the camera location is useful mainly as a proxy for the location of the subject, so its usefulness will vary.		I think the camera location is useful mainly as a proxy for the location of the subject, so its usefulness will vary.
		+
		+	[[User:Jens\|jens]] 04:59, 15 May 2012 (UTC) Raphael,
		+	Regarding item 3:<br>
		+	I think, if 1 and 2 are not available one can (hopefully) obtain from the picture where the location of the camera was. That can only be an approximate position but better than nothing. Means, the first two items can be positions and the third item can be a string if a psn can't be specified.

CATRXN

2012-05-14T15:32:30Z

←Older revision		Revision as of 15:32, 14 May 2012
Line 9:		Line 9:
	Data type: Enumeration		Data type: Enumeration

-	Definition: The principal subject matter of the regulations, restrictions, recommendations or nautical information	+	Definition:
		+
		+	The principal subject matter of the regulations, restrictions, recommendations or nautical information

SUBJCT

2012-05-14T15:31:41Z

←Older revision		Revision as of 15:31, 14 May 2012
Line 13:		Line 13:
	Definition:		Definition:

-	The subject matter of ~~a regulation~~, restriction, recommendation or nautical information.	+	The principal subject matter of the regulations, restriction, recommendation or nautical information
		+
		+

CATRXN

2012-05-14T15:30:10Z

←Older revision		Revision as of 15:30, 14 May 2012
Line 9:		Line 9:
	Data type: Enumeration		Data type: Enumeration

-	Definition: ~~A simple indication~~ of ~~the sphere of jurisdiction being controlled by~~ the regulations	+	Definition: The principal subject matter of the regulations, restrictions, recommendations or nautical information

SUBJCT

2012-05-14T15:25:38Z

←Older revision		Revision as of 15:25, 14 May 2012
(One intermediate revision not shown.)
Line 38:		Line 38:
	Comments:		Comments:

-	~~No comments~~.	+	This attribute should be populated if the subject matter of a regulation, restriction, recommendation or nautical information cannot be encoded with the use of the attribute categoryOfRegRestRecNautInf.

ACTXEP

2012-05-14T15:18:55Z

←Older revision		Revision as of 15:18, 14 May 2012
Line 34:		Line 34:
	Comments:		Comments:

-	This attribute should be populated if a regulation, restriction, recommendation or nautical information concerns an action or ~~exception~~ which cannot be coded with the use of the attribute actionOrActivity.	+	This attribute should be populated if a regulation, restriction, recommendation or nautical information concerns an action or activity which cannot be coded with the use of the attribute actionOrActivity.

CATRXN

2012-05-14T15:15:51Z

←Older revision		Revision as of 15:15, 14 May 2012
Line 8:		Line 8:

	Data type: Enumeration		Data type: Enumeration
		+
		+	Definition: A simple indication of the sphere of jurisdiction being controlled by the regulations
		+
		+

CATBRC

2012-05-14T15:06:41Z

←Older revision		Revision as of 15:06, 14 May 2012
Line 9:		Line 9:
	Camel case: categoryOfBroadcastAndOrCommunication		Camel case: categoryOfBroadcastAndOrCommunication

-	Attribute type: E	+	Attribute type: Simple
		+
		+	Data type: Enumeration

CATRXN

2012-05-14T15:03:18Z

←Older revision		Revision as of 15:03, 14 May 2012
Line 32:		Line 32:
	9 : health		9 : health

-	10: natural resources or ~~exploitations~~	+	10: natural resources or exploitation

	11: port		11: port

	12: finance		12: finance
		+
		+	13: agriculture

Talk:GRAPHC

2012-05-14T04:59:44Z

←Older revision		Revision as of 04:59, 14 May 2012
Line 75:		Line 75:
	2. derived from exif<br>		2. derived from exif<br>
	3. estimated by deriving from image		3. estimated by deriving from image
		+
		+	[[User:Rmm\|raphael]] 04:59, 14 May 2012 (UTC):
		+	Would not the geographic features with which the image is associated in the dataset denote the subject? Additional information if any would presumably be placed in the caption.
		+
		+	Dates: Let's wait a while and see what TSMAD do with dates and times.
		+
		+	Jens, could you explain item 3 in your proposal?
		+
		+	I think the camera location is useful mainly as a proxy for the location of the subject, so its usefulness will vary.