I’ll be activating Mont Valin (VE2/SG-002) on september 1st for the first activation in history in Canada. I hope to making this a successful activation despite not beeing a weekend so I’ll be looking for ur sigs.
Tuesday 1st September 2009
14:00 VA2SG/P on VE2/SG-002 14.060-cw7.030cw14.070-psk14.285usb
First canadian SOTA activation in history, also AO27 AO51 (Posted by VA2SG)
Good luck the the first activation in VE2. I won’t be able to work you, but I hope you make lots of contacts. I hope some of the other radio hams in VE2 go out SOTA activating as well and I hope you some other activations as well.
You will have hundreds of eager chasers looking for you!
But possibly at the wrong time!
This is alerted for 1100Z which, correct me if I’m wrong, is 5:00am LOCAL TIME in VE2 land. Do you intend to be on the summit this early or do you intend to activate it at 11:00am LOCAL TIME?
12th September… I was adding activations and spotted it.
Please change the title of this thread to “Second Canadian SOTA activation” and we can continue!
Perhaps we need Jon to change this so that you need to enter your timezone when you register for the board and always enter local time for your alerts. That way we let the server do the arithmetic and display the alert for your local time.
Perhaps we need Jon to change this so that you need to enter your
timezone when you register for the board and always enter local time
for your alerts.
I can think of many pitfalls with this. Far easier to stick to UTC throughout; it’s needed for logging anyway.
Yep !!! 11h UTC… will be 7h AM here. We are planning to have a good all day event there !! And there will be VHF contest on the states side USA… So… Yippi !!
I’m sure you can! But as an engineer the fact that there are
pitfalls to get around only makes the task more challenging and
therefore worth doing.
I think the pitfalls are human interface problems rather than technical issues.
Well the entries in the alert database would be in UTC, it’s the
displayed time that gets fondled to local time by applying the user’s
TZ correction.
Is that the user’s home local time or the local time at the activation site? Not the same thing.
A time zone is more than just an offset; you need to specify the daylight savings time rules as well. So everybody needs to be able to select the correct set of conversion rules. And the rules have to be kept up to date.
What happens when the UK Parliament decides that we will go to UTC+1 in winter and Scotland decides to opt out?
It could all be done, but I fear it would add more confusion than there is now. Amateur radio has always worked on the basis of using a common time reference world wide. It’s not a difficult concept and we of all people should be well used to it.
Given that the Internet now means that we can regularly interact in real time with people anywhere in the world, I think it’s about time that we forgot about local time zones entirely. Set all the world’s clocks to UTC, that’s what I say!