Class Name: Property Grid Hook Point

Superclass - Geometry Hierarchy

Definition

A kind of Geometry Hierarchy. A Property Grid Hook Point is used to "instance" a Property Grid into the spatial scope of an Environment Root. In particular, the origin of the spatial axes of a component Property Grid is located at the Property Grid Hook Point component Location.

Since the Property Grid Hook Point separates the Property Grid data from the Location, Property Grid data can be re-used by several Property Grid Hook Points.

Primary Page in DRM Diagram:

• 6

Secondary Pages in DRM Diagram:

• 3
• 13

Example

1. A 1-dimensional Property Grid of data_table_type EDCS_CC_OCEAN_FLOOR_BATHYMETRY contains a depth axis only. The Property Grid Hook Point Location serves to position this grid into the currently scoped 'world' spatial reference frame.
2. A 2-dimensional Property Grid of table_type EDCS_CC_TERRAIN_ELEVATION contains elevation relative to the south-west corner of the grid. The Property Grid Hook Point Location serves to position this grid corner into the currently scoped 'world' spatial reference frame.

FAQs

If a Property Grid has all 3 spatial axes, isn't the hook Location redundant?

No, the hook point Location serves several purposes:

1. Since the spatial axes are relative, the hook Location provides the axis offset origins.
   
2. It makes a Location associated with the grid visible to API search filters (in the currently scoped 'world' spatial reference frame).

Constraints

• No Attribute Conflicts
• Non Crossing Aggregations
• Non Cyclic Aggregations
• Precedence of Attribute Set Index
• Non Crossing Associations

Associated by (one-way)(inherited)

• optionally, a Hierarchy Summary Item
• optionally, some Reference Surfaces

Associated with (two-way)(inherited)

• optionally, some Features
• optionally, some Geometry Hierarchies

Composed of (one-way)(inherited)

• optionally, some {ordered} Attribute Set Indices
• optionally, a Classification Data
• optionally, some Property Tables
• optionally, some Property Table References
• optionally, some Property Values
• optionally, a Reference Surface
• optionally, some Sound Instances
• optionally, a Spatial Domain

Composed of (one-way)

• one Location
• optionally, a LSR Transformation

Composed of (two-way)

• one or more Property Grids
• optionally, a Geometry Node

Composed of (one-way metadata)(inherited)

• optionally, a Time Constraints Data
• optionally, an Access
• optionally, some Browse Graphics
• optionally, some Cross References
• optionally, a Data Quality
• optionally, a Keywords
• optionally, a Point of Contact

Component of (two-way)(inherited)

• optionally, some Alternate Hierarchy Related Geometries through Geometry Hierarchy Data
• optionally, some Animation Related Geometries
• optionally, some Classification Related Geometries through Geometry Classification Data
• optionally, an Environment Root
• optionally, some Geometry Separating Plane Relations through Geometry Separating Plane Data
• optionally, a Geometry Model
• optionally, some Level of Detail Related Geometries through Geometry Level of Detail Data
• optionally, some Oct Tree Related Geometries through Geometry Oct Tree Data
• optionally, some Time Related Geometries through Geometry Time Constraints Data
• optionally, some Perimeter Related Geometries through Geometry Perimeter Data
• optionally, some Quad Tree Related Geometries through Geometry Quad Tree Data
• optionally, some Spatial Index Related Geometries through Geometry Spatial Index Data
• optionally, some State Related Geometries through Geometry State Data
• optionally, some Union of Geometry Hierarchies