Wrong Zone logged in CQ WW

[ny4i]

While doing some testing, I noticed that if I have CQ-WW-CW running, when I log a US call of W4RD with a zone of 3 (like I used to do when I lived in Utah as NY4I in zone 3 instead of zone 5), the RxData.QTH.Zone is set to zone 5.

I would think if the exchange was a zone, this should override the zone from any lookup. I have not yet checked but it would appear this is being overridden by the zone lookup instead of what was actually entered.

I'm looking for confirmation to make sure I am not doing something else wrong.

[n4af]

AFAIK, zone is pulled from cty.dat. Note: only exceptions to call area/zone are recorded. So something like 4u1wb (DC) is recorded in cty.dat =4U1WB(5)[8] for CQ/IARU zones.

On Tue, Apr 2, 2024 at 1:00 PM Tom Schaefer @.***> wrote:

While doing some testing, I noticed that if I have CQ-WW-CW running, when I log a US call of W4RD with a zone of 3 (like I used to do when I lived in Utah as NY4I in zone 3 instead of zone 5), the RxData.QTH.Zone is set to zone 5.

I would think if the exchange was a zone, this should override the zone from any lookup. I have not yet checked but it would appear this is being overridden by the zone lookup instead of what was actually entered.

I'm looking for confirmation to make sure I am not doing something else wrong.

— Reply to this email directly, view it on GitHub https://github.com/n4af/TR4W/issues/752, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVLCUCB5B2EI3LOFADOWTTY3LPZDAVCNFSM6AAAAABFTYKCMKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDCMBQHA2DIMA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[ny4i]

Right but if I work a 4 station on Utah (zone 3) and I log 3 which they give me, then I would think that should be put in the RxData.QTH.Zone instead of what it gets from cty.dat.

If this is letting cty.dat override the zone entered int he exchange, I would call that a bug.

Tom

On Apr 2, 2024, at 1:35 PM, Howie Hoyt @.***> wrote:

AFAIK, zone is pulled from cty.dat. Note: only exceptions to call area/zone are recorded. So something like 4u1wb (DC) is recorded in cty.dat =4U1WB(5)[8] for CQ/IARU zones.

On Tue, Apr 2, 2024 at 1:00 PM Tom Schaefer @.***> wrote:

While doing some testing, I noticed that if I have CQ-WW-CW running, when I log a US call of W4RD with a zone of 3 (like I used to do when I lived in Utah as NY4I in zone 3 instead of zone 5), the RxData.QTH.Zone is set to zone 5.

I would think if the exchange was a zone, this should override the zone from any lookup. I have not yet checked but it would appear this is being overridden by the zone lookup instead of what was actually entered.

I'm looking for confirmation to make sure I am not doing something else wrong.

— Reply to this email directly, view it on GitHub https://github.com/n4af/TR4W/issues/752, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVLCUCB5B2EI3LOFADOWTTY3LPZDAVCNFSM6AAAAABFTYKCMKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDCMBQHA2DIMA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/n4af/TR4W/issues/752#issuecomment-2032655975, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6TWSUK4KZM76LBLKQT6C3Y3LT6NAVCNFSM6AAAAABFTYKCMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZSGY2TKOJXGU. You are receiving this because you authored the thread.

[n4af]

agreed. but i cannot seem to duplicate. if i log ny4i as '"3" it logs as "3" ?? QSO: 1800 CW 2024-04-02 1801 N4AF 599 05 W4PD 599 03

QSO: 1800 CW 2024-04-02 1802 N4AF 599 05 W3AU 599 06

QSO: 1800 CW 2024-04-02 1803 N4AF 599 05 NY4I 599 03

On Tue, Apr 2, 2024 at 1:41 PM Tom Schaefer @.***> wrote:

Right but if I work a 4 station on Utah (zone 3) and I log 3 which they give me, then I would think that should be put in the RxData.QTH.Zone instead of what it gets from cty.dat.

If this is letting cty.dat override the zone entered int he exchange, I would call that a bug.

Tom

On Apr 2, 2024, at 1:35 PM, Howie Hoyt @.***> wrote:

AFAIK, zone is pulled from cty.dat. Note: only exceptions to call area/zone are recorded. So something like 4u1wb (DC) is recorded in cty.dat =4U1WB(5)[8] for CQ/IARU zones.

