My wife and I do a lot of travelling around the USA and love our Nuvi 350... One deficiency in the unit seems to be it's inability to change time of arrival info, etc. when crossing into another time zone.... I wonder if anyone has thought of a way to show the co-ordinates on interstate highways where the time zone crosses them ---load them as a POI and include perhaps an alert so that we can change our clocks and adjust the arrival info in the Nuvi unit...
... One deficiency in the unit seems to be it's inability to change time of arrival info, etc. when crossing into another time zone....
Do a search of POI Factory for "time zone" (with the quotes) and you'll find many threads relating to this subject. Here are just a few:
Hope this helps.
I too would like to be alerted when I drive on interstate highways and cross into another time zone. I know the GPSr cannot change automatically nor can it compensate for the time change when calculating the est arrival time, but, I'd like to know when I've "crossed over the line" ( in a nice way of course ).
I just may take on this project.
Last month I was in Hawaii and manually adjusted the time on my Nuvi to show Hawaiian time. I did not have my MSN receiver with me in Hawaii. When I got home and plugged the Nuvi into the MSN receiver I got a message telling me that it appeared that I had moved to a new time zone and did I want to use the current time. I touched the yes button and my Nuvi was reset to Daylight Savings Time east coast! Pretty cool. I know that MSN is not ubiquitous so this feature doesn't solve all problems but at least where MSN service is available you will get a warning from them about the time zone.
Since you'll have a nearly infinite number of points to code in. Time zones in the US are not a simple matter of longitude. They follow political boundaries, rivers and just plain arbitrary courses. Indiana alone could make a person crazy.
Just think of how many point that there could be. For each road crossing a time line that is not straight.
And any point that is not a road ... off roading!.
But if I start with Interstate and US highways I will limit the number of points to plot. I'll just stay on the roadways to start. And for the record, I would not think there is a "nearly infinite" number of points for a lot of mathematical reasons.
Now I'm off to the races.
give us updated time for the time zone we are in !
Just need the first tower in the new time zone !
I like what you have done to create the time zone USA POI file.
Question: Are you done or are you moving East and increasing the number of points as time allows you to do so?
Great work, so far. Only problem is, right now the file doesn't help us poor slobs who live East of the Mississippi.
...right now the file doesn't help us poor slobs who live East of the Mississippi.
I may be poor, but not a slob (except when I eat)...lol
What, there are people east of the Mississippi? No one told me that! :+)
I will definitely move towards the east as time allows. I have been remiss in my duties on the Denver metro project but the time zones (TZpoi) idea really got me thinking. I hope to have the TZpoi complete by the end of next week, i.e. 10/27/2007
I'm curious if anyone has tried ( driven/simulated ) the proximity alerts with this file? I created the filename with "redlight" in the name because POILoader will run in express mode and automatically set the prox to 1/4 mile.
I'm also looking for a good MP3 file to play when the prox alerts are triggered. Right now, I only have a very weak "alarm clock" sound and it's not that cool. IMHO.
p.s. thanks for the kudos too.
I'll be looking forward to seeing the finished product.... I want to try it out but don't expect to be crossing any TZ's until mid Nov....
Could the alert just be a verbal "You are now approaching another Time Zone."
The new DST rules for 2007 will be in effect on the 1st Sunday of November NOT the last Sunday of October. ( http://aa.usno.navy.mil/faq/docs/daylight_time.php )
It will be interesting to see if the GPSr can handle the new "fall-back" scenario.
The firmware updates should have already handled this for most (if not all) updated models.
Lets see if the world can handle it......another 2000....lol.
But if I start with Interstate and US highways I will limit the number of points to plot. I'll just stay on the roadways to start.
What a major undertaking!
Thought you may be interested in knowing that line 60 of the Time Zones redlight.csv Last update 10/20/2007 appears to have the incorrect latitude. The file coordinates put a person in Victoria Island, Northwest Territories, Canada, not in NV/UT as indicated. Might I suggest using POI Verifier, or something similar, before posting? Also, would it work to name the file Time Zones - NOT redlight.csv to eliminate file-name confusion?
Again, hats off!
Good catch, I fixed the POI for I-80 from Nevada to Utah. I tried to test most of these points with my nuvi 650 but with 323 of them, it's too much.
I will definitely look into loading POI Verfier and checking the file.
I'll also rename it but let people know in the POI file posting page that if they use the "redlight" term in the file name they can pre-set the prox alerts to 1/4 mile. After all the forums devoted to proximity alerts and their subsequent problems, I was just giving some of the newbies a hint on how to auto-set the alerts.
end of line
I guess that's a good sign.
Any interest in a TZ file for Europe?
I just started a new job covering northwest IN. It has a funny time zone change and I will find your POI file very helpful. I have found the need to edit it however, since IN now goes on DST. It appears that when you created the file they were still not going on DST. Can you help me edit it for only northwest IN? Thanks. John
Today, I was thinking about creating a POI list for timezone changes, but noticed that one has already been created. I noticed that it is incomplete, though, and I would like to help fill in the gaps. I'll even add Canada, just for good measure.
My computer has MS Streets & Trips, which shows county lines, thus I can pinpoint the exact locations (except for the few places where the time zone lines goes through the middle of the county).
Let me know how I can help.
This actually wouldn't be that difficult since most of continental Europe is in the same time zone (UTC +1). You could start by obtaining all the crossings between Spain and Portugal, plus the "Chunnel" between France and England.
Finland is in a different time zone (UTC +2), so you could include any borders crossings with Sweden and Norway.
Other UTC+2 countries include the western former Soviet republics, plus Romania, Bulgaria, and Greece. I don't know if Garmin has map data for these countries, though, so would it be worth it to create POI files for their border crossings?
Look in the Alphabetized list of POI files. There is a Time Zone POI file there. It won't change the ETA, I don't think, but it says it will alert you when you are aproaching a change.
nspencer64 is correct, it won't change your ETA but will give you an alert. I have the POI loaded in my 2820 and I know it worked when I entered New Mexico from the east. I have my alert set at 800 feet.
I can't wait to try this out...thanx!!
Does the file shows the legal time zone boundary in places where the "de facto" time zone is different? For example, although Nevada is in Pacific Time Zone, a few towns that border the Mountain Time Zone states of Utah and Idaho are on Mountain Time. Therefore, the correct place for the time zone change POI should be outside the town, not at the state border.
Another place where this is occurs is Phenix City, AL, which is on Eastern Time, even though the rest of Alabama is on Central Time.
Why is it so important to know exactly where the time zone line is? If I'm driving cross country I can schedule my meals, hotels, etc. if I get a warning 50 or 100 miles from the actual crossover point. The time of arrival never seems to be too accurate anyway. I'll settle for just a reminder to reset my watch.
My thought exacatly as long as you know that you are getting close to a time change then i can't see what else matters. I leave in Utah and cross into Nv all the time at Wendover The line is inside the Nv border not at the state line which is about a mile to 2 miles away.
I drive through the Florida panhandle fairly regularly. The first couple of times I crossed the time line the inability of a nuvi to adjust for time zones was a bit of a frustration. If the box knows where on the planet it is, it should know what time it is. It would seem that inconveniencing a few people in Indiana would be preferable to inconveniencing everybody. I wish that Garmin could develop an update for this.
So so it is alright to inconvenience other so you arn't inconvenienced?
Don't you think that is a little one sided?
And just how much inconvenience is it? If you already know that you will be crossing a time zone, your mind should have already compensated for it.
This isn't a big deal as far as I'm concerned, but my cellphone changes when I cross a time zone, so you'd think the GPS could be easily programmed to do it also.
But the cellphone is getting the time directly from the tower, whereas the GPSr is not supplied with that information from the satallites and would need to make the calculations.
As noted in this current Time Zone thread, the new Garmin 785T will have the automatic tome zone change feature.
So yes Spullis, a GPS can and will be programmed to do it.
......for a price. Anything can be hard for the right amount of $$$$.
I would have thanked this was early GPSr feature.
Your phone signal comes from a local tower so you get the local time (and there is someone at the phone company who makes certain it is correct).
The GPS signal is from three or more satellites that can be anywhere over almost half a hemisphere, so it gets a little more difficult. Solving that depends on user input - particularly if you are somewhere that plays with daylight saving. As pointed out, it can be done but you need deeper pockets!
By definition, the GPS "knows" where it is, it shouldn't be THAT hard to program in the logic to change the clock when it crosses the timezone line. Now, modifying the ETA based on crossing timezones may be trickier and that may be why it wasn't done. However, as someone already stated, it's been done on at least one Garmin model.
-84 54.257, 30 38.003
I-10 West of Tallahassee at crossing of Applichacola River
This might need to be converted to deg.dec notation to update the csv file. I think this should be correct: -84.90429, 30.63349
I just uploaded the revised version of the USA Time Zones which has 1315 crossings. I took the latest Indiana Information about which counties are in what time zone and in Arizona I just circled the state.
I did not include roads that are dead ends across the zones (I think).
Thank goodness for cut and paste otherwise I would not be done yet.
There might be mistakes but they can be corrected. Enjoy
Thanks for the update - I'll download the data into MS Streets & Trips to test it out. Since that program shows county lines (most TZ boundaries are concurrent with county lines), I should quickly be able to tell if all points are included at the correct location.
I just uploaded the revised version of the USA Time Zones which has 1315 crossings. Enjoy
The only file I see is the one at:
and it contains only 324 crossings.
I guess it is the time line for uploading to being available by the owner of the site. I will check later and if not available, will put it on my website.
My file consists 1315 places.
I uploaded the text version to one of my websites at http://latvietislatvija.com/Time_Zones_USA.txt. Copy the file, change the txt to csv and Excel or Tourpoint Editor will open and you can save as you please.
I first took a large Rand McNalley road map book and drew the time change lines. I opened Google earth to where I could see the county lines. I opened Acme Mapper in map version and with google moving along the county lines, I had Acme give me the coordinate which I pasted in Excel and the road names if shown.
For Arizona I just went around it for it doesn't observe DST while the Navajo Nation does but the Hopi Indians who live inside Navajo reservation do not.
Looks rather comprehensive. I did spot just a handful of lines that didn't have a - in front of the longitude. I'll give it a whirl and let you know. Thanks for the work you put into this.
I just checked it and corrected it I think. Thanks.
I am still trying to figure out Hopi Nation, Navajo Nation and Arizona.
terms | privacy | contactCopyright © 2006-2019