Prefix bug

[w9mdb]

JTAlert 2.6.20 sending QSO to Log4Om 1.23.0
Prefix registers as "W" instead of "WA3" as this example shows...screen shot of QSO and the entry from the Communicator log.

Screenshot 2015-11-14 00.02.59.png (47.1 KiB) Viewed 5408 times

2015-11-13 22:38:58.7199 INFO: #=qje$IehhV$W0BRu75i71jzRmw54m0HOJiWfXS_mtIrtM=: Incoming TCP QSO <CALL:6>WA3FWA<DXCC:3>291<COUNTRY:13>United States<QSO_DATE:8>20151114<QSO_DATE_OFF:8>20151114<TIME_ON:6>043400<TIME_OFF:6>043800<FREQ:8>3.577266<FREQ_RX:8>3.577266<BAND:3>80m<BAND_RX:3>80m<MODE:4>JT65<RST_SENT:3>-12<RST_RCVD:3>-06<QSL_SENT:1>N<QSL_RCVD:1>N<LOTW_QSL_SENT:1>R<LOTW_QSL_RCVD:1>R<EQSL_QSL_SENT:1>R<EQSL_QSL_RCVD:1>R<GRIDSQUARE:4>EN90<DISTANCE:3>883<TX_PWR:2>25<LAT:11>N040 30.000<LON:11>W081 00.000<COMMENT:39>61ft Attic Dipole - thanks for the QSO!<NAME:18>Joseph C Mielnicki<QTH:10>Pittsburgh<STATE:2>PA<CQZ:1>5<ITUZ:1>6<PFX:3>WA3<CONT:2>NA<MY_GRIDSQUARE:6>EM49hv<MY_CQ_ZONE:1>4<MY_ITU_ZONE:1>7<STATION_CALLSIGN:5>W9MDB<QSO_COMPLETE:1>Y<A_INDEX:2>14<K_INDEX:1>3<SFI:3>103 <EOR>

[IW3HMH]

W is the "generic" prefix for the country.
I'll check if and when i save that, instead of retrieving the one from QRZ/HAMQTH

[w9mdb]

Any reason not to use the one the the add request?

[G4POP]

Any reason not to use the one the the add request?

Because it is not a listed DXCC prefix and it would screw up the statistics in Log4OM because that uses the recognised DXCC list which lists K,W,N,AA-AK as the authorised prefixes for the USA

See http://www.arrl.org/files/file/DXCC/201 ... eleted.txt for full list

[w9mdb]

But the ADIF spec wants WPX -- not that ARRL list.
http://www.adif.org/303/adif303.htm

http://www.cq-amateur-radio.com/cq_awar ... _rules.pdf

[w9mdb]

I also see that LOTW corrects the prefix to WPX for the WPX award. When I download the LOTW ADIF they are corrected as in this example:

ARRL Logbook of the World Status Report
Generated at 2015-11-14 13:52:43
for w9mdb
Query:
QSL ONLY: YES
QSL SINCE: 2015-11-13 00:00:00

<PROGRAMID:4>LoTW
<APP_LoTW_LASTQSL:19>2015-11-14 08:35:04

<APP_LoTW_NUMREC:2>30

<eoh>

<CALL:6>KA1MDQ
<BAND:3>40M
<FREQ:7>7.07666
<MODE:4>JT65
<APP_LoTW_MODEGROUP:4>DATA
<QSO_DATE:8>20151114
<TIME_ON:6>063500
<QSL_RCVD:1>Y
<QSLRDATE:8>20151114
<DXCC:3>291
<COUNTRY:24>UNITED STATES OF AMERICA
<APP_LoTW_DXCC_ENTITY_STATUS:7>Current
<PFX:3>KA1
<APP_LoTW_2xQSL:1>Y
<CQZ:1>5
<ITUZ:1>8
<GRIDSQUARE:4>FN41
<STATE:2>MA
<CNTY:13>MA,BARNSTABLE
<eor>
73
Mike W9MDB

[G4POP]

This has been discussed before as revealed by a forum search see: viewtopic.php?f=25&t=1142&p=6721&hilit=WPX#p6721

This is why we don't include a standard hard coded or a special award for CQ WPX but it is on our Mantis list for further development

Changing the DXCC prefix to that required for CQ WPX would screw up the DX awards

Using the DXCC prefix for WPX would not work for WPX.

We need to pars the call sign field contents to obtain a WPX valid prefix that is acceptable for CQ awards

[w9mdb]

Who uses the shortened ARRL prefix for awards? Log4OM?
The DXCC is normally used for any DX awards that I'm aware of (not that I'm aware of everything but prefixes seem like an awfully hard way to do a DX awards when the DXCC code is much more tightly controlled).
And not following the ADIF standard for the PFX field sounds like dangerous waters to me.
I thought that was the whole point of standards. So you plan on noting to people that you don't follow it?

73
Mike

[G4POP]

The DXCC is normally used for any DX awards that I'm aware of (not that I'm aware of everything but prefixes seem like an awfully hard way to do a DX awards when the DXCC code is much more tightly controlled).

1. That is why we use the ARRL DXCC prefix list for the DXCC awards!

And not following the ADIF standard for the PFX field sounds like dangerous waters to me.

2. Agreed and we need to address what is exported as the ADIF prefix field data - However we cannot do that before we implant a system to parse the prefix from the call sign and implement the CQ WPX award. Once that is done we then have the data to export!

3. The data in the Country, IOTA, SOTA tab is "DXCC" Data and as such conforms to the ARRL DXCC information and our country file.

4. When we have attended to item 2 above there will be an additional field titled WPX or perhaps Prefix and that will then become the exported field in the ADIF

5. Meanwhile I suggest that you use your LOTW ADIF download to satisfy your CQ WPX award requirements.

I thought that was the whole point of standards.

6. Yes it is "the whole point of standards" but the ADIF standard has recently become a nightmare as far as changes to awards and award credits and most of our time has been devoted to that and other updates that were required in Log4OM

So you plan on noting to people that you don't follow it?

Answered above!

If we have not been as fast in making these changes as you require I apologise, this is because we have limited resources in manpower and time so we are not able to fix things as fast as some other software developers.

Log4OM is only three years old so we are a new kid on the block in comparison to other free or paid for programs that are available which no doubt provide far superior facilities than Log4OM.

I hope the foregoing provides the answers that you require but please let me know if they do not.

[w9mdb]

You answered quite nicely. Thanks.
Keep up the good work.
73
Mike W9MDB