Accept filters

From The DXSpider Documentation Wiki
Revision as of 18:47, 24 January 2023 by G0vgs (talk | contribs) (Created page with "=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 abb...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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>