Re: Why is DXKeeper changing some imported Grids?


Joe Subich, W4TV
 

On 2022-07-05 2:59 AM, Dave AA6YQ wrote:

---- If the specified grid square is 4 characters in length, then if
the first 4 characters of the computed grid square don't match the
specified grid square, the first 4 characters of the computed grid
square will be utilized, and the resolution of the geographic
inconsistency will be noted in the after-action report.

---- If the specified grid square is 6 characters in length, then if
the 6 characters of the computed grid square don't match the
specified grid square, the computed grid square will be utilized, and
the resolution of the geographic inconsistency will be noted in the
after-action report.
To my thinking, the grid square is more likely to be correct than the
Latitude/Longitude. The supplied grid square should be used in
preference to any computed grid square when there is a disagreement.

- If "Callbook" is selected is selected in the "Preferred Location
Source" panel, DXKeeper will seek Location information from the
Callbook lookup results for the imported or received QSO's callsign.
If no Location information is specified in the Callbook lookup
results, DXKeeper will seek Location information from the imported
or received QSO.
The "Callbook" grid square (and Latitude/Longitude) should *ONLY* be
used if the callbook source indicates that it is "user supplied". Any
gridsquare indicated as "Geocoded", "from DXCC" or "from gridsquare" should be (optionally) ignored in all cases. Latitude/Longitude may
be used to compute distance if desired but gridsquares that are not
user supplied should be uniformly treated as unreliable.

One "unintended consequence" of using callbook latitude/longitude
is that you will probably need to include a flag for Lat/Lon that
are derived from a callbook in order to prevent overwriting of grid
data if the user does some kind of "recalculate grid/distance"
operation (if that is possible).

73,

... Joe, W4TV


On 2022-07-05 2:59 AM, Dave AA6YQ wrote:
Location information can be specified with a latitude and longitude,
or with a grid square.
There are two relevant sources of Location information:
1. a QSO imported from an ADIF or tab-delimited file, or received
from another application (e.g. JTAlert)
2. a Callbook lookup.
Both of the above sources of Location information can specify just a latitude and longitude, just a grid square, or a latitude, longitude,
and grid square: >
- If a Location information source only specifies a latitude and
longitude, a grid square containing the location specified by the latitude and longitude will be computed >
- If a Location information source only specifies a grid square, the
latitude and longitude of the center of the specified grid square
will be computed. >
- If a latitude, longitude, and grid square are all specified by a
Location information source, a 6-character grid square containing the
location specified by the latitude and longitude will be computed: >
---- If the specified grid square is 4 characters in length, then if
the first 4 characters of the computed grid square don't match the
specified grid square, the first 4 characters of the computed grid
square will be utilized, and the resolution of the geographic inconsistency will be noted in the after-action report. >
---- If the specified grid square is 6 characters in length, then if
the 6 characters of the computed grid square don't match the specified grid square, the computed grid square will be utilized, and
the resolution of the geographic inconsistency will be noted in the
after-action report. >
My current thinking:
A new "Preferred Location Source" panel will be placed in the
lower-left corner of the Configuration window's Callbook tab: >
https://www.dxlabsuite.com/dxkeeper/PreferredLocationSource.jpg
The explanatory popup for the "Imported or received QSO" option will be "If the imported or received QSO and Callbook both specify valid location information, use the location information specified in
the imported or received QSO". >
The explanatory popup for the "Callbook" option will be "If the imported or received QSO and Callbook both specify valid location information, use the location information specified in the Callbook for the QSO's callsign" >
The "Preferred Location Source" panel will default to "Imported or received QSO", because that was DXKeeper's behavior prior to version
16.6.5.
When processing a QSO imported from an ADIF or tab-delimited file,
or received from another application,
- If "Imported or received QSO" is selected in the "Preferred Location Source" panel, DXKeeper will seek Location information from the imported or received QSO. If no Location information is specified
in the imported or received QSO, DXKeeper will seek Location
information from the Callbook lookup results for the imported or
received QSO's callsign. >
- If "Callbook" is selected is selected in the "Preferred Location Source" panel, DXKeeper will seek Location information from the Callbook lookup results for the imported or received QSO's callsign. If no Location information is specified in the Callbook lookup results, DXKeeper will seek Location information from the imported
or received QSO. >
Comments? Better ideas?
73,
Dave, AA6YQ

Join DXLab@groups.io to automatically receive all group messages.