On Tue, Apr 2, 2024 at 1:00 PM Tom Schaefer @.***> wrote:

While doing some testing, I noticed that if I have CQ-WW-CW running, when I log a US call of W4RD with a zone of 3 (like I used to do when I lived in Utah as NY4I in zone 3 instead of zone 5), the RxData.QTH.Zone is set to zone 5.

I would think if the exchange was a zone, this should override the zone from any lookup. I have not yet checked but it would appear this is being overridden by the zone lookup instead of what was actually entered.

I'm looking for confirmation to make sure I am not doing something else wrong.

— Reply to this email directly, view it on GitHub https://github.com/n4af/TR4W/issues/752, or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABVLCUCB5B2EI3LOFADOWTTY3LPZDAVCNFSM6AAAAABFTYKCMKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDCMBQHA2DIMA>

. You are receiving this because you are subscribed to this thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub < https://github.com/n4af/TR4W/issues/752#issuecomment-2032655975>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AC6TWSUK4KZM76LBLKQT6C3Y3LT6NAVCNFSM6AAAAABFTYKCMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZSGY2TKOJXGU>.

You are receiving this because you authored the thread.

— Reply to this email directly, view it on GitHub https://github.com/n4af/TR4W/issues/752#issuecomment-2032670978, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVLCUF6YWYYLW3LUWUFB7LY3LUV3AVCNFSM6AAAAABFTYKCMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZSGY3TAOJXHA . You are receiving this because you commented.Message ID: @.***>

[ny4i]

I agree. I also checked the ADIF file and it shows up as logged.

NY4E 15m 20240402 165507 165507 599 599 CQ-WW-CW CW 21.0743 599 05 03NY4I So the issue is there is most likely code looking at the exchange but the RXData.QTH.Zone is set to 5. Should I think of the QTH.Zone as the info derived from the cty.dat location and not the info from the exchange? That is OK as I can grab the value from the exchange if I need to do so. Tom > On Apr 2, 2024, at 2:05 PM, Howie Hoyt ***@***.***> wrote: > > > agreed. but i cannot seem to duplicate. > if i log ny4i as '"3" it logs as "3" ?? > QSO: 1800 CW 2024-04-02 1801 N4AF 599 05 W4PD 599 03 > > QSO: 1800 CW 2024-04-02 1802 N4AF 599 05 W3AU 599 06 > > QSO: 1800 CW 2024-04-02 1803 N4AF 599 05 NY4I 599 03 > > On Tue, Apr 2, 2024 at 1:41 PM Tom Schaefer ***@***.***> > wrote: > > > Right but if I work a 4 station on Utah (zone 3) and I log 3 which they > > give me, then I would think that should be put in the RxData.QTH.Zone > > instead of what it gets from cty.dat. > > > > If this is letting cty.dat override the zone entered int he exchange, I > > would call that a bug. > > > > Tom > > > > > On Apr 2, 2024, at 1:35 PM, Howie Hoyt ***@***.***> wrote: > > > > > > > > > AFAIK, zone is pulled from cty.dat. > > > Note: only exceptions to call area/zone are recorded. So something like > > > 4u1wb (DC) is recorded in cty.dat > > > =4U1WB(5)[8] for CQ/IARU zones. > > > > > > On Tue, Apr 2, 2024 at 1:00 PM Tom Schaefer ***@***.***> > > > wrote: > > > > > > > While doing some testing, I noticed that if I have CQ-WW-CW running, > > when > > > > I log a US call of W4RD with a zone of 3 (like I used to do when I > > lived in > > > > Utah as NY4I in zone 3 instead of zone 5), the RxData.QTH.Zone is set > > to > > > > zone 5. > > > > > > > > I would think if the exchange was a zone, this should override the > > zone > > > > from any lookup. I have not yet checked but it would appear this is > > being > > > > overridden by the zone lookup instead of what was actually entered. > > > > > > > > I'm looking for confirmation to make sure I am not doing something > > else > > > > wrong. > > > > > > > > — > > > > Reply to this email directly, view it on GitHub > > > > , or unsubscribe > > > > < > > https://github.com/notifications/unsubscribe-auth/ABVLCUCB5B2EI3LOFADOWTTY3LPZDAVCNFSM6AAAAABFTYKCMKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDCMBQHA2DIMA> > > > > > > . > > > > You are receiving this because you are subscribed to this > > thread.Message > > > > ID: ***@***.***> > > > > > > > — > > > Reply to this email directly, view it on GitHub < > > https://github.com/n4af/TR4W/issues/752#issuecomment-2032655975>, or > > unsubscribe < > > https://github.com/notifications/unsubscribe-auth/AC6TWSUK4KZM76LBLKQT6C3Y3LT6NAVCNFSM6AAAAABFTYKCMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZSGY2TKOJXGU>. > > > > > You are receiving this because you authored the thread. > > > > > > > — > > Reply to this email directly, view it on GitHub > > , or > > unsubscribe > > > > . > > You are receiving this because you commented.Message ID: > > ***@***.***> > > > — > Reply to this email directly, view it on GitHub , or unsubscribe . > You are receiving this because you authored the thread. >

