Group of obstacles
Coding rules
The VerticalStructure.group property can be used to indicate that an obstacle consists of a number of closely situated similar objects. This property is not specified in the ICAO PANS-AIM provisions for obstacle data sets, but it might be useful in certain situations, as the ICAO Charting Manual provides a specific symbol for groups of obstacles.
The EUROCAE/RTCA standard for obstacle data sets indicates that vegetation that cannot be captured as individual obstacles should be captured as a polygon. In this case the group = 'YES' indicates that the polygon is actually occupied by a number of similar trees or other vegetation.
Note: If there exists in the middle of the group an obstacle that is significantly higher than the group, this should not be included in the group. That should be still provided as an individual obstacle. As a consequence, the geometry of that individual obstacle (point, line, polygon) intersects the geometry of the group (polygon). This should be kept in mind by data users as a particular case where two obstacles can have intersecting horizontal projections.
The TOD Manual provides guidance on the provision of data for grouping obstacles that have a similar height. Adjacent point obstacles of similar height and elevation can be grouped into an obstacle of type polygon or line. The decision if the objects are captured as single obstacle or as a group depends on the operational needs e.g. if operations are planned or not between obstacles. When obstacles that are similar in height, type and are located close to each other are captured as individual points, the TOD Manual indicates that they can published as a group. This approach is supported in AIXM through the coding of a single VerticalStructure with multiple VerticalStructurePart and group = YES, to indicate that the parts constitute a group rather than elements of a single volume.
Therefore, the group property may be used to indicate that the obstacle consists of a group of objects with similar type and elevation and located closely to each other, as follows:
- for obstacles with polygon (ElevatedSurface) or line (EleveatedCurve) geometry
- for obstacles that have multiple parts, each with point (ElevatedPoint) geometry
Coding Examples
Case 1: Polygon (e.g. group of wind turbines)
Case where a large number of obstacles with similar elevation are grouped, an area encompassing the grouped obstacles (perimeter) may be provided instead of providing each individual obstacle.
The wind park can be represented as a polygon as shown in the figure below.
In AIXM such as case may be coded as a VerticalStructure consisting of one (or more) VerticalStructurePart with ElevatedSurface geometry and group = 'YES'. The example below shows the encoding of a wind park comprising 8 wind turbines as polygon:
Case 2: Line (e.g. group of wind turbines)
Another case is the provision of multiple obstacles as a line. For example, wind turbines positioned in a line as in the figure below (red line).
In AIXM such as case may be coded as a VerticalStructure consisting of one (or more) VerticalStructurePart with ElevatedCurve geometry and group = 'YES'. The example below shows the encoding a wind park consisting of an unknown amount of wind turbines with similar elevation (height) as one line:
Case 3: Series of points (e.g. group of wind turbines)
There may be an operational benefit to provide each individual obstacle (e.g. wind turbine) belonging to a group of obstacles of similar height (e.g. wind park) .
In AIXM there are two possibilities to encode such a case:
Option A. The wind park as such is encoded as one VerticalStructure. Each individual wind turbine is encoded as a VerticalStructurePart. In this case, the group = 'YES' is used to indicate that the obstacle parts are similar in type and height and are close to each other.
Option B: Each individual wind turbine is encoded as its own VerticalStructure. The wind turbines are not related to each other.
The example below shows the encoding of Option A: