Use ADIF field POTARefList for Multiple Parks | Export | NY4I

Feature Requests
1

New feature request by @NY4I!

When I work multiple parks, I only see a single park in the ADIF export file (i.e., SIG:4POTA <SIG_INFO:8>US-13182 <POTA_REF:8>US-13182 ).

The ADIF Specification has a field called POTARefList which allows you to add multiple parks to the single QSO record. It would be very helpful going forward if you could add the multiple parks to that field. POTA does not yet support imports with POTARef or POTARefList but I understand they are working on it.

My logging software creates a POTA n-fer with this field so the QSO only appears in one ADIF record. The common technique where some loggers will make multiple records (which you fortunately do not do) caused LOTW to think the multiple contacts is a duplicate since date, time, band and call are the same). .

But if everyone would emit (and import) the POTARefList as a field to indicate multiple parks, we would just have a single QSO record in ADIF.

For WRL, the export is not conveying all the information about the park since it only puts the first park I entered.

If I have done something wrong and it should work, please let me know.

I also cannot see any way that I can view the multiple parks when reviewing the contact in the QSO manager.

2

My apologies. I used the wrong field name. The field is the POTA_REF you use now. But the issue is the QSO record in the ADIF file only has the single park and not both. This is from the ADIF specification for POTA_REF:

a comma-delimited list of one or more of the contacted station’s POTA (Parks on the Air) reference(s).

Examples:
<POTA_REF:7>US-5033
<POTA_REF:7>VE-5082
<POTA_REF:40>US-0817,US-4566,US-4576,US-4573,US-4578