In CIQ Simulator, we have Simulation. > Time Simulation for setting different clock times / speed up clock time simulation.
Is there a way to set the timezone in simulator also?
Specifically:
`Sys.getClockTime().timeZoneOffset`
Thanks,
Jay
In CIQ Simulator, we have Simulation. > Time Simulation for setting different clock times / speed up clock time simulation.
Is there a way to set the timezone in simulator also?
Specifically:
`Sys.getClockTime().timeZoneOffset`
Thanks,
Jay
I guess this precision would be more than good enough for 95% of the people. but I wouldn't be surprised if there are some users who live close to a border and if they set it to auto timezone, then they'll jump to the other zone multiple times a day, even though they never left their country, so I'd guess that even Garmin would recommend to these people to set the tz manually.
You cannot set the timezone manually on a Garmin watch afaik, unless you mean indirectly, by syncing with your phone
LocalMoment: it would use some geo spatial data. I'll say it again. Even a 1MB map will be ok for 99.9999% of the places. Look at the 2nd map I linked above. if you are on any pixel with a color other than the brown used for the borders, then you'll be OK. The closer you get to a border (you "step" onto the brown pixels) then it won't be that easy. It's a bit like how long is GB's border. It depends on the zoom.
So if you're walking or biking across such border, you'll have to travel at least 2 pixels (assuming the border is just 1 pixel wide) to be surely on the other side. Depending on how far north or south are it will also be different distance. (There might be better representations though) so I would guess you'll eventually see the timezone changed, but it could be 10 km after you crossed the border.
Yeah, you've moved the goalposts from: "Garmin doesn't use GPS to determine time zone" to "even if Garmin uses GPS to determine time zone, it's not precise"
Notice I never said that what Garmin is does is correct or precise. I simply stated what they do, based on what they say and what other users say.
Your implicit point was that DaveBrillhart's assumption that the Garmin TZ would change during an activity base on GPS was wrong. That was what you were responding to. According to you, it doesn't do what he thinks it does.
My point is that he is right, as far as I know.
Your original response says nothing about precision and only that you doubt TZ is automatically set from GPS. I think you made it very clear that you think the watch needs to use the paired phone to determine a change in time zone.
Now you are retroactively arguing a different point. It's fine if you want to argue a different point, but please don't do so retroactively, as if that's what you meant the whole time, in an attempt to invalidate the initial response to your original point.
Also, how do you think your phone automatically determines time zones? I think it's the same way: from your location. If you set it manually, you're asked to specify a city (at least on iphone and in linux).
So maybe the phone's TZDB is more accurate (due to having more storage space), but I don't see how the general method would be any different, unless I'm missing something.
To be clear I am addressing this point:
"So having an accurate DB for this is not that simple IMHO. This means that most probably if you are close to the border between 2 timezones, then it'll not be precise."
This point would apply to both Garmin watches and phones, except again maybe a phone has more room for a more precise TZDB (wrt to determining TZ from location coords).
Or maybe I'm wrong about exactly how it works on both Garmins and phones.
Guess what? All I said was that Garmin says they determine TZ from GPS and other users said so too.
To be clear, the following statements are distinct:
1) I doubt Garmin sets TZ from GPS
2) Maybe Garmin sets TZ from GPS, but even if they do, it's not precise
I was responding to 1), which is what you originally said / implied.
LocalMoment: it would use some geo spatial data. I'll say it again. Even a 1MB map will be ok for 99.9999% of the places.
Yes, and why wouldn't Garmin use the exact same method to determine the time zone of the device itself?
Because it's not perfect? Perfect is the enemy of good.
Again, Garmin has used this method for a long time, even before syncing time with the paired phone was a possibility.
Again, I never said it was perfect or even good, I only said that's what they do.
Recap:
- DaveBrillhart: Has anyone tested how fast the device changes time zones during a GPS activity when cross a TZ border?
- You: I doubt it does that (determine TZ from GPS). I think you would need to sync with your phone
- Me: According to Garmin and other users, it does do that (determine TZ from GPS)
- You: Determining TZ from GPS isn't precise
- Me: You said it doesn't do that at all
I'm not sure if I or you missed the point, DaveBrillhart never wrote that there's no phone with him when the DF would be tested. I agree it can be read that way, but it can be also not that way. I just wrote what I tested in my kitchen, indoors by setting the TZ of the phone manually and then clicking on sync in GCM. From here you started to talk about GPS only, without phone, etc. Which might or might not be what he meant. To me it sounded that your point was more to contradict me than to answer his question.
FYI the phone knows your TZ because of the GSM standard. You could now argue that maybe it also knows what is my TZ even if I'm in airplane mode. I doubt, but maybe you're right. I never tested this, but you're free to do so. Change your TZ manually, then remove your SIM card, turn of airplane mode, change to auto TZ, go outside and see if if it changes back and after how much time.