Editting Speed/Red Light Camera File

 

When I edit my Speed and Redlight Camera File that I downloaded from this site and try and save it I get this pop up window:

Speed cameras.csv may contain features that are not compatible with CSV (Comma Delimited). Do you want to keep the workbook in this format? To keep this format which leaves out any incompatible features click Yes.

To preserve the features, click No. Then save a copy in the latest Excel format

To see what might be lost, click Help.

I'm opening the file in MS Office 2010 Excel, and it only gives me CVS (Comma Delimited) as the only .csv format to save. Is this the right file format that the original file is saved as or am I doing something wrong or do I need to use Extra POI Editor?

Just save it

I get that all the time and just go ahead and answer "yes"

BUT - tell us why you are editing this file, please.

Notepad

You can also open the file with Windows Notepad, make your edits and save the file without popup error messages. For a simple edit, Notepad works fine.

Speed file

jgermann wrote:

BUT - tell us why you are editing this file, please.

I use notepad and delete all the @ in the file so that I'm able to choose a specific distance that my wav file will alert me.

--
Nüvi 255WT with nüMaps Lifetime North America born on 602117815 / Nüvi 3597LMTHD born on 805972514 / I love Friday’s except when I’m on holidays ~ canuk

just interested

canuk wrote:

... I use notepad and delete all the @ in the file so that I'm able to choose a specific distance that my wav file will alert me.

Do you also delete the word "Speed" in each name?

What are the individual steps you take and what is the result of these steps?

Speed & RLC changes

I use vi (unix style text editor) to change numerous things in the csv before importing them into EPE to make a gpx out of them.

These forums choke on the unix slashes and other symbols, so I'd have to give you a dropbox location if you want to see the edit command details. Or PM me and I'll reply with the files.

I convert all Canadian metric to US English units. If I travel in Canada, 50kph is 31 mph. I'd get a ticket if I went 50mph!

I need to make a few other changes to get EPE to import them properly, as the csv form is a little too free form for accurate importing. I use the gpx in MapSource and BaseCamp to plot where the cameras are, as it makes it easier to check their accuracy when I find some at unexpected locations or where they don't exist anymore.

--
Zumo 550 & Zumo 665 My alarm clock is sunshine on chrome.

John

I had a hunch I'd pick your curiosity grin

1- After having downloaded the speed file I open it with notepad.
2- Click edition
3- Click replace
4- Research @
5- Replace by (I leave this blank)
6- Click replace all (This will remove all the @ in the file)
7- Click yes when exiting the program to save this new file

When I use POI Loader, I'm now able to insert the exact distance before my wav file alerts me of an upcoming speed camera. (1320 feet = 1/4 mile, 2640 feet = 1/2 mile etc)

Cheers smile

--
Nüvi 255WT with nüMaps Lifetime North America born on 602117815 / Nüvi 3597LMTHD born on 805972514 / I love Friday’s except when I’m on holidays ~ canuk

i was trying to understand

canuk wrote:

...
1- After having downloaded the speed file I open it with notepad.
2- Click edition
3- Click replace
4- Research @
5- Replace by (I leave this blank)
6- Click replace all (This will remove all the @ in the file)
7- Click yes when exiting the program to save this new file

When I use POI Loader, I'm now able to insert the exact distance before my wav file alerts me of an upcoming speed camera. (1320 feet = 1/4 mile, 2640 feet = 1/2 mile etc)

Cheers smile

I was trying to understand whether you were doing a semi "along the route" POI file.

Since you do not search and replace the word "Speed" in the file, POI Loader recognizes that it is dealing with a "speed camera" file (because "Speed" in in each record); and, since it does not have a specific value coming from an @x (where x is the speed - even though the file still contains the original value, like 40 or 50), POI Loader assumes a default alert speed of 0, which means you will always be alerted.

And, I assume that you run POI Loader in Manual mode but instead of using an "Alert when speed is greater than Alert speed" of x, you choose "Alert when you get close to a point" and type in 1320 or 2640. ???? I did not understand this - I would have thought it was one or the other.

Now - I start thinking of whether the "30 meters" comes into play. I have not checked this out but I assume Globe Turtle has the camera coordinatees literally "on" the road.

Clarifying

jgermann wrote:

And, I assume that you run POI Loader in Manual mode but instead of using an "Alert when speed is greater than Alert speed" of x, you choose "Alert when you get close to a point" and type in 1320 or 2640. ???? I did not understand this - I would have thought it was one or the other.

That's correct, I run the POI Loader in manual mode in order to set the specific distance I've choosen for my wav alert to go off.

If I don't delete the @ in the file, all the alerts will all go off at either 0.2 or 0.3 miles (I don't recall the specific distance) before arriving at the speed camera.

When I delete all the @ in the file I can then choose a shorter or longer distance before the alerts go off.

I gave two examples (1320 + 2640) in the amount of feet you can add into POI Loader before your alerts go off but in reality you only add one set of numbers.

The beauty using this method is the alerts will now only go off at the distance you've choosen.

