Talk:PILBOP - Revision history

Jens: /* Definitions of PILBOP */

2018-05-30T13:24:23Z

Definitions of PILBOP

Rmm at 05:28, 23 May 2018

2018-05-23T05:28:50Z

Rmm: /* Definitions of PILBOP */ new section

2018-05-23T05:24:13Z

Definitions of PILBOP: new section

Jens at 09:54, 9 January 2018

2018-01-09T09:54:24Z

Rmm at 07:22, 9 January 2018

2018-01-09T07:22:04Z

Rmm: /* Definition of CATPIL */ new section

2018-01-09T06:11:35Z

Definition of CATPIL: new section

Rmm at 03:18, 26 August 2009

2009-08-26T03:18:41Z

Rmm: /* Proposed new attribute Location Name */

2009-08-11T06:57:32Z

Proposed new attribute Location Name

Rmm: /* Proposed new attribute Location Name */ new section

2009-08-11T06:55:58Z

Proposed new attribute Location Name: new section

Jens at 11:53, 28 April 2009

2009-04-28T11:53:28Z

← Older revision		Revision as of 13:24, 30 May 2018
Line 55:		Line 55:
	* S-101 DCEG 1.0.0 Beta 1: A location offshore where a pilot may board a vessel in preparation to piloting it through local waters. (Defence Geospatial Information Working Group; Feature Data Dictionary Register, 2010).		* S-101 DCEG 1.0.0 Beta 1: A location offshore where a pilot may board a vessel in preparation to piloting it through local waters. (Defence Geospatial Information Working Group; Feature Data Dictionary Register, 2010).
	<br> Eivind remarks that the [[PLTMOV]] value ''disembarkation'' is contradictory to the definition of PilotBoardingPlace. NIPWG should review and resolve.		<br> Eivind remarks that the [[PLTMOV]] value ''disembarkation'' is contradictory to the definition of PilotBoardingPlace. NIPWG should review and resolve.
		+
		+
		+	[[User:Jens\|jens]] ([[User talk:Jens\|talk]]) 15:24, 30 May 2018 (CEST) I will contact Al to seek harmonisation between our data model and S-101 Beta. I strongly believe that our model offers more options for encoders and that this model reflects the rela world bettern than the current S-101 Beta version.

← Older revision		Revision as of 05:28, 23 May 2018
Line 54:		Line 54:
	* GI registry: The meeting place to which the pilot comes out.		* GI registry: The meeting place to which the pilot comes out.
	* S-101 DCEG 1.0.0 Beta 1: A location offshore where a pilot may board a vessel in preparation to piloting it through local waters. (Defence Geospatial Information Working Group; Feature Data Dictionary Register, 2010).		* S-101 DCEG 1.0.0 Beta 1: A location offshore where a pilot may board a vessel in preparation to piloting it through local waters. (Defence Geospatial Information Working Group; Feature Data Dictionary Register, 2010).
		+	<br> Eivind remarks that the [[PLTMOV]] value ''disembarkation'' is contradictory to the definition of PilotBoardingPlace. NIPWG should review and resolve.

← Older revision		Revision as of 05:24, 23 May 2018
Line 48:		Line 48:

	[[User:Jens\|jens]] ([[User talk:Jens\|talk]]) 10:54, 9 January 2018 (CET) That is an harmonisation and I agree.		[[User:Jens\|jens]] ([[User talk:Jens\|talk]]) 10:54, 9 January 2018 (CET) That is an harmonisation and I agree.
		+
		+	== Definitions of PILBOP ==
		+
		+	[[User:Rmm\|raphael]] ([[User talk:Rmm\|talk]]) 07:24, 23 May 2018 (CEST): Conflicting definitions as of 22 May 2018:
		+	* GI registry: The meeting place to which the pilot comes out.
		+	* S-101 DCEG 1.0.0 Beta 1: A location offshore where a pilot may board a vessel in preparation to piloting it through local waters. (Defence Geospatial Information Working Group; Feature Data Dictionary Register, 2010).

