Upload POTA log.
After performing park activation operations, if there are only a few communication logs, you can manually add the communication records through the web interface and upload the results.
It can also be used with N1MM's DX General Logging for record-keeping.And by modifying the bulk records and then uploading the documents, this method should work for everyone.
The method is as follows:
Export ADIF file for DX General Logging records in N1MM.
Modify the file using ADIFMaster to meet POTA's upload requirements. This typically involves adding or modifying four fields.
<MY_SIG>
<MY_SIG_INFO>
<SIG>
<SIG_INFO>
The specific content can be modified in bulk according to actual circumstances and the logging requirements outlined below.
Finally, upload the electronic LOG in ADIF format via the web.
Appendix: POTA logging requirements
(Translated by a URL-based robot based on the original text)https://docs.pota.app/docs/rules.html#logging-requirements
Log requirements
① Once the log submission is complete and all the logging requirements are met, it will be considered a valid activation.
Hunters do not need to submit logs. Only authorized operators can submit them. Hunters receive recognition points through the logs submitted by the authorized operator.
② Submitting logs does not have a time limit.
Because hunters rely on logs from activators to earn points/rewards, polite operators will not delay uploading their logs.
③ A log can cover multiple activity days, but should only cover a single park (if the park spans multiple locations). This also applies to activities involving clubs and multiple operators.
④ The log files must be in ADIF format, except for any exceptions specified at the end of this section.
See also: The "Activator Reference Section" for a detailed description of how to use these ADIF fields.
Required fields:
<STATION_CALLSIGN>or<OPERATOR>
For each QSO, the club/group log must include both<STATION_CALLSIGN> And<OPERATOR> Fields, including<STATION_CALLSIGN> This is the name of a club or group.
A single log entry should contain the same call sign in two fields, or it can be contained in only one field.
<CALL>
<QSO_DATE>
<TIME_ON>
<BAND>
<MODE>or<SUBMODE>
POTA stores a single pattern. If both a pattern and a sub-pattern are provided, the sub-pattern overrides the pattern.
Optional fields:
<MY_SIG>
<MY_SIG_INFO>
<SIG>
<SIG_INFO>
<MY_STATE>
Exceptions to ADIF by POTA
POTA accepts<BAND> 'SUBMM' sub-millimeter wavelength QSO
⑤ All logs must be uploaded through the POTA account designated for the club/group, not through individual accounts.
⑥ Invalid QSOs in the log will be rejected.
Repeated QSOs will be rejected by the upload tool.
The uniqueness of POTA QSOs depends on the following combination:
This log is (<STATION_CALLSIGN> ) Upload,
<CALL> ,<MODE> ,<QSO_DATE> ,<BAND> ,<MY_SIG_INFO> ,<SIG_INFO> , Location (e.g., park crossing inter-regional boundaries, selected during upload)
<CALL> Cannot be used with<STATION_CALLSIGN> or<OPERATOR>Same (i.e., the radio or operator cannot communicate with itself)
The QSO time cannot be scheduled for a future date.
💡 Note: If the information in a specific rule section differs from other information provided on the website (e.g., guidelines), then the rule section takes precedence. Please ensure that help@parksontheair.com Tell us about the inconsistencies.
Additional notes/guidance (partial)
The club and several operators
Generally, individuals should not use the other person's call sign during operation; instead, they should use the call sign of the club or special event when multiple operators are involved. The call sign for the club or special event should be used during the operation (e.g., during a day trip!) and recorded in<STATION_CALLSIGN> 。The operating personnel's call sign should be<OPERATOR> (Typically not used in the air). Once uploaded to the holder's account.<STATION_CALLSIGN> (See POTA logging requirements 3), this system records for the holder.<STATION_CALLSIGN> and<OPERATOR> Under the call sign.
Please refer to the POTA Guide for Clubs for planning, implementation, and operating SPOTs for our club or group activities.
Microphone transmission
When multiple people are communicating simultaneously but not under a club call sign, the operator can choose to "pass the microphone," allowing them to take turns speaking. In this case, each person should upload their own LOG according to the rules.
Connectivity between parks
Operators can communicate with another operator to earn park-to-park (P2P) points. It is strongly recommended that both operators (although not required) record the other operator's park number in the SIG\_INFO field of the ADIF log file.
The purpose of using SIG\_INFO is to ensure that all eligible P2P points are obtained when one or both parties activate multiple parks. For example, if your counterpart activates three stations, you are entitled to receive three P2P points. In this case, in the ADIF file, there will be three different SIG\_INFO entries for one of the three parks, with the same content as the other entries. If this information is not present, you will only receive one P2P point and two "headhunter" points.
Another different scenario is when, within the same UTC day, you use the same call sign multiple times from different parks. Each QSO line in your ADF file, except for the first one, must have a unique park number specified using SIG_INFO, otherwise the system will reject all QSOs as duplicates.
Matching rules
The POTA's p2p detection logic depends on (1) the data from SIG\_INFO when multiple parks are activated simultaneously, or (2) sequential rover movement.
After repeated QSO checks, each line in Adif's log file can potentially earn P2P. A unique park reference SIG\_INFO is included in each line to prevent it from being deleted due to duplicate data.
The P2P matching requires that the QSO times in both active logs must be consistent within 15 minutes.
All required fields (as specified in the rules and LOG requirements) must match.
It's necessary to perform an exact match on the call sign. If I am identified as N3VEM/M, while another active user identifies me as simply N3VEM, then these would not match.
Activate across multiple parks
If you are a "Double Park" and connected to an active "Triple Park," two ADIF log files will be generated, each with three lines. Another activation will generate three ADIF files, each with two lines. Therefore, you will receive 6 p2p points, and the other activator will also receive 6 p2p points.
闽ICP备2021006864号-7
闽公网安备35020602002794号