I don't have this problem with the RLC file as it doesn't have the @ and once again I can choose the distance (in feet) before the alerts go off.

--
Nüvi 255WT with nüMaps Lifetime North America born on 602117815 / Nüvi 3597LMTHD born on 805972514 / I love Friday’s except when I’m on holidays ~ canuk

Proximity for speed alerts

canuk wrote:

...
If I don't delete the @ in the file, all the alerts will all go off at either 0.2 or 0.3 miles (I don't recall the specific distance) before arriving at the speed camera.

...

I guess I need to test some of these things out since I can not get to Gary Hayman's Tips any more. As I recall, Gary detailed all this.

The general rule is that the "proximity alert" distance for speed values is 36 seconds * speed (where speed is the value in the file and NOT the speed at which the device is traveling).

What I do not remember is whether the "result" is expressed in meters or in feet and/or whether this is determined by the choice one makes in POI Loader.

But, lets say that the result is in feet and the "speed" value was 40: then 36 * 40 equals 1,440 feet as the proximity distance of the alert.

On the other hand, the speed file has some entries that contain "??", so this will result in the "default" speed of "0" being used. I do not remember whether this results in the default proximity alert distance of 400 meters/0.25 miles or something else.

I offer that you could do something similar and use EPE to put a "proximity" of, say, 1320 in every record and save the file as .gpx. This is because proximity alert information listed for individual POIs in a .gpx file overrides all other proximity alert information. You would still have the word "speed" in the name of each individual record so that the alert would occur when you are just driving around as opposed to having to be "on a route".

I think I am saying all this correctly; like I said, I need to test some of these thing out.

Edit

jgermann wrote:

I get that all the time and just go ahead and answer "yes"

BUT - tell us why you are editing this file, please.

Just adding and removing locations on the files.

Awesome

canuk wrote:

I had a hunch I'd pick your curiosity grin

1- After having downloaded the speed file I open it with notepad.
2- Click edition
3- Click replace
4- Research @
5- Replace by (I leave this blank)
6- Click replace all (This will remove all the @ in the file)
7- Click yes when exiting the program to save this new file

When I use POI Loader, I'm now able to insert the exact distance before my wav file alerts me of an upcoming speed camera. (1320 feet = 1/4 mile, 2640 feet = 1/2 mile etc)

Cheers smile

This is awesome. Learnt something new. Thanks Canuk.

DOBS108

canuk wrote:

1- After having downloaded the speed file I open it with notepad.
2- Click edition
3- Click replace
4- Research @
5- Replace by (I leave this blank)
6- Click replace all (This will remove all the @ in the file)
7- Click yes when exiting the program to save this new file

It's dobs108 back in late 2010 early 2011 who shared with all of us the above trick smile

--
Nüvi 255WT with nüMaps Lifetime North America born on 602117815 / Nüvi 3597LMTHD born on 805972514 / I love Friday’s except when I’m on holidays ~ canuk

I use a 3 step process

jgermann wrote:
canuk wrote:

...
If I don't delete the @ in the file, all the alerts will all go off at either 0.2 or 0.3 miles (I don't recall the specific distance) before arriving at the speed camera.

...

I guess I need to test some of these things out since I can not get to Gary Hayman's Tips any more. As I recall, Gary detailed all this.

The general rule is that the "proximity alert" distance for speed values is 36 seconds * speed (where speed is the value in the file and NOT the speed at which the device is traveling).

What I do not remember is whether the "result" is expressed in meters or in feet and/or whether this is determined by the choice one makes in POI Loader.

But, lets say that the result is in feet and the "speed" value was 40: then 36 * 40 equals 1,440 feet as the proximity distance of the alert.

On the other hand, the speed file has some entries that contain "??", so this will result in the "default" speed of "0" being used. I do not remember whether this results in the default proximity alert distance of 400 meters/0.25 miles or something else.

I offer that you could do something similar and use EPE to put a "proximity" of, say, 1320 in every record and save the file as .gpx. This is because proximity alert information listed for individual POIs in a .gpx file overrides all other proximity alert information. You would still have the word "speed" in the name of each individual record so that the alert would occur when you are just driving around as opposed to having to be "on a route".

I think I am saying all this correctly; like I said, I need to test some of these thing out.

