XCSoar and LK8000 data sources

This page was last updated on 26 July, 2022.

This page tells you where to find the data files that XCSoar and LK8000 need and where to put them on the SD card. Once the files are in place you still have to start the program and use its Config|Setup System dialogue to tell it which files it needs to use via the 1 Site page. Once that's complete and you've made any other changes to suit yourself (such as the units to use for speed and height), restarting the program should show you the information you require.

UK data files

UK Landout and CGC Field Book Databases

These files include only landout locations with one or more runways that are at least 375m long and 17m wide.

Notes

1. The UK Landout and CGC Field Book Databases were generated using the BGA turnpoints list identified as Turnpoints on the preceeding UK data files table and should be used with that version.

2. Frequencies listed in these files were checked against the 833 AIP supplimentary list downloaded on 13 December 2018. This covers all airfields marked as Conversion Completed as well as those marked as Planned Conversions, which should have finished conversion by 06Jan2019. As a result, some of the listed airfields are shown with 25kHz channel spacing: these details will be updated when the change is notified in AIP messages. Use with caution and report any errors to me for correction.

3. This airfields.txt file is the one I used to set GRL as my home field before the UK Landouts Database was available. It is only useful if you are NOT using the database because this information is incorporated in it.

   Although you can set your HOME airfield from the waypoints list in either XCSoar or LK8000, this is only a temporary setting that will be lost if you close down and restart the program. However, if you set it by editing airfields.txt this setting will become permanent. If you don't permanently define your HOME airfield and you're using Simulate mode or there is no GPS signal, the program starts up showing some place to the far north-west of the terrain map. If you'd rather it started at your field, download airfields.txt and edit it, changing the airfield name and description to match your home field. The airfield name (GRL GrnsdnLd) must match the name of a turnpoint on your field exactly as it appears in the Turnpoints file: spaces, punctuation and capitalisation must all match. The second and subsequent lines are descriptive and can contain anything you think is useful.

4. XCSoar and LK8000 use OpenAir format airspace files. Use the ASSelect web application, which allows you to select the detail level you want to see in your cockpit. Once these details are selected, it generates an OpenAir format file that you download and install in your navigation system. ASSelect offers the option of displaying IFR feathers on the approaches to suitably equipped runways, so if there is a nearby IFR-equipped field that only has an ATZ you'll probably want to select this as a reminder to avoid loitering on an IFR approach.

   As both XCSoar and LK8000 can handle two airspace files you may want to download and install SPINE. Use it to check NOTAMS when you're planning a task. It offers you the option of generating an OpenAir format file containing all the plottable NOTAMs for the selected day. This can be loaded into your navigation device to show NOTAMs alongside permanently restricted airspace.

   It is a good idea to check the accuracy of these files against a current map covering your task area before using them because they may be missing updated details. The ASSelect application, SPINE and OpenAir files do not have official approval, so use them at your own risk.

5. The pair of mapping files used by LK8000 are:
   • An .LKM file, which contains topology (towns,roads, etc.)
   • A .DEM file, which contains the terrain (shaded 3D countryside).
   Neither contains airfields: these are defined in the turnpoints file. Their use is optional: if you don't want to see topology or terrain, don't install them. If they are installed the Display menu controls whether topology and/or terrain is displayed.

6. An .XCM file defines the topology (towns, roads and water) and terrain (shaded 3D countryside) but not airfields: these are defined in the turnpoints file. It is optional: if you don't want to see topology or terrain, don't install it. If it is installed the Display menu controls whether topology and/or terrain is displayed.

   The files made available here were generated by Dave Mansfield and myself for our own use. They cover the area occupied by all the BGA turnpoints and vary in size between 1.9MB and 3.3MB. Generate your own if they are too big for your PNA or PDA.

7. CAI Turnpoint File specification.

8. CUP file format description.

9. The UK Landouts Database is an unofficial list of airfields, microlite strips and fields that may be used at your own risk for landing out: some of them may be unsuitable for use depending on the time of year, the type of glider you are flying or your skill level. It is your responsibility to determine whether a field is suitable: the description includes obstructions and runway details that were visible with Google Earth when they were added to the database.

   Follow this link for a more detailed description of the database contents and how you customise and install it.

10. If you're still using Microsoft's Internet Explorer to access this website you may find that it wants to save .CUP files with an .HTM extension, which, of course, means that the file won't be recognised by any navigation program. If IE is going to do this you'll see the changed file name in the file saving dialogue and can change it back to .CUP before you hit Save. If you missed that and save it with an .HTM extension, just use Windows Explorer's rename dialogue to change the extension back to .CUP before you upload the file to your SD card, Oudie or PNA.

Non-UK Data files

If you need non-UK data files, search these sites:

1. Either the LK8000 or the XCSoar web site depending on which program you're using.

2. The Soaring Server. XCSoar uses Cambridge Instruments format turnpoint and airspace files. If you can't find any suitable airfield files, copy mine (referenced above) and modify it to suit, so at least XCSoar will know where your home airfield is.

