That is fine I will review the ADIF and fix the distances for you before I send it backDF5WW wrote:Will do![]()
Looks like that the ZIP is on the way to your email found at qrz.com.
Imported log distance problems
- G4POP
- Log4OM Alpha Team
- Posts: 11607
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Imported log distance problems
73 Terry G4POP
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: Imported log distance problems
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 ...

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



Nice helpful community here ...


73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.
- G4POP
- Log4OM Alpha Team
- Posts: 11607
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Imported log distance problems
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.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 ...![]()
This feature was implemented specifically because we have had a lot of HRD ADIF files with incorrect distances.
73 Terry G4POP
- IW3HMH
- Site Admin
- Posts: 2988
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: Imported log distance problems
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
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
Daniele Pistollato - IW3HMH
- G4POP
- Log4OM Alpha Team
- Posts: 11607
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Imported log distance problems
It's an HRD screw up Lele, the same incorrect distance issue that we had before!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
73 Terry G4POP
- G4POP
- Log4OM Alpha Team
- Posts: 11607
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Imported log distance problems
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.
Log4OM Log update fixed the distance and heading errors in the HRD ADIF.
73 Terry G4POP
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: Imported log distance problems
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 ....
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 ....
73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.
- G4POP
- Log4OM Alpha Team
- Posts: 11607
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Imported log distance problems
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
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
73 Terry G4POP
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: Imported log distance problems
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 ....

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 ....


73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.
Re: Imported log distance problems
Hi Terry,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
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)
Sandro IW3RAB