...
The following pattern should be used as a base for generating the E field text from the AIXM data:
old:
new:
Code Block | ||||
---|---|---|---|---|
| ||||
old: template = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")] \n "Apron" "APN.BL.name" "closed" "APE.BL.annotation (4)" "\n" \n [ "due to" "APE.BL.availability.annotation (5)"]\n {"\n" "APE.BL.annotation(6)" "."} ["."]. new: template = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")] \n "Apron (4)" "APN.BL.name" "closed" "APE.BL.annotation (5)" "\n" \n [ "due to" "APE.BL.availability.annotation (6)"]\n {"\n" "APE.BL.annotation(7)" "."} ["."]. |
Reference | Rule | ||||||||
---|---|---|---|---|---|---|---|---|---|
(1) | If AHP.BL.locationIndicatorICAO=YES, then ignore this branch. | ||||||||
(2) | Insert here the type of the airport decoded as follows
| ||||||||
(3) | a. If AHP.BL.name is not NIL, then insert it here. Otherwise b.insert here the text "located at" followed by the AHP.BL.ARP.ElevatedPoint decoded according to the text NOTAM production rules for aixm:Point. | ||||||||
(4) | For the potential applications/implementations - the word "APRON" may appear twice depending on the coded APN.BL.name (e.g. APRON MILITARY APRON or APRON APRON A1). Caution shall be exercised for NOTAM production to avoid possible duplications. | ||||||||
(5) | Insert here the APE.annotation note with propertyName="extent" and purpose="DESCRIPTION" translated into free text according to the decoding rules for annotations. | ||||||||
(56) | Insert here the ApronElement/ApronAreaAvailability.annotation with propertyName="operationalStatus" and purpose="REMARK" translated into free text according to the decoding rules for annotations. | ||||||||
(67) | Other annotations of APE.BL shall be translated into free text according to the decoding rules for annotations. |
...