Pskreporter spotter locations

Feature Requests
1

Hi,

as some spotters use imaginary callsigns in pskreporter, the functions to limit spotter DXCC/Zone/Continent leak every now and then.

The reason is obvious. For example:

  • LLN201 is logically evaluated as Norway - but by grid locator it resides in Canada.
  • RST38H is logically evaluated as European Russia - but by grid locator it resides in USA.

Typically those ‘callsigns’ start with at least three letters, or include at least four letters in a row, or include at least three numbers in a row.

73, Jukka

2

Hello Jukka,

Thanks for the feedback. Do you have more real-life examples of such bogus spotter callsigns? Then I’ll try to come up with a comprehensive regular expression that matches them all (without matching valid ones) to block them server-side.

73,

Manuel HB9DQM

3

Ok Manuel nice,

I’ll try to collect some more examples within next few days and will be back with those.

Meanwhile… I believe that something like grep -vqE “([1][A-Z][A-Z]|[A-Z][A-Z][A-Z][A-Z]|[0-9][0-9][0-9])” will drop 95% of those, passing valid callsigns, except four-letter suffixes. (Yep for sure you don’t make it that primitive grep way, but for sure caught the idea.)

73, Jukka

  1. A-Z ↩︎

4

Hi,

at least these have been active lately:

LLN201
RST38H
161OS344
KPH1
KFS/OMNI
F/SWL/PRIVAS
F61695
SWL-JO72FG
G/RS36870/GLOS
13GD073
9PAT508
PD750AMS
MITTELKAERNTNER-WEBSDR

An in addition to those, most of reports on 11m band are from non-ham callsigns starting with two numbers.

73, Jukka

1 Like
5

I have now come up with the following regex:

/^(([A-Z]{1,2}[0-9]?|[0-9][A-Z])\/)?([A-Z]{1,2}|[0-9][A-Z])[0-9]{1,2}[A-Z]{1,3}(\/(M|P|QRP|[0-9]))?(-[0-9])?$/i

No DXCC lookup is performed on spotter callsigns that don’t match this regex. This means that the spots will still be processed, but triggers that have conditions on spotter DXCC/continent/zone will not match.

Here is a small sample of spotter callsigns that matched or didn’t match the filter:

allowed.txt (26.8 KB)
blocked.txt (1.5 KB)

6

Thanks for paying attention for this so quickly!

Just one comment about your samples I have:

Out-filtered callsign OH6OKSA. That is a legit Finnish vanity callsign. (Ol’ man’s surname happens to be Oksa.)

Ok, four-letter suffixes are rare but they do exist. Some *IOTA, *IARU, *DARC also happens.

(I’ll try to forget the days of OH2STAYHOME and so on, umpf.)

73, Jukka

7

OK, I guess we can allow one more suffix character without also allowing to many bogus callsigns.

8

Ok - is it already alive?

I can keep on eye about how it serves.

73, Jukka

9

Yes, the new code is in production :smiling_face:

1 Like