Frequently Asked Questions about the AIP Data Set Coding guidelines.

Work in Progress

The list contains the received questions. We are not yet at a stage of frequently asked questions.

Many questions have not received an answer yet.

When more questions are available, re-organisation might be needed.

Does an AIP data set contain the full data of an AIP?

No, it's just a poor name, but there was nothing better...

Are there any coding guidelines for airport working hours?

Not part of any digital data set specified by ICAO, try to apply the general coding guidelines for schedules, see Schedules.

I have a general question concerning coordinates. How is the preferred sequence? LAT/LONG or LONG/LAT? We have recognized, that customers of AIXM-data want to have it always the same from different suppliers.

AIXM 5.1 and later is using GML (Geography Markup Language) for encoding positions and geometries such as curve and surface. Please see OGC 12-028r1, Use of Geography Markup Language (GML) for Aviation Data for full details.

In GML, the order of the coordinates and their meaning is indicated by the Coordinate Reference System (specified with the srsName attribute). For AIXM, the recommended CRS is EPSG::4326, which is WGS-84. 2 dimensional, with latitude first and longitude second.

Where is the difference between building an airspace of multiple volumes by using PARTs and using simply more Geometry Components in an airspace?

The use of PART type Airspace is a legacy of the AIXM 4.5 model (and earlier versions), where it was not possible to have more than one geometry volume. When data is encoded natively in AIXM 5.1, I would expect to not see any PART type Airspace.

The only reason to encode airspace parts is when that part is also used for something else than contributing to the geometry of a single airspace. For example, when there is a specific service in that part, when it has a different airspace classification, etc. However, in that case a more specific type should be used, such as FIR_P, CTR_P, TMA_P, etc.

Browser not supported