Data base validation
Both FAA and EASA recognise the import of database integrity.
The following excerpt is an insight on the basic criterion.
"These Conditions establish:
(a) The procedure for the issuance of a letter of acceptance (LOA) for organisations that translate, format and/or integrate information that originates from State aeronautical information services (e.g. AIP) into electronic databases for airborne navigation systems.
(b) The rights and obligations of the applicant for, and holders of, such letters of acceptance.
A.132. Definitions
(a) Navigation Database - Data (such as navigation information, flight planning waypoints, airways, navigation facilities, SID, STAR) that is stored electronically in a system that supports an airborne navigation application.
(b) Data Service Provider – An organisation (not including the State AIP provider), which collects, originates or processes aeronautical data and provides a navigation database in a generic format (such as ARINC 424). Such organisations are eligible for a Type 1 LOA under these Conditions (see Guidance Para 5.7) showing that the generic database has been formatted under controlled conditions.
(c) Data Application Integrator - An organisation that incorporates either State AIP data or a generic database into a format compatible with specific target airborne navigation equipment with a defined intended function. Such organisations require an interface with the equipment design organisation, and are eligible for a Type 2 LOA under these Conditions (see Guidance Para 5.7). This provides a list of equipment models and part numbers where compatibility has been demonstrated to the Agency, permitting the supply of navigation databases directly to end users/operators.
(d) Data Quality Requirements - A specification of the characteristics of data to ensure that data is compatible with its intended use."
https://www.easa.europa.eu/system/files/dfu/rule_Op_01_05_Nav_database_supp_doc.pdf