I have made a poi .csv file for wachovia atms that I used Garmin poi loader on. I want the alarm to notify you .25 miles before you get to the ATM. But, when I test it, I have to pull in to the branch parking lot and drive very close to the ATM before I get the alert. No matter what I do, it does the same thing. The entries in the file are like:
-80.77572,35.31792,WACHOVIA ATM 7975,8300 MEDICAL PLAZA
-79.99771,35.96875,WACHOVIA ATM 3006,833 MONTLIUE AVE
The file was originally named redlightWachovia.csv and I changed the name to redlight@20Wachovia.csv. Both of them resulted in the situation I described above. What am I doing wrong?
It may not be you. I used my home to test alerts and the results for my nuvi 750 varied. It may depend upon spare processor power and other factors. You could try 0.5 mile.
Yes, I loaded it in manual load and put in 2640 feet for the distance and still got the same thing. Somebody please tell me why it won't work.
I created a csv with the two points you posted. I named it testredlight.csv and loaded it to my unit. I simulated a route past each location.
The second one alerted fine.
The first one didn't alert. I suspect that it is too far from the road to trigger the alert or in this particular location, it appears (on the Garmin maps and on Google Maps, but not on the Google Satellite view) to not be accessible from the main roadway.
If you aren't getting alerts on the other locations, they likely have these types of issues.
Be aware that the Garmin proximity alerts work as an "along the route/road" type alert. They do not function as a radius alert. You must be traveling along the road on which the POI is located, traveling in the direction of the POI, and the POI must be sufficient close to the road in order for the alert to be triggered.
The first point is (at its closest) 127' from the road. From the experiments I did - this is too far away to trigger, in 'Map' mode. The maximum distance seemed to be more like 75'. (This could vary with firmware, unit etc ... and I could just be wrong!)
The second point seems to be located within the required range of a road (Kirkman Way) - though remember, roads are made up of precise points, joined together by infinitely thin lines and your current gps position is a large blob of uncertainty (in comparison) - so things are never quite what they seem!). This isn't a factor here - but it's worth bearing in mind...
In 'map mode', the longest possible warning is 0.3 miles. This is the distance (by road), to the POI from the North-East end of Kirkman Way. If you approach from the Montlieu Ave end, you will get (at best) 106ft of warning.
In Routing mode, none of that applies. If your computed route takes you down Kirkman Way, you will get the alert (at the distance requested (by road)). If your route does not include Kirkman Way, you will get no alert at all.
See this post:
For details of why the "@20" has no effect when combined with "Redlight", see:
I created a csv with the two points you posted.
You've done it again
Isn't it past your bedtime? : )
Thanks to both of you although I'm not too happy to get that piece of news. I have all the longs and lats for the 5,000 ATMs on the network and was hoping to alert customers whenever they get near one. I guess I'll have to settle for them just being able to find them through custom poi's and sometimes (probably rarely) being alerted, when they get close.
...and was hoping to alert customers whenever they get near one. I guess I'll have to settle for them just being able to find them through custom poi's and sometimes (probably rarely) being alerted, when they get close.
If they select one from the list and hit "Go", they'll get alerts - because now they form part of the Route... although in this case, they're probably not appropriate - they'd clash somewhat with the navigation instructions.
TourGuide Alerts are a workaround (being circular in nature) - but of course, are not available on all units.
terms | privacy | contactCopyright © 2006-2019