QTH locator - Resolved

[ON7YK]

Hello ,

I'm just test the nice logbook programm .

In the settings options I activeted that LOG4OM take qrz.com as callsign loock up info.

I find out that al my calls have a wrong QTH loc in your program.

My calls :
ON7YK in qrz.com is JO20XL in your prg it is JO20FM
C56YK in qrz.com is IK13PK in your prg it is IK13XJ
C5YK in qrz.com is IK13PK in your prg it is IK13XJ
C5S in qrz.com is IK13PK in your prg it is IK13xj


73' de C5YK

[G4POP]

Hello Andre,
Well that is a really strange one!

I have just tried all of your calls using QRZ lookup and they all work fine.

However if I use the HamQTH lookup the result is as you describe, although doing the same lookups on the HamQTH website they are returned correctly!

For now please ensure that you use the QRZ lookup by clicking the third dot down alongside 'Use QRZ.COM' and I will ask Daniele to check this out.

Our apologies for this but you are the first person to identify this issue.

73 Terry G4POP

[IW3HMH]

If you don't have a paid subscription to QRZ.COM the locator will not be provided via XML query. HAMQTH will provide this information for free, if you've joined their website and set Log4OM to use those data.

When locator is missing, Log4OM uses the country center coordinates to determine an approximate bearing for your antennas.

In your sample all C5xxx reports the same locator, that is the country center.

73
Daniele IW3HMH

[ON7YK]

Hello ,

Tnx for you reply.

Very important LOG4OM give me a locator but it is not the right one ...


1 : In the settings I put this one that I only use QRZ.COM for the callsign information.

2 : I'am since a very long time member of QRZ.com as full premium subscriber with all my call signs ( look on qrz.com) and in the qrz details you see that my
locator is correct and also pointed on qrz map , and not in the center of the land.
For my Belgium callsign LOG4OM give my JO20FM il live in JO20XL .......

3: When I'm using other log programs like winlog, hrd, dxlab the loock up info is always correct with my exact QTH locator and this info is coming from QRZ.COM.

73' de C5YK (ON7YK / C56YK / C5S)

[G4POP]

Hello ,

Tnx for you reply.

Very important LOG4OM give me a locator but it is not the right one ...


1 : In the settings I put this one that I only use QRZ.COM for the callsign information.

2 : I'am since a very long time member of QRZ.com as full premium subscriber with all my call signs ( look on qrz.com) and in the qrz details you see that my
locator is correct and also pointed on qrz map , and not in the center of the land.
For my Belgium callsign LOG4OM give my JO20FM il live in JO20XL .......

3: When I'm using other log programs like winlog, hrd, dxlab the loock up info is always correct with my exact QTH locator and this info is coming from QRZ.COM.

73' de C5YK (ON7YK / C56YK / C5S)

Hi Andre,
This is what I don't understand, like you I am a long term paid subscriber and for me QRZ returns the correct results although I have an issue with HamQTH lookups! That is why I went into detail about clicking the correct button in settings to ensure that you were getting a QRZ and not a HamQTH lookup.

We have had an instance where the password that a user had for QRZ included a - Hyphen which caused a problem so I wonder if your password includes anything other than a number or letter as perhaps you not being logged in correctly because of something like this?

As always its probably a really silly explanation we just have to find it!

73

[ON7YK]

Hello Terry,

You are right .
It is the password.
Other logbook programs giving me a alert when the connection fail like example wrong password etc..

you see there is always a moment that we are learning , sorry for your time
so I can start to test.

73' C5YK André

[G4POP]

Thanks Andre,
We learn all the time and Daniele has now changed the program to allow these other characters so the next release will accept them.

However we need to add a password error trap and warning in the near future.

73

[IW3HMH]

mmmh checking if there is a suitable way to get wrong password exceptions. I think something should be written on the log file, and i've troubles to popup a message due the fact all the calls to external sources are asynchronous and on separated threads.

I'll check that, and think about a "validate password" button somewhere...

thanks for reporting
73
Daniele

[G4POP]

Just a test button and send enquiry for a known call and check response?

Terry

[IW3HMH]

no, because a call can change.
A roundtrip on QRZ/HAMQTH logon procedures to check if users/password are ok

73
Daniele