Q regarding callsigns

[KB1JCY]

I'm developing a program that uses a Amateur callsign as a username. Obviously I have to keep out bogus callsigns. To do this, I have to write a regular expression pattern that tests what the user inputs as a callsign. Now are all international callsigns 2x3, 1x3, 1x2, 2x2 or is just an Northern American thing? What prefix/suffix patterns exist?

[K4MSM]

link

[M0MJH]

'JCY,

It's quite random really. I have heard callsigns using 1x1, 1x2, 1x3, 2x1, 2x2, 2x3, 2x4 (i think this is only special calls and VK foundation licencees). In my case, I have 2 '1x3' callsigns and 1 '2x3' callsign. Also in our country we have special contest callsigns that are 1x1 (like M4U).

Hope that 'helps'

Mark
M0MJH

[KB3LIX]

If this is an international application, there are nations that have 2 consecutive numerics in the call. Several that come to mind are Slovenia S59?, Macedonia Z35?, Namibia V51?, Aruba P40?,
Belieze V31??.
There are many others, above is just a few of the many combinations.

[M0MJH]

Ahha,

Thanks 'LIX, I had forgotten about those ones!

[W1VT]

I recall listening to TO00FB in Tahiti talk about getting his call sign--in some countries you just have to convince the government official representing the "FCC" of that country to give you what you want. I know another ham who would spent hours in negotiations getting his special callsign.

[K9STH]

A number of countries issue call signs for specific events (like 50 years of their existence) that can have 4 to 6 items in the prefix. Some of these are for very short periods and some last at least a year.

Glen, K9STH

[KB1JCY]

Thanks for the info. The way it sounds, 2x3, 2x2, 1x3, 1x2, and 2x1 are the most common? The application is for individual operators, not special stations or club stations. Obviously I should put a test into the code for calls that deviate from the standard which can be later investigated by a human.

[N5KRC]

Quote[/b] (KB1JCY @ May 02 2007,18:43)]I'm developing a program that uses a Amateur callsign as a username. Obviously I have to keep out bogus callsigns. To do this, I have to write a regular expression pattern that tests what the user inputs as a callsign.

The problem with this methodology is that the user can still use a 'bogus' callsign, provided they follow the proper format...

Maybe another approach, assuming your application is network-connected, might be to quarry the various databases online and determine if the call is actually registered or not...

Just food for thought...

[KB1JCY]

Quote[/b] (N5KRC @ May 03 2007,08:22)]The problem with this methodology is that the user can still use a 'bogus' callsign, provided they follow the proper format...

Maybe another approach, assuming your application is network-connected, might be to quarry the various databases online and determine if the call is actually registered or not...

Just food for thought...

That sort of was the plan. Perform an initial screen of what callsign the user enters (check to make sure it matches known patterns) then query QRZ's XML webservice for final verification. I don't want to query QRZ every time the app needs to check a callsign. That would be slow and would be "expensive" in terms of RAM usage and time needed to serialize and process the XML results.