Any further thoughts on this?
I was reading the rules on POTA activations and I think everything is correct. If you look at it from the contacted person it is a QSO from two locations. If you look at it from the locations you will have two QSOs. This is what it says:
Exchanges:
POTA does not require a formal exchange, although many activators will want to receive reports, names, and actual signal locations.
P2P contacts will require each activator to provide their park reference to the other. Be sure to record the other activator’s park reference.
You may want to provide your park information as part of your CQ or QSO. Providing your location helps hunters with beam antennas rotate for better signal.
Not sure I understand your first paragraph. But the rest I agree with the exchange part of the rules. My view is about the actual logging of the QSOs. If I understand the POTA documentation when logging activators at multiple parks. It says log the same QSO multiple times. I may be wrong and have reached out to POTA for clarification but this is what their documents say.
“ Proper use of SIG_INFO is necessary to receive all eligible P2P credits when one or both activators are activating multiple parks. For example, if you work a three-fer activator, you are eligible for three P2P credits. In that case,
list the same QSO three times in the ADIF log file, each with one of the three park references in SIG_INFO, with the rest unchanged. Failure to do so will give you only
one P2P credit and two hunter credits.”
How about a new button on the logging page. Call it New Op or Next OP or whatever. It will do two things.
It will log the current contact, then clear the call sign data and put the cursor in the call sign field.
You will be able to add as many additional ops as you need. When your done, use the regular log button for the last contact. This will be useful in a number of situations besides just POTA.
If what you wrote is correct—my English probably isn’t the best for explaining what I think—there’s no problem, and the records are being kept correctly. Simply put, POTA contacts appear here by contact, not by location. But when you download the file to put it in POTA, the contacts will be counted by location, so as the locations are saved you will have your QSOs correctly recorded.
It’s true that in POTA, QSOs are counted by the different locations contacted. So I don’t know if it would be good for POTA to display QSOs by location.
73
Any updates or anything on this thread?Seems to got dropped.
1 Like
@WX4WG Hey Billy,
Its on our list (which is lengthy at this point), just haven’t had a chance to get to it as of yet.
Thanks & 73
Brad K4AZE
1 Like
I’ve been on the same boat over this passed weekend.
I logged the first Operator, got the signal reports, park etc.,
second op give me the callsign and signal report but no park number, so I had to go and manually add that later..
I saw this 2,3 op option on a different app, when you add a comma between first and a second operator it will log both of them separate with retaining rest of the info.
Also…I think I found a small bug:
When I started to punch a callsign but lost the operator because signal went away, I deleted his callsign and started with a new operator, at the same time my operating frequency disappeared, I had to punch that frequency again, that happened multiple times.
3 Likes
Thank you @KD9ZNA, we will add a feature to make logging multiple operators much smoother very soon!
Also, thank you for the bug report, we will also take a look at that.
I would prefer a button “Copy from last QSO” which copies everything except callsign and time. So every operator gets the correct timestamp when you effectly speak to him and log him.
73 Pepe DL/HB9EVT
Maybe in POTA mode, when you are logging, down by the “Log This” button, you could have one for “Log This and another at this park” (with obviously a better label). It should retain everything, and the user would have to choose to delete either operator or park #.
Alternatively, next to operator (and park number) could be a + button to add a second operator or park. Clicking it would add another field for operator or park. Using a comma between operators and park numbers is easier from a UI perspective. You could just mention the availability of it in the tool tip.
It is also just easier from a logging perspective too. If you know you have multiple operators, who all have the same info aside from their call sign, it’s just a lot easier to just throw in a comma to create two separate log entries with the same info.
Yeah, we are saying the same thing. “UI” means “user interface”. I was saying it’s easier for the user (the logger) to log with a comma in the field.