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

Import ADIF files for data transfer #10

Closed
rolnas opened this issue Jun 18, 2023 · 10 comments
Closed

Import ADIF files for data transfer #10

rolnas opened this issue Jun 18, 2023 · 10 comments
Labels
enhancement New feature or request

Comments

@rolnas
Copy link

rolnas commented Jun 18, 2023

There is generation of ADIF files for export, but there are no way to import back data from another source (at least ADIF format).

@mbridak mbridak added the enhancement New feature or request label Jun 18, 2023
@mbridak
Copy link
Owner

mbridak commented Jun 18, 2023

True.
I don't know if it will.

@DE8MSH
Copy link
Contributor

DE8MSH commented Oct 30, 2023

Hi. I know you don't know. ;) But will it? It'd be a very nice feature. With check if we had QSO before. 👋🏻

@cbspidi
Copy link

cbspidi commented Jun 25, 2024

bumping an old issue, but...
a solution could be to implement an integration to qrz.com with API key
you could implement two handy functions

  • lookup in your logbook
  • lookup in qrz database for potential matches, this is more useful than first one

@cbspidi
Copy link

cbspidi commented Jul 19, 2024

@DE8MSH , in case you would still like to have those contacts inside the not1mm
I did it by exporting ADIF from QRZ then I opened it with ADIF master and exported the data into CSV file
Next, I wrote a quick Python script to export some(not all) data from the CSV file and SQL insert it into the SQLite DB file.

It was not a pretty process, but it got the data into the program, so I can enjoy knowing if I had previous contact.
The process I come up is not as good as I would like it to be, that is due to me not knowing how is data structured inside the database, ie. what is expected and where and what needs to change / where and why.

I would happily share the python script I put together to do the above.

@FastThenLeft
Copy link

FastThenLeft commented Feb 15, 2025

Michael - please resist putting in features that are NOT contesting features! During a contest, the only time I care if I worked you before is in the contest I'm in right now! This isn't a general logging program. It's a contest program! There are several great general purpose logging programs that run on Linux and do all the features the OP is asking for and tons more. I use CQRLog for general logging on Linux. The OP can use one of those. THIS PROGRAM however is the only decent contesting program available for Linux. Please keep it that way by resisting general logging features and other things not related to contesting.

@mbridak
Copy link
Owner

mbridak commented Feb 23, 2025

I think this could be better served not by making a program to inject ADIF data back into the database, but to rather create an already supported call history file. Which can then be easily loaded by an already existing mechanism.

See this

So say @rolnas, @DE8MSH or @cbspidi want to use the general logging plugin, but see past contact info they've had on other programs like the contacts name or a remark from a past log. @cbspidi could modify his already written program to convert the ADIF to a slightly different CSV type file. The general logging plugin looks for the fields Call, Name and UserText. So if his program was slightly modified to add a header to the start of the CSV type file then output the wanted fields, you'd get something like:

!!Order!!,Call,Name,UserText,
# Remark to let the user know it's meant for the general plug in.
K6GTE,MIKE,Programmer
K5TUX,RUSS,A podcaster
N2CQR,,I think his name is Bill
N6QW,Pete,Pasta Pete

Bada Bing Bada Boom.

Everyone's happy.

@mbridak
Copy link
Owner

mbridak commented Mar 10, 2025

@cbspidi @DE8MSH @FastThenLeft @rolnas To maybe help the situation a little I wrote another program to map an ADIF files taggs to a Not1MM/N1MM compatible call history file. It can be installed with:

pipx install adif2callhistory

mapped fields

When the file is saved, you will end up with something like:

!!Order!!,Call,Name,Loc1,Sect,State,Exch1
K6PV,,,LAX,CA,1D
K7SS,DANIEL A ESKENAZI,CN87tn,WWA,WA,1D
K6AA,UNITED RADIO AMATEUR CLUB INC,DM03ur,LAX,CA,3A
K0EU,RANDALL K MARTIN,DM79lp,CO,CO,1B
W3AO,NATIONAL PRESS RADIO CLUB,FM18pv,MDC,MD,1E
W6ZE,ORANGE COUNTY AMATEUR RADIO CLUB INC,DM13cs,ORG,CA,6A
...

@cbspidi
Copy link

cbspidi commented Mar 11, 2025

Thank you @mbridak , I take the output is a data ready for the SQL injection, nice!

@mbridak
Copy link
Owner

mbridak commented Mar 11, 2025

Well, I guess you could use it for that. But it's more to be used as a call history file. Come to think of it, I should probably list each contest and list which fields each one looks for...

@mbridak mbridak closed this as completed Mar 18, 2025
@rolnas
Copy link
Author

rolnas commented Mar 18, 2025

This issue is not solved, because original problem is not solved. Import is important if we work (for e.g.) in multiple category or if a part of contest were in one program and other in anoher (that happens for e.g. in field days). It is normal to have import if there is export of data. Not everyone have knowledge to write a script to convert ADIF to SQL for injection to sqllite DB.

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

No branches or pull requests

5 participants