开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
  1. DXLab
  2. Topics

Missing Distances/Grids after carefully following distance computation procedure.

 
Edited

Dave/all
?
Using DXKeeper 17.9.9
?
I have imported an .adif log using the procedure here:
?
I have checked, in the upper left of the ImportQSOs tab "Query callbook and available databases for missing items".
?
In the Callbook tab I also have selected, at the bottom, the radio button for Callbook under Preferred Location Source.
?
I have selected, under QRZ.com, the radio button XML Data and provided my login to qrz.com and I have a valid xml data subscription.??
?
I also, under Secondary Callbook, have checked enabled and selected HamQTH and clicked "warn when primary callbook cannot be accessed".??
?
However, after import the import completes, MOST of the grid squares are in the log, BUT, there are some missing grid squares.? ?I then use the grid squares to compute the distance with the procedure that is posted online in the help files (setting the antenna path to short? with advanced filter).? ??
?
I have gone back to QRZ to see if QRZ.com has the grid square listed for the missing grid squares and qrz DOES have the grid square.? ?
?
My question:? ?What might be the most probable reasons for the missing grid squares??? Again, most do end up being populated during import.? ?I would guess 10-20% are missing.??
?
I can post the .adif log I am using but it is 2.9 MB and I am not exactly sure how to share it or if I need to do that for complete understanding.? ?
?
Thank you in advance for any thoughts.? ?I hope I provided enough info, if not, please let me know what othe info would be helpful/needed.??
?
Thank you in advance.??
--
Mike KM2B
 

+ AA6YQ comments below
Using DXKeeper 17.9.9
?
I have imported an .adif log using the procedure here:
?
I have checked, in the upper left of the ImportQSOs tab "Query callbook and available databases for missing items".
?
In the Callbook tab I also have selected, at the bottom, the radio button for Callbook under Preferred Location Source.
?
I have selected, under QRZ.com, the radio button XML Data and provided my login to qrz.com and I have a valid xml data subscription.??
?
I also, under Secondary Callbook, have checked enabled and selected HamQTH and clicked "warn when primary callbook cannot be accessed".??
?
However, after import the import completes, MOST of the grid squares are in the log, BUT, there are some missing grid squares.? ?I then use the grid squares to compute the distance with the procedure that is posted online in the help files (setting the antenna path to short? with advanced filter).? ??
?
I have gone back to QRZ to see if QRZ.com has the grid square listed for the missing grid squares and qrz DOES have the grid square.? ?
?
My question:? ?What might be the most probable reasons for the missing grid squares??
?
+ In the QRZ.com panel on the Configuration window's Callbook tab, is the "Ignore geocoded gridsquare ..." box checked?

"check the?Ignore geocoded grid squares, latitudes, and longitudes?box if location data derived from the postal address via "geocoding" should not be used (location data provided by the callsign's owner will always be used)"



? ? ?73,

? ? ? ? ? ?Dave, AA6YQ
 

+# More AA6YQ comments below
+ In the QRZ.com panel on the Configuration window's Callbook tab, is the "Ignore geocoded gridsquare ..." box checked?

"check the?Ignore geocoded grid squares, latitudes, and longitudes?box if location data derived from the postal address via "geocoding" should not be used (location data provided by the callsign's owner will always be used)"

# A grid square determined by "geocoding" means that the grid square was "determined" from a postal address; I've appended Perplexity's explanation of this process below. In my view, a geocoded grid square is fine for determining where to point your antenna, but insufficiently precise if you are pursuing a grid-based award like VUCC. That's why Ignore geocoded grid squares, latitudes, and longitudes is an option.

? ? ? 73,

? ? ? ? ? ? ? Dave, AA6YQ

Geocoding is the process of converting a postal address or textual description of a location into geographic coordinates, typically latitude and longitude. Here’s how it works:

Steps in Geocoding

  1. Input Address:

    • The user provides an address, which can include details like street name, city, state, and postal code. This input serves as the starting point for geocoding.

  2. Address Normalization:

    • The address is standardized to conform to postal service formats (e.g., USPS standards in the U.S.). This involves correcting spelling errors, abbreviations, and formatting inconsistencies to ensure compatibility with official databases.

  3. Address Validation:

    • The normalized address is checked against official databases (e.g., USPS or GNIS in the U.S.) to ensure it exists and is deliverable. This step helps eliminate errors and ensures accuracy.

  4. Matching with Geocoding Data:

    • The geocoding engine parses the address into components (e.g., street name, number, city) and searches for matching records in its database. This database may include street networks, postal codes, landmarks, and administrative boundaries.

  5. Address Interpolation:

    • If the exact location isn’t available, interpolation is used. For example, if a street segment has known coordinates for house numbers 100 and 200, the geocoding engine estimates the position of house number 150 based on its relative position within that range.

  6. Output Coordinates:

    • The geocoding engine returns latitude and longitude values corresponding to the address. These coordinates can represent varying levels of precision:

      • Rooftop level: Exact location within property boundaries.

      • Street level: Approximate location along a street segment.

      • Neighborhood or community level: Broader areas like ZIP code centroids.

