On Friday night I am planning to camp out, overnight on a summit. I will be active in the evening and again in the morning. As this passes 00:00 UTC. Do I log it as a single activation or two? I know it won’t matter to my activator points, but it could for chasers.
On NYD you get two activations for one ascent if you log enough contacts either side of roll over. Perfectly legit.
It’s easier in ZL/VK/JA etc.
Because during the rest of the year there was a problem with the recording of contacts with UTC rollover in between start and end, a number of us have been splitting the contacts into two activations. This was a suggested fix by a member of the MT.
One of course scores no activator points for one of the logs but it kept the logs in proper chronological order.
These days I rarely get to a peak before UTC rollover so the problem isn’t often there.
To split or not to split? It surely is up to the activator.
Let me share a recent experience. I suppose it might be relevant. Yesterday I came back form an overnight activation of SP/BZ-041. I log on paper, so once at home I entered 35 QSOs into my logging program and exported to the SOTA CSV file. There were 22 contacts on July 30th and 13 on 31st, in chronological order. I uploaded the file to Sotadata, no problems with uploading. But there are two minor issues:
In Sotadata activation logs view, upon clicking Show my chasers I can only see chasers from the first day of the activation.
When viewing the activation contacts I see them ordered by hour only. This means my contacts from July 31st (marked red in the screenshot) are shown before contacts made on 30st (orange).:
When I deleted the single log and uploaded two instead, split by date, the above issues are resolved, but as @VK3ARR observed, my total activation count was wrong (as was the activation count for the hill in question). After all, I climbed (and activated) Łopień once, not twice.
That’s why I went with single log in the end. The inconveniences thereof are minor, for me at least.
Perhaps the 2nd issue could be fixed in Sotadata, if on the single activation page contacts were ordered by date and time, not by time only.
I very regularly camp on top of summits and always record as two seperate activations. This including an overnight stay on Cross fell on New Years Eve/Day which got me 22 points.
I think it makes sense to record as two activations so that your activator log is consistent with chaser logs. Also, by putting activations on consecutive days it gives a bit of a signpost in your SOTA log for summits that you spent the night on.
With the weather I decided to play safe so just did GW/NW-041. Got a few spots of rain but all was good. The next few days look grim with high winds. However things look more settled after that. So watch this space!
There is no “can of worms” as far as i can see?? the rules are clear, 1 activation on 1 UTC day… if the time ticks accross the UTC day to the next, then happy days! Chasers that you re-work get double points… and for an extra bonus, do it on new years eve into new years day… activators AND chasers get double points then!
Take a read of the thread that I referenced. That will demonstrate how different people have taken different interpretations from the rules - and how in many parts of the world (i.e. those near the international date line) single activations spanning the UTC boundary are the norm, rather than the exception (due to the fact that arriving at a summit shortly before UTC midnight is probably the most common time to arrive).
My point being this ‘can of worms’ has been discussed, litigated and exhausted many times before. And the conclusion (from the MT) in the past has been that it is the activator’s call whether they can class a single summit visit crossing the UTC day as a single or two separate activations. The details (workarounds) of how the database can be made to understand that are also discussed - which explains the ‘odd’ behaviour noted by the earlier poster around QSO times & dates.
If you submit an activation via CSV, ADIF or FLE formats, the system will automatically handle the situation correctly even if the activation straddles two UTC days.
Yes, even on NYE/NYD activations, where the software is smart enough, and has been smart enough since 2019, to handle that correctly and uploads it as two separate activations automatically.
If you only have 2 QSOs before UTC and 2 QSOs after UTC and you upload separately, you get zero points for both. It will actually take effort to submit two activations, and the end result is to get no points.
I don’t really understand, given all that is handled automatically, why someone would go to the effort to split an activation into two. It doesn’t impact the chasers getting points, it isn’t used for confirmation of QSOs, it adds an unnecessary extra activation which not only makes the activation counts on a summit wrong, it also adjusts your points per activation, QSOs per activation, etc averages.
The only downside is some activations look a little weird on reporting, but that’s merely cosmetic and I have plans on how to fix that eventually (no, the suggestion provided above doesn’t cover all use cases)
I avoid an activation just before UTC roll over, I always wait until after unless I am sure I can score at least 4 QSO before roll over. When Hugh and I did 2 summit activation’s per day on our journeys through the out back sometimes we would try to get 1 person on air before roll over then the second person on after roll over. For us this is a morning problem as winter local time is 09:30 am a good time to arrive on a summit after a 2 or 3 hour expedition to make the summit from home or camp. We also split the modes of operation so Hugh will go first on SSB then I will go second on CW other wise no chaser points for the second person on the summit at the same time no one bothers to chase from my experience. I can always round up a score on 15m or 20m CW after Hugh has finished on 40m SSB. I had a post about this years ago and we made our way of doing it the norm for us and everyone is happy. When the system and rules where first invented it was in UK using UTC time who would have though folks would be on a summit at midnight normally. Part of the magic of SOTA world wide these days. So it was not a stupid question.
Regards Ian vk5cz . .