AIXM Model Overview
Coding Examples
Note for a whole AIXM Feature
The figure below shows the encoding of a Note related to a whole feature, viz. a DesignatedPoint.
.png?version=1&modificationDate=1493911027000&cacheVersion=1&api=v2&width=1024&height=456)
Note for a specific Property
The figure below shows the encoding of a Note related to a specific property of a AIXM feature, viz. the altimeterCheckLocation of an AirportHeliport.
.png?version=1&modificationDate=1493911021000&cacheVersion=1&api=v2&width=1024&height=514)
Note for an AIXM Object
In case of an AIXM object, there are actually two options.
The figure below shows the first option, the encoding of a Note related to the AIXM Object as such, viz. the City.
This has the meaning that the note is for a specific instance of the object. In this example the note is only applicable for 'BERN' and not any other served City (if any).
%20-%20Option%201.png?version=1&modificationDate=1493911018000&cacheVersion=1&api=v2&width=1024&height=515)
The figure below shows the second option, the encoding of a Note on the feature the object is related to, in other words for a specific property of that feature, viz. the servedCity of the AirportHeliport.
This has the meaning that the note is relevant for all related instances of this object and not a specific one. In this example, if the airport would not only serve 'BERN', but also another city, the note will be also applicable for that other served city.
%20-%20Option%202.png?version=1&modificationDate=1493911020000&cacheVersion=1&api=v2&width=1024&height=511)
Coding rules
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks |
|---|---|---|---|---|
| NTE-101 | For the lang attribute either ISO 639-2 shall be used. | Data harmonisation | TBD |