ADIF Import from fldigig - no locator

[G4POP]

Hi Juergen,
No problem and please keep the ideas coming.

By posting these things to the forum it demonstrates the issues people see and the resolution to the problem or our reasons for not changing things - Information flow is very good.

Heinz,
I think Daniele may have an idea about your locator problem, more information when we know what it is

[IW3HMH]

I think it's an issue with the "post-process" activity i'm doing to fill data with qrz/hamqth informations.
Today i will check this part of the code to see if it's the case.

by the way distance can be set automatically by code. I'll do that.
73
Daniele

[IW3RAB]

I think it's an issue with the "post-process" activity i'm doing to fill data with qrz/hamqth informations.
Today i will check this part of the code to see if it's the case.

by the way distance can be set automatically by code. I'll do that.
73
Daniele

If I manually import an ADIF line from a JT-ALERT programs log this work.
This mean that an automatic import not recalculate the distance also if field is 'null' or 'zero' or 'absent' and GRIDSQUARE and MY_GRIDSQUARE are valid
locator = locator.Trim().ToUpper();
if (Regex.IsMatch(locator, "^[A-R]{2}[0-9]{2}[A-X]{2}$"))........and so on for the standard 4,6 and other lenght, but encodes with base 18 for the first alphabetics pair and with base 24 for the succesive.

The locator and distance calculation on old QSO are zero.
This is a problem of old hrd and I thik to solve in holidays..

73 Sandro IW3RAB

[IW3HMH]

There is a function in Log4OM to fix distances.
Open QSO Archive
Select all QSO needed
Click on FIELD UPDATE function

Set Update qso distance/bearing and execute checks.

This is a massive update, so take a backup!

[IW3RAB]

There is a function in Log4OM to fix distances.
Open QSO Archive
Select all QSO needed
Click on FIELD UPDATE function

Set Update qso distance/bearing and execute checks.

This is a massive update, so take a backup!

All type of backup will be performed
After 1976 (my first impact with computers) all my data is triplicated and also paper backup in two location is performed.

Sandro, IW3RAB

[G4POP]

Hi Terry,
sorry for the delay but I had and still have nasty toothache
just for info...
At my main pc i have installed Win7 (64).
Fresh installation of both (Log4OM and fldigi).
Creating new database (sqlite) -> locator would been overtaken.
I thought fine and importered my other qsos from an adif file.
After that moment the locator wasn't imported anylonger

Strange...

cu Heinz

Hi Heinz,
This post is for everyone's benefit just to let them know that with a great deal of patience and cooperation from Heinz we were able to rectify two bugs in the Fldigi integration.

One caused the locator not to be imported in certain circumstances and the other caused the comments field to be ignored.

So many thanks to you Heinz we all appreciate your help.

[IW3HMH]

to be honest, one of the bugs is related to a bad ADIF tag in the FLDigi ADIF generated file.
ADIF fields reports COMMENT, FLDIGI saves it as COMMENTS.

This could be useful to be updated on FLDigi side too

[DK5UR]

It was a pleasure to assist in solving this problem!

I always like to help...