Home' RTCA Documents for Review : DO-201B User Requirements for Navigation Data Contents ED-77A/DO-201BforOpenConsultation/FRAC
© EUROCAE, 2018
service message conforms for semantic interoperability reasons. The message syntax
specifications are treated as a separate concern based on constraints, opportunities and
cost considerations at the implementation level.
SWIM infrastructure is the interoperable technical infrastructure (ground/ground and
air/ground) over which the data is distributed. Its implementation may, depending on the
specific needs of common and agreed technical profiles, differ from one context to
another, both in terms of functional scope and implementation. The potential SWIM
technical infrastructure services (e.g., messaging, security, etc.) offered by the SWIM
infrastructure are as much as possible based on mainstream IT technologies and IP
Achieving interoperability across all areas illustrated in Figure 3-4 will require
Registries help service providers publicize services and users discover services and
make decisions about which ones are best to use among many that might be similarly
appropriate or adequate.
Although the term “SWIM registry” is used in the singular, there will likely be multiple
SWIM registries in different enterprises or regions. Multiple SWIM registries may (or
may not) be cross-linked.
A registry improves the accessibility to information facilitating a common understanding
of the services available through SWIM. For instance, the registry makes available the
information service descriptions through which information service providers expose
information about their services and information service consumers discover those
information services, which meet their needs.
Aeronautical Information Management and Relationship to ICAO Annex 15
Irrespective of whether or not an AIS/AIM service operates in a traditional data
distribution and management environment, or in a SWIM environment, the same
principles as outlined in ICAO Annex 15 apply.
The information management resources and processes established by an aeronautical
information service (AIS) is to be adequate to ensure the timely collection, processing,
storing, integration, exchange and delivery of quality-assured aeronautical data and
aeronautical information to other users.
ICAO Annex 15 defines data quality requirements – accuracy, resolution, integrity,
traceability, timeliness, completeness and format. Adherence to all these elements is
necessary for the provision of quality navigation data.
Appendix D to this document outlines further considerations pertaining to data quality
requirements, especially adherence to the AIRAC procedures and the role of NOTAMs
in updating information.
AERODROME ENVIRONMENT STANDARDS
Section 4.1 and Table 4-1 include requirements for aerodrome data such as
airport/heliport and runway/helipad information. Many of these data elements are also
defined in DO-272()/ED-99() in the context of aerodrome mapping databases.
Therefore, data elements included under the provisions of this document for navigation
databases may be duplicated or be similar to data captured and delivered under the
provisions of DO-272()/ED-99() for airport map databases. For example, runway
threshold positions are provided in the same fashion in both navigation and airport map
databases, but whether the threshold is displaced is provided in different ways between
the two database standards.
Values for like data elements may differ between a navigation database instance and
airport map database instance (e.g., when the databases come from different suppliers
or based on different data quality requirements).
Links Archive Navigation Previous Page Next Page