Hi,
One thing that I did notice that was really helpful in the cluster view was the SOTA identifiers in the cluster comment field. When I see those, I immediately go to those frequencies to help summit activators get their magic 4 contacts if I can.
It would be wonderful to have the same sort of information for POTA. I don't know how this is done, if it needs special arrangements or specific operations or whatever but wow, would that be so neat!
Thank you for hearing me out.
POTA Location IDs in Cluster View
POTA Location IDs in Cluster View
Ron (NG7V)
- G4POP
- Log4OM Alpha Team
- Posts: 11592
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: POTA Location IDs in Cluster View
The sota references are entered by the station spotting so if POTA operators dont enter the POTA ref we cant display it
73 Terry G4POP
Re: POTA Location IDs in Cluster View
Update:
I found an alternate solution for POTA:
I added a new cluster in my list of clusters: hamalert.org:7300
This cluster receives a feed from pota.app with park designations in the comment field like the sota.org cluster.
To use the cluster, you must register and set a filter aimed at the K division of POTA (for the US) with a telnet destination. When adding the cluster to Log4OM2, the telnet connection must login to the hamalert.org site on port 7300. The filter has selections for all POTA programs world-wide.
It takes about 15.5 minutes to set up because the hamalert.org site is not easy to work with until you have worked with it for 12.7 minutes.
I found an alternate solution for POTA:
I added a new cluster in my list of clusters: hamalert.org:7300
This cluster receives a feed from pota.app with park designations in the comment field like the sota.org cluster.
To use the cluster, you must register and set a filter aimed at the K division of POTA (for the US) with a telnet destination. When adding the cluster to Log4OM2, the telnet connection must login to the hamalert.org site on port 7300. The filter has selections for all POTA programs world-wide.
It takes about 15.5 minutes to set up because the hamalert.org site is not easy to work with until you have worked with it for 12.7 minutes.
Ron (NG7V)
Re: POTA Location IDs in Cluster View
Ron,ng7v wrote: 12 Apr 2023, 15:12 Update:
I found an alternate solution for POTA:
I added a new cluster in my list of clusters: hamalert.org:7300
This cluster receives a feed from pota.app with park designations in the comment field like the sota.org cluster.
To use the cluster, you must register and set a filter aimed at the K division of POTA (for the US) with a telnet destination. When adding the cluster to Log4OM2, the telnet connection must login to the hamalert.org site on port 7300. The filter has selections for all POTA programs world-wide.
It takes about 15.5 minutes to set up because the hamalert.org site is not easy to work with until you have worked with it for 12.7 minutes.
Excellent update. I've just set one up for my installation and looks like it will be working FB. I see you don't live too far away from Wil Baber - wj9b in Middleton, ID. He was/is a mentor of mine from my 2nd CWA Class.
73 - Nolan Kienitz - KI5IO
Plano, TX
Plano, TX