Page 2 of 3
Re: Imported log distance problems
Posted: 17 May 2013, 22:00
by G4POP
DF5WW wrote:Will do
Looks like that the ZIP is on the way to your email found at qrz.com.
That is fine I will review the ADIF and fix the distances for you before I send it back
Re: Imported log distance problems
Posted: 17 May 2013, 22:17
by DF5WW
Hi Terry,
it´s fine that you think so but you don´t have to fix .... i only need a way how
I can fix it .... Think you and Daniele have work enough .... Sending my export log from HRD is only a feature to find out what´s going wrong when imported HRDlogbook ADIF and the distance is wrong. If we have an update in 2.100.13 or later no problem

We are all the testers
Nice helpful community here ...

Re: Imported log distance problems
Posted: 17 May 2013, 22:27
by G4POP
DF5WW wrote:Hi Terry,
it´s fine that you think so but you don´t have to fix .... i only need a way how
I can fix it .... Think you and Daniele have work enough .... Sending my export log from HRD is only a feature to find out what´s going wrong when imported HRDlogbook ADIF and the distance is wrong. If we have an update in 2.100.13 or later no problem

We are all the testers
Nice helpful community here ...

The system is already in place as described on pages 95- 96 of the user guide "log checks" and providing you locator is entered in the options it will correct the whole log if you click select all.
This feature was implemented specifically because we have had a lot of HRD ADIF files with incorrect distances.
Re: Imported log distance problems
Posted: 17 May 2013, 23:25
by IW3HMH
i'm interested in the log too.
If something screws up the database i need to know.
I think it was a visualization issue... something related to distance value. Need to check.
Thanks for reporting, lurking on the code right now
73
Daniele
Re: Imported log distance problems
Posted: 18 May 2013, 06:13
by G4POP
IW3HMH wrote:i'm interested in the log too.
If something screws up the database i need to know.
I think it was a visualization issue... something related to distance value. Need to check.
Thanks for reporting, lurking on the code right now
73
Daniele
It's an HRD screw up Lele, the same incorrect distance issue that we had before!
Re: Imported log distance problems
Posted: 18 May 2013, 08:28
by G4POP
Corrected ADIF file and an SQLIte database file returned to Juergen this morning.
Log4OM Log update fixed the distance and heading errors in the HRD ADIF.
Re: Imported log distance problems
Posted: 19 May 2013, 06:16
by DF5WW
Hi Terry,
also here (send an email) thank´s for the nice work. Most distances was o.K. when the fixed Database was used only the 4 digit Locators should have a problem but meanwhile i fixed manually .......
But tried to log a 4 digit Grid square and the distance was wrong too (400 km to JP50 "original" 1152 km) .... could it be that Log4Om has a Problem to calculate the distance to a 4 digit Grid ??? Simply peanuts, i think it will be fixed in one of the next releases
B.t.w. running Win7 ultimate 64 Bit and program was installed and runs as administrator.
Have a nice weekend all ....
Re: Imported log distance problems
Posted: 19 May 2013, 09:23
by G4POP
Hi Juergen,
I have to admit that I did not even look at the 4 digit Locators so completely missed that issue.
This morning I have had a quick check as it would seem that we do have an issue with 4 Digit locators, guess we never checked them because they are quiet unusual because most people use 6 digits and the microwave fraternity use 8!
I will point this annomolly out to Daniele and we will correct this as soon as possible
Re: Imported log distance problems
Posted: 19 May 2013, 13:43
by DF5WW
Hi Terry,
i use normaly also 6 digit locators (if coming down from Ham QTH or sended from the station and i can fill in (some uses 10 digits)) but if you work JT65 or JT9 only 4 digits will be logged via JT-Alert or JT-Alert-X to the logbook software.... If this will be fixed in the next releases, fine .... Think here´s a new software and the programmers listen to the users ..... That´s what counts
Nice weekend ....

Re: Imported log distance problems
Posted: 19 May 2013, 14:24
by IW3RAB
G4POP wrote:Hi Juergen,
I have to admit that I did not even look at the 4 digit Locators so completely missed that issue.
This morning I have had a quick check as it would seem that we do have an issue with 4 Digit locators, guess we never checked them because they are quiet unusual because most people use 6 digits and the microwave fraternity use 8!
I will point this annomolly out to Daniele and we will correct this as soon as possible
Hi Terry,
all JT serie protocol put in their logs a 4 digit locators.
If I connect from my locator JN65 to eg. JO01 I know my exact square (JN65vp).
If I not found the destination in a online resource I can calculate the distance to JO01nn, the center of square.
73 Sandro IW3RAB (Loc JN65vp34xn)