Garmin CSV to GPX Converter

M8TJT · Posted: Fri May 06, 2016 7:24 pm Post subject:

But how can he 'up' the speeds of the overspeed alert. The only way I can think of off the top of my head, is what he is trying by increasing the speeds in all the CSVs and the associated sound and BMP files. Not for the feint hearted, as the OP has implied.

Kremmen · Posted: Sat May 07, 2016 5:31 am Post subject:

All I can think of is use the separate overspeed function so they are all in one file then hit that file with a small macro to increase all the @xx speeds by a percentage.

A good ploy if done carefully to stop the Garmin issuing alerts when you are at the speed limit. Garmins are a bit sensitive on this one.

If you rely on overspeed warnings then to be done and used with caution and with the the usual disclaimers especially as more forces are reigning in the 10% + 2 leeway.
_________________
DashCam:
Viofo A119 V3

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

So I just gave that a try. It was difficult to test in the limited time I had, but I upped the @speeds by 10% and went for a drive.

I got the approach warnings regardless of speed. What seemed to be happening was that if I was below the overspeed speed, but over the POI speed AND not accelerating, there was no overspeed warning. If I was accelerating, I got the overspeed warning even if under the POI speed.

So that sounds very workable and should be a useful improvement for me. This was without directional alerts on this occasion.

Thanks
Stuart[/i]

Kremmen · Posted: Sat May 07, 2016 2:22 pm Post subject:

Sounds correct.

The mandatory approach warning is triggered by the # lines and that overrides the Garmin logic that if you are significantly under the limit and not accelerating then you sometimes don't get any notificatiin that there is a camera ahead.

What your saying about not accelerating for the overspeed warning is how I understand the Garmin AI works.
_________________
DashCam:
Viofo A119 V3

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

Thanks Kremmen - I'll test a bit harder (though convinced it is working as described) and report back if any different.

In the meantime, I have created an alternative set of directional voice alerts if anyone's interested. My aim was to make them as snappy as possible whilst still conveying type of camera, speed and direction. For example, mine say "unverified, fifty, west" rather than "unverified mobile camera fifty miles per hour west". They are a female synthesised voice (UK accent) which is not a million miles away from Emily.

If someone can suggest a good download site to use, I'm happy to bung the zip file up in case anyone wants it.

Thanks
Stuart

Kremmen · Posted: Sun May 08, 2016 5:53 pm Post subject:

I'm happy to include them into the install package.

Dropbox is best for me to collect them
_________________
DashCam:
Viofo A119 V3

Oscargrouch · Regular Visitor Joined: Apr 29, 2009 Posts: 79

Just to add my two penneth; what has been suggested is a good idea for those who want it. Personally, I would stick with knowing that if I am over 30mph in a 30mph zone; I would prefer the warning, then it is up to me if I want to run the gauntlet: with a possible ticket for doing 32mph in a 30mph zone, which you cannot argue against cos your doing over 30mph.
_________________
Garmin Nuvi 2599 LMT-D

Kremmen · Posted: Mon May 09, 2016 5:18 am Post subject:

?

All that's been offered is an alternative set of new voices. The functionality is still the same.
_________________
DashCam:
Viofo A119 V3

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

That's what they call a miss quote K. Or perhaps Oscar has not found the "post reply" button at the bottom of the page and thinks that the only way of posting is to quote the post above.

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

Kremmen · Posted: Mon May 09, 2016 10:07 am Post subject:

With a bit of work you could probably create a vbs or Excel script with all the known speeds in it.

Saves doing it longhand each time.

Just some IF and THEN statements and for completeness END IF.

If there's enough call for it I could build a user defined % process in but this would be on the understanding that if anyone gets nicked because they have tinkered with the file.... and that is the case for the defence your honour.
_________________
DashCam:
Viofo A119 V3

M8TJT · Posted: Mon May 09, 2016 12:02 pm Post subject:

SELECT CASE
END SELECT
would be a better option

Function ConvertSpeeds(intSpeed as integer)as integer
'Function returns the speed passed to intSpeed into _
intSpeed + 10% + 2 _
Returns zero (or whatever) if passed speed is not one of the 'Cases'

Kremmen · Posted: Mon May 09, 2016 12:42 pm Post subject:

I was thinking of a user defined %

I hate hard coding

You know what I'm going to say re timescales Very Happy

_________________
DashCam:
Viofo A119 V3

Privateer · Posted: Mon May 09, 2016 1:16 pm Post subject:

Even though I'm not a Garmin user, may I add my thoughts?

On some TomTom units you can set the system to warn you if you over-speed, however the map has to have the correct speed limit for this to work. But that's for general over-speeding. What's being discussed here is over-speeding warnings for known PGPSW speed trap sites - which is different.

Personally, I want to be warned of speed traps as I approach them, regardless of whether I'm driving above or below the speed limit. If I continue to drive above the speed limit then I want additional warnings.

I think that if you set a buffer of say +2 mph and 10% then you have no room for error if you drive in an area that has zero tolerance, i.e. in Wales where 30 means 30.

On the other hand, if your users want it then I'd give them two variables to set, the additional mph and the additional percentage, so if you gave them that and they choose +2 and +10% then a 30 speed limit would warn at 35 and a 70 speed limit would warn at 79. However if you do this I recommend that you round down the result to the nearest integer for the warning activation speed.

Regards,
_________________
Robert.
iPhone 6s Plus, iOS 14.0.1: iOS CamerAlert v2.0.7
TomTom GO Mobile iOS 2.3.1; TomTom (UK & ROI and Europe) iOS apps v1.29
Garmin Camper 770 LMT-D

Kremmen · Posted: Mon May 09, 2016 2:20 pm Post subject:

Yes

Garmin has an annoying habit of telling you that you are speeding when you're not.
I've had instances where my speedo is showing 30, Garmin is showing 28 and yet I still get the repetition overspeed warning.

What I intend to do is provide a new screen. This screen will have separate settings for 20 through 70mph and will allow each one to have it's own setting.

So you could have 30 at 30 but 40 at say 44 etc.

There will be some trial and error but if I do the change then this speed increase can be applied to both the included and separate overspeed file(s).

You are spot on though that this needs to be applied with extreme caution. Use it as 10% + 2mph on the M25 near the junction with the M23 and HADECS3 will have you.

Unfortunately I'm not in a position for some weeks to get stuck in as I'm into some serious decorating (hall stairs landing) that was in a right state.
Started prep on 8th April and finished prep 8th May. Had to be cut back to the wood in places. Just finished the ceiling emulsion today (Monday) and the first layer of primer/undercoat starts tomorrow.
_________________
DashCam:
Viofo A119 V3

	PocketGPS
	Web