← Older revision		Revision as of 09:54, 9 January 2018
Line 46:		Line 46:

	[[User:Rmm\|raphael]] ([[User talk:Rmm\|talk]]) 08:22, 9 January 2018 (CET): S-101 DCEG 0.0.2 defines the feature Pilotage District instead of the attributes PILDST and NPLDST. At this time the GI registry contains both the feature and the attribute. Propose harmonizing with S-101 and removing PILDST and NPLDST from PILBOP.		[[User:Rmm\|raphael]] ([[User talk:Rmm\|talk]]) 08:22, 9 January 2018 (CET): S-101 DCEG 0.0.2 defines the feature Pilotage District instead of the attributes PILDST and NPLDST. At this time the GI registry contains both the feature and the attribute. Propose harmonizing with S-101 and removing PILDST and NPLDST from PILBOP.
		+
		+	[[User:Jens\|jens]] ([[User talk:Jens\|talk]]) 10:54, 9 January 2018 (CET) That is an harmonisation and I agree.

← Older revision		Revision as of 07:22, 9 January 2018
Line 41:		Line 41:
	[[User:Rmm\|raphael]] ([[User talk:Rmm\|talk]]) 07:11, 9 January 2018 (CET): CATPIL (categoryOfPilotBoardingPlace is not defined in the S-101 DCEG or the GI registry).		[[User:Rmm\|raphael]] ([[User talk:Rmm\|talk]]) 07:11, 9 January 2018 (CET): CATPIL (categoryOfPilotBoardingPlace is not defined in the S-101 DCEG or the GI registry).
	<br>Proposed definition: Classification of pilot boarding place by method used to board pilots.		<br>Proposed definition: Classification of pilot boarding place by method used to board pilots.
		+
		+
		+	== PILDST/NPLDST attributes and S-101 Pilotage District ==
		+
		+	[[User:Rmm\|raphael]] ([[User talk:Rmm\|talk]]) 08:22, 9 January 2018 (CET): S-101 DCEG 0.0.2 defines the feature Pilotage District instead of the attributes PILDST and NPLDST. At this time the GI registry contains both the feature and the attribute. Propose harmonizing with S-101 and removing PILDST and NPLDST from PILBOP.

← Older revision		Revision as of 06:11, 9 January 2018
Line 36:		Line 36:

	[[User:Rmm\|raphael]] 03:18, 26 August 2009 (UTC): Just a note to say that the group is invited to consider adding bindings for attributes [[NTCTIM]], [[PLTRQS]] and [[SVAPRC]] to [[PILBOP]] (in addition to [[GMLLCN]], above). These suggestions are based on our experience working on data capture for the test examples of pilotge information.		[[User:Rmm\|raphael]] 03:18, 26 August 2009 (UTC): Just a note to say that the group is invited to consider adding bindings for attributes [[NTCTIM]], [[PLTRQS]] and [[SVAPRC]] to [[PILBOP]] (in addition to [[GMLLCN]], above). These suggestions are based on our experience working on data capture for the test examples of pilotge information.
		+
		+	== Definition of CATPIL ==
		+
		+	[[User:Rmm\|raphael]] ([[User talk:Rmm\|talk]]) 07:11, 9 January 2018 (CET): CATPIL (categoryOfPilotBoardingPlace is not defined in the S-101 DCEG or the GI registry).
		+	<br>Proposed definition: Classification of pilot boarding place by method used to board pilots.

@@ Line 33: / Line 33: @@
 [[chalim]] should be considered when developing the ProdSpec. At certain places the [[PILBOP]] depends on different vsl limitations