Installing data files

XCSoar

• XCSoar expects to find these files in the XCSoarData directory. Its placement depends on which PNA or PDA you're using to run XCSoar: details can be found on the main XCSoar website. If you're running the program from an SD card on a PNA, XCSoarData should in the root directory of the SD card. If it isn't there, create it. PDAs and other devices may require it to be in other locations.

• Put the files you've downloaded in the XCSoarData directory.

• Start the program and make sure that they are all referenced in the appropriate box on the 1 Site page in the Setup System dialogue:

  File type	File name box	Notes
  MAP database	.XCM file	Contains topology and terrain details
  Waypoints More waypoints	BGA waypoints UK landouts/ private list
  Airspace	Airspace 1 Airspace 2	Permanent restricted airspace NOTAMS generated by SPINE
  Topology and Terrain	Map file	-
  Waypoint details	Waypoint notes	If there are no additional comments about any of the turnpoints ot landouts then all you need to do is to set the 'Airfields file' parameter to the name of the airfields.txt file. Otherwise this should contain the name of the appropriate waypoint notes file. If you're using UK landouts, this should contain the name of the UK Landouts notes file.

LK8000

• LK8000 expects to find these files in subdirectories of the LK8000 directory. See the LK8000 manual for details. The placement of the LK8000 directory depends on which PNA or PDA you're using to run the program: details can be found on the main LK8000 website. If you're running the program from an SD card on a PNA, LK8000 should in the root directory of the SD card which is where it should be unzipped. PDAs and other devices may require it to be in other locations.

• Put the files you've downloaded in the appropriate subdirectory of the LK8000 directory.

• Start the program and make sure that they are all referenced in the appropriate box on the 1 Site page in the Setup System dialogue:

  File type	File name box	Notes
  Map file	.LKM file
  Terrain file	.DEM file
  Waypoints 1	.DAT file	The BGA waypoints file
  Waypoints 2	.DAT file	UK landouts file or a private list of landouts and/or turnpoints
  Airspace 1	OpenAir file	Permanent restricted airspace
  Airspace 2	OpenAir file	SPINE-generated plottable NOTAMS
  Waypoint notes	.TXT file	The UK landouts notes file or airspaces.txt to set the HOME turnpoint of there are no additional notes about waypoints.

Polars

The programs have a collection of built-in polars which can be added to by using Winpilot format polar files (.plr). Many predefined polars are available from http://www.winpilot.com/polar.asp. If the polar for your glider isn't built in or available from the Winpilot site you'll have to modify a similar file or create your own. Polars are defined in files that conform to the XCSoar polar format.

Put the polar file in the XCSoarData directory, start the program and configure the polar using the 7 Polar page of the Setup System dialogue:

• Set the Type box to Winpilot file
• Set the Polar file box (Custom polar file for LK8000) to the polar file name.

Note: if you're using a file to override a built-in polar the Polar file box will show a name ending in .plr if your file is selected: if the name does not end in .plr you're using a built in polar.

Generating UK turnpoint files under Linux

Wine can be used to run TpSelect, the BGA turnpoint file generator, on a non-Windows computer. Its always advisable to run unrelated applications in separate Wine prefixes so I use .wine_tpselect. There are two tweaks needed:

• Before installing TpSelect, set the prefix:

  export WINEPREFIX=$HOME/.wine_tpselect

• Install mfc42.dll with winetricks before running the TpSelect installer. It won't run otherwise.
• I used winecfg to set msvcrt.dll to (native,builtin) though this may not be necessary.

I launch TpSelect with a small shell script:

#!/bin/bash
export WINEPREFIX="$HOME/.wine_tpselect"
cd $HOME/.wine_tpselect/drive_c/Program\ Files/TpSelect
wine tpselect.exe

TpSelect appears to be fully functional when run this way though, as normal when Wine is used to run Windows applications, it may run a little slower than normal. It checks for updates, retrieves the latest BGA turnpoints file, allows you to select turnpoints or add your own and generates a Cambridge format file that XCSoar uses without complaint. The help system works though it is fairly slow and may pop up a Mozilla firefox error, which can be safely ignored.

Generating OpenAir airspace files under Linux

SPINE runs successfully under Wine. See the preceding section for details. Initial set-up is the same except that you do not need to install mfc42.dll or set msvcrt.dll to (native,builtin).

SPINE is straight forward. Install it, preferably in its own Wine environment, and run it. Everything works including its self-updating feature.

The downloadable ASSelect application was replaced by an interactive website which should work correctly under Linux with any web browser. I have used it successfully under Firefox and Pale Moon. That said, I have found a problem with Pale Moon if the screen is bigger than 1280 x 800 pixels: menu items can't be selected with a screen size of 1600 x 900 pixels, but this is most likely to be a problem that's specific to Pale Moon rather than the website.