Re: Reasonable call prefilter
|
13 seems to be a de facto standard.? The callsign field in the Cabrillo standard is 13 characters wide. Contest loggers like Win-Test and DXLog have the same.
Bj?rn SM7IUN
+ AA6YQ comments below
The ITU has fairly clear regulations on valid amateur callsigns
<>
essentially limiting callsigns to Letter-number (e.g. W1, G5, F2, etc.), Letter-letter-number (e.g., WA1, KH6, PY3, VE2, etc.), Letter-number-number (e.g. A61, C53, E77, etc.) or Number-letter-number (e.g., 2E1, 3B8, 4L1, 4X4, 5A1, etc.) followed by up to four characters the last of which must be a letter *except* in the case of half series assignments (3DA-3DM Eswatani, 3DN-3DZ Fiji, SSA-SSM Egypt, and SSN-SSZ
Sudan) where the prefix should be *three* characters followed by a number then a maximum of *three* characters the last of which must be a letter.
*However* Article 19, section 3 includes language that permits the use of callsigns with more than four characters in the suffix "On special occasions, for temporary use".
DXKeeper permits logging callsigns of up to 13 characters (to handle up to 7 character callsigns with a "portable" prefix or suffix).? I could not find a reference to maximum callsign size for SpotCollector.
For those who chase Special Event operations, what is a reasonable
(practical) limit for the length of special event (special occasion, temporary use) callsigns that one might encounter on the air or see via the cluster network?? Is the 13 character limit in DXKeeper workable (assuming there is no need for a "portable" modifier to an already jumbo sized callsign <G>)?
+ There have been no complaints posted here about DXKeeper's 13-character limit on callsigns.
+ SpotCollector also imposes a 13-character limit on callsigns.
? ? ? ?73,
? ? ? ? ? ? ? Dave, AA6YQ
|
Bj?rn SM7IUN