# More conditions **URL:** https://forum.hamalert.org/t/more-conditions/13 **Category:** Feature Requests **Created:** [April 7, 2023, 6:20pm UTC](https://forum.hamalert.org/t/more-conditions/13 "2023-04-07T18:20:29Z") **Posts on this page:** 1 **Showing post:** 10
### 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: [May 31, 2024, 3:36pm UTC](https://forum.hamalert.org/t/more-conditions/13/10 "2024-05-31T15:36:37Z")
See also the discussion here: > [@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: --- _[View the full topic](https://forum.hamalert.org/t/more-conditions/13)._