Anybody else having issues with importing history adif files with this release?
Trying to import my adif file 17k qso’s and the import box just disappears after 3 to 4 seconds.
November release imported the file just fine, have rebooted phone (Android) even uninstalled and reinstalled the app.
I agree that previously you would see a count of the ADIF records imported and being used for history. I cannot see this count anywhere. The layout has changed a little since I previously used this feature but still I cannot work out where it would be if indeed it was working.
After the last release which didn’t function as expected it deleted all my previous activations where I had to uninstall the app.
I went to import assuming I could import my history files, but only allows one file at a time and imports it to the current activation.
Is there a way to import all my previous activations in one hit?
I tried searching Import and only this thread appeared.
Bob G6CKK
The options are as follows:
Importing an ADIF file as a history file does not contain the information to separate activation chunks into separate operations.
Yes, I’m also running into this issue. I have an iPhone and Android phone that have the December release and once I do the “Clear ADIF History” and then did a “Import History from ADIF” it failed to import them. I have an Android tablet that is still running the November release and I was able to clear and import without any issue. I ran the ADIF file through ADIF Master to verify there aren’t any errors in the file. Is there a specific place to log app bugs? KK7PZE
you just did - this topic is tagged bug-report
Just tested Jan pre2 and the adif import seems to be working better, not 100% though, out of my 18k qso’s it only imported 9,999 of them, i deleted the data and re-imported them, this time it only imported 6000 or so.
I have exported only SSB contacts from my logbook which is substantially smaller than the full log and that had trouble importing - same as before the box would disappear within a matter of seconds without importing any, terminating the application and re-importing the log seemed to work.
Tom,
Putting aside that this is still a current issue yet to be resolved.
Can you share your expectation on this feature?
At some point in the past having historical records allowed for callsign lookup which may have been a benefit if you are offline. You could get a gridsquare and name for your current Operation log.
Then we got the start of statistics which at the moment only go as far as to say “and many more contacts” after the current operation stats are presented.
So having say 50 thousand non-unique records in history may not be delivering what you expect.
If the import succeeded, how would you expect to enjoy the benefit from it?
Alan
Thanks Alan,
I just realized the callsign lookup is not working offline even though i have imported my adif, i’m pretty sure this used to work in the past so not sure what happened with that. This feature was useful especially when out in the sticks with no net.
If it’s offline names for callsigns, I use a names file. It has 77,000+ names in it and works well offline with Jan pre2 and with QRZ actually turned off.
Having QRZ turned off actually improves performance for data entry especially when cell coverage is sub-optimal.
But names file lookups do not populate your QSO log. They are good for saying “Hello Tom” as soon as the callsign is entered. I do a bulk lookup for the operation when I am finished if I want.
Since the ADIF history import feature is in its current state I am not sure if the lookups from this source work at all atm.
But one thing to remember is that for the purpose of lookups, you only need unique records. Multiples are of no benefit here. And an ADIF export from most logger applications will give you a stack of ADIF fields which serve no purpose at all for PoLo. With multiples and all the additional fields you will end up with a very large file. You cannot view or edit this data once imported.
77,000 unique names is about 8Mb and is very fast on my devices.
Alan
Thanks again Alan,
Ill export unique calls/names from from my log and whack them into my call notes. That will work for me just fine.
Cheers
Tom
I think you might be hitting some of the memory limits when loading those QSOs.
Perhaps you can load multiple smaller files one after the other. Or generate an export that has fewer fields.
Name, City, State and Grid are the fields we actually care about.
Using ADIF History is much better and more performant than callsign notes, and has the added benefit of saving the names and locations into the log, not just showing a note on the screen.
Thanks Sebastián,
I tried splitting my log into 3 files and still maxed out at 9,999 - not to worry for now as i just exported all my SSB contacts only and imported that.
All good now, even offline i can see names of people that i have worked before.
A lot of OPs use my callsign notes file which gets updated frequently with one click. It requires a one-off install. OPs don’t have to download, clear and import a new file each time. It’s just there in their device when they start using it. So it’s quite a bit more convenient.
Alan
Yeah, the convenience factor is a big plus.
Another advantage is that my notes file has a lot of OPs callsigns and names who do not have a QRZ listing. But I know their name when they call me.
I use both, a call notes file on google drive and the adif import, both work great when offline.
Cheers