I've seen some posts recently in various places talking about how one does #ParksOnTheAir activations, so I figured I would write up how I do it.

Firstly, as a half-fast contester and uninhibited technical specialist, I go a little overboard when compared against other activators. I run an Icom IC-7300, usually at 95 watts, into an end-fed half-wave antenna strung up about 20 feet (6 meters) above ground.

#HamRadio #AmateurRadio #AmateurFunk #RadioAmatori

I use a ridiculously large capacity 48-volt LiFePO4 battery, coupled with a 48-volt to 13.8-volt DC-DC converter rated at 30 Amps, which lets me activate for long stretches of time.

I use an all-weather sports tent to keep the sun/rain/bugs off of me, which also helps with the wind in the wintertime. I have a rubber mat I use to protect the floor of the ham pod. I set up a folding chair, and a 3-foot-by-2-foot collapsible table to hold the radio box.

My radio box includes a small Windows 10 computer which runs directly off 13.8 volts, and a Sceptre LCD monitor which likewise runs directly off 13.8 volts.

For CW, I use a K1EL WKmini keyer. When operating SSB, I use an Arlan Communications RadioSport headset with a foot switch PTT.

For logging, I run N3FJP's Amateur Contact Log #ACLog. I log my park number in the <MY_SIG_INFO> field, and other activators' park numbers in the <SIG_INFO> field. For 2fers, 3fers, nfers, I just comma-separate the parks.
For bonus nerdiness, I use a Raspberry Pi 3 with an Adafruit Ultimate GPS HAT. The GPS provides location and accurate time. The Pi is configured to use the pulse-per-second from the GPS, and acts as a stratum-1 NTP server. The logging PC uses the Pi to keep accurate time, which is essential for FT-8 operation.

The Pi also runs a PostGIS instance loaded with a custom database populated with TIGER Geo data which allows me to look up the County, State, CQ Zone, and ITU Zone for any location in the United States.

I have a custom python script which glues the GPS, GIS, and ACLog together. The script automatically updates the AC Log configuration with the correct location data from PostGIS, as well as the correct latitude, longitude, and six-character maidenhead grid square.

The script watches for the Call Tab event from N3FJP, and when the script receives it, the script sends the API commands to N3FJP to populate the per-record State, County, CQ and ITU zones, and Grid Square fields. Hitting enter to log the contact results in those values being stored in the contact record.

The script also watches for WSJT-X UDP packets, and checks the grid square against the current location. If WSJT-X has the wrong grid square, the script sends a configuration packet to WSJT-X with the correct grid square. There is a setting in WSJT-X which must be enabled to make this work.

When wrapping up my activation, I export the contacts logged during the session to a USB thumb drive for handling when I get home.

Once at home, I import the ADIF file into my main N3FJP ACLog database and upload to #LogbookOfTheWorld. To help with the uploads (which otherwise would require the creation of a station location for each park), I have configured TQSL to override station location with QTH details from the log (Preferences > Log Handling).
I also run a post-processing script I wrote to take the ADIF file and split it up the way #POTA likes it: If <MY_SIG_INFO> has comma-separated values, then a separate log file is written for each park. If <SIG_INFO> has comma-separated values, then a separate contact record is written to each log file for each park. That file then gets uploaded to the POTA website.

Finally, I use ACLog's reporting abilities to give a breakdown of states and countries for my activation, which I compute for the overall activation, as well as per-band. ACLog also generates the colored map of the United States for me.

The last step is to write up the posts and describe the photos!

73, and I hope to get you in the log!