...
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks |
|---|---|---|---|---|
| SERASE-701 | If a Service has a clientAirspace that is an ATS airspace or a special activity airspace the Unit.name of the related to the Service shall be provided. | PANS AIM | TBD | |
| SERASE-702 | If a Service has a clientAirspace that is an ATS airspace or an special activity airspace the Service.type shall be provided. | Data consistency | TBD | |
| SERASE-703 | If a Service has a clientAirspace that is an ATS airspace or an special activity airspace the Service.call-sign shall be provided. | Data consistency | TBD | |
| SERASE-704 | If a Service has a clientAirspace that is an AD 2.17/AD 3.17 airspace the Unit.airportLocation of the unit providing the service should be provided. | Data consistency | TBD | |
| SERASE-705 | If a CallSignDetail.callSign is provided, also a CallSignDetail.language shall be provided. | AIXM 4.5 / Minimal data rule | AIXM-5.1_RULE-1A33D3 | |
| SERASE-706 | For the provision of the CallSignDetail.language Language codes - ISO 639-2 shall be used. | Data harmonisation | TBD | |
| SERASE-707 | AirTrafficManagementService shall not be used as Service in case the clientAirspace is an ATS airspace or a special activity airspace. | Data harmonisation | TBD | |
| ASE-708 | Each Service related to a Airspace should have a radioCommunication with coded RadioCommunicationChannel.frequencyTransmission and RadioCommunicationChannel.frequencyReception (if applicable). | Data harmonisation | TBD |
Coding Examples
The figure below shows an ATS Unit providing a Tower service within an airspace by using the DONLON CTR as example.
...