I noticed yesterday that the speed camera alerts were going off when I exceeded the speed limit ... NOT when I exceeded the value put into the formula (+9 MPH). I wonder why?
The formula I used was Alex Krull's:
Here's one line for an example of my Speed-Cameras.csv file after applying the formula:
-112.15595 33.46202 Speed @74 I-10 & 43rd Av AZ Phoenix poi-factory Jul07 10
The alert should go off at 74+ MPH not 65+ MPH.
What am I doing wrong?
There is a different formula in http://www.poi-factory.com/node/19045?page=2, so you need to update the formula you use.
Check to see if you have duplicates of the file. it may be either the unmodified CSV or an old GPI file. You need to check for both.
"The POI Loader will allow you to set proximity or speed alerts. When you select the Manual option in POI Loader for loading your custom POIs you will have the option to either assign a speed such as 35 MPH (or KPH depending on your preference) or a distance value such as 500ft (or meters). When you approach the point going 5 MPH less than the assigned value you will get one alert tone but if you are going that speed or greater you will get continuous alert tones. With the distance proximity it will only alert when you have reached that distance as you approach the POI.
Are you saying that the Felix Krull Excel formula no longer works? I thought the Excel formula was a work-around the Garmin default you quoted?
Thanks Box Car. I'll try it.
Visit the "Speed Camera Loading for Dummies" thread http://www.poi-factory.com/node/19045?page=2 and look for sjohnson's post dated 26 May 2010. He updated the formula I had recoded to allow it to work with 3-digit speed limits (100 km/h in Canada). It also handles the speed limits that have question marks in the file. I don't know how to show a link to a particular post in these forums, so you'll have to scroll a bit to find it.
Felix - thanks. I went there and got it. Going on another road trip (PHX to KY to CHI to BOS to NY to NC) in September and trying to do some prep work on it.
terms | privacy | contactCopyright © 2006-2020