I've been recording more of my POTA and SOTA activation, and then experimenting with how to publish the results as well as exploring what information I can derive from the recordings post-activation. One thing I'm findin out is that—of course—my CW copy isn't perfect. Searching through the entire recording of an activation is a bit much for me at the moment, so I lighted on a middle ground technique:
I was fairly certain that ChatGPT could help with this coding task. I was right. The entire coding session took 14 minutes from start to finish. I told ChatGPT about the undocumented REST API presented by pota.app , gave it an example, and asked it to write a Python script for me that would accept a callsign through the Linux input pipe and then tell me either all the info for the callsign, or print that the callsign wasn't found. Out dropped a script. Then, I needed to be able to parse my log format to grab all the callsigns. I fed ChatGPT an example file:
2024_12_27 US-4571 trying new camera and counterpoise
Talked to Maine twice the same station and to ny once at least
-122.45015547881034
37.72509947349236
k5ohy,2024/12/27 22:42:00,339,539 tx
w7pct,2024/12/27 22:44:00,339,599 or
w7tf,2024/12/27 22:49:00,339,559 id
n7bbq,2024/12/27 22:52:00,339,559 az
n7wpo,2024/12/27 22:53:00,579,559 wa
wa7lnw,2024/12/27 22:54:00,559,559 ut
w4kly,2024/12/27 22:57:00,559,339 ga
w7dz,2024/12/27 23:04:00,339,559 wa
k1nf,2024/12/27 23:14:00,559,229 me
wi0s,2024/12/27 23:17:00,229,229 nm
k5ogr,2024/12/27 23:20:00,559,519 ar
k8hr,2024/12/27 23:21:00,559,559 oh
ag6ze,2024/12/27 23:23:00,229,599 ca
wa5rml,2024/12/27 23:25:00,449,559 tx
kz5q,2024/12/27 23:32:00,559,599 tx
va3uz,2024/12/27 23:33:00,339,559 on
kd7j,2024/12/27 23:35:00,449,559 or
n9snu,2024/12/27 23:36:00,569,529 il
k7gud,2024/12/27 23:38:00,559,519 id
na7c,2024/12/27 23:51:00,559,559 ut
n3rx,2024/12/27 23:54:00,339,449
wb7tlk,2024/12/27 23:59:00,569,559 wa
Comments
Post a Comment
Please leave your comments on this topic: