Notes on SN10 Moving Map Airspace Data Preparation
(for Version 2.40, updated 22-Sep-2014)

====================================================================
========================  Preparing Map Data  ======================

Airspace data must be pre-processed and then appended to the end of
an SN10 NDB file (see DBFORMAT.TXT for a complete description of the
NDB file format). Unlike the point data in the NDB file, the airspace
description data in an NDB file is not human-readable and consists of
a long list of lines that look like:
   A 15,48,181,245,27,50,124,0,1,1,49,50,45,66,0,0,0,0,0,0,

Airspace data is available in preprocessed form from ILEC for
various European countries. Prepare (or obtain a prepared) NDB file
as usual, and then append the pre-processed airspace data to the end
of the NDB file. After you have appended the airspace data, check
your NDB file using the DBC32 utility. After you have verified that
your NDB file is OK, load the NDB file into your SN10 as usual.
Check your NDB file using DBC32 in a command window as follows:
   DBC32 mySite.NDB
Note: For older platforms, use 16-bit DBC instead of DBC32.

Airspace description files in Tim Newport-Peace's TNP format must be
translated for use in the SN10 using the AIRPAR32 utility we provide.
For free airspace data in TNP format, visit the world-wide turnpoint
exchange's Special Use Airspace section at:
  http://acro.harvard.edu/SOARING/JL/SUA/HomePage.html
Also, Lynn Alley's excellent site provides USA data:
  http://www.soaringdata.info
You can download an airspace file covering a large area, then
edit this down to the portions you need for your site (set
INCLUDE=NO or delete unwanted sections).

For a complete description of the TNP format, please see:
  http://www.spsys.demon.co.uk/software/airspace.zip
Note that TNP files are sometimes distributed with file
type SUA.

AIRPAR32.EXE is a 32-bit Windows console application with two
required arguments:
  - the complete TNP-format file name (ie bayreuth.tnp)
  - coordinates of the home point **IN QUOTES**. These coordinates
    must match or be very close to the home point in your NDB
    file.
For example:
  airPar32 bayreuth.air "49:59.067 N 011:38.317 E"
AIRPAR32 will write the processed airspace data into a file
named AIRSPACE.TXT, which you should append to your NDB file.
Linux users: AIRPAR32 runs happily under Wine.

If you wish to use a TNP file containing airspace information
for a very large area (for example, the entire USA), AIRPAR32
can also ignore airspace outside a square centered at the home
point. The square of airspace you wish to use is specified by
the distance in km from the home point to the edge of the square.
For example:
   airpar32 conUS.sua "42:25.500 N  71:47.470 W" -C 150
will output only those airspace figures partially or wholly within
the square centered at "42:25.500 N  71:47.470 W" and 150km to
the edge (the square is 300km across).

Note: Airspace data processing has been implemented as a separate
step from NDB file processing because:
- The SN10 has not enough resources to process these files directly
- To continue to support DOS PC and DOSBOX users we had to
  keep HL small !


====================================================================
Please let me know what you think; your feedback is appreciated !

Thanks in advance for your comments, Fly Safe, and Have Fun,
Best Regards, Dave Nadler

Dave Nadler "YO"
USA East Coast (978) 263-0097
drn@nadler.com