On 2025-02-02 9:26 AM, Gilbert Baron W0MN via groups.io wrote: I guess they are behind as show by this from the Website. Horrible. LotW is processing normally and is current. That "clip" shows that you have not successfully uploaded any QSOs since early December. I suggest you go to "Your Account" (top menu) -> "Your Activity" (left menu) and check the Activity and results of each upload for errors and correct any you find. 73, ... Joe, W4TV On 2025-02-02 9:26 AM, Gilbert Baron W0MN via groups.io wrote: This listing shows the number of QSOs you have uploaded and the number of matches (QSLs) each of your call signs. It also shows the oldest and newest QSO date for each call sign.
*Call Sign*
*# QSOs*
*# QSLs*
*Oldest*
*Newest*
W0MN
10,229
4,455
1953-12-27 18:30:00
2024-12-04 19:59:56
W0RYM
1,105
3
1953-12-27 18:30:00
1978-11-05 02:20:00
AC0RYM
41
0
1976-01-01 17:56:00
1976-11-11 14:35:00
I guess they are behind as show by this from the Website. Horrible.
Outlook LT Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb
|
On 2025-02-02 9:32 AM, William WC2L wrote: I really should have included a reply from the ARRL: That reply is terribly out of date. Here is what they posted on January 14 (although it is somewhat optimistic): DXCC Application Processing Caught Up 01/14/2025
DXCC? application processing is back to typical processing times.
In October, we reported that the ARRL DXCC? System had been returned
to service following work that was completed to ensure the security
and integrity of the system following the cyber-attack in May. Over
4,000 DXCC applications have been logged into the system for
processing since returning the system to service.
We are currently processing applications submitted in December, and
we continue to mail orders for paper DXCC certificates and
endorsement stickers. There were 315 certificates mailed between
December 27, 2024, and January 13, 2025.
I made a "simple" DXCC application on 2024-12-27 by LotW with no new certificates or endorsement stickers and it has still not been processed. It has now five weeks plus when simple LotW applications were being processed in three days or fewer prior to the data breach. 73, ... Joe, W4TV On 2025-02-02 9:32 AM, William WC2L wrote: I really should have included a reply from the ARRL:
/Due to the ARRL cyber attack, we find ourselves with thousands of unprocessed DXCC applications. Please note we currently have a five month processing delay.
We are working on May card/paper applications and completing credit card charges for July Logbook applications. We expect these Logbook applications to be
completed in the DXCC and Logbook programs in four to five weeks. Once fully processed, your credits will be moved over in your Logbook account.
Certificates and stickers will be mailed at a later date.
Online DXCC is still unavailable, but progress is being made to restore the system.
You can obtain updates by visiting www.arrl.org under ARRL Systems Service Disruption.
For concerns other than inquiries as to your application processing date or credit cards being charged, please feel free to let me know. Take care.
/
On 2/2/2025 9:28 AM, William WC2L wrote:
LOTW is very far behind!!
Will WC2L
|
Re: Marker size on google mymaps?
Dave,
?
Thanks!? I have never heard of Perplexity but it is good to learn you confirmed the scale is ignored.
?
My action was captured by Perplexity options:? ?"- Rely on Google My Maps' automatic handling of feature visibility at different zoom levels.
?
:-)? ?
?
The map will just look ugly, with giant markers, until I zoom in.? ?Once zoomed in, it is quite nice and marker sizes are reasonable.? Fortunately, google earth provides a good zoomed out view with marker size 1 (for me and my dense set of data).??
--
Mike KM2B
|
I really should have included a
reply from the ARRL:
Due to the ARRL cyber attack,
we find ourselves with thousands of unprocessed DXCC
applications. Please note we currently have a five month
processing delay.
We are working on May card/paper applications and completing
credit card charges for July Logbook applications. We expect
these Logbook applications to be
completed in the DXCC and Logbook programs in four to five
weeks. Once fully processed, your credits will be moved over
in your Logbook account.
Certificates and stickers will be mailed at a later date.
Online DXCC is still unavailable, but progress is being made
to restore the system.
You can obtain updates by visiting under ARRL
Systems Service Disruption.
For concerns other than inquiries as to your application
processing date or credit cards being charged, please feel
free to let me know. Take care.
On 2/2/2025 9:28 AM, William WC2L
wrote:
LOTW is very far behind!!
Will WC2L
On 2/2/2025 7:53 AM, Gilbert Baron
W0MN via groups.io wrote:
Not sure if missing something with new
sync methods or if LOTW is just behind. Looking at status
the latest LotW Sent is Y and date of latest QSO (not
necessarily confirmed, some just received and shown as a QSO
on a LOTW Query is WAY BACK at Dec 4 2024.
?
It seems that a QSO that old that is
shown as Sent in DXKeeper should have the date sent and date
received showing in the log page unless L:oTW is up to date.
?
If I go to ARRL LotW query page the lates
QSO shown is Dec 4
That agrees with DXKeeper
?
All QSOes sent from DXKeeper show R for
sent but the Date sent item Shows none after Dec 4.
?
?
Am I missing something or is LoTW really
that far behind?? I suspect I am missing something here with
my DXKeeper operation.
?
Outlook
LT Gil W0MN
Hierro
Candente Batir de Repente
44.08226
N 92.51265 W EN34rb
?
?
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP
Laptop
--
William Liporace WC2L
or
AR-Cluster Node telnet dxc.wc2l.com 7373 or 144.93 MHz
wc2l@...
--
William Liporace WC2L
or
AR-Cluster Node telnet dxc.wc2l.com 7373 or 144.93 MHz
wc2l@...
|
LOTW is very far behind!!
Will WC2L
On 2/2/2025 7:53 AM, Gilbert Baron W0MN
via groups.io wrote:
Not sure if missing something with new sync
methods or if LOTW is just behind. Looking at status the
latest LotW Sent is Y and date of latest QSO (not necessarily
confirmed, some just received and shown as a QSO on a LOTW
Query is WAY BACK at Dec 4 2024.
?
It seems that a QSO that old that is shown
as Sent in DXKeeper should have the date sent and date
received showing in the log page unless L:oTW is up to date.
?
If I go to ARRL LotW query page the lates
QSO shown is Dec 4
That agrees with DXKeeper
?
All QSOes sent from DXKeeper show R for
sent but the Date sent item Shows none after Dec 4.
?
?
Am I missing something or is LoTW really
that far behind?? I suspect I am missing something here with
my DXKeeper operation.
?
Outlook
LT Gil W0MN
Hierro
Candente Batir de Repente
44.08226
N 92.51265 W EN34rb
?
?
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP
Laptop
--
William Liporace WC2L
or
AR-Cluster Node telnet dxc.wc2l.com 7373 or 144.93 MHz
wc2l@...
|
This listing shows the number of QSOs you have uploaded and the number of matches (QSLs) each of your call signs. It also shows the oldest and newest QSO date for each call sign. Call Sign | # QSOs | # QSLs | Oldest | Newest | W0MN | 10,229 | 4,455 | 1953-12-27 18:30:00 | 2024-12-04 19:59:56 | W0RYM | 1,105 | 3 | 1953-12-27 18:30:00 | 1978-11-05 02:20:00 | AC0RYM | 41 | 0 | 1976-01-01 17:56:00 | 1976-11-11 14:35:00 |
? ? ? I guess they are behind as show by this from the Website. Horrible. ? ? Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Gilbert Baron W0MN via groups.io
Sent: Sunday, February 2, 2025 6:53 AM
To: [email protected]
Subject: [DXLab] LOTW confirmations? Not sure if missing something with new sync methods or if LOTW is just behind. Looking at status the latest LotW Sent is Y and date of latest QSO (not necessarily confirmed, some just received and shown as a QSO on a LOTW Query is WAY BACK at Dec 4 2024. ? It seems that a QSO that old that is shown as Sent in DXKeeper should have the date sent and date received showing in the log page unless L:oTW is up to date. ? If I go to ARRL LotW query page the lates QSO shown is Dec 4 That agrees with DXKeeper ? All QSOes sent from DXKeeper show R for sent but the Date sent item Shows none after Dec 4. ? ? Am I missing something or is LoTW really that far behind?? I suspect I am missing something here with my DXKeeper operation. ? Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb ? ?
--
W0MN EN34rb 44.08226 N 92.51265 W Hierro candente, batir de repente HP Laptop -- W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
|
Not sure if missing something with new sync methods or if LOTW is just behind. Looking at status the latest LotW Sent is Y and date of latest QSO (not necessarily confirmed, some just received and shown as a QSO on a LOTW Query is WAY BACK at Dec 4 2024. ? It seems that a QSO that old that is shown as Sent in DXKeeper should have the date sent and date received showing in the log page unless L:oTW is up to date. ? If I go to ARRL LotW query page the lates QSO shown is Dec 4 That agrees with DXKeeper ? All QSOes sent from DXKeeper show R for sent but the Date sent item Shows none after Dec 4. ? ? Am I missing something or is LoTW really that far behind?? I suspect I am missing something here with my DXKeeper operation. ? Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb ? ? -- W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
|
Re: Marker size on google mymaps?
+ AA6YQ comments below
If you find a way to control the scale in Google MyMaps, please let me know.
I asked Perplexity (a free AI search engine) how to control the scale of KML files plotted on MyMaps; its response is appended below. Note the citations at the end of the response. ? ? ? 73, ? ? ? ? ? ?Dave, AA6YQ
KML files plotted on Google My Maps do not have a direct "scale" parameter like in Google Earth. Instead, the visibility and appearance of KML elements in Google My Maps are primarily controlled by the zoom level of the map[5].
In Google My Maps:
1. The zoom level determines what features are visible, similar to how scale works in traditional maps.
2. Features become visible or hidden as you zoom in or out, but this is not directly controlled by a scale parameter in the KML file[4].
3. The size and detail of features adjust automatically based on the current zoom level of the map.
4. Unlike Google Earth, which uses regions and Level of Detail (LoD) elements for scale-dependent rendering[3][4], Google My Maps does not support these KML-specific visibility controls.
5. Google My Maps automatically handles the rendering and visibility of KML features based on its own internal logic, which is optimized for web-based map viewing[9].
To control the appearance of KML features in Google My Maps, you may need to:
- Split large datasets into smaller, more manageable KML files[9].
- Use styling elements within the KML to control the appearance of features.
- Rely on Google My Maps' automatic handling of feature visibility at different zoom levels.
It's important to note that Google My Maps has limitations on the size and complexity of KML files it can handle effectively, so very large datasets may require alternative approaches or simplification[8][9].
Citations:
[1] https://cloud.google.com/looker/docs/reference/param-lookml-dashboard-google-maps
[2] https://developers.google.com/maps/documentation/maps-static/start
[3] https://gis.stackexchange.com/questions/416803/google-earth-is-there-a-way-to-create-a-kml-with-scale-dependent-visibility
[4] https://gis.stackexchange.com/questions/20160/is-it-possible-to-do-scale-dependent-rendering-in-google-maps-with-kml
[5] https://gis.stackexchange.com/questions/7430/what-ratio-scales-do-google-maps-zoom-levels-correspond-to
[6] https://www.spatialmanager.com/new-altitude-parameters-kmlkmz-google-earth-provider/
[7] https://stackoverflow.com/questions/12308424/change-the-size-of-all-markers-of-a-kml-file-with-api-google
[8] https://developers.google.com/earth-engine/guides/scale
[9] https://stackoverflow.com/questions/22664745/kml-scalability-plotting-hundred-thousands-of-gps-points-in-kml
[10] https://developers.google.com/maps/documentation/javascript/kmllayer?hl=en
---
Answer from Perplexity: pplx.ai/share
|
Re: Marker size on google mymaps?
+ AA6YQ comments below
Google Earth IS sensitive to the scale parameter in the kml file.?
+ Yes, that's why DXView uses it to control the scale in Google Earth.
?
I made two otherwise identical kml files, one with scale 1 and the other with scale 4.? ?The results indicate that with each zoom level:
?
Google MyMaps is entirely insensitive to the scale value, unlike google earth.? ?All layers look identical independent of the scale value in the kml.
?
+ If you find a way to control the scale in Google MyMaps, please let me know. ? ? ? 73, ? ? ? ? ? ? Dave, AA6YQ
|
Re: Marker size on google mymaps?
Dave,
?
Google Earth IS sensitive to the scale parameter in the kml file.? ?But....
?
I made two otherwise identical kml files, one with scale 1 and the other with scale 4.? ?The results indicate that with each zoom level:
?
Google MyMaps is entirely insensitive to the scale value, unlike google earth.? ?All layers look identical independent of the scale value in the kml.
?
Apology:? Should have done that test first before posting.? ?
?
Thanks Dave.
--
Mike KM2B
|
Re: Filter Spots by Propagation?
Band filter and set the appropriate start/end UTC times.
I typically use something like SS-90 for start and SR+90
for end (on 40/30) but you can adjust that for your QTH.
73,
... Joe, W4TV
toggle quoted message
Show quoted text
On 2025-02-01 1:33 PM, Jim Miller - AB3CV via groups.io wrote: Since beginning to chase WAZ I get a lot of spots on 40m for R0*** (typ. zone 18) during the time of day when propagation (Min Useable Freq) makes that a non starter. Is there a way to filter these out so I don't get alerts on them?
Thanks
Jim ab3cv
|
Re: Filter Spots by Propagation?
Yes, you can do that. ?See the link below.
toggle quoted message
Show quoted text
On Feb 1, 2025, at 12:33 PM, Jim Miller - AB3CV via < jtmiller47@...> wrote: Since beginning to chase WAZ I get a lot of spots on 40m for R0*** (typ. zone 18) during the time of day when propagation (Min Useable Freq) makes that a non starter. Is there a way to filter these out so I don't get alerts on them?
?
Thanks
?
Jim ab3cv
|
Filter Spots by Propagation?
Since beginning to chase WAZ I get a lot of spots on 40m for R0*** (typ. zone 18) during the time of day when propagation (Min Useable Freq) makes that a non starter. Is there a way to filter these out so I don't get alerts on them?
?
Thanks
?
Jim ab3cv
|
Updated DARC DOK award list
Carlo IK2RPE has updated the award list that DXKeeper uses to populate its DOK award selectors - if you have the "DARC DOK region selection" box checked in the "Other Awards" panel on the Awards tab of DXKeeper's Configuration window.
For immediate access to this updated list,
1. terminate DXKeeper
2. download the file from
into DXKeeper's Databases folder, replacing the existing file with the same name
3. start DXKeeper
This updated award list will be included with the next public version of DXKeeper.
Thanks, Carlo!
? ? ? ? ?73,
? ? ? ? ? ? ? ? Dave, AA6YQ
|
Re: Recompute results-73 QSOs with "Broken ARRL Section"
+ AA6YQ comments below
That’s pretty interesting. So the Alt/Recompute button must correlate with the LOTW data to show the correct ARRL section?
+ No, LoTW doesn't report ARRL sections. For the Continental US, Alaska, and Hawaii, DXKeeper's Secondary Subdivision Database contains all Counties. For Counties in States with multiple ARRL section, each County specifies its ARRL section.
If so, that’s another pretty deep little facet to this already comprehensive program. Does anyone have a dog-eared copy of the “DXLab for Dummies” book? I need to borrow it…
+ My advice is contained in the opening section of
+ One-at-a-time, scan the Reference Documentation for each DXLab application your using, in whatever order you wish. Ignore details during this scan, but keep a list of functionality you'd like to explore later. When you're done scanning, prioritize the items on your "functionality to explore" list, and explorer them one at a time be returning to the Reference documentation and by searching the index to "Getting Started with DXLab" for step-by-step instructions:
+ This approach prevents burnout from attempting to grok it all in one fell swoop, and minimizes posts of the form "I wish I knew that functionality was available 3 years ago!"
73,
Dave, AA6YQ
|
Re: Recompute results-73 QSOs with "Broken ARRL Section"
That’s pretty interesting. ?So the Alt/Recompute button must correlate with the LOTW data to show the correct ARRL section? ?If so, that’s another pretty deep little facet to this already comprehensive program. ?Does anyone have a dog-eared copy of the “DXLab for Dummies” book? ?I need to borrow it…
Steve ?K4WA
toggle quoted message
Show quoted text
On Jan 31, 2025, at 6:07?PM, Jim McPhee via groups.io <jmcphee@...> wrote:
? Dave,,
?
Thanks for your response. I did just click the Recompute button with the Alt key depressed, and the inconsistencies were changed/corrected to the one that the "ARRL Section is inconsistent with". In trying to understand where the "correct ARRL Section" was coming from, I found that most, if not all, of these QSOs were with NPOTA/POTA stations. It would appear that the "correct ARRL Section" was being derived from the park ID, or somewhere else in the QSO details? And in the dozen or so that I checked the corrections did agree with the location of the parks.
?
Thanks for sharing with me how to make those corrections, even though they may not really matter as far as awards go.
--
Jim McPhee
Placitas, NM
W5ABA
|
Re: Recompute results-73 QSOs with "Broken ARRL Section"
Dave,,
?
Thanks for your response. I did just click the Recompute button with the Alt key depressed, and the inconsistencies were changed/corrected to the one that the "ARRL Section is inconsistent with". In trying to understand where the "correct ARRL Section" was coming from, I found that most, if not all, of these QSOs were with NPOTA/POTA stations. It would appear that the "correct ARRL Section" was being derived from the park ID, or somewhere else in the QSO details? And in the dozen or so that I checked the corrections did agree with the location of the parks.
?
Thanks for sharing with me how to make those corrections, even though they may not really matter as far as awards go.
--
Jim McPhee
Placitas, NM
W5ABA
|
|
|
Can I delete, add and/or rearrange columns in Spotcollector??
|
Re: Recompute results-73 QSOs with "Broken ARRL Section"
+ AA6YQ comments below
After seeing Dave recommend another user invoke the "Recompute" function, I decided to do it as well. Result was 73 QSOs, 60 of them from 2016, flagged as ?"Broken ARRL Section". Interestingly, there are a few cases where multiple contacts with the same station resulted in different inconsistencies being reported. According to QRZ right now, N0UR is located in Steele County, MN. I do have the "Automatically recompute realtime award tracking" enabled. Should I be concerned by this, and if so, what actions should I take to remediate it?
?
| N0UR |
2016-09-17 1645 |
20M |
SSB |
291 |
United States |
Broken: |
ARRL Section MN is inconsistent with DXCC Entity K and State IA and County MN,Steele |
| N0UR |
2016-10-13 1810 |
20M |
SSB |
291 |
United States |
Broken: |
ARRL Section MN is inconsistent with DXCC Entity K and State ND and County ND,McKenzie |
| N0UR |
2016-10-15 1627 |
20M |
SSB |
291 |
United States |
Broken: |
ARRL Section MN is inconsistent with DXCC Entity K and State MT and County MT,Big Horn |
| N0UR |
2016-10-16 1552 |
20M |
SSB |
291 |
United States |
Broken: |
ARRL Section MN is inconsistent with DXCC Entity K and State SD and County SD,Jackson |
| N0UR |
2016-11-10 1737 |
20M |
SSB |
291 |
United States |
Broken: |
ARRL Section MN is inconsistent with DXCC Entity K and State WI and County WI,Polk |
?
+ In a QSO with a station in the US, Alaska, or Hawaii,? a broken ARRL Section is one that is inconsistent with its QSO's State and County. + In a QSO with a station in Canada, a broken ARRL Section is one that is inconsistent with its Province. + As stated in
"If the Alt key is depressed when the Recompute button is clicked, correctable errors in primary and secondary administrative subdivisions and in ARRL sections will be corrected and the corrections reported as Actions; for example, each inconsistent ARRL section item will be replaced with a value deduced from its QSO's DXCC entity, State, and County items."
+ While there are contests in which your QSO partner's ARRL Section is part of the exchange, I'm not aware of any awards based on ARRL Sections.
? ? ? ?73,
?
? ? ? ? ? ? ?Dave, AA6YQ
|
William WC2L
Gilbert Baron W0MN