# Add the gridsquare data to the data that can be sent to a URL

**URL:** <https://forum.hamalert.org/t/add-the-gridsquare-data-to-the-data-that-can-be-sent-to-a-url/2445>\
**Category:** Feature Requests\
**Created:** [July 14, 2026, 7:12am UTC](https://forum.hamalert.org/t/add-the-gridsquare-data-to-the-data-that-can-be-sent-to-a-url/2445 "2026-07-14T07:12:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![VK5PJ](https://forum.hamalert.org/letter_avatar_proxy/v4/letter/v/b77776/32.png) [@VK5PJ](https://forum.hamalert.org/u/VK5PJ)\
**Post date:** [July 14, 2026, 7:12am UTC](https://forum.hamalert.org/t/add-the-gridsquare-data-to-the-data-that-can-be-sent-to-a-url/2445/1 "2026-07-14T07:12:38Z")

</div>

I use the send to URL feature to compile a web public page ( [VK5PJ handy 50 MHz spots Opening page](https://vk5pj.com/php/) ) showing activity on 50 MHz from Australia, one thing that has been missing from the quite comprehensive dataset is the Grid of the Station and the Spotter, which I would think would be available from pskreporter already? Not sure if this is a pskreporter limitation or one inside hamalert?

I would love to have the grids so I can calculate a distance for each spot i compile

Regards,

Peter, vk5pj

---

<div class="post-metadata">

**Author:** ![DL2TT](https://forum.hamalert.org/letter_avatar_proxy/v4/letter/d/ecccb3/32.png) [@DL2TT](https://forum.hamalert.org/u/DL2TT)\
**Post date:** [July 21, 2026, 4:30am UTC](https://forum.hamalert.org/t/add-the-gridsquare-data-to-the-data-that-can-be-sent-to-a-url/2445/2 "2026-07-21T04:30:48Z")

</div>

Hi Peter,

We hit the same issue on the European side, HamAlert’s send-to-URL doesn’t pass a grid locator field, even though PSKReporter itself has it. Occasionally a locator turns up buried in the raw comment text for some spots, but not reliably enough to count on.

What worked for us: we run a separate database that logs PSKReporter spots directly, keyed by callsign. When a HamAlert spot has no grid, we just look that callsign up there and take its most recent known locator. Only catch: it only fills in stations that actually report via PSKReporter, manual cluster spots stay empty. Once you have both grids, distance is just a standard Maidenhead-to-lat/lon plus haversine calculation.

[https://cqcloud.de/eu6m\_spots.html](https://cqcloud.de/eu6m_spots.html)

Happy to share more detail if useful.

73,  
Thomas, DL2TT

---

<div class="post-metadata">

**Author:** ![VK5PJ](https://forum.hamalert.org/letter_avatar_proxy/v4/letter/v/b77776/32.png) [@VK5PJ](https://forum.hamalert.org/u/VK5PJ)\
**Post date:** [July 23, 2026, 11:41pm UTC](https://forum.hamalert.org/t/add-the-gridsquare-data-to-the-data-that-can-be-sent-to-a-url/2445/3 "2026-07-23T23:41:20Z")

</div>

Hi Thomas,

Glad to know I am not the only one struggling with this, had considered creating a 2nd DB with calls and Grids in it for local lookup but unsure I want to go that far and then possiblly end up with stale data that I have to manage. I supose I could query QRZ for a grid. Hmm food for thought but it would have been nice to get it from one location.

regards, Peter, vk5pj