The Import QSOs tabbed dialog enabled you to import QSOs from standard ADIF files:
Click the Start button, and use the file selector to choose the file containing the QSOs to be imported. The Progress panel provides a display of real-time statistics, as well as errors encountered
Click the Abort button to terminate the import operation before it completes.
Options allow you to prevent the importing of duplicate QSOs, import from non-standard ADIF files produced by other applications, recover or insert missing information, save errors to a file, and/or display a report showing any advances in award progress attributable to the imported QSOs:
if you are importing QSOs into an empty log, you can uncheck the Check Duplicates on Import checkbox to improve performance; if you are importing into a populated log and wish to prevent the importing of duplicates, check the Check Duplicates on Import box and specify the range (in minutes)
0 means an imported QSO must exactly match a logged QSO's begin date/time to be considered a duplicate
a number larger than 0 specifies a range before and after the imported QSO's begin date/time; if a matching logged QSO's begin date/time falls in this range, the imported QSO will be considered a duplicate
if the file you are importing contains QSOs that may be missing Station Callsign fields, you can check the Substitute ... for missing station callsigns box to replace this missing information with the callsign specified in the Station callsign text box in the Default panel of DXKeeper's configuration window.
if the file you are importing contains QSOs that may be missing Operator Callsign fields, you can check the Substitute ... for missing operator callsigns box to replace this missing information with the callsign specified in the Operator callsign text box in the Default panel of DXKeeper's configuration window.
if the file you are importing contains QSOs that may be missing Owner Callsign fields, you can check the Substitute ... for missing owner callsigns box to replace this missing information with the callsign specified in the Owner callsign text box in the Default panel of DXKeeper's configuration window.
If your log contains one or more QTH definitions and you've specified a default QTH identifier, the Substitute QTH ID...box will be enabled. Checking this box will place the specified default QTH identifier into the myQTH item of any imported QSO whose ADIF record lacks an APP_DXKEEPER_MY_QTHID tag.
Errors will be noted in the Progress panel, up to a maximum of 65,000 characters. To additionally record all error reports to a file, check the Report import errors in error file checkbox; if errors are detected, they will be recorded in an error file whose pathname is created by appending _error.txt to the pathname of the file being imported, over-writing any existing file with that pathname. If the Report import errors in error file box is checked and no import errors are detected, any pre-existing error file with that pathname will be deleted.
Checking the Query Callbook for missing items box will lookup each imported QSO in the selected Callbook and fill in any items not present in the imported QSO with information from the Callbook; this option will be disabled if no Callbook is currently selected.
Checking the Produce and Display Award Progress Report box tracks all changes to award progress attributable to the imported QSOs, generates a report in a file whose pathname is created by appending _progress.txt to the pathname of the file being imported (over-writing any existing file with that pathname), and displays this report. Award progress is subject to the objectives you've specified in the DXCC/Top Bands & Modes panel.
if you are importing a standard ADIF file, the check the Import Standard ADIF button; if you are importing a file exported by DXBase, Logger 16, MMTTY, or Writelog, check the appropriate button as described below:
checking the Import From DXBase button will set the DXCC entity for each imported QSO from information exported by DXBase
checking the Import From Logger16 radio button will result in all but the first word of each incoming Name field to be relocated to the Comment field.
checking the Import From MMTTY button will extract transmit and receive contest sequence numbers from the RST sent and received fields respectively.
checking the Import from Writelog button will enable DXKeeper to correctly interpret Writelog's DXCC prefixes in <PREF> tags, ensuring that each imported QSO is assigned to the correct DXCC entity
if you are importing a contest log, the following options may be useful:
if you check the Guarantee unique start times box , DXKeeper assumes that the ADIF file being imported contains QSOs in ascending order of start time, and compares imported QSO's start time to that of its immediate predecessor; if a QSO's start time is the same or earlier than that of its predecessor's start time, the imported QSO's start time is set to that of its predecessor plus 5 seconds, time and the imported end time is set to 1 second after the start time -- thereby guaranteeing that each imported QSO has a unique start time.
If you check the Recover State, Province, & Section from box and enter or choose an ADIF tag, the specified field of each imported QSO will be inspected word by word for a Grid Square or for
a US State abbreviation (if the QSO's DXCC entity is USA, Alaska, or Hawaii)
a Canadian Province abbreviation (if the QSO's DXCC entity is Canada)
an ARRL section abbreviation (if the QSO's DXCC entity is the USA, Alaska, Hawaii, US Virgin Islands, Puerto Rico, US Pacific possessions, or Canada)
If unambiguous, a CQ zone and ITU zone will be derived from the State, Province, and Grid Square. Any Information found in or derived from the specified field will only be utilized if field specifications are absent from the imported QSO.
if you check the Replace Station Callsign with box, the Station Callsign of every imported QSO will be replaced with the specified value.
if you check the Replace Operator Contest ID with box, the Contest ID of every imported QSO will be replaced with the specified value.
If an imported QSO is missing a Station Callsign field but contains an Operator field, and both the Substitute ... for missing station callsigns and Replace Station Callsign with boxes are unchecked, then the contents of the Operator field will be imported as the Station Callsign
If an imported QSO contains is missing an Owner Callsign field, and the Substitute ... for missing owner callsigns box is unchecked, then
if the imported QSO contains a Station Callsign field, its contents will be imported as the Owner Callsign
if the imported QSO does not contain a Station Callsign field but does contain an Operator field, the Operator field's contents will be imported as the Owner Callsign.
Interactions with other configuration settings
If the WPX box is checked, the Import operation computes a WPX prefix for imported QSOs for which one is missing.
If the Initialize eQSL Sent to 'R' box is checked, imported QSOs will have their eQSL sent field set to R.
If the Initialize LotW Sent to 'R' box is checked, imported QSOs will have their LotW sent field set to or R.
Other considerations
If an imported QSO contains an ARRL Section and its DXCC Entity is specified, but is missing a State or Province, the State or Province will be determined from the ARRL Section and DXCC Entity if the relationship is unambiguous. For example, an ARRL Section of EMA with a DXCC Entity of USA will automatically set the State to MA.
The following conversions are performed automatically during import:
Frequencies containing two decimal points, like those exported by DXBase, will be correctly interpreted
the mode PSK will be imported as PSK31
the mode BPSK will be imported as PSK31
the mode BPSK31 will be imported as PSK31
the mode BPSK63 will be imported as PSK63
the mode MFSK will be imported as MFSK16
the modes USB and LSB are imported as SSB.
Information imported with a Prop_Mode tag that exceeds the field-width (8) will be appended to the Comment field.
When an imported ADIF record contains an APP_DXKEEPER_MY_QTHID tag, the associated QTH identifier is placed in the imported QSO's myQTH item. If the log contains no QTH definition with this QTH identifier, then a new QTH definition is created, and assigned this QTH identifier. If the imported ADIF record contains any of the following ADIF 2.0, their associated data is used to populated the newly-created QTH definition: MY_CITY, MY_CNTY, MY_COUNTRY, MY_CQZONE, MY_GRIDSQUARE, MY_IOTA, MY_ITUZONE, MY_LAT, MY_LON, MY_POSTAL_CODE, MY_STATE, and MY_STREET.