1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
4 <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.20">
5 <TITLE>The DXSpider User Filtering Primer v1.0: Accept filters </TITLE>
6 <LINK HREF="filtering_en-8.html" REL=next>
7 <LINK HREF="filtering_en-6.html" REL=previous>
8 <LINK HREF="filtering_en.html#toc7" REL=contents>
9 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="filtering_en-8.html">Next</A>
13 <A HREF="filtering_en-6.html">Previous</A>
14 <A HREF="filtering_en.html#toc7">Contents</A>
16 <H2><A NAME="s7">7.</A> <A HREF="filtering_en.html#toc7">Accept filters </A></H2>
18 <P>An accept filter line means that if a spot matches pass it on to the user, send
19 it down the line to the next rule or to the user, and trash, dump, all other
20 spots that do not match to the next filter line. </P>
24 Syntax: accept/spots [0-9] <pattern>
28 <P>Any of the following patterns may be used in this line ...</P>
36 call_dxcc <numbers>
38 call_zone <numbers>
39 call_state <state2-letter abbreviations>
44 by_state <state2-letter abbreviations>
45 origin <prefixes> Used primarily be SYSOPS, not by users and not discussed.
46 channel <prefixes> Used primarily be SYSOPS, not by users and not discussed.
50 <P>Using these patterns, we can accept spots based upon ...</P>
55 Callsign of the spot (country or zone)
56 Callsign of the spotter (country or zone)
57 Contents of the "information field" which comes with the spot
62 <H2><A NAME="ss7.1">7.1</A> <A HREF="filtering_en.html#toc7.1">Filters to accept spots based on frequency</A>
68 Syntax: accept/spot [0-9] freq <range>
72 accept/spot [0-9] on <range>
76 <P>Important: as noted before, both <EM>freq</EM> and <EM>on</EM> are exactly
77 the same and can be used interchangeably.</P>
79 <P>For range, you can specify a frequency like 7040, a range of frequencies
80 like 0/30000 ( the whole HF spectrum) or use any of the band/region names
81 defined in the SHOW/BANDS command (see above).</P>
85 <P>This will pass on a HF spots only from 0 to 30,000 kHz and dump all others.</P>
89 accept/spot 1 on 0/30000
93 <P>This passes on all spots in the frequency range 144000 -> 148000 kHz and trash
102 <P>This rule will only pass on spots on 6m, 4m, 2m, and 220 and reject all
111 <P>This rule will pass on all spots on the 160m, 80m, 60m, 40m, 30m, 20m, 17m,
112 15m, 12m, 10m bands and all spots on 70cm and 23cm bands only. All other
113 spots are trashed.</P>
117 accept/spot 4 freq hf and freq uhf
122 <H2><A NAME="ss7.2">7.2</A> <A HREF="filtering_en.html#toc7.2">Sub-bands as part of range</A>
125 <P>In conjunction with range, you can use the following sub-band names: CW, RTTY,
126 DATA, SSB, and SSTV by using a back-slash [(band or region)/sub-band] as part
127 of the range definition. </P>
131 <P>This rule will only accept and pass on HF phone spots rejecting all others</P>
135 accept/spot 0 freq hf/ssb
139 <P>This filter rule will accept all HF CW spots but will not include DATA and
140 RTTY spots in the CW range. In addition all other spots will be dumped.</P>
144 accept/spot 1 on hf/cw and not (on hf/data or on hf/rtty)
149 <H2><A NAME="ss7.3">7.3</A> <A HREF="filtering_en.html#toc7.3">Filters to accept spots based on info</A>
155 Syntax: accept/spot [0-9] info <string>
159 <P>This filter is used to key on information contained in the information section
160 of the spot. One could use this to accept any spots containing IOTA, QSL OP or
161 any other "key-word" used in the information string of the spot. </P>
165 <P>This filter will accept spots containing IOTA information only and reject all
170 accept/spot 0 info IOTA
174 <P>This filter will accept only 10m SSB spots, but will still permit any spots
175 that contain iota information in addition - rejecting all other spots.</P>
179 accept/spot 1 on 10m/ssb and info iota
183 <P>This next filter will accept spots asking or containing QSL information and dump
188 accept/spot 2 info QSL
192 <P>Note: The following series of filters are based on <EM>call</EM> and
193 <EM>by</EM>. Call always references the callsign of the spotted DX station.
194 By always references the callsign of the spotting station.</P>
196 <H2><A NAME="ss7.4">7.4</A> <A HREF="filtering_en.html#toc7.4">Filters to accept spots based on call</A>
202 Syntax: accept/spot [0-9] call <prefixes>
206 <P>This filter is misleading in a way. It is strictly based on the spotted call
207 sign letters or numbers entered and not based on countries or DXCC entities. </P>
211 <P>This filter will accept spots for G1AAA, GJ2BBB, and GW3CCC and reject all
212 others, including M0AAA.</P>
220 <P>This next filter will accept spots for PA3AAA and reject spots for PB4BBB as
221 well as all others.</P>
225 accept/spot 1 call PA
229 <P>This filter will accept spots for callsigns beginning with "K", i.e., K1AA,
230 KC4AAA, KH6DDD and reject spots for W3BG and N3RD as well as all other
240 <H2><A NAME="ss7.5">7.5</A> <A HREF="filtering_en.html#toc7.5">Filters to accept spots based on call_dxcc</A>
246 Syntax: accept/spot [0-9] call_dxcc <numbers or prefixes>
250 <P>This filter is based on DXCC entities and uses either the country prefixes or
251 the DXCC entity number found by using the command <EM>show/prefix</EM>. See
252 example of <EM>show/prefix</EM> above.</P>
258 accept/spot 0 call_dxcc 226,197
262 accept/spot 0 call_dxcc ve,w
266 <P>(Both will work) These spot filters will accept all spots for US and Canada
267 stations and trash all others.</P>
269 <P>The folowing spot filter will accept all spots for US stations and yet reject
270 any spots for W3FM who is always being spotted by Europeans and filling up my
275 accept/spot 1 call_dxcc w not call w3fm
280 <H2><A NAME="ss7.6">7.6</A> <A HREF="filtering_en.html#toc7.6">Filters to accept spots based on call_itu</A>
283 <P>Similarly, call_itu and call_zone use ITU regions that can also be obtained
284 using the <EM>show/prefix</EM> command (see above.)</P>
288 Syntax: accept/spot [0-9] call_itu <numbers>
294 <P>This spot filter will accept all spots for ITU region 7 and reject all
299 accept/spot 0 call_itu 7
304 <H2><A NAME="ss7.7">7.7</A> <A HREF="filtering_en.html#toc7.7">Filters to accept spots based on call_zone</A>
310 Syntax: accept/spot [0-9] call_zone <numbers>
314 <P>This filter is based on CQ zones and uses the CQ zone number found by using
315 the command <EM>show/prefix</EM> (see above.)</P>
319 <P>This spot filter will accept all spots for CQ zone 5 and reject all others.</P>
323 accept/spot 0 call_zone 5
328 <H2><A NAME="ss7.8">7.8</A> <A HREF="filtering_en.html#toc7.8">Filters to accept spots based on call_state</A>
334 Syntax: accept/spot [0-9] call_state <state2-letter postal codes>
338 <P>This filter is based on state of the call spotted for those callsigns contained
339 in the usdb database. </P>
343 <P>This spot filter will accept all spots of stations located in the
344 Commonwealth of Pennsylvania and reject all others. It's the PA QSO Party
349 accept/spot 0 call_state pa
354 <H2><A NAME="ss7.9">7.9</A> <A HREF="filtering_en.html#toc7.9">Filters to accept spots based on by</A>
357 <P><EM>by</EM> filters are similar to and function exactly as call filters except
358 that they act on the spotting station callsign and not the spotted callsign</P>
362 <P>This filter is similar to and functions like the call <prefixes> (See above)
363 except that it accepts spots generated by the spotting callsign and dumps all
368 Syntax: accept/spot [0-9] by <prefixes>
372 <P>This filter is based on DXCC entities and uses the DXCC entity number found
373 by using the command <EM>show/prefix</EM> and it accepts spots generated
374 within the spotting DXCC entity and rejects other spots.</P>
378 Syntax: accept/spot [0-9] by_dxcc <numbers>
382 <P>This next filter is based on ITU regions and uses the ITU region number found by
383 using the command <EM>show/prefix</EM> (see above), except that it accepts
384 spots generated by a spotting callsign within the ITU region and rejects all
389 Syntax: accept/spot [0-9] call_itu <numbers>
393 <P>This filter is based on CQ zones and uses the CQ zone number found by using
394 the command <EM>show/prefix</EM> (see above), except that it accepts spots
395 generated by a spotting callsign within the CQ zone and rejects all other
400 Syntax: accept/spot [0-9] call_zone <numbers>
404 <P>This filters is based on the state location of the spotting station found
405 by using the command <EM>show/usdb</EM> and accepts only those spots
406 generated by stations from the states(s) specified rejecting all other spots.</P>
410 Syntax: accept/spot [0-9] by_state <state2-letter postal codes>
416 <A HREF="filtering_en-8.html">Next</A>
417 <A HREF="filtering_en-6.html">Previous</A>
418 <A HREF="filtering_en.html#toc7">Contents</A>