<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>GPS Insight Blog &#187; nationwide tracking</title>
	<atom:link href="http://blog.gpsinsight.com/tag/nationwide-tracking/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gpsinsight.com</link>
	<description>Advanced GPS Fleet Tracking</description>
	<lastBuildDate>Wed, 25 Jan 2012 16:59:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>We&#8217;re ready for Daylight Savings Time this year (finally)&#8230;</title>
		<link>http://blog.gpsinsight.com/2009/02/were-ready-for-daylight-savings-time-this-year-finally/</link>
		<comments>http://blog.gpsinsight.com/2009/02/were-ready-for-daylight-savings-time-this-year-finally/#comments</comments>
		<pubDate>Sun, 01 Mar 2009 03:05:00 +0000</pubDate>
		<dc:creator>rdonat</dc:creator>
				<category><![CDATA[Arizona]]></category>
		<category><![CDATA[Miscellaneous]]></category>
		<category><![CDATA[New Features]]></category>
		<category><![CDATA[Reporting]]></category>
		<category><![CDATA[Reports]]></category>
		<category><![CDATA[GPS Insight]]></category>
		<category><![CDATA[GPS Tracking]]></category>
		<category><![CDATA[nationwide tracking]]></category>
		<category><![CDATA[Vehicle Tracking]]></category>

		<guid isPermaLink="false">http://www.gpsinsight.com/blog/?p=527</guid>
		<description><![CDATA[GPS Insight recently added functionality ensuring that reports are 100% accurate when running them across daylight savings time (DST) boundaries. We are headquartered in Scottsdale, and Arizona doesn&#8217;t &#8220;celebrate&#8221; daylight savings time which is actually really convenient from a computer standpoint (in other parts of the country, when DST hits, scheduled computer jobs either fail [...]]]></description>
			<content:encoded><![CDATA[<p>GPS Insight recently added functionality ensuring that reports are 100% accurate when running them across daylight savings time (DST) boundaries. We are headquartered in Scottsdale, and Arizona doesn&#8217;t &#8220;celebrate&#8221; daylight savings time which is actually really convenient from a computer standpoint (in other parts of the country, when DST hits, scheduled computer jobs either fail to run or run twice when scheduled between 2 &amp; 3 AM). But since Ben Franklin invented it, &amp; the rest of the world (and most of our customers) need reports accurately after they change DST settings twice a year, we needed make them happy.</p>
<p><a title="Ben Franklin Daylight Savings Time inventor" href="http://www.gpsinsight.com/blog/wp-content/uploads/2009/02/dst0.png"><img src="http://www.gpsinsight.com/blog/wp-content/uploads/2009/02/dst0.thumbnail.png" alt="Ben Franklin Daylight Savings Time inventor" width="226" height="223" /></a></p>
<p>This is something surprisingly difficult to make work for all our customers, but we finally spent a few weeks working on this to avoid customer questions (and complaints) which tend to happen twice a year during time changes.</p>
<p>We have always supported different time ZONES so that the same vehicles can be viewed from the perspective of user-based time zones (see a national customer&#8217;s various users with different time zones, below:)</p>
<p><a title="GPS Insight supports multiple time zones" href="http://www.gpsinsight.com/blog/wp-content/uploads/2009/02/dst1.png"><img src="http://www.gpsinsight.com/blog/wp-content/uploads/2009/02/dst1.thumbnail.png" alt="GPS Insight supports multiple time zones" /></a></p>
<p>However, when running historical reports such as stop reports for a time of year DIFFERENT than the current time zone setting, everything was off by an hour.</p>
<p>No longer! Thankfully, we usually only had two or three complaints about this each time it changed, but this is the right thing to do, &amp; now everything works properly.</p>
<p>Bear in mind that customers running scheduled reports would always see the correct report time, providing they ran it before the 2 AM &#8220;switch&#8221; time. Unfortunately, for multi-day reports spanning that time zone, things will look weird. But that&#8217;s due to an unnatural shift from 2 AM to 3 AM and back from 3 AM to 2 AM once a year.</p>
<p>Nothing I can do about that, sorry &#8212; that&#8217;s where our support can help you properly interpret your reports, and we encourage everyone to call if/when you have questions, problems, or suggestions.</p>
<p>If you don&#8217;t like DST (like me &#8212; it puts us 3 hours earlier than NY half the year, which means I have to wake up earlier&#8230;), take it up with Ben Franklin.</p>
<p>Rob.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.gpsinsight.com/2009/02/were-ready-for-daylight-savings-time-this-year-finally/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

