User-Created Database (.UDB.TXT format)

Your private airport is not in the native .NG2 database? Or, it's there but full runway and/or communication information not there?

Starting with Navgps Pro version 3.14, you can create a database with all the features of the .NG2 database entries. You can specify runways, approach info, communication frequencies etc.

Like .NDB files, these are also text-files. They have the file extension .UDB.TXT (e.g. my_database.udb.txt) and can be created with any text-editor - including the built-in editor in PocketPC.

The format is compatible with Navgps Pro only. Navgps Basic users can still use the .NDB file format.

With this feature, now there are three sources for av-data:

  1. native .NG2 database files - updated every 28 days.
  2. older .NDB user-created text-files.
  3. .UDB.TXT text-files.

IMPORTANT: If there are duplicate entries, here's how Navgps Pro handles it:

  • For non-airports (i.e. VOR, NDB and FIX), duplicate entries in .NDB files get superceded by .UDB.TXT entries and those get superceded by .NG2 entries.
  • For airports, duplicate entries in .NDB files get superceded by .NG2 entries and those get superceded by .UDB.TXT entries.

    This means that you can replace a native .NG2 airport entry with your own.

Click here to view an example file - sample.udb.txt. To download, right-click on the link and then select "Save Target As..." menu option.

The file is annotated and should be relatively easy to create your own entries.

A few hints:

  • Be sure the file has the proper .UDB.TXT extension.
  • You can have as many files as you want.
  • You can check whether the entries were loaded correctly by clicking on the '?' button on the Navgps intro-screen.
  • Once tested, keep the file as small as possible. For example, remove unnecessary text etc. - this will reduce memory requirements.

WARNING: User is solely responsible for the accuracy and validity of the file. It's common sense and strongly suggested to try out the file first in VMC conditions.