Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update pota.txt #3069

Merged
merged 1 commit into from
Apr 10, 2024
Merged

Update pota.txt #3069

merged 1 commit into from
Apr 10, 2024

Conversation

Ciemon
Copy link
Contributor

@Ciemon Ciemon commented Apr 10, 2024

After changes made to park naming in the POTA programme this update provides a sorted list of the latest park numbers from POTA.

After changes made to park naming in the POTA programme this update provides a sorted list of the latest park numbers from POTA.
@magicbug
Copy link
Owner

There was some discussion on the ADIF Spec group about POTA changes and if I understood it there was some breaking changes so one reference turning into something else, which for logging apps creates a headache as adding the new references then leaves old ones behind.

Are they providing a remap csv of some kind so old can match with new.. as this is ultimately a breaking change

@Ciemon
Copy link
Contributor Author

Ciemon commented Apr 10, 2024

The current documentation set states:

Required ADIF fields

STATION_CALLSIGN or OPERATOR
CALL
QSO_DATE
TIME_ON
BAND
MODE or SUBMODE

Optional ADIF fields

MY_SIG and MY_SIG_INFO
SIG and SIG_INFO
MY_STATE

The new park references are in place now, the old ones are not recognised by the website. As an example park https://pota.app/#/park/G-0597 (which is linked from a QSO in my log) fails to resolve, but https://pota.app/#/park/GB-0597 does resolve as it's the new name and URL.

Currently if I use GB-0597 within Cloudlog, I'm asked to add it, which then correctly links into the POTA site for the information Cloudlog requires.

@magicbug
Copy link
Owner

I'm happy to add the new list, but I think POTA will need to provide a way of mapping old to new this seems poorly thought out on their part.

@magicbug magicbug merged commit 5b70a1b into magicbug:dev Apr 10, 2024
1 check passed
@phl0
Copy link
Contributor

phl0 commented Apr 11, 2024

This clearly needs a migration to map the already logged QSOs to the new references.
Once I asked for an ADIF download of the hunter log to be used to insert/update references. This was denied with "would not trust the info entered by activators" ... 🤷‍♂️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants