Parks on the Air® Logging Made Easy

Original author: KB2FMH
To ensure problem free processing, remember to always double check your log based on the information contained herein before uploading. It is not a race and there is no prize for immediate uploading.
The integrity of your log is your responsibility.
Table of Contents
- Why is logging for Parks on the Air so complicated?
- How does an ADIF log work?
- What is required in a POTA Log?
- What are the other fields for?
- One Call, Different Operators (Club activations)
- One Park, more than one geographical location
- What about Multi Operators that are not in a club (Special Event or DX activity)?
- What if we’re operating a Special Event Station (SES) from a Park?
- How do I log a multi-park activation properly, so all credits are given?
- Do I need to make separate files if I use different modes?
- What’s with the file naming rules – why can’t I name it My Way?
- Naming your files:
- What if I made a mistake, how do I replace the log file?
- Summary
Why is logging for Parks on the Air so complicated?
That is a question often asked by both veterans and new amateur operators upon joining the program. They are accustomed to just entering a call into a computer / web based logging application and that’s it – the computer does the rest.
Well, the answer is: It isn’t complicated at all. There are some very easy to follow parameters (Rules if you like that word) that are in place to make sure every log entered goes the right way and both activators and hunters get the achievement credits due to them.
Yes, it is an achievement driven program in a way so to ensure the integrity of the program certain simple rules are in place, easily found on the website, docs.pota.app. But this is about logging only so let’s go….
Parks on the Air has a log sorting system that uses the common “Amateur Data Interchange Format” (ADIF) file type which is used to exchange information between logging programs and log databases such as QRZ, eQSL, Club Log, LoTW etc. It is globally uniform and simple.
For the purpose of continuity, Parks on the Air uses this format so any logging program an activator may use will be compatible with our system.
How does an ADIF log work?
Imagine a spreadsheet such as that used in software like Excel or the like; there are columns and rows.
In an ADIF file the columns are called Fields, and the Rows are where the data goes. Software that reads ADIF files is designed to look for particular fields, labeled in the top row (header) of each column, then it extracts the information from those fields to essentially read the log and sort the information accordingly.
The result is what you see in your activator or hunter logs as well as your activity stats and achievement allocations.
What is required in a POTA Log?
Parks on the Air has just Five Required data fields that Must be in your log for it to be accepted and Five secondary fields for particular situations. The fields are labeled with “Tags” as they’re called.
The five required fields are: CALL (callsign of hunters) QSO_DATE, TIME_ON, MODE and BAND. These are self-explanatory. Date and Time are of course UTC (Universal Time Coordinate). No other fields are needed but can be in them without harm. To save you time, it is suggested to have your call in the field labeled STATION_CALLSIGN so let’s call it Six required fields from now on.
While you Can input the station call, park # and location if more than one is in the dropdown during the uploading, it is better to have this data inside the file. It is covered as we go through the document.
For a simple activation by one operator in a single park this set is enough to get your log processed without issue. You still only need these six data sets, just remember to change the date and put the correct UTC time when logging or transcribing from paper!
What are the other fields for?
The first set of “optional” fields is for Park identification
These fields are MY_SIG_INFO and SIG_INFO. “SIG” meaning Special Interest Group. Your park ID: Location appropriate letter(s) (US, JP, AU, NL), a dash (-) and 4 or more numbers, is put in MY_SIG_INFO. This field is the same for Every contact whether a P2P or not. If you have no P2Ps, it is ignored but, when you get that call of “park to park” in your radio, you can put the “other” operator’s park # in the field labeled SIG_INFO but it is not required for your P2P to be credited (as long as the other operator sends in a properly formatted log of course). P2Ps are matched using those six required data fields when both logs are loaded.
NOTE: If you receive a 2fer or 3fer etc.. P2P from the Other activator, just make additional entries in your log But, make sure to put something Different in the SIG_INFO field so the entries do not dupe. It can literally be anything that will differentiate each entry – as simple as 1, 2, 3 etc..
All data should be identical, Including Time, except the park numbers. That is what will present them as unique entries to our parsing system.
One Call, Different Operators (Club activations)
This is where the two fields for call signs are required. They are STATION_CALLSIGN and OPERATOR. These are used when there are operators using a call other than their own during an activation.
Example, using a typical club activity, but it holds true for any time the On-Air call is not that of the operator of the radio:
The We Love Radio Club of Galifray activates a park for its anniversary using the club call, W1WHO, as the on air callsign. Club member N1ABC is at the mic / key. Both the club and the operator are registered with individual Parks on the Air accounts.
Since the club call is the one given on air to incoming calls / hunters, W1WHO is put in the field STATION_CALLSIGN and N1ABC is put in OPERATOR. These fields are carried through with each entry by your logging application when put in during the initial setup for that park’s specific log.
When submitted and processed, the club and the operator get credit for the activation, but hunters get credit for the actual contact with the club call only, since it was a single contact. If the operator Also gives his / her call, then a separate log must be submitted for each call. Only the Station / On Air call will get P2P credits – that is what the other activator is logging.
If operators are changed during the activation, the OPERATOR field must be updated with different calls when the change occurs, so all get the proper credits to their account.
One Park, more than one geographical location
If you activate a park that is in more than one state / province / prefecture / territory, you should include the specific location in the data field labeled MY_STATE. This will allow our parsing algorithms to assign the credits properly for hunters WAS achievements and activators trying to build their Activated States matrix there are many parks, historic trails and scenic rivers that span multiple locations in all countries, so it is Your Job to know where you were and put it in the filename. If you do not include the MY_STATE field you’ll have to choose it manually when uploading your file(s). The choices are visible on the park’s info / stats page when you need it.
The MY_STATE field will be parsed for any location whether a US State, Canadian Province, Australian Territory, Japanese Prefecture, Russian Oblast or whatever is used in the country you are in.
What about Multi Operators that are not in a club (Special Event or DX activity)?
When two or more operators activate a park, presuming they all make the same contacts, a single log can be replicated for each and named accordingly for each callsign (more about naming later).
What if we’re operating a Special Event Station (SES) from a Park?
For SES calls, the operator or event coordinator secures the special call at www.1x1callsigns.org following the specific instructions for it. They then send an email with the call and usage date range to us at dx-ses@parksontheair.com and we add it to our special call management account. That SES Call is put in the log file field labeled STATION_CALLSIGN with the single operator’s call in the OPERATOR field. Hunters will get the park / points from Only the SES call, which is what is given Over the Air, while the operator gets the activation and any achievement specific to the activation Only. The event call gets the P2Ps as it is what others are logging.
Spotting an SES with multiple operators**:**
When many are spotting the same call on our spotting page there must be a /X (a unique identifier) appended after the call to not have one spot bump the previous, even if different bands / modes are used because unlike the common DX clusters, our system currently allows only one instance of a call spotted regardless of band or mode. . Only the SES call is given on the air though, without the /x identifier. We suggest using the band after the / such as K3Y/40 for 40 meters as an example.
Some folks will log it with the /X in their personal log but it only matters if they expect confirmations Outside of Parks on the Air. The important thing would be to make sure to tell any P2Ps to log ONLY the SES call, sans the /x, and You do the same in the event log. Hunters will get the park regardless of how they log the contact because it is the Activator’s log that counts.
NOTE: The Club / SES specific logging also applies for any activity of DX operators in a park somewhere.
.
How do I log a multi-park activation properly, so all credits are given?
This situation is commonly referred to as 2fers, 3fers etc.. and logging is very simple for these. Create one initial log for Any of the park numbers you’re activating, it makes no difference which – just make sure it is identified in the MY_SIG_INFO field when initiating the log, so it carries over to each entry.
DO NOT USE Any other field names! We’ve seen some folks create their own field labels and then hammer our help desk asking Why something didn’t go right. The ONLY fields recognized are those described above.
When complete, you can change the park number in different ways. You can open the log in any text editing software – I use Notepad in Windows and click edit/find and replace / replace all after changing the park number, or ADIF Master which is an application for reading and editing ADIF files. Find the MY_SIG_INFO field if using ADIF Master and select all cells in the column. Right click in one of the selected cells and choose Replace in Selection. It should show the park number in the find box, and you put the second (and third if needed in a sequential edit) park number in the “Replace With” box, apply the changes, close that dialog box and click FILE > “Save As” and rename the file with the new park number (presuming you saved and logically named the initial log).
In Notepad, which is on every Windows based computer, open the file, then EDIT > Replace, put the initial park number in the Find What box, put the other park(s) in the Replace With box and click Replace All. Close that dialog window and again, FILE > Save As, changing the park number in the filename accordingly. For MAC / Apple users, the equivalent application is called simply “TextEdit”
NOTE: Always make sure there is a DASH (-) between the location identifier and the numbers in the Park ID.
If you forget and just have for example US1234, the file will be rejected. The DASH must be in the park number (US-1234).
If you are not very computer savvy there is a very simple web based tool for editing log files - Get to a computer and visit https://wd4dan.net/adifeditor/. Drag your file in, one at a time, and select Validate from the horizontal menu (or TOOLS from the main menu line), choose Validate PARKS ON THE AIR and it will highlight any errors. You can then fix any, save the repaired file and load it with confidence.
Do I need to make separate files if I use different modes?
Absolutely not. Whether you operate with all SSB or a mix of SSB, CW, AM, FT2/4/8, Satellite and PSK31 (or Any mode you like) you only make One file for a given park. If you mix modes during an activation and use WSJT-X, just import those entries into your adi file before uploading.
As long as you enter the data accordingly for each mode, our system will sort it out during processing – we’re That good!
What’s with the file naming rules – why can’t I name it My Way?
Before we launched the Self-Uploader feature we had just 10 area coordinators processing All logs; not just from US operators but from around the globe.
During that time having a standardized file naming system made tracking logs for any future repairs easier. I personally saved every log I ever processed and if an activator said they did not get what they expected once the log was in, I could easily find what they’d sent and look for any problems.
Naming your files:
Now, to the naming issue: In preparing for self-uploading a standard had to be agreed upon for the developers to work with thus, a standard filename format was mandated to get everyone ready for when self-uploading was released.
The standard is as such –
callsign@park#-yyyymmdd
An example using one of my own activations would look like this:
KB2FMH@US-8088-20220202.adi
which was an activation at park US-8088 on February 2nd , 2022. Maintaining a uniform naming system will help You know.
What if I made a mistake, how do I replace the log file?
If you find you need a log replaced due to a mistake of a busted call, wrong mode or band, a time offset or anything else you’d like to edit after your upload is processed – You can now delete a processed upload yourself within 24 hours of uploading it. After that you would have to solicit the Help Desk to remove it.
Any logs that fail with errors or an Unknown Failure / Unhandled Exception will need to be deleted by our support staff by clicking the little down arrow to the right of the log and requesting support. This brings up an internal email style window where you can type in your request or question.
One of our support staff will reply quickly, and have been known to respond within minutes – they don’t sleep much!
Lastly, there are many different logging programs out there that put many different fields in a log file.
Fields such as Frequency, Name, Grid / Locator, County, QTH, Name, Lat / Lon, Comments etc.. are Not required for our system so do not waste time worrying about this data.
Summary
If you have Any questions that are Not answered in this document or the documents at docs.pota.app ask our Help Desk (help@parksontheair.com) or your call area coordinator Before doing anything – we’re here to help, Anytime you may need it..
Please, do not rely on hearsay from others or the so-called Facebook experts. The people who built the system and work with it daily know how it works and what is required, that’s why they are doing it.
References
- We recommend / Support the N3FJP ACLog software and have very clear instructions on setting it up for POTA use. In Fact, the developer, Scott Davis, created a POTA Template at our request.
- A great video by our own Matt Herre, N3NWV, on how to customize your ACLog application can be viewed here - youtu.be/VePKcyP8ppw
- Instructions for ACLog in general can be viewed Here - youtu.be/aIaNKCKkstM
- To download ACLog, follow this link - www.n3fjp.com/aclog.html
- Our old Help / Getting Started - FAQs section is now docs.pota.app
- Web based adif validator / editing tool - https://wd4dan.net/adifeditor/5
Remember
The most important rule of Parks on the Air is Have Fun - Now get out and activate!
What a log looks like
| STANDARD REQUIRED LOG DATA FOR ANY LOG MATCHING SYSTEM | ||||||
|---|---|---|---|---|---|---|
| # | CALL | BAND | MODE | SUBMODE | QSO_DATE | TIME_ON |
| 1 | AB3CDE | 20m | SSB / CW / FT8 | BLANK | 20260907 | 224623 |
| 2 | XE2VF | 40m | RTTY | BLANK | 20260907 | 224904 |
| 3 | IK4REG | 30m | MFSK | FT2 / FT4 | 20260907 | 225427 |
| 4 | KW9ZYX | 80m | AM / FM | BLANK | 20260907 | 230817 |
| 5 | KW9ZYX | 80m | AM / FM | BLANK | 20260907 | 230817 |
Continued below
| POTA SPECIFIC LOG DATA | |||||
|---|---|---|---|---|---|
| # | MY_SIG_INFO | STATION_CALLSIGN | OPERATOR | SIG_INFO | MY_STATE |
| 1 | US-1234 | ON AIR CALL | USE IF DIFFERENT THAN ON AIR CALL | BLANK | STATE/ PROVINCE/ PREFECTURE/ TERRITORY Etc. YOUR PARK IS IN |
| 2 | US-1234 | ON AIR CALL | BLANK | ||
| 3 | US-1234 | ON AIR CALL | BLANK | ||
| 4 | US-1234 | ON AIR CALL | 1 | ||
| 5 | US-1234 | ON AIR CALL | 2 |
- The left - Green - is the set of required data fields used for every log and can be sent as-is to QRZ, LoTW, Club Log etc. for QSL matching with those you contact who also upload to these services. You Can load with just this to POTA, and type in your call, the park ID and State/Province/Prefecture etc.., if required by the park being in more than one state. If in one location only, the park ID assigns it accordingly.
- The right - Pink - are the additional fields POTA uses to assign proper credits to the park and operators. MY_SIG_INFO is where Your park number goes, for Each entry (Each logged entry must contain all data fields).
- STATION_CALLSIGN is usually enough if it is only you, using your call. The Operator field can be left empty.
- OPERATOR is used if the on-air call is a Club, Special Event or DXpedition call with different operators using that call on the air - they put Their Call in to get activation credits.
- SIG_INFO is used when you get a P2P call from an activator who is in more than one park - a 2-Fer for instance. You Only need to have Different data, the park #s are not required, just Different characters to not dupe the second (or third if a 3Fer comes in) entry. The example entry highlighted shows one call in duplicated entries - one entry for each of two parks with the same band, mode, date and time. Again, park numbers are Not Needed, only something Different to isolate the multi-park entries. For single P2Ps nothing is needed in the SIG_INFO (their park) field.
- MY_STATE is used when your park spans More than One State/Province/Prefecture etc, which many historic trails and scenic rivers do. You put in the appropriate abbreviation so our parsing software knows where to credit the park. * These can be found on the park’s stats / info page if you are unsure.
- We require No other data; No Grids, Sig Reports, any location info like coordinates, counties, states, comments, names - ONLY what is in the matrix above. All else is just clutter that slows down the processing after uploading.