[ny4i]

I found it. I was using RXData.QTH.Zone instead of RxData.Zone. TomPrincipal Solutions ArchitectBetter Software Solutions, Inc. 727-437-2771813-205-6388 (mobile/text)On Apr 2, 2024, at 2:06 PM, Howie Hoyt @.***> wrote: agreed. but i cannot seem to duplicate.

if i log ny4i as '"3" it logs as "3" ??

QSO: 1800 CW 2024-04-02 1801 N4AF 599 05 W4PD 599 03

QSO: 1800 CW 2024-04-02 1802 N4AF 599 05 W3AU 599 06

QSO: 1800 CW 2024-04-02 1803 N4AF 599 05 NY4I 599 03

On Tue, Apr 2, 2024 at 1:41 PM Tom Schaefer @.***>

wrote:

Right but if I work a 4 station on Utah (zone 3) and I log 3 which they

give me, then I would think that should be put in the RxData.QTH.Zone

instead of what it gets from cty.dat.

If this is letting cty.dat override the zone entered int he exchange, I

would call that a bug.

Tom

On Apr 2, 2024, at 1:35 PM, Howie Hoyt @.***> wrote:

AFAIK, zone is pulled from cty.dat.

Note: only exceptions to call area/zone are recorded. So something like

4u1wb (DC) is recorded in cty.dat

=4U1WB(5)[8] for CQ/IARU zones.

On Tue, Apr 2, 2024 at 1:00 PM Tom Schaefer @.***>

wrote:

While doing some testing, I noticed that if I have CQ-WW-CW running,

when

I log a US call of W4RD with a zone of 3 (like I used to do when I

lived in

Utah as NY4I in zone 3 instead of zone 5), the RxData.QTH.Zone is set

to

zone 5.

I would think if the exchange was a zone, this should override the

zone

from any lookup. I have not yet checked but it would appear this is

being

overridden by the zone lookup instead of what was actually entered.

I'm looking for confirmation to make sure I am not doing something

else

wrong.

—

Reply to this email directly, view it on GitHub

https://github.com/n4af/TR4W/issues/752, or unsubscribe

<

https://github.com/notifications/unsubscribe-auth/ABVLCUCB5B2EI3LOFADOWTTY3LPZDAVCNFSM6AAAAABFTYKCMKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDCMBQHA2DIMA>

.

You are receiving this because you are subscribed to this

thread.Message

ID: @.***>

—

Reply to this email directly, view it on GitHub <

https://github.com/n4af/TR4W/issues/752#issuecomment-2032655975>, or

unsubscribe <

https://github.com/notifications/unsubscribe-auth/AC6TWSUK4KZM76LBLKQT6C3Y3LT6NAVCNFSM6AAAAABFTYKCMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZSGY2TKOJXGU>.

You are receiving this because you authored the thread.

—

Reply to this email directly, view it on GitHub

https://github.com/n4af/TR4W/issues/752#issuecomment-2032670978, or

unsubscribe

https://github.com/notifications/unsubscribe-auth/ABVLCUF6YWYYLW3LUWUFB7LY3LUV3AVCNFSM6AAAAABFTYKCMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZSGY3TAOJXHA

.

You are receiving this because you commented.Message ID:

@.***>

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>