It's a bit more complicated than just a 'rough table'. A significant amount of detail is required for it to work properly - at least if you want it to be correct outside of the boundaries of the rough table. See this: https://www.timeanddate.com/time/dst/2016.html ....(yes so a map can be coded , roughly into software. a table of sectors/zones)....
Rough function would be better than no function though. (at least if you can turn it on and off) That's how most dashcams seem to do it.It's a bit more complicated than just a 'rough table'. A significant amount of detail is required for it to work properly - at least if you want it to be correct outside of the boundaries of the rough table. See this: https://www.timeanddate.com/time/dst/2016.html .
Also, if memory serves me properly, there are a few areas where the time adjustment is 30 minutes versus 1 hour. Factor in that the criteria can change on an annual basis and it becomes a maintenance nightmare - more so given that it would be a secondary function of the camera.
If it works roughly it is fine. I have other dashcams that are like this and it's better than nothing. One just needs to provide a disclaimer that the limitations are X or Z up front. And with a smartly trimmed table you can get to be pretty accurate anyway.Only if it works (just ask those who are having issues with exposure).
If it works roughly it is fine. I have other dashcams that are like this and it's better than nothing. One just needs to provide a disclaimer that the limitations are X or Z up front. And with a smartly trimmed table you can get to be pretty accurate anyway.
Edit: Regardless, with a 15MB set of 28000 data points that most people use online you can be pretty much 100% spot on. Maybe the 9665 doesnt have THAT much free memory though so it would need to be a dirty set of points and not all the boundaries. Or someone would need to edit the boundaries to trim them. NOTHING of this is impossible to do. It's just a matter of planning and design (coding) before and after you make your hardware.
the GPS data used is basically just location co-ordinates and UTC time, a GPS navigation device knows where you are as it also has its own map data overlay and it's much easier to just code in which locations are in which timezone, that only works when there is corresponding map data, it won't set times for regions it has no information about, we don't have map data to interpret locations and as time is only provided as UTC (or GMT 0) the offset to suit local timezone needs to be set, it's a very simple menu adjustment that takes about 10 seconds to do
I would disagree with that philosophy.If it works roughly it is fine....
Hello, can someone from StreetGuardian please answer the GPS time sync question? I don't want to take just the word of people who are against the feature. Is it in the works, is it in the firmware? What happened to the promised plans? Thanks.
Well from a product strategy and marketing standpoint, it can give the impression of being in the stone age. And for truckers and road trippers and those who live and work anywhere near timezone boundaries, it can be a fundamentally important consideration for the camera to update to local time automatically when crossing time zones. And for all users, but especially commercial or other heavy driving users, having the wrong time stamp because they forgot or didn't realize they had to manually change the time zone could cause confusion later.It makes no business sense at all to spent money that will only benefit some customers some of the time - in this case spending 30 seconds twice a year to change a time zone.
Well, I personally don't see this being developed for any consumer level dash cam for a number of reasons already mentioned (development cost, lack of maps data, specifics changing annually, hardware limitations, etc.). More expensive commercial systems targeted towards the trucking industry may be able to make a business case....And for all users, but especially commercial or other heavy driving users, having the wrong time stamp because they forgot or didn't realize they had to manually change the time zone could cause confusion later....
And putting out a product with a partial, or 'rough', solution will give the impression of it being an inferior or second rate product with haphazard development standards.Well from a product strategy and marketing standpoint, it can give the impression of being in the stone age.....
Thus the business case. If you're going strictly for a hardcore niche market, then you can lower the priority even further. If you're trying to expand beyond that, then it raises the priority of all these absurd hang-ups that so many people have, because you want them as customers. It still doesn't necessarily make it worth messing with or even possible in the first place based on the hardware chosen. But it remains a consideration to be ranked against others for limited resources.As I've watched the dash cam market, as well as this web site develop over the years I see more and more people getting absurdly hung up and complainy over one minor feature or lack thereof
So I have not been able to ascertain from the changelogs or this discussion, maybe someone can answer: Is there a firmware out for the V1 or V2 cams that has the ability to automatically set the timezone from GPS, and set the time based off of that as well? (I remember being told this was being worked on a year or so ago for the next FW)