Garmin CSV to GPX Converter

Kremmen · Posted: Thu Jan 14, 2016 12:31 pm Post subject:

The .vbproj file is the key to loading the project into the Visual Studio program.
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

dales · Posted: Fri Jan 15, 2016 1:18 pm Post subject:

Hi K
I haven't used the KKK so I don't know its data file content.

Kremmen · Posted: Fri Jan 15, 2016 1:50 pm Post subject:

Hi

The compass points are in the description field and are displayed in the warning banner when a camera alert is triggered. The description is limited to the 8 points.

What needs to be remembered is that I have people who want the current output to remain as-is plus the Merc community are using the current output as well.

If only NSEW are required then a Garmin speed zoned set with a 4th column containing the degrees would be useful for analysis. I don't know which of the current outputs is the Ash one. I did look this morning but it wasn't obvious. I also looked at the iGo set but none seemed to be speed zoned.
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

dales · Posted: Fri Jan 15, 2016 2:11 pm Post subject:

Just 8 compass points - that's tough.

The Ash10 download is the one called CameraManager3 [ UK - Single file with all cameras].

NB if you have selected to include pMobiles, these come in the download as a separate csv.

They are a single csv ie not speedzoned, but it shouldn't take long to "speed zone" them locally, should it?
_________________
nuvi 2599LMT-D, oregon 700, basecamp, memory-map.

Kremmen · Posted: Fri Jan 15, 2016 2:33 pm Post subject:

Ta

The single file is what I feared. My code is all centred around reading in and processing each file by type then speed whilst allowing other integrated features like the adjacent (duplicate warning) removal then the RedSpeed separation.

It's as I suspected a complete rewrite from the ground up.
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

dales · Posted: Fri Jan 15, 2016 2:42 pm Post subject:

...or see if MaFt can oblige with a speedzoned version of CameraManager3 containing both degrees and compass points.

Therein lies the future for lots of PGPSW users.

Dales.
_________________
nuvi 2599LMT-D, oregon 700, basecamp, memory-map.

dales · Posted: Fri Jan 15, 2016 4:57 pm Post subject:

...or see if MaFt can oblige with an optional speedzoned Garmin file, but with just 4 compass points as an alternative to the present 8 (if the users of the description banner could reconcile themselves to this). Once again, for these banner users, 8 compass points is arguably unecessary precision.
_________________
nuvi 2599LMT-D, oregon 700, basecamp, memory-map.

Kremmen · Posted: Fri Mar 04, 2016 8:00 am Post subject:

Updated version.

A few minor bugs (they didn't affect any cameras being reported). Plus some cosmetic tidying.

Once installed the version should be 2016.03.03

https://www.dropbox.com/s/4kpnpbwlk6k2e78/CSV%20to%20GPX%20Installer.zip?dl=0
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

Kremmen · Posted: Sat Mar 05, 2016 8:38 am Post subject:

Updated version.

This latest update only affects CSV files that come from the new CSV Direction Converter:

There are a small number of Mobile and PMobile cameras that have no speed info. For the GPX converter to work out the warning proximity/distance they need to have a value. The default value is 60mph.
Yesterdays version(s) wrote 60mph into the Garmin warning banner text which more than likely could be wrong.
When these cameras are detected, the proximity will still reflect 60mph but the warning banner will omit this info.

Therefore, please download the CSV Direction Converter program as well as these cameras are marked in there so the GPX Converter can identify them.

Once installed the version(s) should be 2016.03.05

https://www.dropbox.com/s/4kpnpbwlk6k2e78/CSV%20to%20GPX%20Installer.zip?dl=0
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

sussamb · Posted: Sat Mar 05, 2016 9:07 am Post subject:

As a relative newbie to your program could you explain how it's best to update? Do we have to reinstall all files right from the start again or can we unzip the files and just copy a couple of files into our 'working directory'? If so which files?
_________________
Where there's a will ... there's a way.

Kremmen · Posted: Sat Mar 05, 2016 11:12 am Post subject:

Unfortunately I only have access to Visual Basic Express 2013 now.

That limits me to the 'ClickOnce' method of publishing.

So - uninstall the current version then install the new version.

Once installed you will need to point it to your Working Directory then check your preferred settings.
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

sussamb · Posted: Thu Mar 10, 2016 9:32 am Post subject:

Just downloaded the latest camera files and am now seeing a discrepancy between what CSV Convertor is saying is the number of files and POI Loader, they've always been the same before.

Convertor reports total of 16483, removing adjacent cameras of 985 so a total of 15498 but POI Loader reports 16436? Now using the latest version of Convertor so wondering if there is an error with it somewhere?

Also have lots of folders building up in the Application files folder? Are all these necessary or can they be deleted?
_________________
Where there's a will ... there's a way.

Kremmen · Posted: Thu Mar 10, 2016 10:39 am Post subject:

As it happens I'm working on the converters now as a few minor niggles have been detected, plus a few other issues.

What settings have you used so I can test them with the latest version? Presumably this is with yesterdays release?

Any old files in previous versions can be deleted.

\Windows\Users\[name]\AppData\Local\CSV_Direction & Kremmen for PGPSW.

The Kremmen one is completely obsolete on the latest build (not released yet) as it seems Microsoft put the publisher name in here instead of the Product name. I've therefore changed the publisher name to be the product name.

One of the main changes with the new version is that the old version used to ignore cameras, except RedLight, that had no speed. Because there is no speed I can't calculate the warning proximity.
The change is that I have assumed a dummy speed of 60mph. Therefore any Mobile or PMobile cameras that have no speed will warn you at whatever proximity you have 60mph set for.
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

sussamb · Posted: Thu Mar 10, 2016 10:53 am Post subject:

Here you go, UK selected for download from PGPSW, latest files

As for the other query, it's the folder named Application files in the working directory I was concerned about.
_________________
Where there's a will ... there's a way.

Kremmen · Posted: Thu Mar 10, 2016 11:01 am Post subject:

I've just run it here and I get 15497 as the total GPI with POILoader agreeing.

Dales did pick up on a count issue which was corrected but I can't remember which version that was fixed in.

You are still 1 out in POILoader which is interesting.
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

	PocketGPS
	Web