Key Components

  • Geocoding Engines: Software tools or APIs (e.g., Google Maps Geocoding API) that perform the conversion using algorithms and extensive geographic databases.

  • Data Sources: Databases containing information about streets, postal codes, landmarks, and administrative areas.

  • Accuracy Levels: Precision varies depending on data availability; rooftop-level geocoding is most accurate while community-level geocoding is less precise.

Geocoding is widely used in mapping applications, navigation systems, tax compliance, logistics planning, and spatial analysis tasks.

Citations:

Answer from Perplexity:

 

Dave,
?
Many thanks for the detailed information
?
"Ignore geocoded gridsquare ..." box was indeed marked checked and I have now unchecked it and then spent some time trying to properly delete the entire existing log.? ?This is on a different computer from my own log with DXKeeper and just for our club's field day.??
?
I did just spend some time trying to properly delete all entries in DXKeeper so I can re-import and see if more grid squares are populated.??
?
However, try as I might (meaning I did look at your instructions) I could not delete the existing log.??
?
How I tried to do:? ?First, with two different methods, I filtered the log page display to contain the dates of our Field Day (and hence capture all of the log).? ?
?
I then, for each method of filtering, I clicked the top of DXKeeper windo to insure that was the live window then pressed CNTRL + DELETE (first pressing CNTRL and then, while continuing to press, pressing DELETE KEY.? This was the procedure I found after searching DXLab site information for delete.??
?
However, no delete occurred?? ?Please let me know the proper procedure for delete.? ?My apology for asking for something that is probably totally obvious but I cannot seem to do it today.
?
Thank you in advance.??
--
Mike KM2B
 

OK,
?
Wait,?
?
I did the following.
?
1.? Uninstalled DXKeeper.
2.? Deleted KM2B.mdb
3.? Reinstalled DXKeeper from DXLauncher.
?
Restarted DXKeeper.? Log is empty.
?
So, all good.? ?Although, if you want to post a delete process I will place it in my DXLab folder for the future.
?
As always, thank you for your patience, knowledge and help.
--
Mike KM2B
 
Edited

Dave,
?
OK, that process did not work BUT, I re-red the instructions and INSTEAD of pressing the DELETE key on my keyboard Pressed CNTRL and then clicked Delete on the LogQSO's pane and boom.....all QSO's are gone
apology for making a mess on the reflector.?
--
Mike KM2B
 

Dave and all,
?
Last update.? ?
?
I did uncheck the "Ignore geocoded gridsquare" box after deleting all previously imported contacts with the missing grids.
?
Upon a much more lengthy import, essentially ALL grid squares are present enabling me to map all of them, which, I will post examples of a bit later.
?
Dave, thank you for your tools, your support and your patience.? Awesome tools....which I will post more about analyzing our 2024 field day event later.
--
Mike KM2B
 

+ AA6YQ comments below?
I did the following.
?
1.? Uninstalled DXKeeper.
2.? Deleted KM2B.mdb
3.? Reinstalled DXKeeper from DXLauncher.
?
Restarted DXKeeper.? Log is empty.
+ Some of your logged QSOs were missing grid squares because when you imported them, you had the "Ignore geocoded grid squares..." option enabled in the QRZ panel on the Configuration window's Callbook tab.
?
+ To fill in the missing grid squares after disabling that option, you could have done the following on the Main window's "Log QSOs" tab:

1. Filter the Log Page Display with the SQL expression

len(GRIDSQUARE)=0

2. Depress the CTRL key while clicking the CBA button

+ Unless error messages of the form "Component X is missing" or "Library Y can't be found" are displayed, one should never attempt to solve a problem by uninstalling and then re-installing a DXLab application. It's the automotive equivalent of pulling the engine on your car because the gas tank is empty: it can't possible solve the problem, but can create new problems that are far worse than the actual problem.

? ? ? ?73,

? ? ? ? ? ? ?Dave, AA6YQ
?
?
?
?
 

# More AA6YQ comments below
+ Some of your logged QSOs were missing grid squares because when you imported them, you had the "Ignore geocoded grid squares..." option enabled in the QRZ panel on the Configuration window's Callbook tab.
?
+ To fill in the missing grid squares after disabling that option, you could have done the following on the Main window's "Log QSOs" tab:

1. Filter the Log Page Display with the SQL expression

len(GRIDSQUARE)=0

2. Depress the CTRL key while clicking the CBA button
# CORRECTION! Depress the ALT key while clicking the CBA button.

# See
?
? ? ?73,

? ? ? ? ? Dave, AA6YQ

1 - 9 of 9