Garmin CSV to GPX Converter

[wibbley]

Hi Kremmen,

sorry to jump in here, I am a little confused & don't seem to be getting the warnings working correctly. Hope you all can help. Firstly I assume we are talking about 'CSV Converter' I have version 2013.07.22.2116 & use it with a garmin nuvi 3598 & the full pgps camera files.

Reading the destructions, I understand that there is no voice for an overspeed warning, one has to be found on t'internet. I found one that says 'caution slow down' & added this to my camera folder on the pc, naming it 'overspeed.wav'

CSV Converter all seems to work ok, I use it to download & unzip the camera files & use the default settings within the program to generate the gpx files. All thre columns then turn green.

When approaching any camera, I get the normal pgps voice warning & then the added 'caution slow down' no matter how slowly I approach the camera. Is this correct? I assumed I would only get the 'caution slow down' warning if travelling faster than the speed limit?

What I would like is the overspeed warning only when I am above the speed limit & near a camera. I assumed this is what should happen?

Kremmin, in a previous post you said "

With the new separate overspeed warning I included recently you can now differentiate between an advance warning and a subsequent overspeed warning. "

How do I do this? I have OverSpeed Warn box ticked for separate.
Please could you explain a little more.


thanks for your help & support.

[Kremmen]

Hmmm

I have an overspeed warning set and it only triggers on mine when I'm over the limit.

What I'll do later is logon to my main PC and produce a screendump of my screen so we can compare notes.
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

[Kremmen]

...
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

[m-a-r-k]

I see that you have the Approach set to 14 seconds. I think this may the reason why you aren't getting any repeat warning and I am, as I have Mobiles set to 30 seconds (the handheld laser guns can reach a very long way).
There is a delay between the Approach bing and the extra Overspeed warnings. I'm just wondering if 14 sec isn't long enough to trigger the extra warnings - you'd have passed by the camera before they are triggered.

Try a longer Approach setting, say 30s and see if you get the extra warnings.
_________________
Mark B
Garmin nüvi 350
SW V6.20, GPS SW V3.00
City Navigator Europe NT 2018.10

[m-a-r-k]

[Kremmen]

I've recently turned Mobile's off as I tend to stay within the limit. I personally only want to know when I'm approaching a fixed camera.

The Garmin default distance is 36 seconds and I found that far too long. I based my 14 and 6 seconds on roughly the same periods I used to get from my Talex which I found a good set of distances.

As I said, I have 2 fixed cameras near me that are on opposite carriageways so I can overstep the mark to test.

One of the cameras is a fixed 50 Gatso. If I do 60mph I get the initial warning and 1 additional overspeed warning. If I do 55mph I often get 2 overspeed warnings as there is obviously time to fit them in. I can see where 30 seconds would produce a string of back to back warnings but unfortunately that's Garmin and nothing I can do about it.
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

[m-a-r-k]

Sorry for being really obtuse here
So what does setting OverSpeed to zero do? You've obviously used that in the past for Mobiles.

In the past you've said (the first of several such mentions):

[Kremmen]

Setting the overspeed to zero should only produce GPX files with an included # and no @ lines.

On older Garmin units this was sufficient for them to only produce a single approach warning and that is all I used to get on both my Garmin 2200 and my Garmin 50.

You have confirmed via inspection that you have GPX files with only # in them but you are still getting continual overspeed warnings.

If this is the case then Garmin have changed their software to produce this and I have no control.

I'm planning to update my cameras this weekend and I will be setting all my overspeed to zero and then see what happens.

I'm as intrigued by this as you are.

Shame I can't use the 'GPS off' facility to simulate speeding to test !
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

[m-a-r-k]

Does any of this have to do with the Proximity Points/Alerts/Audio: Single Tone or Continuous setting on the device? I did try setting to Single Tone on one journey to no avail.

I could also experiment with a silent OverSpeed sound file, but that also means no over speed warning on Gatsos where I do feel I need them.

Argh!
_________________
Mark B
Garmin nüvi 350
SW V6.20, GPS SW V3.00
City Navigator Europe NT 2018.10

[Kremmen]

I know

The test I want to perform is to create a series of files with the just the # in them.
If you look at the current ones you should have two almost identical lines one with # and one with @

The way I understood it the # produced a mandatory warning and the @ produced the overspeed where necessary. The proximity is set by the seconds value.

So the theory is that, in my case, I will always get a warning 14 seconds before the camera regardless of my speed. The second line with the @ inside should only produce a warning when 6 seconds away and your over the limit.

What you can do, if you have time, is identify one of your local cameras and tinker with the file. You are safe to mess with both the proximity and the # and @ markers.

I am really short of time at the moment hence all the chat and no action.
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

[wibbley]

HI,

When producing the 'overspeed' file using csv converter & then opening it using 'POI Editor for Tomtom' (POIEdit does not like opening gpx files for some reason) I only get a list of files with '@' there is no '#' anywhere.

Using csv converter & the latest pgpsw camera database, it shows 15080 total cameras read, 14037 cameras written. 'POI Editor for Tomtom' shows 14200 lines.

So It seems Garmin can have a proximity alert AND overspeed alert but not just overspeed alert with no proximity warning. Just a limitation of Garmin I suppose.

Oh for a GarTom or for an open source product.....

Thanks for developing the CSV converter program, it makes downloading & installing the PGPSW database so much simpler & removing the duplicate cameras is great. It would be great to include the sox.exe and a overspeed.wav in the download, to save new users having to hunt for these files themselves.

[m-a-r-k]

I'm unable to test this at the moment until maybe Monday, but I've looked at the GPX files and looked at the different Proximity values for @ and # lines.

Here's the question that needs testing: What if I had a Proximity value of zero for the @ lines in the Mobile camera files?

At the moment when the OverSpeed setting is set to zero you aren't writing any @ lines to the GPX files. But what if you did - using zero or if not allowed 1?

Without any @ lines maybe the Garmin is taking over and making the extra warnings by itself. If the @ lines were put in with zero or a low valve, maybe, just maybe the device will follow the instructions accordingly.

I'm not holding my breath...
_________________
Mark B
Garmin nüvi 350
SW V6.20, GPS SW V3.00
City Navigator Europe NT 2018.10

[PhilHornby]

[Kremmen]

It's been ages since I looked at the code so I needed to refresh myself.

If the approach or overspeed value is set to zero then the converter ignores that type of camera event and you shouldn't get a line written.

This can be tested by setting say the Gatso50 to zero/zero and there should be no Gatso50 written.
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

[m-a-r-k]

If the idea works you could change the code and get the converter to write the line out surely?
I could quickly test it with values of 1 or I think I'll just edit the gpx files for my 2 local mobile sites.
_________________
Mark B
Garmin nüvi 350
SW V6.20, GPS SW V3.00
City Navigator Europe NT 2018.10

We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?.
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!