I tried looking for more info on the activation spanning midnight UTC issue and haven’t come up with anything…has a workaround been found (besides entering fake dates and times for part of the activation to cement everything together like the following?):
HL4/W2VLA/P,23/07/10,0001,HL/JB-017,144MHz,FM,DS4OVT,REALLY 22/07@2338–500mW 59+ (to Kimje 45km)
HL4/W2VLA/P,23/07/10,0002,HL/JB-017,144MHz,FM,DS1SED/4,REALLY 22/07@2353–5W 59+ (to Jeonju 20km)
HL4/W2VLA/P,23/07/10,0024,HL/JB-017,144MHz,FM,DS5OEO,5W 54 (to KDN L2? 100km or home 50km?)
HL4/W2VLA/P,23/07/10,0043,HL/JB-017,144MHz,FM,DS4PXG/M,5W 57 (to Byeonsando 80km)
HL4/W2VLA/P,23/07/10,0117,HL/JB-017,144MHz,FM,DS4QBE/P,500mW 56 (to Iksan 35km)
Thanks and 73–
In reply to GM4ZFZ:
One thing we have left undone is a discussion about
times. Currently SOTA activations rely on some sort of
midnight definition (not well defined).
This works ok as all Associations are in similar
timezones. Once someone in a distinctly different time
zone joins, we will have a problem!
I’m not sure it matters that a user is in a different time zone since
all times in the system are in GMT.
However, it may be a problem with summits in radically different time
zone since qso will cross the midnight boundary.
I think the way forward would be to append the Associations Table with
a +/- GMT field which would mean the database code would have
something to work with to take this issue into consideration.