Planning a first POTA rove: UTC rollover, two-fers, 10 QSOs per park, and logging without headaches
- Replies 2
- Views 32
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
I'm putting together a plan for a one-day rove through several parks and want to sanity-check the details before anyone gets burned by a logging mistake. The basics as I understand them: every park has a reference like K-0001 (country prefix, dash, number), an activator needs at least 10 valid QSOs in a single UTC day to get credit for that park, and hunters get credit by working activators, with the credit tied to the activator's uploaded log.
Here are the points I'd like the group to poke at.
First, the UTC day. If you start at a park in the late afternoon local time and the clock passes 0000Z mid-session, the QSOs split across two UTC dates. You can end up with 6 contacts on one date and 6 on the next, and neither counts as a valid activation. Checking what time 0000Z falls in your local time before you leave is cheap insurance.
Second, two-fers and three-fers. Some parks overlap, for example a state park inside a larger national trail or forest, each with its own reference. You can activate all of them from one spot if you're physically inside each boundary. Each reference needs its own 10 QSOs, and your log needs to carry every reference. The usual approach is to put the references in the park field of your logger, comma-separated, and then confirm how the upload handles it. Mapping boundaries ahead of time is worth the effort, because the parking lot can be inside one park and the picnic table you actually set up at can be in another.
Third, spotting and logging. I plan to self-spot on the POTA site or app with frequency, mode and park reference, and update the spot if I move. Spots from the Reverse Beacon Network can show up for CW and digital if you call CQ POTA, but I wouldn't count on it in a weak-signal location. For logging, I'll keep a paper backup, log in a program that supports POTA ADIF fields, and export one file per park per UTC day for upload. Does anyone have a workflow for roves that keeps those files from getting mixed up?
Fourth, equipment and rules. Power isn't a factor in the 10-QSO requirement, so QRP is fine, but each park has its own rules on things like antenna supports, trees, drones, vehicles off pavement and quiet hours. I'd rather read the land manager's page than assume an end-fed wire thrown over a branch is acceptable.
What have you found works best for rove logistics, and what would you check before leaving the driveway?
Link to comment
https://www.hamradiobase.com/forums/topic/11439-planning-a-first-pota-rove-utc-rollover-two-fers-10-qsos-per-park-and-logging-without-headaches/Share on other sites