FAQ

We frequently get requests from developers in the flight simulation community who want to extend and improve the flight simulation experience. We in the Navigraph Development Team are very excited about collaborating with members of the community, and want to help in all the ways we can, but to manage the large interest we have to be efficient. Here is a list of Frequently Asked Questions (FAQ) which we hope will help with the first set of questions that may arise when you consider working with data from Navigraph. Browsing these before making contact with us may save you some time.

What does it cost to develop with Navigraph data?Read the “What does it cost to develop with Navigraph data?” section

For the developer it is free to implement functionality using Navigraph data. Instead we split the cost between the subscribing end-users.

Which data can Navigraph provide?Read the “Which data can Navigraph provide?” section

We can provide navigation data and charts. However, there are conditions associated with boths types of data.

What are some of the conditions that limit the use of Navigraph data?Read the “What are some of the conditions that limit the use of Navigraph data?” section

First and foremost the data from Navigraph must not be used for any real world application. The data must only be used for flight simulation. To prevent charts from unlawfully being used in a real world aircraft we impose restrictions on the Navigraph Charts API in that it can only be used for Electronic Flight Bags (EFBs) in virtual cockpits of addon aircraft, inside the simulator. We do permit breaking off EFBs to auxiliary screens, but only if the simulator is running concurrently on the same local network. Also we do not encourage the Navigraph Navigation data API being used to produce chart-like renditions, diagrams or any other pictorial interpretation of navigation data that could be used as a chart. We reserve the right to turn off API access for any developer who does not pay attention to our development recommendations. This is why it is very important that you describe the intended audience and purpose of your software to us.

What types of navigation data can Navigraph provide?Read the “What types of navigation data can Navigraph provide?” section

We can provide almost all types of aeronautical data, but the most common requests include information about airports; waypoints; airways; and airspaces. This includes information about runways; frequencies of landing systems; layout of approaches, STARs, and SID layout; holding patterns; and communication frequencies. Note that these are just examples of data - more information is available in our documentation.

Which data formats can Navigraph provide?Read the “Which data formats can Navigraph provide?” section

We can parse the aeronautical data into any format you like. We tend to work with text files, binary files, and relational databases. The structure of those files can be anything you like. Please note that you will save a lot of time if you have a well-documented format to present to us; or if you prefer, have a well-described format that you want to build upon.

How is the navigation data delivered?Read the “How is the navigation data delivered?” section

We typically deliver the navigation data parsed into your preferred data format directly to the end-user via client apps. We can also deliver the navigation data via our Navigraph Navigation data API which can be integrated into your software. We cannot license the navigation data to the developer, only to the end-user, which is why we cannot give the data to you directly - except for a test data set in the early stages of development.

Do you provide data in ARINC 424 format?Read the “Do you provide data in ARINC 424 format?” section

No, we only provide data parsed specifically for flight simulators.

Can you provide me with documentation over the data format of a certain addon?Read the “Can you provide me with documentation over the data format of a certain addon?” section

No. We can provide you with documentation of a general data format which we have designed, but we are not free to share documentation that has been sent to us by other developers. You can, however, make direct contact with a particular developer and make separate arrangements with them.