# Add "ITU Zone" condition similar to "CQ Zone" **URL:** \ **Category:** Feature Requests\ **Created:** [February 2, 2026, 2:03pm UTC](https://forum.hamalert.org/t/add-itu-zone-condition-similar-to-cq-zone/2391 "2026-02-02T14:03:11Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![KS9J](https://forum.hamalert.org/letter_avatar_proxy/v4/letter/k/46a35a/32.png) [@KS9J](https://forum.hamalert.org/u/KS9J)\ **Post date:** [February 2, 2026, 2:03pm UTC](https://forum.hamalert.org/t/add-itu-zone-condition-similar-to-cq-zone/2391/1 "2026-02-02T14:03:11Z")
HamAlert has been instrumental in helping me obtain various CQ WAZ award milestones. It would be great if HamAlert would add a similar condition for ITU Zones in order to assist me with the RSGB’s Worked ITU Zone award: > **[HF awards - Radio Society of Great Britain - Main Site : Radio Society of...](https://rsgb.org/main/operating/amateur-radio-awards/rsgb-hf-awards/)** I’m having to implement workarounds to identify stations in various ITU zones. Thank you, Larry KS9J ---
**Author:** ![HB9DQM](https://forum.hamalert.org/user_avatar/forum.hamalert.org/hb9dqm/32/5_2.png) [@HB9DQM](https://forum.hamalert.org/u/HB9DQM)\ **Post date:** [February 4, 2026, 8:18am UTC](https://forum.hamalert.org/t/add-itu-zone-condition-similar-to-cq-zone/2391/2 "2026-02-04T08:18:30Z")
The HamAlert backend supports ITU zones, but as we’re currently lacking a way of reliably determining the zone for each spotted callsign, the condition is not exposed in the UI. Unfortunately, the Club Log API, which is otherwise excellent for determining DXCC and CQ zone even for special callsigns, does not return ITU zone information. > ---
**Author:** ![KS9J](https://forum.hamalert.org/letter_avatar_proxy/v4/letter/k/46a35a/32.png) [@KS9J](https://forum.hamalert.org/u/KS9J)\ **Post date:** [February 5, 2026, 9:34pm UTC](https://forum.hamalert.org/t/add-itu-zone-condition-similar-to-cq-zone/2391/3 "2026-02-05T21:34:11Z")
Thank you, Manuel, for the response! I hope you (we) locate somewhere that has an API you could use. For now, I’ll continue to enter stations’ grid squares into the zone-check.eu website to identify their ITU zones. Hmm…maybe you could exploit some API from that site? Larry KS9J ---
**Author:** ![HB9DQM](https://forum.hamalert.org/user_avatar/forum.hamalert.org/hb9dqm/32/5_2.png) [@HB9DQM](https://forum.hamalert.org/u/HB9DQM)\ **Post date:** [February 10, 2026, 8:28am UTC](https://forum.hamalert.org/t/add-itu-zone-condition-similar-to-cq-zone/2391/4 "2026-02-10T08:28:56Z")
Hmm, I guess if we had a reliable, scalable way of obtaining station coordinates (lat/lon) for any given callsign, then it wouldn’t be hard to implement an ITU zone lookup like in the web application that you mentioned. Knowing the coordinates would also make a locator condition possible, something that has been requested before. I’ve investigated station location APIs in the past, but so far, no suitable solution has come up. > [@Spotter maximum distance](https://forum.hamalert.org/t/spotter-maximum-distance/321/3): > > I guess the issue is where to obtain accurate data on callsign location from, in order to have a universal solution that works for callsigns worldwide and regardless of the spot source. [QRZ.com](http://QRZ.com) comes to mind with their API, but based on a recent inquiry to their staff about bulk lookups ([Trigger "QRZ.COM entry exists" for callsign pse? - #4 by HB9DQM](https://forum.hamalert.org/t/trigger-qrz-com-entry-exists-for-callsign-pse/526/4)) I don’t think this would work in practice at HamAlert’s scale. Related: ---
**Author:** ![UN8FR](https://forum.hamalert.org/letter_avatar_proxy/v4/letter/u/85e7bf/32.png) [@UN8FR](https://forum.hamalert.org/u/UN8FR)\ **Post date:** [June 19, 2026, 1:32pm UTC](https://forum.hamalert.org/t/add-itu-zone-condition-similar-to-cq-zone/2391/5 "2026-06-19T13:32:20Z")
Manuel, it would be nice to add support for regions from cty-xxxx.zip, from the EU\_cty.dat, AS\_cty.dat, cty\_rus.dat, etc.