search

smurphboy / OARCLogger

Worked All OARC Season 2 Logger
MIT License
1 stars 0 forks source link

QRZ ADIF Imports - FT4 becomes AM #25

Open MartinCRichards opened 1 year ago

MartinCRichards commented 1 year ago

I know you mentioned FT4 was hidden under MFSK, but if I import from a QRZ ADIF, "FT4" is imported as AM :-(

smurphboy commented 1 year ago

Can you share the ADIF or run it through https://www.rickmurphy.net/adifvalidator.html and share the output?

FT4 is a submode not a mode as such that ADIF isn't valid. But let's confirm that.

MartinCRichards commented 1 year ago

Oops... Guess we have to tell QRZ.com it's their bad...

Processing file g6fji.298729.20230703133639.adi The following messages represent issues where the submitted ADIF file is not compliant with the ADIF standard.

For the QSO with M0LTE on 2023-07-03 40M FT4: ADIF Compliance error on line 27: The tag 'MODE' has an invalid value 'FT4' - not in the enumerations

For the QSO with M0LTE on 2023-07-03 6M FT8: ADIF Compliance error on line 27: 'FT4' is not a valid MODE

g6fji.298729.20230703133639.adi.txt

smurphboy commented 1 year ago

Lol. More seriously. I could write a special case to handle it, as I suspect it will be a common problem.

Although this is why I didn't want to support ADIF, it's so widely abused...

MartinCRichards commented 1 year ago

I guess when you're as big a QRZ you can set your own standards...

smurphboy commented 1 year ago

If you have nothing nice to say about someone... say nothing ;-)

I'll have a look at handling the error and report back. Not high priority for me though sadly.