ADIF to Map Amateur Ham Radio Contacts by K2DSL

Running the application:
Q: Creating an ADIF file to use
Q: Specifying an override Grid Square
Q: What needs to be in the ADIF file?
Q: What application limits are there?

Problems:
Q: Why do map points show off the west central coast of Africa?
Q: I don't get any or very few map points displayed
Q: The application generates an error

Running the application:
Q: Creating an ADIF file to use
A: Most logging programs allow the export of your logged contacts in a common format known as ADIF. Check your specific logging program to determine how to export all/selected contacts in ADIF format.

Q: Specifying an override Grid Square
A: Some logging programs that create an ADIF file do not provide the necessary info associated with your home QTH and where your contacts were made from. You can specify a 4 or 6 character grid square associated with your home QTH. If you are unsure of your home QTH grid square, you can use my Maidenhead Grid Square Locator Map to find it.

Q: What needs to be in the ADIF file?
A: At a minimum, each QSO record associated with a contact in your log file needs to provide the call sign of the station you worked and either a latitude/longitude or grid square associated with that contact. The latitude/longitude or grid square provides the information necessary to map the contacted station location on a map. Some contacts/contests capture grid square and if properly represented in the generated ADIF file, that can be used. Typically, you will need to apply callbook data against your logbook records to associate a latitude/longitude or grid square which each contact. Please refer to your logbook documentation on how to specify or apply external callbook data to your records.

The ADIF file is a text file you should be able to view on your local computer. If you open the file and do a search for the following words, you can determine if the necessary info is provided: LAT LON and/or GRIDSQUARE. They will look similar to the following: <LAT:11>N039 00.000 <LON:11>W122 50.000 <GRIDSQUARE:6>CN87mq

Q: What application limits are there?
A: The uploaded ADIF file is limited to 1MB in size. Depending on the logbook program and what it exports this can accommodate a couple thousand contacts. The program needs to complete all processing of your ADIF file in 5 minutes or it will terminate. The generated KML which can be downloaded, and it will remain on my server for up to 1 day before removal. If you need the file longer, download the KML file to your local computer.

Google also has some limits. The KML file must be under 3MB which shouldn't be an issue. The more likely limit by Google is the # of points to be mapped needs to be under 1000. Including your home QTH, your ADIF file needs to be 999 contact records or less.

Problems:
Q: Why do map points show off the west central coast of Africa?
A: If you notice any map points off the west coast of Africa that seem out of place, it is likely because there was a problem determining the location (latitude/longitude) of a station in your logbook. That spot on the map represents latitude=0 & longitude=0. If it seems to represent your home QTH, you should specify an override grid square when processing your ADIF file.

Q: I don't get any or very few map points displayed
A: If the application can't determine a specific location (latitude/longitude) to place a map point, the contact record is skipped. This is likely because there is no latitude/longitude or grid square associated with your contacts. See What needs to be in the ADIF file? for additional information.

If your export is directly from eQSL, the necessary lat/long or grid data is not included in the ADIF file.

Q: The application generates an error
A: If you receive an error when trying to process your ADIF file, I would appreciate if you can zip up your ADIF file and mail it to me at david@levinecentral.com along with any information you can provide such as the program which generated the ADIF file, the version of the program, the error you received, what web browser you are using, and any other information you feel would be helpful in diagnosing the issue.