Talk:PILBOP

Drafted by Northern before SNPWG 6

30.06.06 agreed SNPWG6

16.08.2006 checked DA

8.Nov.2006 checked Northern

SNPWG8 improve clapbp

14.01. Jens added dirctn; dstntn

14 Feb 08 WEG Changed clapbp to catpbp and agreed

12 July08 Jens agreed too

Submitted to Hydro register manager Date

Submitted to Nav register manager Date

--raphael 10:29, 20 March 2009 (CET)

S57 MD8 mentions new attribute CALSGN (which is also one of the attributes of condet)

jens 14:24, 20 March 2009 (CET)

Correct, that was forgotten. Although we might have this attribute available twice, I added to this object to satisfy S57. The duplication of CALSGN will not cause in the new S100 structure due to loose bindings between objects and attributes as we have it now with S57. That is why our approach offers more than only a list of objects/attributes. It offers the first approach to a ProdSpec too.

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

Proposed new attribute Location Name

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

This attribute is intended to be bound to PILBOP but could also be bound to other objects.