Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

Hull and Outfitting

Labelling GRIDLN Elements

  • Last UpdatedDec 09, 2025
  • 1 minute read

GRIDLN elements may be labelled, either individually or using Autotagging. Intelligent Text hash codewords may be used to extract data from them in the normal way.

GRIDLN elements do not have ppoints but do have an origin position in the Design model, however this may well fall outside the VIEW boundary. To aid the labelling of GRIDLNs the following special cases apply in Draft:

  • Draft considers all GRIDLNs to be of infinite length.

  • For all GRIDLNs Draft considers ppoint 0 to lie at their origins.

  • For a GRIDLN that passes through a VIEW, Draft considers the 2 intersections that it will make with the VIEW boundary to be ppoints 1 and 2, and the mid-point between them to be ppoint 3. Labels can be attached to these 'ppoints' (that means, attribute NPPT). The default label position (that means, NPPT -1) is at P3.

  • For a GRIDLN that does not pass through a VIEW ppoints 1, 2, and 3 are not defined. The default label position (that means, NPPT -1) is at P0.

It must be stressed that this concept of ppoints on GRIDLNs applies only in Draft. These ppoints only have World positions, their directions are not defined. Ppoint markers are generated by the Update Design process and can be identified by the 'IDP @' command in the normal fashion.

TitleResults for “How to create a CRG?”Also Available in