-== Proposed new attribute  Location Name ==
+[[User:Rmm|raphael]] 03:18, 26 August 2009 (UTC): Proposal for new attribute [[GMLLCN]] was moved to its own page.
-[[User:Rmm|raphael]] 06:55, 11 August 2009 (UTC) : A new attribute GML location name is proposed. This attribute is intended for a verbal description or designation of the location of a place.  It is a renamed form of one the attributes suggested in the BSH/JEppesen pilot report and the GML attribute locationName which plays the same role in GML.  Comment received in 2008 after the BSH-Jeppesen study suggested using GML locationName instead of the unnamed new attribute suggested in that study. This would work, but makes the conceptual model dependent on GML (the single such dependency).  I think an attribute for strings designating locations will be useful because in some cases displaying a verbal description of the place may be useful to the human user of the ECDIS though not to the software.  E.g., "on a line between X and Y", "between buoys M and N", "in the vicinity of feature X" can be visually checked (though sometimes only approximately).  The introduction of this attribute will not prevent spatial objects being created for the same location wherever needed.
+[[User:Rmm|raphael]] 03:18, 26 August 2009 (UTC): Just a note to say that the group is invited to consider adding bindings for attributes [[NTCTIM]], [[PLTRQS]] and [[SVAPRC]] to [[PILBOP]] (in addition to [[GMLLCN]], above).  These suggestions are based on our experience working on data capture for the test examples of pilotge information.

← Older revision		Revision as of 06:57, 11 August 2009
Line 59:		Line 59:

	Distinction: OBJNAM		Distinction: OBJNAM
		+
		+	This attribute is intended to be bound to [[PILBOP]] but could also be bound to other objects.

← Older revision		Revision as of 06:55, 11 August 2009
Line 32:		Line 32:

	[[chalim]] should be considered when developing the ProdSpec. At certain places the [[PILBOP]] depends on different vsl limitations		[[chalim]] should be considered when developing the ProdSpec. At certain places the [[PILBOP]] depends on different vsl limitations
		+
		+	== Proposed new attribute Location Name ==
		+
		+	[[User:Rmm\|raphael]] 06:55, 11 August 2009 (UTC) : A new attribute GML location name is proposed. This attribute is intended for a verbal description or designation of the location of a place. It is a renamed form of one the attributes suggested in the BSH/JEppesen pilot report and the GML attribute locationName which plays the same role in GML. Comment received in 2008 after the BSH-Jeppesen study suggested using GML locationName instead of the unnamed new attribute suggested in that study. This would work, but makes the conceptual model dependent on GML (the single such dependency). I think an attribute for strings designating locations will be useful because in some cases displaying a verbal description of the place may be useful to the human user of the ECDIS though not to the software. E.g., "on a line between X and Y", "between buoys M and N", "in the vicinity of feature X" can be visually checked (though sometimes only approximately). The introduction of this attribute will not prevent spatial objects being created for the same location wherever needed.
		+
		+	As usual, comments invited.
		+
		+	Attribute: Location Name
		+
		+	Acronym: GMLLCN
		+
		+	Attribute type: Simple
		+
		+	Camel case: gmlLocationName
		+
		+	Data Type: text (string)
		+
		+	Definition: A verbal designation or description of the location of a feature.
		+
		+	References: GML 3.2
		+
		+	Remarks: This attribute is derived from the “locationName” element in GML. It is intended for designating locations in language a human reader can understand, for designating imprecise locations, or for designating locations which may not have corresponding spatial objects defined in the data set.
		+	This attribute must not be used for encoding the official name of a feature.
		+
		+	Example: “on a line between X and Y”; “1 mile E of Sandy Hook Light”; “North mole bearing 211", “offshore”.
		+
		+	Distinction: OBJNAM

← Older revision		Revision as of 11:53, 28 April 2009
Line 31:		Line 31:
	[[User:Jens\|jens]] 13:52, 28 April 2009 (CEST)		[[User:Jens\|jens]] 13:52, 28 April 2009 (CEST)

−	[[chalim]] should be considered when developing the ProdSpec. At certain places the [[~~pilbop~~]] depends on different vsl limitations	+	[[chalim]] should be considered when developing the ProdSpec. At certain places the [[PILBOP]] depends on different vsl limitations