Skip to content

Made adif generate a canonical POTA log with or without --pota#148

Open
ericmoritz wants to merge 2 commits into
on4kjm:masterfrom
ericmoritz:support-pota-hunters
Open

Made adif generate a canonical POTA log with or without --pota#148
ericmoritz wants to merge 2 commits into
on4kjm:masterfrom
ericmoritz:support-pota-hunters

Conversation

@ericmoritz
Copy link
Copy Markdown

POTA references in non-POTA logs are supported by the canonical FLE app. This patch enables that functionality in FLEcli

Branch: support-pota-hunters

POTA references in non-POTA logs are supported by the canonical FLE
app. This patch enables that functionality in FLEcli

Branch: support-pota-hunters
@ericmoritz ericmoritz force-pushed the support-pota-hunters branch from fdb4d81 to 68754a8 Compare October 31, 2024 00:15
There is no reason why a POTA log should not be generated like the
canonical one without the --pota flag.

Now the --pota flag turns on validation. If you forget to turn on
--pota and include a MyPark header directive, POTA.app will reject
your log because it is missing MY_SIG_INFO.

Branch: support-pota-hunters
@ericmoritz ericmoritz changed the title Add support for POTA hunters Made adif generate a canonical POTA log with or without --pota Jan 14, 2025
@ericmoritz
Copy link
Copy Markdown
Author

ericmoritz commented Jan 14, 2025

A friend of mine used FLEcli to generate their POTA log, however they forgot to include the --pota flag. This resulted in them uploading a log without Park to park SIG_INFO fields.

The --pota flag now acts as a flag to turn on POTA log validation to ensure an activator doesn't forget their MyPota header. Otherwise the adif subcommand outputs the same log regardless if --pota is enabled or not.

@nicheath
Copy link
Copy Markdown
Contributor

It would be good for --sota and --wwff to act like this too.

@jmMeessen
Copy link
Copy Markdown
Collaborator

Hello @ericmoritz

Thank you to have submitted this PR.
I apologize for taking way too much time to look at it. Life has not been easy for me since 2024. I am now settled in France with a new callsign (F4VXN).

I cleaned the configuration (it gets stale after 2 years). I will now be able to look at this PR and generate a new release.

CC: @nicheath

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