Garmin CSV to GPX Converter

Kremmen · Posted: Mon May 09, 2016 3:17 pm Post subject:

The current program logic allows for the @ lines to be within the main files or in a separate combined file (overspeed.gpx).

If in the main files then the overspeed warning is just the normal wav warning that was used for the approach.

The combined overspeed file allows a separate wav warning, I do provide an overspeed.wav for this.

What has been currently applied is a fix to the combined file as this is easier. If I do it within the program I can apply the higher threshold in both options, plus, I can maintain the proximity at the same place.

Well I know what I mean Very Happy

_________________
DashCam:
Viofo A119 V3

M8TJT · Posted: Mon May 09, 2016 7:33 pm Post subject:

Privateer · Posted: Tue May 10, 2016 11:40 am Post subject:

Kremmen · Posted: Tue May 10, 2016 2:04 pm Post subject:

They seem to have some AI that can determine that you are close to the limit so it issues warnings to stop you accelerating into trouble.

The request is understandable. Unfortunately I have a lack of time at the moment to do it as it needs a proper job doing, not something to be rushed.
_________________
DashCam:
Viofo A119 V3

stuartb · Occasional Visitor Joined: Oct 25, 2005 Posts: 43

Kremmen · Posted: Tue May 10, 2016 6:27 pm Post subject:

Unfortunately, as posted here quite a few times historically, you don't always get an approach warning if the Nuvi thinks you are sufficiently below the limit.

We used to get quite a few posts about missing cameras. This phenomenon only raises its head with the @ marker and why I use the # marker to force an approach warning.
_________________
DashCam:
Viofo A119 V3

stuartb · Occasional Visitor Joined: Oct 25, 2005 Posts: 43

Thanks for clarifying - I meant the behaviour as tested using your program.

Stuart

Kremmen · Posted: Wed May 11, 2016 12:20 pm Post subject:

_________________
DashCam:
Viofo A119 V3

porge · Lifetime Member Joined: Jan 18, 2009 Posts: 25

hi guys, not used this process for a fair while, but upon downloading the converter, i am getting this message, has something changed that im missing?

invalid file format

example "Expecting gatso_Fifty.CSV not Gatso_50.csv ?

M8TJT · Posted: Sun May 15, 2016 3:52 pm Post subject:

You must use the converter to unzip the file after downloading. The unzipping process in the converter also changes the filenames to the accepted ones.

Oh, and by the way, it's all in the help file.

Kremmen · Posted: Sun May 15, 2016 3:52 pm Post subject:

Exactly as per the error message.

Look it up in the help manual for the explanation.

It basically means you have unzipped the PGPSW file outside of the Converter. Use the Converters own unzip facility because it performs other necessary pre actions.

Being as you are not the first to mention this recently added warning I'm thinking that previously you may have run the Converter using the _50 instead of _fifty.

If that was the case then using the Converter is pointless because the Garmin would have overridden the proximity distances you set and used Garmins default 36 seconds.
_________________
DashCam:
Viofo A119 V3

M8TJT · Posted: Sun May 15, 2016 3:54 pm Post subject:

Beecha K.

As it now seems to be a fairly common problem, when you have finished painting K, perhaps the error message could give a clue as to why the error is being raised? Wink

Kremmen · Posted: Sun May 15, 2016 5:07 pm Post subject:

Surely it does ?

It says it's found _50 but is expecting _fifty.

Looking at the csv, bmp and wav filenames in the 3 displayed panels I would hope would be enough ?

I could add a further line to the message to use the Converter to unzip the PGPSW zip file.
_________________
DashCam:
Viofo A119 V3

M8TJT · Posted: Sun May 15, 2016 7:01 pm Post subject:

	PocketGPS
	Web