Filtering SC for special callsigns by mode


Tim K9WX
 

I have been using the “Identifying Special Callsigns” feature (http://dxlabsuite.com/spotcollector/Help/ConfigurationSpecialCallsigns.htm) of SpotCollector with good success, but I wonder if there is some beneficial additional functionality available that I am missing.

 

I would like SC to display the callsigns of CWops members that I have yet to work on a given band, but only for the CW mode, in pursuit of CWops awards, along with any spots relevant to my DXCC or Challenge objectives without regard to band or mode.

 

Using the CWops roster as the Leaderboard special callsign list, I can display spots for all CWops members on unworked bands along with spots needed for DXCC or Challenge objectives, but the spot database display shows this for all modes and not just CW.  So, in the case of CWops members, I end up seeing many spots for modes that are not of interest.

 

If I invoke the Mode filter and set it for CW, then SC displays only the needed entries for CW, which works fine for the CWops awards, but I will miss other desirable entries such as an ATNO on FT8.

 

The ideal solution would be to allow me to further filter the Leaderboard spot displays by mode so that it contributes only the CWops counters that I need to the display, in conjunction with the display of other spots I need for DXCC and Challenge goals regardless of mode.

 

Is there a way to do this in the existing program?

 

Tim K9WX


Dave AA6YQ
 

I have been using the “Identifying Special Callsigns” feature (http://dxlabsuite.com/spotcollector/Help/ConfigurationSpecialCallsigns.htm) of SpotCollector with good success, but I wonder if there is some beneficial additional functionality available that I am missing.

I would like SC to display the callsigns of CWops members that I have yet to work on a given band, but only for the CW mode, in pursuit of CWops awards, along with any spots relevant to my DXCC or Challenge objectives without regard to band or mode.

Using the CWops roster as the Leaderboard special callsign list, I can display spots for all CWops members on unworked bands along with spots needed for DXCC or Challenge objectives, but the spot database display shows this for all modes and not just CW. So, in the case of CWops members, I end up seeing many spots for modes that are not of interest.

If I invoke the Mode filter and set it for CW, then SC displays only the needed entries for CW, which works fine for the CWops awards, but I will miss other desirable entries such as an ATNO on FT8.

The ideal solution would be to allow me to further filter the Leaderboard spot displays by mode so that it contributes only the CWops counters that I need to the display, in conjunction with the display of other spots I need for DXCC and Challenge goals regardless of mode.

Is there a way to do this in the existing program?

+ Yes. Assuming that the tag you've specified for CWops members in the "Special Callsign List" is

cwops

+ use this SQL expression

<NEEDFILTER> or ((TAGS like '*<cwops>*') and (MODE='CW'))

+ The necessary capabilities are described in

https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#Filtering%20with%20SQL%20expressions

73,

Dave, AA6YQ


iain macdonnell - N6ML
 



On Fri, Apr 23, 2021 at 11:16 AM Dave AA6YQ <aa6yq@...> wrote:
I have been using the “Identifying Special Callsigns” feature (http://dxlabsuite.com/spotcollector/Help/ConfigurationSpecialCallsigns.htm) of SpotCollector with good success, but I wonder if there is some beneficial additional functionality available that I am missing.

I would like SC to display the callsigns of CWops members that I have yet to work on a given band, but only for the CW mode, in pursuit of CWops awards, along with any spots relevant to my DXCC or Challenge objectives without regard to band or mode.

Using the CWops roster as the Leaderboard special callsign list, I can display spots for all CWops members on unworked bands along with spots needed for DXCC or Challenge objectives, but the spot database display shows this for all modes and not just CW.  So, in the case of CWops members, I end up seeing many spots for modes that are not of interest.

If I invoke the Mode filter and set it for CW, then SC displays only the needed entries for CW, which works fine for the CWops awards, but I will miss other desirable entries such as an ATNO on FT8.

The ideal solution would be to allow me to further filter the Leaderboard spot displays by mode so that it contributes only the CWops counters that I need to the display, in conjunction with the display of other spots I need for DXCC and Challenge goals regardless of mode.

Is there a way to do this in the existing program?

+ Yes. Assuming that the tag you've specified for CWops members in the "Special Callsign List" is

cwops

+ use this SQL expression

<NEEDFILTER> or ((TAGS like '*<cwops>*') and (MODE='CW'))

That doesn't solve the problem, which was to show only CWOps members *on CW, who have not been worked before on CW* (but also show other stations who are Needed on other modes).

I can't think of any way to do it with SpotCollector's current capabilities....

73,

    ~iain / N6ML


 


Dave AA6YQ
 

@ AA6YQ comments below

I have been using the “Identifying Special Callsigns” feature (http://dxlabsuite.com/spotcollector/Help/ConfigurationSpecialCallsigns.htm) of SpotCollector with good success, but I wonder if there is some beneficial additional functionality available that I am missing.

I would like SC to display the callsigns of CWops members that I have yet to work on a given band, but only for the CW mode, in pursuit of CWops awards, along with any spots relevant to my DXCC or Challenge objectives without regard to band or mode.

Using the CWops roster as the Leaderboard special callsign list, I can display spots for all CWops members on unworked bands along with spots needed for DXCC or Challenge objectives, but the spot database display shows this for all modes and not just CW. So, in the case of CWops members, I end up seeing many spots for modes that are not of interest.

If I invoke the Mode filter and set it for CW, then SC displays only the needed entries for CW, which works fine for the CWops awards, but I will miss other desirable entries such as an ATNO on FT8.

The ideal solution would be to allow me to further filter the Leaderboard spot displays by mode so that it contributes only the CWops counters that I need to the display, in conjunction with the display of other spots I need for DXCC and Challenge goals regardless of mode.

Is there a way to do this in the existing program?

+ Yes. Assuming that the tag you've specified for CWops members in the "Special Callsign List" is

cwops

+ use this SQL expression

<NEEDFILTER> or ((TAGS like '*<cwops>*') and (MODE='CW'))


That doesn't solve the problem, which was to show only CWOps members *on CW, who have not been worked before on CW* (but also show other stations who are Needed on other modes).

@ The stated desire is "display the callsigns of CWops members that I have yet to work on a given band, but only for the CW mode"

I can't think of any way to do it with SpotCollector's current capabilities....

@ On the Configuration window's "Spot Database" tab, check the Controls panel's "Maintain DXCC entity-band-mode fields" box, and then click the Recomputation panel's Recompute button.

@ Then use this SQL expression:

<NEEDFILTER> or ((TAGS like '*<cwops>*') and (MODE='CW') and (BandModeWorked='N'))

@ This will limit the display of active CWOPs stations (not otherwise needed) to those that haven't been worked in CW on the spotted band.

@ Note that enabling the "Maintain DXCC entity-band-mode fields" option will increase SpotCollector's resource consumption, as it will more frequently query the log file in order to keep each Spot Database Entry's BandModeWorked field up to date.

73,

Dave, AA6YQ


Tim K9WX
 

Thanks, Dave.  Would there be a corresponding SQL expression that would limit the display of active CWops stations to those that haven't been worked on CW this calendar year, regardless of band?

Tim K9WX


On Fri, Apr 23, 2021 at 09:14 PM, Dave AA6YQ wrote:
@ Then use this SQL expression:

<NEEDFILTER> or ((TAGS like '*<cwops>*') and (MODE='CW') and (BandModeWorked='N'))

@ This will limit the display of active CWOPs stations (not otherwise needed) to those that haven't been worked in CW on the spotted band.


Dave AA6YQ
 

+ AA6YQ comments below
Would there be a corresponding SQL expression that would limit the display of active CWops stations to those that haven't been worked on CW this calendar year, regardless of band?

+ The SQL expression

((TAGS like '*<cwops>*') and (MODE='CW') and (ModeWorked='N'))

+ Will identify active CWops stations never before worked on CW. There is no way to implement the "not worked on CW this calendar year" constraint in an unchanging SQL expression.

+ How many CWOps stations are there?

       73,

            Dave, AA6YQ

 


Tim K9WX
 

The current CWops roster has just under 2500 calls, although a few of them are duplicates as some members have more than one call.

Tim K9WX


Dave AA6YQ
 

+ AA6YQ comments below

The current CWops roster has just under 2500 calls, although a few of them are duplicates as some members have more than one call.

+ Thanks. I suspect that's too many for a simple filter like

(MODE='CW') and (CALLSIGN in ('VK9NS', 'OH2BH','P5DX', ....))

+ which you would edit each time you log a QSO with a CWOPs member.

73,

Dave, AA6YQ


Dave AA6YQ
 

# More AA6YQ comments bewlo
+ AA6YQ comments below

The current CWops roster has just under 2500 calls, although a few of them are duplicates as some members have more than one call.

+ Thanks. I suspect that's too many for a simple filter like

(MODE='CW') and (CALLSIGN in ('VK9NS', 'OH2BH','P5DX', ....))

+ which you would edit each time you log a QSO with a CWOPs member.

# You could use this SQL expression

((TAGS like '*<cwops>*') and (MODE='CW'))

# if after logging a CW QSO with a cwops station whose callsign is X, you were willing to immediately edit SpotCollector's Special Callsign List entry for X to change its tag from cwops to workedcwops.

   73,

         Dave, AA6YQ