XCSoar and LK8000 data sources

This page was last updated on 05 December, 2011.

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

File type Updated Download Importance Purpose Note
Airfields 06/07/2009 airfields.txt Low Sets the default airfield. 1
Airspace - Download the OpenAir Format file from the Soaring Server's UK Airspace page.. High Defines controlled airspace in the UK.

Since this file is being refreshed quite frequently, you should regularly check for an update.
2
LK8000 Topology and terrain - Download from the LK8000 website. Optional Mapping data comes as pairs of files: you need both. 3
XCSoar Topology and terrain 24/04/2011
31/03/2011
31/03/2011
UK_2011.xcm
UK_2010_20K.xcm
UK_2010_9K.xcm
Optional Contains the digital mapping used to paint the moving map and to set the context of turnpoints.
UK_2011 was created by David Mansfield by modifying a map generated from the LK8000 mapping database. It now shows the inland water that was missing from maps created by the new XCSoar terrain generator. I have checked it with XCSoar 6.0.6. I'm leaving UK_2010_20K and UK_2010_9K maps (20 and 9 arc-second resolution respectively, which were generated with the older terrain generator) online for the time being.
4
Turnpoints 29/07/2011 bga_2011b.dat High The complete 2011 BGA turnpoints in Cambridge format, generated from Tim Newport-Peace's master file with TpSelect 3.1. 5

Notes

  1. I don't know of any available list of UK airfields suitable for landing out: if you know of an up to date, accurate machine-readable source, please contact me, even if your list only covers your club's local area. There is a project starting with the aim of collecting landout information for the whole of the UK and making it available for loading into glider navigation systems.

    This airfields.txt file is the one I use to set GRL as my home field. If you don't install it and you're using the simulator 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.

  2. XCSoar and LK8000 use OpenAir format airspace files. 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. This file does not have official approval.
  3. The pair of mapping files used by LK8000 are: 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 it they are installed the Display menu controls whether topology and/or terrain is displayed.
  4. 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 mysrelf for our own use. They cover the area occupied by all the BGA turnpoints. They vary in size between 1.9MB and 3.3MB. Generate your own if they are too big for your PNA or PDA.

  5. CAI Turnpoint File specification.

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

LK8000

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:

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:

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.