LOTW Improvements

[W1DQ]

LOTW IMPROVMENTS

The LOTW system could be improved by making it able to accept alternate call sign sequences when testing a particular logged QSO for a QSL match. For example, accept the call sign G3XXX/3A as being equivalent to the call sign 3A/G3XXX.

Currently LOTW only grants a QSL when the call sign sequence in an uploaded log entry exactly matches the call sign sequence used when issuing an LOTW User Certificate. If your log entry’s sequence is different, a match will not take place and you lose out.

LOTW issues Certificates without regard to call sign sequence, some this sequence, some that sequence. LOTW does not take into consideration that some national laws regulate the call sign sequence that a licensed visitor must utilize.

Even so, there is no guarantee that a Certificate holder will use the sequence appearing on the Certificate. The holder might choose to use the sequence G3AAA/W2 when trying to attract USA-based stations but the sequence W2/G3XXX when trying to attract stations outside the USA.

A work around for this shortfall is to create and upload multiple log entries for an applicable QSO utilizing each possible sequence alternate, but this should not be necessary as it results in duplicity, wasted storage space and requires extra effort.

In the case of a printed QSL card undergoing ARRL confirmation review there is no sequence comparison with that recorded in the submitter’s logbook; credit is granted regardless of the sequence, so why not the same for LOTW?

[W4PG]

Interesting issue.

In years past, it seemed the usual format for a callsign while operating portable was to place the portable indicator at the end of the call. That has changed to placing the portable indicator at the beginning of the callsign now. Without looking, I think at least for US hams, there is a regulation specifying that now, but I'm posting strictly on memory and that could be wrong.

One problem is at least two logging programs I use *require* the portable indicator at the beginning of the callsign in order to correctly ID the DX entity. W4PG/VP9 will return the USA as the entity, however VP9/W4PG returns the correct entity (Bermuda, in this case). Thus, I now use the latter format no matter what the station says so my log correctly IDs the DX entity.

...........Bob

[W4PG]

After reading a bit of the FCC Rule book from the ARRL, it seems this issue is a bit confusing.

If one is operating portable in another country under IARP authorization, the portable identifier can go EITHER before or after the primary call. If one is operating under the authorization of CEPT, the portable identifier must PRECEDE the primary callsign.

However, when a Canadian station is operating in the US, the US station locator must FOLLOW the Canadian call sign (eg: VE8RCS/W1).

BUT, when our British Brothers are operating in the US, they are required to place the US location identifier BEFORE their call sign (eg: W6/G5BFU).

Reference: 13th edition The ARRL FCC Rule Book. Not sure if this is still the law today, but suspect so.



No doubt, this creates a bit of confusion for LoTW!!

[W1DQ]

Originally Posted by W4PG

If one is operating portable in another country under IARP authorization, the portable identifier can go EITHER before or after the primary call. If one is operating under the authorization of CEPT, the portable identifier must PRECEDE the primary callsign.

However, when a Canadian station is operating in the US, the US station locator must FOLLOW the Canadian call sign (eg: VE8RCS/W1).

BUT, when our British Brothers are operating in the US, they are required to place the US location identifier BEFORE their call sign (eg: W6/G5BFU).

There is no international requirement with regard to sequence to standardize with and so variations will exist and may conflict.

Regardless of sequence and utilizing your example, one can readily deduce that both VE8RCS and G5BFU are operating from the USA Entity. This is all the more reason that LOTW should have the capability of determining the equivalence of alternate call-sign sequences when testing for a QSO match and QSL confirmation.

Under the current system when the log input sequence differs from the LOTW certificate sequence, both parties lose.

[K6VAR]

Couldn't this be fixed by adding five fields to the database?

Portable? yes/no
Mobile? yes/no
Marine? yes/no

if yes to any above, choose DXCC entity of operation: ______
for the DXCC entity, choose State or Province: ___________

LOTW would check the home calls for a match. If no match, then don't bother looking at the P/M/MM fields.

If the home calls match, then check the five new fields for a match. QSL only if all fields match.

[W1DQ]

There need not be any modification of the database. Merely incorporate an algorithm into the match test sequence that will:

1. determine the location of the character(s) “/” so as to segregate the sub-groups within in a call sign.

2. If the ending sub-group is:

a. a single number - 0 through 9, or

b. a single letter or letters that designate low power or mobile operation, such as “QRP” or “P”or “MM” (or other appropriate designator)

then retain that group at the end.

3. Reverse the sequence of the remaining groups and test the call sign again for a Certificate match.