Difference between revisions of "Accept filters"

From DXSpider Documentation Wiki
Jump to: navigation, search
(New page: �[1m7. Accept filters�[0m An accept filter line means that if a spot matches pass it on to the user, send it down the line to the next rule or to the user, and trash, dump, all o...)
 
 
Line 1: Line 1:
�[1m7.  Accept filters�[0m
+
=Accept filters=
  
An accept filter line means that if a spot matches pass it on to the
+
An accept filter line means that if a spot matches pass it on to the user, send it down the line to the next rule or to the user, and trash, dump, all other spots that do not match to the next filter line.
user, send it down the line to the next rule or to the user, and
+
trash, dump, all other spots that do not match to the next filter
+
line.
+
  
 +
Syntax: accept/spots [0-9]  <pattern>
  
      Syntax: accept/spots [0-9]  <pattern>
+
Any of the following patterns may be used in this line ...
  
 +
freq <range>
 +
on <range>
 +
info <string>
 +
call <prefixes>
 +
call_dxcc <numbers>
 +
call_itu <numbers>
 +
call_zone <numbers>
 +
call_state <state2-letter abbreviations>
 +
by <prefixes>
 +
by_dxcc <numbers>
 +
by_itu <numbers>
 +
by_zone <numbers>
 +
by_state <state2-letter abbreviations>
 +
origin <prefixes>  Used primarily be SYSOPS,  not by users and not discussed.
 +
channel <prefixes> Used primarily be SYSOPS,  not by users and not discussed.
  
Any of the following patterns may be used in this line ...
+
Using these patterns, we can accept spots based upon ...
  
 +
*Frequency of the spot
 +
*Callsign of the spot (country or zone)
 +
*Callsign of the spotter (country or zone)
 +
*Contents of the "information field" which comes with the spot
  
      freq <range>
+
==Filters to accept spots based on frequency==
      on <range>
+
      info <string>
+
      call <prefixes>
+
      call_dxcc <numbers>
+
      call_itu <numbers>
+
      call_zone <numbers>
+
      call_state <state2-letter abbreviations>
+
      by <prefixes>
+
      by_dxcc <numbers>
+
      by_itu <numbers>
+
      by_zone <numbers>
+
      by_state <state2-letter abbreviations>
+
      origin <prefixes>  Used primarily be SYSOPS,  not by users and not discussed.
+
      channel <prefixes> Used primarily be SYSOPS,  not by users and not discussed.
+
  
 +
Syntax: accept/spot [0-9] freq <range>
  
Using these patterns, we can accept spots based upon ...
+
or
  
 +
accept/spot [0-9] on <range>
  
      Frequency of the spot
+
'''Important:''' as noted before, both '''freq''' and '''on''' are exactly the same and can be used interchangeably.
      Callsign of the spot (country or zone)
+
      Callsign of the spotter (country or zone)
+
      Contents of the "information field" which comes with the spot
+
  
 +
For range, you can specify a frequency like 7040, a range of frequencies like 0/30000 ( the whole HF spectrum) or use any of the band/region names defined in the SHOW/BANDS command (see above).
  
�[1m7.1. Filters to accept spots based on frequency�[0m
+
Examples...
  
 +
This will pass on a HF spots only from 0 to 30,000 kHz and dump all others.
  
      Syntax: accept/spot [0-9] freq <range>
+
accept/spot 1 on 0/30000
  
      or
+
This passes on all spots in the frequency range 144000 -> 148000 kHz and trash all others.
  
      accept/spot [0-9] on <range>
+
accept/spot 2 freq 2m
  
 +
This rule will only pass on spots on 6m, 4m, 2m, and 220 and reject all others.
  
  Important: as noted before, both �[4mfreq�[24m and �[4mon�[24m are exactly the same and
+
  accept/spot 3 on vhf
can be used interchangeably.
+
  
 +
This rule will pass on all spots on the 160m, 80m, 60m, 40m, 30m, 20m, 17m, 15m, 12m, 10m bands and all spots on 70cm and 23cm bands only. All other spots are trashed.
  
  For range, you can specify a frequency like 7040, a range of
+
  accept/spot 4 freq hf and freq uhf
frequencies like 0/30000 ( the whole HF spectrum) or use any of the
+
band/region names defined in the SHOW/BANDS command (see above).
+
  
 +
==Sub-bands as part of range==
  
Examples...
+
In conjunction with range, you can use the following sub-band names: CW, RTTY, DATA, SSB, and SSTV by using a back-slash [(band or region)/sub-band] as part of the range definition.
  
 +
Examples ...
  
This will pass on a HF spots only from 0 to 30,000 kHz and dump all
+
This rule will only accept and pass on HF phone spots rejecting all others
others.
+
  
 +
accept/spot 0 freq hf/ssb
  
      accept/spot 1 on 0/30000
+
This filter rule will accept all HF CW spots but will not include DATA and RTTY spots in the CW range. In addition all other spots will be dumped.
  
 +
accept/spot 1 on hf/cw and not (on hf/data or on hf/rtty)
  
This passes on all spots in the frequency range 144000 -> 148000 kHz
+
==Filters to accept spots based on info==
and trash all others.
+
  
 +
Syntax: accept/spot [0-9] info <string>
  
      accept/spot 2 freq 2m
+
This filter is used to key on information contained in the information section of the spot. One could use this to accept any spots containing IOTA, QSL OP or any other "key-word" used in the information string of the spot.
  
 +
Examples ...
  
This rule will only pass on spots on 6m, 4m, 2m, and 220 and reject
+
This filter will accept spots containing IOTA information only and reject all others
all others.
+
  
 +
accept/spot 0 info IOTA
  
      accept/spot 3 on vhf
+
This filter will accept only 10m SSB spots, but will still permit any spots that contain iota information in addition - rejecting all other spots.
  
 +
accept/spot 1 on 10m/ssb and info iota
  
This rule will pass on all spots on the 160m, 80m, 60m, 40m, 30m, 20m,
+
This next filter will accept spots asking or containing QSL information and dump all other spots
17m, 15m, 12m, 10m bands and all spots on 70cm and 23cm bands only.
+
All other spots are trashed.
+
  
 +
accept/spot 2 info QSL
  
      accept/spot 4 freq hf and freq uhf
+
'''Note:''' The following series of filters are based on '''call''' and '''by'''.  Call always references the callsign of the spotted DX station.  By always references the callsign of the spotting station.
  
 +
==Filters to accept spots based on call==
  
  [1m7.2.  Sub-bands as part of range�[0m
+
  Syntax: accept/spot [0-9] call <prefixes>
  
In conjunction with range, you can use the following sub-band names:
+
This filter is misleading in a way. It is strictly based on the spotted call sign letters or numbers entered and not based on countries or DXCC entities.
CW, RTTY, DATA, SSB, and SSTV by using a back-slash [(band or
+
region)/sub-band] as part of the range definition.
+
  
 +
Examples ...
  
Examples ...
+
This filter will accept spots for G1AAA, GJ2BBB, and GW3CCC and reject all others, including M0AAA.
  
 +
accept/spot 0 call G
  
This rule will only accept and pass on HF phone spots rejecting all
+
This next filter will accept spots for PA3AAA and reject spots for PB4BBB as well as all others.
others
+
  
 +
accept/spot 1 call PA
  
      accept/spot 0 freq hf/ssb
+
This filter will accept spots for callsigns beginning with "K", i.e. K1AA, KC4AAA,  KH6DDD and reject spots for W3BG and N3RD as well as all other spots.
  
 +
accept/spot 2 call K
  
This filter rule will accept all HF CW spots but will not include DATA
+
==Filters to accept spots based on call_dxcc==
and RTTY spots in the CW range. In addition all other spots will be
+
dumped.
+
  
 +
Syntax:  accept/spot [0-9] call_dxcc <numbers or prefixes>
  
      accept/spot 1 on hf/cw and not (on hf/data or on hf/rtty)
+
This filter is based on DXCC entities and uses either the country prefixes or the DXCC entity number found by using the command show/prefix. See example of show/prefix above.
  
 +
Examples ...
  
  �[1m7.3.  Filters to accept spots based on info�[0m
+
  accept/spot 0 call_dxcc 226,197
  
 +
or
  
      Syntax: accept/spot [0-9] info <string>
+
accept/spot 0 call_dxcc ve,w
  
 +
(Both will work) These spot filters will accept all spots for US and Canada stations and trash all others.
  
This filter is used to key on information contained in the information
+
The following spot filter will accept all spots for US stations and yet reject any spots for W3FM who is always being spotted by Europeans and filling up my screen.
section of the spot. One could use this to accept any spots containing
+
IOTA, QSL OP or any other "key-word" used in the information string of
+
the spot.
+
  
 +
accept/spot 1 call_dxcc w not call w3fm
  
Examples ...
+
==Filters to accept spots based on call_itu==
  
 +
Similarly, call_itu and call_zone use ITU regions that can also be obtained using the show/prefix command (see above.)
  
  This filter will accept spots containing IOTA information only and
+
  Syntax: accept/spot [0-9] call_itu <numbers>
  reject all others
+
  
      accept/spot 0 info IOTA
+
Example ...
  
 +
This spot filter will  accept all spots for  ITU region 7 and reject all others.
  
  This filter will accept only 10m SSB spots, but will still permit any
+
  accept/spot 0 call_itu 7
  spots that contain iota information in addition - rejecting all other
+
spots.
+
  
 +
==Filters to accept spots based on call_zone==
  
      accept/spot 1 on 10m/ssb and info iota
+
Syntax:  accept/spot [0-9] call_zone <numbers>
  
 +
This filter is based on CQ zones and uses the CQ zone number found by using the command show/prefix (see above.)
  
This next filter will accept spots asking or containing QSL
+
Example ...
information and dump all other spots
+
  
 +
This spot filter will  accept all spots for CQ zone 5 and reject all others.
  
      accept/spot 2 info QSL
+
accept/spot 0 call_zone 5
  
 +
==Filters to accept spots based on call_state==
  
  Note: The following series of filters are based on �[4mcall�[24m and �[4mby�[24m.  Call
+
  Syntax: accept/spot [0-9] call_state <state2-letter postal codes>
always references the callsign of the spotted DX station.  By always
+
references the callsign of the spotting station.
+
  
 +
This filter is based on state of the call spotted for those callsigns contained in the usdb database.
  
�[1m7.4. Filters to accept spots based on call�[0m
+
Example ...
  
 +
This spot filter will  accept all spots of stations located in the Commonwealth of Pennsylvania and reject all others. It's the PA QSO Party Weekend.
  
      Syntax: accept/spot [0-9] call <prefixes>
+
accept/spot 0 call_state pa
  
 +
==Filters to accept spots based on by==
  
This filter is misleading in a way. It is strictly based on the
+
'''by''' filters are similar to and function exactly as call filters except that they act on the spotting station callsign and not the spotted callsign
spotted call sign letters or numbers entered and not based on
+
countries or DXCC entities.
+
  
 +
So ...
  
  Examples ...
+
This filter is similar to and functions like the call <prefixes> (See above) except that it accepts spots generated by the spotting callsign and dumps all other spots.
  
 +
Syntax: accept/spot [0-9] by <prefixes>
  
This filter will accept spots for G1AAA, GJ2BBB, and GW3CCC and reject
+
This filter is based on DXCC entities and uses the DXCC entity number found by using the command show/prefix and it accepts spots generated within the spotting DXCC entity and rejects other spots.
all others, including M0AAA.
+
  
 +
Syntax:  accept/spot [0-9] by_dxcc <numbers>
  
      accept/spot 0 call G
+
This next filter is based on ITU regions and uses the ITU region number found by using the command show/prefix (see above), except that it accepts spots generated by a spotting callsign within the ITU region and rejects all other spots.
  
 +
Syntax:  accept/spot [0-9] call_itu <numbers>
  
This next filter will accept spots for PA3AAA and reject spots for
+
This filter is based on CQ zones and uses the CQ zone number found by using the command show/prefix (see above), except that it accepts spots generated by a spotting callsign within the CQ zone and rejects all other spots.
PB4BBB as well as all others.
+
  
 +
Syntax:  accept/spot [0-9] call_zone <numbers>
  
      accept/spot 1 call PA
+
This filters is based on the state location of the spotting station found by using the command show/usdb and accepts only those spots generated by stations from the states(s) specified rejecting all other spots.
  
 
+
  Syntax:  accept/spot [0-9] by_state <state2-letter postal codes>
  This filter will accept spots for callsigns beginning with "K", i.e.,
+
K1AA, KC4AAA,  KH6DDD and reject spots for W3BG and N3RD as well as
+
all other spots.
+
 
+
 
+
      accept/spot 2 call K
+
 
+
 
+
�[1m7.5.  Filters to accept spots based on call_dxcc�[0m
+
 
+
 
+
      Syntax:  accept/spot [0-9] call_dxcc <numbers or prefixes>
+
 
+
 
+
This filter is based on DXCC entities and uses either the country
+
prefixes or the DXCC entity number found by using the command
+
�[4mshow/prefix�[24m. See example of �[4mshow/prefix�[24m above.
+
 
+
 
+
Examples ...
+
 
+
 
+
      accept/spot 0 call_dxcc 226,197
+
 
+
      or
+
 
+
      accept/spot 0 call_dxcc ve,w
+
 
+
 
+
(Both will work) These spot filters will accept all spots for US and
+
Canada stations and trash all others.
+
 
+
 
+
The folowing spot filter will accept all spots for US stations and yet
+
reject any spots for W3FM who is always being spotted by Europeans and
+
filling up my screen.
+
 
+
 
+
      accept/spot 1 call_dxcc w not call w3fm
+
 
+
 
+
�[1m7.6.  Filters to accept spots based on call_itu�[0m
+
 
+
Similarly, call_itu and call_zone use ITU regions that can also be
+
obtained using the �[4mshow/prefix�[24m command (see above.)
+
 
+
 
+
      Syntax:  accept/spot [0-9] call_itu <numbers>
+
 
+
 
+
Example ...
+
 
+
 
+
This spot filter will  accept all spots for  ITU region 7 and reject
+
all others.
+
 
+
 
+
      accept/spot 0  call_itu 7
+
 
+
 
+
�[1m7.7.  Filters to accept spots based on call_zone�[0m
+
 
+
 
+
      Syntax:  accept/spot [0-9] call_zone <numbers>
+
 
+
 
+
This filter is based on CQ zones and uses the CQ zone number found by
+
using the command �[4mshow/prefix�[24m (see above.)
+
 
+
 
+
Example ...
+
 
+
 
+
This spot filter will  accept all spots for CQ zone 5 and reject all
+
others.
+
 
+
 
+
      accept/spot 0 call_zone 5
+
 
+
 
+
�[1m7.8.  Filters to accept spots based on call_state�[0m
+
 
+
 
+
      Syntax:  accept/spot [0-9] call_state <state2-letter postal codes>
+
 
+
 
+
This filter is based on state of the call spotted for those callsigns
+
contained in the usdb database.
+
 
+
 
+
Example ...
+
 
+
 
+
This spot filter will  accept all spots of stations located in the
+
Commonwealth of Pennsylvania and reject all others. It's the PA QSO
+
Party Weekend.
+
 
+
 
+
      accept/spot 0  call_state pa
+
 
+
 
+
�[1m7.9.  Filters to accept spots based on by�[0m
+
 
+
�[4mby�[24m filters are similar to and function exactly as call filters except
+
that they act on the spotting station callsign and not the spotted
+
callsign
+
 
+
 
+
So ...
+
 
+
 
+
This filter is similar to and functions like the  call <prefixes> (See
+
above) except that it accepts spots generated by the spotting callsign
+
and dumps all other spots.
+
 
+
 
+
      Syntax: accept/spot [0-9] by <prefixes>
+
 
+
 
+
This filter is based on DXCC entities and uses the DXCC entity number
+
found by using the command �[4mshow/prefix�[24m and it accepts spots generated
+
within the spotting DXCC entity and rejects other spots.
+
 
+
 
+
      Syntax:  accept/spot [0-9] by_dxcc <numbers>
+
 
+
 
+
This next filter is based on ITU regions and uses the ITU region
+
number found by using the command �[4mshow/prefix�[24m (see above), except that
+
it accepts spots generated by a spotting callsign within the ITU
+
region and rejects all other spots.
+
 
+
 
+
      Syntax:  accept/spot [0-9] call_itu <numbers>
+
 
+
 
+
This filter is based on CQ zones and uses the CQ zone number found by
+
using the command �[4mshow/prefix�[24m (see above), except that it accepts
+
spots generated by a spotting callsign within the CQ zone and rejects
+
all other spots.
+
 
+
 
+
      Syntax:  accept/spot [0-9] call_zone <numbers>
+
 
+
 
+
This filters is based on the state location of the spotting station
+
found by using the command �[4mshow/usdb�[24m and accepts only those spots
+
generated by stations from the states(s) specified rejecting all other
+
spots.
+
 
+
 
+
      Syntax:  accept/spot [0-9] by_state <state2-letter postal codes>
+

Latest revision as of 14:39, 18 December 2008

Accept filters

An accept filter line means that if a spot matches pass it on to the user, send it down the line to the next rule or to the user, and trash, dump, all other spots that do not match to the next filter line.

Syntax: accept/spots [0-9]  <pattern>

Any of the following patterns may be used in this line ...

freq <range>
on <range>
info <string>
call <prefixes>
call_dxcc <numbers>
call_itu <numbers>
call_zone <numbers>
call_state <state2-letter abbreviations>
by <prefixes>
by_dxcc <numbers>
by_itu <numbers>
by_zone <numbers>
by_state <state2-letter abbreviations>
origin <prefixes>   Used primarily be SYSOPS,  not by users and not discussed.
channel <prefixes> Used primarily be SYSOPS,  not by users and not discussed.

Using these patterns, we can accept spots based upon ...

  • Frequency of the spot
  • Callsign of the spot (country or zone)
  • Callsign of the spotter (country or zone)
  • Contents of the "information field" which comes with the spot

Filters to accept spots based on frequency

Syntax: accept/spot [0-9] freq <range>

or

accept/spot [0-9] on <range>

Important: as noted before, both freq and on are exactly the same and can be used interchangeably.

For range, you can specify a frequency like 7040, a range of frequencies like 0/30000 ( the whole HF spectrum) or use any of the band/region names defined in the SHOW/BANDS command (see above).

Examples...

This will pass on a HF spots only from 0 to 30,000 kHz and dump all others.

accept/spot 1 on 0/30000

This passes on all spots in the frequency range 144000 -> 148000 kHz and trash all others.

accept/spot 2 freq 2m

This rule will only pass on spots on 6m, 4m, 2m, and 220 and reject all others.

accept/spot 3 on vhf

This rule will pass on all spots on the 160m, 80m, 60m, 40m, 30m, 20m, 17m, 15m, 12m, 10m bands and all spots on 70cm and 23cm bands only. All other spots are trashed.

accept/spot 4 freq hf and freq uhf

Sub-bands as part of range

In conjunction with range, you can use the following sub-band names: CW, RTTY, DATA, SSB, and SSTV by using a back-slash [(band or region)/sub-band] as part of the range definition.

Examples ...

This rule will only accept and pass on HF phone spots rejecting all others

accept/spot 0 freq hf/ssb

This filter rule will accept all HF CW spots but will not include DATA and RTTY spots in the CW range. In addition all other spots will be dumped.

accept/spot 1 on hf/cw and not (on hf/data or on hf/rtty)

Filters to accept spots based on info

Syntax: accept/spot [0-9] info <string>

This filter is used to key on information contained in the information section of the spot. One could use this to accept any spots containing IOTA, QSL OP or any other "key-word" used in the information string of the spot.

Examples ...

This filter will accept spots containing IOTA information only and reject all others

accept/spot 0 info IOTA

This filter will accept only 10m SSB spots, but will still permit any spots that contain iota information in addition - rejecting all other spots.

accept/spot 1 on 10m/ssb and info iota

This next filter will accept spots asking or containing QSL information and dump all other spots

accept/spot 2 info QSL

Note: The following series of filters are based on call and by. Call always references the callsign of the spotted DX station. By always references the callsign of the spotting station.

Filters to accept spots based on call

Syntax: accept/spot [0-9] call <prefixes>

This filter is misleading in a way. It is strictly based on the spotted call sign letters or numbers entered and not based on countries or DXCC entities.

Examples ...

This filter will accept spots for G1AAA, GJ2BBB, and GW3CCC and reject all others, including M0AAA.

accept/spot 0 call G

This next filter will accept spots for PA3AAA and reject spots for PB4BBB as well as all others.

accept/spot 1 call PA

This filter will accept spots for callsigns beginning with "K", i.e. K1AA, KC4AAA, KH6DDD and reject spots for W3BG and N3RD as well as all other spots.

accept/spot 2 call K

Filters to accept spots based on call_dxcc

Syntax:  accept/spot [0-9] call_dxcc <numbers or prefixes>

This filter is based on DXCC entities and uses either the country prefixes or the DXCC entity number found by using the command show/prefix. See example of show/prefix above.

Examples ...

accept/spot 0 call_dxcc 226,197

or

accept/spot 0 call_dxcc ve,w

(Both will work) These spot filters will accept all spots for US and Canada stations and trash all others.

The following spot filter will accept all spots for US stations and yet reject any spots for W3FM who is always being spotted by Europeans and filling up my screen.

accept/spot 1 call_dxcc w not call w3fm

Filters to accept spots based on call_itu

Similarly, call_itu and call_zone use ITU regions that can also be obtained using the show/prefix command (see above.)

Syntax:  accept/spot [0-9] call_itu <numbers>

Example ...

This spot filter will accept all spots for ITU region 7 and reject all others.

accept/spot 0  call_itu 7

Filters to accept spots based on call_zone

Syntax:  accept/spot [0-9] call_zone <numbers>

This filter is based on CQ zones and uses the CQ zone number found by using the command show/prefix (see above.)

Example ...

This spot filter will accept all spots for CQ zone 5 and reject all others.

accept/spot 0 call_zone 5

Filters to accept spots based on call_state

Syntax:  accept/spot [0-9] call_state <state2-letter postal codes>

This filter is based on state of the call spotted for those callsigns contained in the usdb database.

Example ...

This spot filter will accept all spots of stations located in the Commonwealth of Pennsylvania and reject all others. It's the PA QSO Party Weekend.

accept/spot 0  call_state pa

Filters to accept spots based on by

by filters are similar to and function exactly as call filters except that they act on the spotting station callsign and not the spotted callsign

So ...

This filter is similar to and functions like the call <prefixes> (See above) except that it accepts spots generated by the spotting callsign and dumps all other spots.

Syntax: accept/spot [0-9] by <prefixes>

This filter is based on DXCC entities and uses the DXCC entity number found by using the command show/prefix and it accepts spots generated within the spotting DXCC entity and rejects other spots.

Syntax:  accept/spot [0-9] by_dxcc <numbers>

This next filter is based on ITU regions and uses the ITU region number found by using the command show/prefix (see above), except that it accepts spots generated by a spotting callsign within the ITU region and rejects all other spots.

Syntax:  accept/spot [0-9] call_itu <numbers>

This filter is based on CQ zones and uses the CQ zone number found by using the command show/prefix (see above), except that it accepts spots generated by a spotting callsign within the CQ zone and rejects all other spots.

Syntax:  accept/spot [0-9] call_zone <numbers>

This filters is based on the state location of the spotting station found by using the command show/usdb and accepts only those spots generated by stations from the states(s) specified rejecting all other spots.

Syntax:  accept/spot [0-9] by_state <state2-letter postal codes>