This repository has been archived by the owner on Nov 21, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 11
Example of Route distances coded as KM #5
Comments
wolfi2909
added a commit
that referenced
this issue
Jul 15, 2020
#1 VerticalStructure.name used to code identification of Obstacle instead of VerticalStructurePart.designator #2 Metadata updates #3 Confidence level coded as Metadata instead of annotation #4 Marking coded as annotation instead of markingICAO Standard = OTHER:% #5 gml:Envelope modified to DONLON FIR extent as provided in PANS-AIM #6 Maximum height above ground coded as annotation instead of VerticalStructurePart.verticalExtent etc.
wolfi2909
added a commit
that referenced
this issue
Jul 15, 2020
#1 VerticalStructure.name used to code identification of Obstacle instead of VerticalStructurePart.designator #2 Metadata updates #3 Confidence level coded as Metadata instead of annotation #4 Marking coded as annotation instead of markingICAO Standard = OTHER:% #5 gml:Envelope modified to DONLON FIR extent as provided in PANS-AIM #6 Maximum height above ground coded as annotation instead of VerticalStructurePart.verticalExtent etc.
The current ICAO AIP Specimen (from DOC 8126) has the route distances in KM. The AIXM Donlon specimen tries to stay as close as possible to the ICAO examples. |
Should the topic of the ICAO AIP Specimen be discussed at another level considering most countries are using NM and there is no trend suggesting otherwise? Going to meters and kilometers was a rushed decision probably at some point to promote the metric/SI system but reality is even Russia has reverted to feet recently |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Examples of route segment distances are coded as KM, although technically correct probably from the allowable values, most users are more used to seeing NM for display of route distances, maybe the provided example should use NM instead of KM for the route lengths
The text was updated successfully, but these errors were encountered: