How close to the POI (ie traffic camera) before you get an alert. I notice that at one spot on my trip home from work, I get an alert from the next street over.
If you do a manual upload you can adjust the distance.
Using the poi loader where the drop down menu shows express just pull down and use manual and set the distance to what you want it to be.
I find that a good setting is 750 feet. This seems to work well.
I believe the redlight files trigger by the default distance of approx 1/4 mile. Redlight POIs are along-the-route and should only trigger if you are on the same street (or route) and traveling toward the light. They do not trigger anywhere within the radial distance set. That being said, I believe I received a false trigger when I passed through an intersection and there was a redlight on that cross-street a block from my intersection. My interpretation was that the GPSr, for an instant, thought I was traveling on that cross-street. It immediately went away.
The funny thing about the alert that I get is that I only get it going home, not to work. I think for some reason it misinterprets my route.
Have you looked on your map to see where the coordinates are indicating the camera is? If it happens to be in the middle of the block more than along the street, it may be trying to decide which street it is actually on.
If you choose extras, custom pois, cameras then choose that location. At the bottom a button called "show map" when pushed will show a dot or your icon where the coordinates are for.
It could also be that you are closer to the camera one way (driving West) and as you head back home (going back East) - on the other side of the road, you are just slightly further away. Potentially you are right at the cusp of the trigger. As suggested, upload the POI in manual mode and set the distance a little shorter and you should be fine. If all else fails, you can always edit that camera out of the csv, but then it will not be there as a reminder if/ when you need it later...
terms | privacy | contactCopyright © 2006-2022