I use a 3 step process on the speed camera file. The first step is to do a Find and Replace (aka Search and Destroy) by entering the following into the search box after highlighting Column D. FIND: ~?? (Note the tilde (~) in front of the question marks.) Then I insert an arbitrary value in the Replace With: field. (I use 22 so I know it is a camera that was reported with no speed, but then that's my memory hook.)

The second step is much like Canuck's in that I use an Excel function to strip out everything after the @ symbol. =if(iserr(find("@",d1,1)),d1,left(d1,find("@",d1,1)-1)) and put this into cell C1. Copy C! and then paste it into the remaining cells in that column. Those cells originally having ?? replace the formula with the new value and those with an @ symbol are copied over up to the @. Highlight the column, click copy then save it as values.

Into Cell D1 I put the Speed camera formula originally developed several years ago by Sir Kull which allows you to add a "fudge factor" to the alert. (I use the default 5 increment.) Repeat the Copy and Paste then delete Column C. All the values now have an @ symbol before the speed figures after the word Speed.

And John, the way POI Loader evaluates the speed camera file is a value following the @ symbol takes precedence over the keyword Speed.

--
Illiterate? Write for free help.

You have a long memory

canuk wrote:

It's dobs108 back in late 2010 early 2011 who shared with all of us the above trick smile

canuk, you have a long memory! The other point is to keep it simple, edit in Notepad whenever possible. I set the font very large.

Notepad saves as a .txt file. Rename it to a .csv file afterward.

dobs108 smile

Agree

jgermann wrote:

I get that all the time and just go ahead and answer "yes"

BUT - tell us why you are editing this file, please.

Feel the same way - I edit the alert speed and remove not US locations.

--
Garmin Drive Smart 61 NA LMT-S

While it may seem

While it may seem counterintuitive, there are three things I remove from the entries in the files when I edit them.

1. Redlight
2. Speed
3. POI Factory branding

Redlight I remove because I manually install POI files so I set a specific distance. Speed I remove because the @ symbol automatically generates the alert distance based upon the speed in the POI entry. The POI Factory branding I remove simply because I'm OCD and don't like seeing it on my GPS.

On a side note, I don't remember if I mentioned this though I seem to recall doing so, but Canadian speed camera entries are automatically converted on my GPS into MPH. I have never needed to convert them to US measurements before running them through POI Loader.

--
"Anyone who is capable of getting themselves made President should on no account be allowed to do the job." --Douglas Adams

@ Strephon

I've personally never encountered a problem setting a specific distance with the stock redlight camera file as I have with the speed file.

The speed cameras from both countries are displayed according in the manner in which you set/program the unit (mph or kilometers)

Cheers smile

--
Nüvi 255WT with nüMaps Lifetime North America born on 602117815 / Nüvi 3597LMTHD born on 805972514 / I love Friday’s except when I’m on holidays ~ canuk

I couldn't remember how it

I couldn't remember how it was done. Only that it was done. smile

I can understand how removing the speed limit from the file can be a daunting task. For speed cameras however I prefer the automatic setting rather than setting a specific distance. This is because for red light cameras I set a very short distance of 528 feet (1/10 mile).

--
"Anyone who is capable of getting themselves made President should on no account be allowed to do the job." --Douglas Adams

Hey Wow Ewe's Guys n' Gal

I'm glad I stopped by and read r
This thread.

Y'a never know when you'll learn something interesting!
Thanks again

--
Never argue with a pig. It makes you look foolish and it anoys the hell out of the pig!

neat tricks

these are some neat tricks.

is there a trick to stop the camera alerts from coming on when travelling on a highway?

Please be more specific

dell2015 wrote:

these are some neat tricks.

is there a trick to stop the camera alerts from coming on when travelling on a highway?

If we knew a few more facts of the situation which has prompted you to ask this question, we could better frame an answer.

Thanks

x2

BarneyBadass wrote:

I'm glad I stopped by and read r
This thread.

Y'a never know when you'll learn something interesting!
Thanks again

I'm glad I started this thread, I was editing it the hard way all this time by scrolling through the data.

Thanks dobs108 and Canuk for making my life a lot easier. smile

Editing POI files

I once edited the RLC file because it contained two identical locations for one RLC. It was messing the GPS up.

It wasn't as easy as I thought it would be, but managed to somehow delete once of the entries. The hard part was locating it in the large file.

Using a Windows OS

pratzert wrote:

The hard part was locating it in the large file.

When I know what I'm looking for I hold down the ctrl key and then press the f key. A box appears and I'll put in a key word I'm looking for and it searches the entire document highlighting the word you wrote/looking for.

It's praticial as you can use this in notepad, a web page, pdf file etc.

--
Nüvi 255WT with nüMaps Lifetime North America born on 602117815 / Nüvi 3597LMTHD born on 805972514 / I love Friday’s except when I’m on holidays ~ canuk

Use Extra POI Editor

I open the files using Extra POI Editor. Once open you can add/modify/delete as needed. Then I save in GPX and also OV2 to load on my TomTom

Only because I use gpx do I have to change the name field kph

Strephon_Alkhalikoi wrote:

On a side note, I don't remember if I mentioned this though I seem to recall doing so, but Canadian speed camera entries are automatically converted on my GPS into MPH. I have never needed to convert them to US measurements before running them through POI Loader.

For example:
R/Speed 50 - 16 & 10 @31.1
which is 50kph, 31.1mph
To import into EPE, I parse the name field into Speed@nn and the rest of the name field into the address field. I remove the trailing @31.1 of the name field. So in the above case, I need the Speed 50 to read Speed@31.1 so everything is mph.

If you use csv, you probably leave the whole name field alone which would already have the trailing mph, no conversion necessary in your GPS.

--
Zumo 550 & Zumo 665 My alarm clock is sunshine on chrome.