Corrections

This page lists the changes that were made to the airspace definitions supplied by the CAA before running them through the airspace converter. Some of these changes are just the removal of airspaces that are of no relevance to hang gliding and paragliding activities. Some changes are to fix inconsistencies in the syntax of the data so that it can be parsed and converted correctly. Some changes are are to fix errors that have be discovered in the airspace definitions.

 

Control_Areas

 

NZA 040, NZA 041, NZA 149

The airspaces were removed because they cross the antimeridian and are not handled correctly by the Garmin and Google Earth software. They are not useful for hang gliding and paragliding purposes anyway.

 

NZA 143

Added "anticlockwise" to the last arc so that it reads:

"S 36 43 25.6, E 175 02 17.5, the arc of a circle of 20 NM radius centred on
S 36 47 12.5, E 174 37 52.4 (Whenuapai VORTAC) from
S 36 43 25.6, E 175 02 17.5 anticlockwise to
S 36 36 36.6, E 174 58 57.3 (transponder mandatory). "

 

NZA 145

Changed "S 38 54 22.7, E 176 47 43.0; the arc of a circle, 33 NM radius, centred on "
to "S 38 54 22.7, E 176 47 43.0; the arc of a circle of 33 NM radius centred on ".

Added a ";" to the end of the first arc i.e.
"S 39 05 55.3, E 176 19 39.8; a line joining" .

 

NZA 340

Changed "S 39 05 55.3, E 176 19 39.8; the arc of a circle, 33 NM radius, centred on "

to "S 39 05 55.3, E 176 19 39.8; the arc of a circle of 33 NM radius centred on "

 

NZA 341

Changed "S 177 45 18.8" to "E 177 45 18.8"

 

NZA 637

Deleted the struckout text.

 

NZA 657

Added the ";" to
"S 41 34 05.7, E 172 57 22.0; a line joining "

 

NZA 735

Deleted the struckout text.

 

NZA 841

Removed the ";" from
S 43 49 05.5, E 172 21 38.5; clockwise to

 

General_Aviation_Areas

 

NZG 271

Changed this...
"All that airspace bounded by a circle of 0.41 NM (0.75 km) radius, centred on
S 37 37 49.3 E 176 10 18.9. "

to this...
"All that airspace bounded by a circle of 0.41 NM radius centred on
S 37 37 49.3, E 176 10 18.9. "

 

NZG 275

Refactored this into two sectors as in NZA 633 so that it could be parsed correctly.

 

Mandatory Broadcast Zones

 

NZB 273

Changed this...
All that airspace bounded by a circle of 3 NM radius, centred on

to this...
All that airspace bounded by a circle of 3 NM radius centred on

 

NZB 374

Added "by" to the first line...
All that airspace bounded by...

 

NZB 682

Removed the "," after 'radius".

 

Building Garmin Map Sets

Building the Garmin specific files and loading them into Garmin GPSs is the most difficult part of this whole exercise. Luckily there are a few tools available that make the process easier. Also the Airspace Converter is hardwired to produce maps with sensible default values that have been tested and proven to work.

The tools required are:

• GPSMapEdit for visualising (and editing) maps.
• cGPSMapper for building the Garmin map files.
• MapSetToolKit for installing Garmin map database files into MapSource.
• MapSource or SendMap for collecting several maps together and loading them into the GPS.

The basic process is to use the Airspace Converter to convert the airspace files you want into Polish Map (*.mp) format. Then you can usecGPSMapper to convert the mp files into Garmin database files. Then you have a choice - you can use either SendMap or MapSource to load the files into the GPS. Caution: both of these techniques will replace all the maps already loaded into the GPS. Since I already use MapSource for installing other maps, that is the technique I use. The MapSource technique is discussed below. You can find documentation on SendMap at the cGPSMapper website.

1. Checking the Conversion with GPSMapEdit

If you want to check the conversion to Polish Map format before you move on to building the Garmin files I recommend using GPSMapEdit available from http://www.geopainting.com/en/. Using GPSMapEdit you can open the *.mp files directly to view them. You can also edit them but I recommend editting the source text files and re-running the airspace converter instead, so that the conversion can be repeated later without loosing any edits made in GPSMapEdit.

2. Using cGPSMapper to create Garmin map files

The first step towards creating Garmin files is to use cGPSMapper to convert the Polish Map files into Garmin img files. To do this simply open a cmd window (On Windows click Start, Run then type cmd and click OK), and change to the directory where the *.mp files are. Then run the cGPSMapper executable and tell it the name of the file you want to convert, like this...

<path to the location of cGPSMapper>\cGPSMapper.exe ac filename.mp

Repeat this for each mp file. Each time cGPSMapper will write a new file to the current directory with an 8 digit file name and the img extension. The filename is taken from the ID field in the mp file.

3. Installing maps into Garmin MapSource

To load the maps into MapSource you first need to build a preview map and database file. You can use cGPSMapper to do that, but it is much easier to use MapSetToolkit instead.

Open MapSetToolKit and you should see a screen like this...

MapSetToolKit

1. It is best to set up a single folder to hold your img files and some other configuration files that will be created by MapSetToolKit for use by MapSource. That folder is the 'Mapset directory' (C:\GarminMaps in the example above).
2. You can send multiple map files (see the previous section for naming requirements) into one Mapset (with any name you like). Actually this corresponds with one named 'Product' rather than one named 'Map set' as these terms are used in MapSource.
3. 'Product Code' does not matter for personal use, except that it should differ from any products already installed and any products to be later installed.
4. The Families Mapset section is important if you want to use custom type files. These are used to define your own lines and polygons. Choose a faimily ID (FID) that is not already in use (look in the Mapsets Installed window). The custom type File I have used is attached below as an example.
5. Tick the 'Install in MapSource' checkbox in the Options section then click 'Start'. MapSetToolKit will then build the preview map and database file, and install it all into MapSource.
6. If you subsequently seek to add further maps to your new mapset/product using MapSetToolKit, you may get an error message requiring you to first 'uninstall' that mapset. This takes out the previous registry entry, so be careful not to uninstall the wrong mapsets! (Hopefully in later versions this 'uninstall' step will not be needed simply to add maps).

4. Building a map set and uploading

If all has gone according to plan, when you next open MapSource, it should include your new 'product' (NZAirspace in our example), with whichever maps you have included, available for display and for transfer as usual to your GPS receiver.

MapSource

Unfortunately, MapSource can not display multiple layers, so you can not see your excellent work in full glory combined with other layers over a basemap on the computer screen. For that you have to transfer your maps to your GPS.

But before you hit 'Transfer' > 'Send to device' > 'Maps':

Caution: every current method of transferring maps into Garmin GPS receivers overwrites the previously transferred maps.

Make sure that all of your maps are available in your MapSource program, and assemble those that you need into one group (this is what Garmin calls a Map set) for transfer together into the GPS. To do that you need to select the Map Tool icon on the tool bar (with a picture of a polygon) then select all the maps you want from the map display window. Hint - when they are selected they turn pink on the map display and they are listed in the maps tab on the left. Then you can upload the map set to the GPS receiver.

If you do not use MapSource, there are various free or shareware programs to assemble img files into mapsets and transfer them to your Garmin GPS unit. Examples include SendMap and GPSExplorer.

 

Attachment	Size
custom.txt	5.96 KB