Speedtrap Alert for Android (Split from CamerAlert Thread re

[M8TJT]

Sound plan K. But you might not be speeding at warning distance, but you might be when closer.
But on the balance of probability, a good idea.
Leo?

[marksfish]

[M8TJT]

Different problem. You appear to be talking SPECS, I am talking ordinary cameras when you are still exceeding the camera speed despite being warned about it.

WRT Specs,can you not turn off the average calculations in your scenario. I'll investigate.

[Kremmen]

Getting incorrect warnings is always going to be an issue with recently changed limits.

Unless you can selectively disable cameras, which would be difficult.
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

[M8TJT]

IIRC a double tap on the popup cancels the average calculation, therefor the nag.

Can't you disable cameras? I thought that you could and can't be assed to check. Or do you mean disable (say) the third specs in the sequence along the A27 Eastbound?

[Kremmen]

Yes, selectively deselect a small number of say Specs because the limit is wrong
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

[M8TJT]

It will ALWAYS happen before the database 'catches up'.
The solution to the problem (if it adversely affects your sensibility) is simple. Just disable the overspeed warning for SPECS and drive below the speed limit.

If you are in a SPECS zone, which you will have already been audibly warned about, and have an average speed readout at your disposal, why on earth do you need an audible alert as well anyway. (Unless of course you decide to hide your phone away in some dark and dingy glove compartment.)

[Kremmen]

I tend to look out of the front window, most of the time, not my phone.

Having a verbal warning that you're over cooking it makes you aware the instant, not when you decide to glance.
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

[M8TJT]

There is a flaw in my argument (and yours). markfish was talking about being warned at (say) 60 when the roadworks were long gone and the limit is now 70.

[Kremmen]

I realised straight away the issue that you are now correctly doing 70 but you are being nagged because you are exceeding the 50 or 60 in the warnings.

You obviously still need any other Specs to warn you but this particular stretch is the problem.

Given that these are normally motorway stretches you don't want to fiddle whilst moving and you can't pull over.

It's a catch 22
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

[MaFt]

Do we show an EXITSPECS or an END specs in that stretch?

I.e. is it our data that's incorrect or is the app not playing nice?

(or perhaps a duplicate database with older data that has a MID cam as well as a newer END cam?)

[Leo_A]

openstreetmap road network limits differ from database specs limits?

[Kremmen]

Yes, in places.

Our motorways are normally 70mph but there are a lot of roadworks at the moment and in these roadworks the limit is typically 50mph.

Nothing for you to do on this one Leo. It's a submission and verification issue to keep on top of them.
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :

[MaFt]

Ah, so this is about road speeds and not our camera speeds?

As a side-note, not sure if this helps Leo, but I've noticed that OSM uses 'signals' when it is a variable speed limit.

MaFt

[M8TJT]

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!