Obstacle marking
Simple "marked" or "unmarked" indication
Contrary to lighting, in AIXM 5.1(.1) there is no dedicated element that can be used in order to code if an obstacle is simply "marked" or not. This information is important for VFR flying, as obstacles that are not marked might be more difficult to spot visually.
AIXM 5.1(.1) issue
The issue has been raised in the AIXM CCB and a change proposal (AIXM-322) will align the obstacle marking model with the obstacle lighting model, by introducing a new simple "marked" attribute in the next AIXM model version.
For AIXM 5.1(.1), the workaround for this model limitation consists in creating an annotation with the following elements:
- purpose = 'REMARK'
- translatedNote.LinguisticNote.note = ”marked=YES” (or "NO", as appropriate)
Example - Marked Obstacle
The example blow shows the encoding of an marked obstacle.
Example - Unmarked Obstacle
The example blow shows the encoding of an unmarked obstacle.
Example - Unknown if marked
The example blow shows the encoding when it is not known if the obstacle is marked.
Detailed marking indication
A set of more specific elements can be used addition to code marking information in AIXM for each individual part:
- VerticalStructurePart.markingPattern
- VerticalStructurePart.markingFirstColour
- VerticalStructurePart.markingSecondColour
These details about markings are not required by PANS-AIM (but are described in ICAO Annex 14).
Example - Marked Obstacle With Details
The example blow shows the encoding of an marked obstacle more with details.
Marking property in PANS-AIM
NOTE
The attribute "Marking" was erroneously omitted in ICAO PANS-AIM Table A6-2 when transferring the table from the previous edition of ICAO Annex 15 Appendix 8.