[Dxspider-support] filters

[Steven Franke]

Ron, your point is well taken.  

How about allowing for filtering based on the callsign of the _node_ that 
the spot originated from. Looking at the format of the PC11 protocol
messages, I see that the node callsign comes along with the spot. With the
"power of perl", it'd be easy to write a script to analyze
the spot database from a contest weekend and determine which nodes are
supplying the bulk of the unwanted spots.  

S. J. Franke  
email: s-franke at uiuc.edu

On Wed, 23 Feb 2000, Ron Stordahl wrote:

> Steve
> 
> That would be nice, however the call area derived from the call is no longer
> reliable.  I am a '5' and the '0' district as an example.  Its only going to
> get more jumbled with time I believe.  As to the state this would require a
> data base to determine the state from the call.  It would be possible of
> course, but would it be worth it?
> 
> Its really a puzzle.  The solution might lie in regional internet clusters?
> 
> Ron N5IN
> 
> ----- Original Message -----
> From: "Steven Franke" <sfranke at soliton.ece.uiuc.edu>
> To: <dxspider-support at dxcluster.org>
> Sent: Wednesday, February 23, 2000 11:11 AM
> Subject: [Dxspider-support] filters
> 
> 
> >
> > Here's a vote for the ability to filter based on the state or US call
> > area of the spotter. This would be useful for us during contest weekends
> > when we might like to limit the number of spots that we feed to a
> > downstream node connected via a slow radio link.
> >
> > 73, Steve K9AN
> > email: s-franke at uiuc.edu