Garmin Proximity Alerts

[Kremmen]

I'm in the process of creating a program to write out .gpx files to override the Garmin default of 36 seconds as this setting pulls in cameras on adjacent roads and is therefore too broad.

I've cracked 99% of it and I have a working version.

My final problem is trying to understand how the POI Loader deals with proximity alerts.

Having read various articles I initially put 'feet' into the data field as that is the POI Loader setting I was using. This was clearly wrong as I was getting warned of cameras up to three quarters of a mile away!

I then read a few more articles and it seems that POI Loader uses Metres by default even though you have selected 'MPH and Feet'. This setting was more accurate but still not right as the alerts were now too close.
Next step was to use yards instead of metres which is better but still not right.

Example:

I've set my' Approach' figure to 15 seconds. Travelling at exactly 30 mph approaching a 30 Gatso, as soon as the alert triggers I've timed the seconds and it's 12, not 15. similarly at 50 mph the alert is triggering slightly too close.

My calculation is based on 15 seconds at 30 mph distance covered = 0.1250 of a mile = 220 yards or 201.168 metres.

= POI Loader has a mind of its own

I'll get there
_________________
DashCam:
Viofo A119 V3

[BigPerk]

Just a thought - have you tested the Garmin 36-second default in the same way? Wondering if that's correct or a little bit out as well?
_________________
David
(Navigon 70 Live, Nuvi 360)

[dales]

Just a thought - have you tried the Ash10 CameraManager utility? This allows the user to set warning times (and overspeed warning times) for each type of camera.

And yes, the values produced by Ash10 in the gpx files do not exactly tally with those expected by simple maths - there is clearly something more to the calculation that I haven't grasped.

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

[PhilHornby]

[MaFt]

Personally I just use CBROM's GPS Convertor... Have you given this a try?

MaFt

[Kremmen]

Thanks for the feedback

As far as speedo accuracy is concerned I used the Garmins own speed on a few occasions which differs from my cars digital speedo by circa 2mph at 50 so hopefully I can rule that one out.

I have considered other existing apps but being a developer I want to see if I can do my own.

I have looked at the data of others and I suspect the same may occur as the proximity settings are roughly the same?

I've tried 2 different 'name' formats, one with the @ and one without and that doesn't make any difference as it looks like the 'proximity' setting holds the key.

Once I've cracked this item with a % add-on my next project is to try and remove some of the 'duplicates' where there is a camera on both sides, being as Garmin have omitted a directional facility from their Loader.

On the M25 for example the cameras are on adjoining gantries. This triggers 2 warnings. What I'm finding is that the 'alerts' seem to get stacked up. A second alert will not trigger until the first has finished. This seems to have the effect of sometimes producing the second warning when your right on top of the camera or even just past it.

An interesting project that may take a little time to perfect.


_________________
DashCam:
Viofo A119 V3

[PhilHornby]

[Kremmen]

Thanks for that.

I have indeed noted some strange behaviour. The M25 variable alerts were almost continuous when I had the @0 within the file. When I replaced this with #0 they were less active, which is what I wanted. I've since replaced the #0 with #70 and I'm just getting the single warning. I've also noticed the behaviour you mention when you slow down or speed up within the proximity. Also, I get a Redlight warning as expected. If I stop before the lights then as soon as I set off again I get another warning. I suspect this is by design as a further reminder.

Looking at Ash's file his proximities are more or less the same as mine. His are lower, so as you say, it looks like it's firmware related. As an example, Ash has '360' for 50mph whilst mine is calculating '366' so I would expect mine to be slightly longer.

I have some rework and testing to do but I'll get there in the end. At least I know the proximities are being read in after my 'feet' goof.

One thing I have noticed, even when I was using the neat .csv file on my 2200 is that I always get the approach warning, regardless of speed, unlike some reports of no warnings at all when under the limit. I wonder if Garmin have responded to criticism?

I have downloaded the latest 3.0 firmware.

Thanks for the simulation mode tip, never thought of that
_________________
DashCam:
Viofo A119 V3

[dales]

I may have misread it, but your prog looks to me as though the Redlights are all set for a warning proximity corresponding to 30mph.

But in the database, there are Redlights at all sorts of speeds, 20...30....40...50....0 mph.

Just an observation

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

[Andy_P]

The speed data is recorded for "plain vanilla" Redlight cameras (as opposed to combined Redlight and speed), but it isn't necessarily used.

I'm not sure if Garmin/Ash's program uses the speed number in the individual camera's name or not, but other brands just have all the Redlight cameras in a single file, so they would always have the same warning distance irrespective of the speed limit in force.

"Red/speed" cameras are split up into the individual speed-limit categories though.

There is the argument/opinion that while it is possible to miss a well-hidden camera through slight inattention, there's absolutely no excuse for missing a set of traffic lights at red, so we are lucky to have the ordinary red-light cameras in the database at all!

[PhilHornby]

[Kremmen]

Thanks

Your simulation suggestion was spot on. I did a few 'runs' across known cameras and in all cases where the simulation was at the prevailing speed limit the timing was 16 seconds. This was achieved under better circumstances as I had my eyes on the unit instead of the road and I used a proper stopwatch. Based on this I'm going to back off to Metres and re-test.

I'm happy with this and I can move forward and as I said I'm going to try and cut out duplication where the same camera type is on opposite carriageways thus avoiding the double warnings.

ps: does the .gpi interrogator give any clues to the Cyclops directional info ?

Slowly but surely, onward and upward........
_________________
DashCam:
Viofo A119 V3

[MaFt]

[Kremmen]

Program output now in final testing and "the jobs a goodun"

Proximity alerts now behaving as expected.
Ability to remove most duplicate warnings caused by Garmin not allowing directional POI's via POI Loader.
Built in unzip feature.
Approach and/or Overspeed alerts.
[/list][/list]
_________________
DashCam:
Viofo A119 V3

[MaFt]

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!