In the latest version of MultiPSK (Ref.1) there is a facility for displaying decoded ADS-B information on a user defined map. In the previous post we examined displaying AIS & ADS-B on OpenCPN. The only problem there, is that ADS-B information is not native to OpenCPN, so only the Lat/Long is preserved. In this post we examine creating a user defined map in OpenStreetMap (Ref.2) and then using the Maperitive (Ref.3) application to generate the necessary information files so that it can be used in MultiPSK.
Local Map Generation
Figure 1 shows the Maperitive program interface. Maperitive opens with OpenStreetMap, so I have selected a general area around Toronto. In order to create the two files required for MULTIPSK, I entered the data in Figure 2 into the Command Prompt window and executed it. Figure 3 shows the three files generated and available in the Maperitive output directory. Just copy the first two into the C:MULTIPSK/Maps directory. In the main MULTIPSK menu, select Local Map as in Figure 4. Then in the Maps Menu, Figure 5, under the File column, click in one of the boxes and enter the name of the file you just created and import it.
ADS-B Reception with Local Map
Figure 6 shows the MultiPSK capture window from the main screen, with ADS-B signal decodes and the output on the Local Map.
ADS-B Reception with Google Earth (No Internet/Cache Memory)
Google Earth can also be used off line to show the ADS-B decodes. Before going into the field while you have an internet connection, create a view in Google Earth that matches what you want to see. Then shut the program down. Enough information should now be stored in the memory cache to recreate this view. Figure 7 shows another ADS-B decode from a previous day on Google Earth.
Please send your comments, questions and suggestions to: