Home PageFacebookRSS News Feed
Read the current newsletter! Weekly
TomTom Offers Speed Camera Data to Licence Partners

Article by: Darren Griffin
Date: 24 Mar 2011

You would be forgiven for wondering whether TomTom had a straight face when they penned "The most complete range of speed camera warnings", "provides warnings not readily available from most content providers" and "represents the widest coverage of the freshest data" as a description of their speed camera data.

But those are the words TomTom chose to describe their speed camera data in the glowing press release announcing the launch of the product to licence partners.

I'm sure those of you who have had opportunity to sample their data and compare it with ours might use some other words to describe it, perhaps 'laughable', or 'riddled with errors' or containing more mistakes than an MP's expenses claim'.

And at the bargain price of 34.99 per year, it makes my earlier post about charging for our database all the more relevant. They freely admit to sourcing data in part from the user community so where is their reward to those who contribute? Do they get free access for life, a year or even a discount on their next renewal? No they don't.

TomTom need to stick to the services they are good at, navigation and traffic, and leave the rest to those who can offer a decent service. TomTom have been offering speed cameras for some years and the service is no better now than it was when they started but it is more expensive.

So if you were in any doubt as to where to spend your money when sourcing speed camera data, be you an individual or a TomTom license partner, www.pocketgpsworld.com is the answer.

Posted by MaFt on Thu Mar 24, 2011 12:27 pm Reply with quote

their PR is all 100% true:

News Team Wrote:
"The most complete range of speed camera warnings"

Yes, they have a complete range of warnings - they have some that do a beep, some that go ding, some that go wibble wibble, awooga awooga, ding ding, dong dong, buzzzzzzz...

News Team Wrote:
"provides warnings not readily available from most content providers"

yes, they warn for cameras 200m away from where they exist. most content providers will have them in the correct place.

News Team Wrote:
"represents the widest coverage of the freshest data"

if they have 1 camera on the west coast of america and one on the east end of russia then, travelling west to east, i'd say that's pretty wide coverage. i can certainly smell something fresh - can't decide if it's the countryside or the PR... Wink


Posted by Privateer on Thu Mar 24, 2011 1:07 pm Reply with quote

Is this an early April's Fool story? Shocked

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

Posted by Darren on Thu Mar 24, 2011 1:27 pm Reply with quote

I wish it was Laughing

Darren Griffin - Editor

Posted by M8TJT on Thu Mar 24, 2011 4:24 pm Reply with quote

News Team Wrote:
"provides warnings not readily available from most content providers"
What would these warnings be then?
You have also probably noticed the word 'most' in the quote. So we must be included in with those that that are not included in 'most'

Posted by Alfygiz on Thu Mar 24, 2011 5:54 pm Reply with quote

Darren is absolutely correct

The PocketGPSWorld camera database is very accurate, no doubt in part to it's members providing new sightings etc.

I was recently given the TomTom safety camera database as a present. Their website states the database is updated twice weekly, so why then does it provide warnings for Fixed safety cameras that have NOT existed for years!!! and continues to do so!!!
Seems to me the twice weekly update is very much out-of-date!

TomTom GO 730. App 8.351
Map: West & Central Europe V865.3245

Posted by Oldboy on Thu Mar 24, 2011 7:04 pm Reply with quote

Alfygiz Wrote:
Their website states the database is updated twice weekly, so why then does it provide warnings for Fixed safety cameras that have NOT existed for years!!! and continues to do so!!!
It may be updated twice a week, but there is no mention of Lead Time. Rolling Eyes


TT 910 V7.903 (9183/081205) OS:2344
Europe version 1045.10005
TT Via 135 App 12.075
Western Europe v1095

Posted by DennisN on Thu Mar 24, 2011 10:02 pm Reply with quote

It is difficult to have a sensible discussion about TT's cameras, they are so awful. I have two devices with current Live services subscription, which includes access to the camera database. But I deleted it from both devices long ago and have no intention of reinstating it. It's not as if I've never tried it. With both devices purchased separately and some time apart, I kept the TT cameras on for quite some time to do a comparison - I was safe enough doing so, as I have more than just those two, so I had pgpsw database on another one to keep me on the true path!

The two just do not compare. Sure, we can argue 'til the cows come home as to whose mobile data is best, with no vans in sight most of the time, it could be argued either way. But with fixed cameras like the Specs Average Speed ones, there is no question about the existence of any camera - it's plain as a pikestaff that it's there or not there as the case may be. And TT usually have it the wrong way round - there when it isn't, not there when it is, if you see what I mean. At the very least the TT database is notably out of date. I'm driving 50-60,000 miles a year, so I know what I'm seeing, not just pottering about town with the odd excursion at weekends.


If it tastes good - it's fattening.

Two of them are obesiting!!

Posted by TED21 on Fri Mar 25, 2011 8:33 am Reply with quote

Hi, I've got a tomtom & a Road Angel unit, who are supposed to supply TT with the camera data. Well they are both out of date, TT is the worst of the 2 as some of their supposed data is so far out of date that you can't even see where a fixed camera was.
On the M4 near Heathrow, one side of the road is 50mph and the other is 70mph, TT pings up the speed warning whichever side of the road you are on. In Watford TT pings up a camera that has not been there for over 2 years. Your page does not have enough space to list them all.
I pay for the R.A. updates monthly which for fixed cameras is sort of upto date but, why Oh why does it ping up mobile cameras that have not been there for over a year?
As always, you get what you pay for. I always try to keep under the speed limit but, how easy it is to creap above the limit.

Posted by Darren on Fri Mar 25, 2011 8:39 am Reply with quote

TED21 Wrote:
I always try to keep under the speed limit but, how easy it is to creap above the limit.

You may want to add your comments to this thread.

Some posters have alleged that the only possible reason for a speed camera warning app is to permit speeding Confused

Darren Griffin - Editor

Posted by invisible on Fri Mar 25, 2011 9:22 am Reply with quote

I, too, run a Road Angel Connected next to a TT GO 1000 LIVE. I find the Road Angel Fixed camera database super accurate and - you are spot on here Darren - the TT ccamera database is derisible. What is worse about the TT is the false marketing. They claim to have LIVE updates for cameras, but these are only for mobile ones. The fixed cameras still need downloading manually, and this feature - and others - is just not available.

Can anyone tell me, can we now add the Pocket GPS database as POIs to the TT GO 1000?

Posted by Andy_P on Fri Mar 25, 2011 9:31 am Reply with quote

invisible Wrote:

Can anyone tell me, can we now add the Pocket GPS database as POIs to the TT GO 1000?

YES!!!!!! Smile

There are instructions for the new models here.
(If you can't find it in the future, there are also links to it from the camera download page, just below the "Download" button)

However, do note that currently you can't add the "ogg file" voice warnings available on this site.
Your options for warnings are therefore:

1. Use one of the standard "bing bong" sound effects - quick and easy, but no audible mention of speed limit.

2. Type in your own warnings for each camera type and speed and get the Text-to-Speech voice to read them out - very laborious!

3. Re-name the camera files to something suitable and get the TTS voice to read out the file names instead.


If you want to try option #3 and you use a PC, you can use a a simple "batch file" to rename them automatically for you.
You simply save it in the same folder as the camera files and double click to run it, before you copy the files onto the TomTom each week. See below for an example.

Here is a sample "batch file" (courtesy of member GerryC) which you can use, or modify to give your own warning speech.
It may LOOK scary, but all you need to do is copy and paste all the text inside the box (ignore the "code" bit).


ren pocketgps_uk_gatso_20.ov2    ~camera!_20_mph.ov2
ren pocketgps_uk_gatso_30.ov2    ~camera!_30_mph.ov2
ren pocketgps_uk_gatso_40.ov2    ~camera!_40_mph.ov2
ren pocketgps_uk_gatso_50.ov2    ~camera!_50_mph.ov2
ren pocketgps_uk_gatso_60.ov2    ~camera!_60_mph.ov2
ren pocketgps_uk_gatso_70.ov2    ~camera!_70_mph.ov2
ren pocketgps_uk_gatso_tba.ov2   ~camera!_unknown_limit!.ov2
ren pocketgps_uk_gatso_var.ov2   ~camera!_variable!.ov2

ren pocketgps_uk_gatso_20.bmp    ~camera!_20_mph.bmp
ren pocketgps_uk_gatso_30.bmp    ~camera!_30_mph.bmp
ren pocketgps_uk_gatso_40.bmp    ~camera!_40_mph.bmp
ren pocketgps_uk_gatso_50.bmp    ~camera!_50_mph.bmp
ren pocketgps_uk_gatso_60.bmp    ~camera!_60_mph.bmp
ren pocketgps_uk_gatso_70.bmp    ~camera!_70_mph.bmp
ren pocketgps_uk_gatso_tba.bmp   ~camera!_unknown_limit!.bmp
ren pocketgps_uk_gatso_var.bmp   ~camera!_variable!.bmp

ren pocketgps_uk_gatso_20_X2.bmp    ~camera!_20_mph_X2.bmp
ren pocketgps_uk_gatso_30_X2.bmp    ~camera!_30_mph_X2.bmp
ren pocketgps_uk_gatso_40_X2.bmp    ~camera!_40_mph_X2.bmp
ren pocketgps_uk_gatso_50_X2.bmp    ~camera!_50_mph_X2.bmp
ren pocketgps_uk_gatso_60_X2.bmp    ~camera!_60_mph_X2.bmp
ren pocketgps_uk_gatso_70_X2.bmp    ~camera!_70_mph_X2.bmp
ren pocketgps_uk_gatso_tba_X2.bmp   ~camera!_unknown_limit!_X2.bmp
ren pocketgps_uk_gatso_var_X2.bmp   ~camera!_variable!_X2.bmp

ren pocketgps_uk_mobile_20.ov2   ~mobile!_20_mph.ov2
ren pocketgps_uk_mobile_30.ov2   ~mobile!_30_mph.ov2
ren pocketgps_uk_mobile_40.ov2   ~mobile!_40_mph.ov2
ren pocketgps_uk_mobile_50.ov2   ~mobile!_50_mph.ov2
ren pocketgps_uk_mobile_60.ov2   ~mobile!_60_mph.ov2
ren pocketgps_uk_mobile_70.ov2   ~mobile!_70_mph.ov2
ren pocketgps_uk_mobile_tba.ov2  ~mobile!_unknown_limit!.ov2
ren pocketgps_uk_mobile_var.ov2  ~mobile!_variable!.ov2

ren pocketgps_uk_mobile_20.bmp   ~mobile!_20_mph.bmp
ren pocketgps_uk_mobile_30.bmp   ~mobile!_30_mph.bmp
ren pocketgps_uk_mobile_40.bmp   ~mobile!_40_mph.bmp
ren pocketgps_uk_mobile_50.bmp   ~mobile!_50_mph.bmp
ren pocketgps_uk_mobile_60.bmp   ~mobile!_60_mph.bmp
ren pocketgps_uk_mobile_70.bmp   ~mobile!_70_mph.bmp
ren pocketgps_uk_mobile_tba.bmp  ~mobile!_unknown_limit!.bmp
ren pocketgps_uk_mobile_var.bmp  ~mobile!_variable!.bmp

ren pocketgps_uk_mobile_20_X2.bmp   ~mobile!_20_mph_X2.bmp
ren pocketgps_uk_mobile_30_X2.bmp   ~mobile!_30_mph_X2.bmp
ren pocketgps_uk_mobile_40_X2.bmp   ~mobile!_40_mph_X2.bmp
ren pocketgps_uk_mobile_50_X2.bmp   ~mobile!_50_mph_X2.bmp
ren pocketgps_uk_mobile_60_X2.bmp   ~mobile!_60_mph_X2.bmp
ren pocketgps_uk_mobile_70_X2.bmp   ~mobile!_70_mph_X2.bmp
ren pocketgps_uk_mobile_tba_X2.bmp  ~mobile!_unknown_limit!_X2.bmp
ren pocketgps_uk_mobile_var_X2.bmp  ~mobile!_variable!_X2.bmp

ren pocketgps_uk_pmobile_20.ov2  ~possible_mobile!_20_mph.ov2
ren pocketgps_uk_pmobile_30.ov2  ~possible_mobile!_30_mph.ov2
ren pocketgps_uk_pmobile_40.ov2  ~possible_mobile!_40_mph.ov2
ren pocketgps_uk_pmobile_50.ov2  ~possible_mobile!_50_mph.ov2
ren pocketgps_uk_pmobile_60.ov2  ~possible_mobile!_60_mph.ov2
ren pocketgps_uk_pmobile_70.ov2  ~possible_mobile!_70_mph.ov2
ren pocketgps_uk_pmobile_tba.ov2 ~possible_mobile!_unknown_limit!.ov2
ren pocketgps_uk_pmobile_var.ov2 ~possible_mobile!_variable!.ov2

ren pocketgps_uk_pmobile_20.bmp  ~possible_mobile!_20_mph.bmp
ren pocketgps_uk_pmobile_30.bmp  ~possible_mobile!_30_mph.bmp
ren pocketgps_uk_pmobile_40.bmp  ~possible_mobile!_40_mph.bmp
ren pocketgps_uk_pmobile_50.bmp  ~possible_mobile!_50_mph.bmp
ren pocketgps_uk_pmobile_60.bmp  ~possible_mobile!_60_mph.bmp
ren pocketgps_uk_pmobile_70.bmp  ~possible_mobile!_70_mph.bmp
ren pocketgps_uk_pmobile_tba.bmp ~possible_mobile!_unknown_limit!.bmp
ren pocketgps_uk_pmobile_var.bmp ~verify_mobile!_variable!.bmp

ren pocketgps_uk_pmobile_20_X2.bmp  ~possible_mobile!_20_mph_X2.bmp
ren pocketgps_uk_pmobile_30_X2.bmp  ~possible_mobile!_30_mph_X2.bmp
ren pocketgps_uk_pmobile_40_X2.bmp  ~possible_mobile!_40_mph_X2.bmp
ren pocketgps_uk_pmobile_50_X2.bmp  ~possible_mobile!_50_mph_X2.bmp
ren pocketgps_uk_pmobile_60_X2.bmp  ~possible_mobile!_60_mph_X2.bmp
ren pocketgps_uk_pmobile_70_X2.bmp  ~possible_mobile!_70_mph_X2.bmp
ren pocketgps_uk_pmobile_tba_X2.bmp ~possible_mobile!_unknown_limit!_X2.bmp
ren pocketgps_uk_pmobile_var_X2.bmp ~possible_mobile!_variable!_X2.bmp

ren pocketgps_uk_specs_20.ov2    ~specs!_20_mph.ov2
ren pocketgps_uk_specs_30.ov2    ~specs!_30_mph.ov2
ren pocketgps_uk_specs_40.ov2    ~specs!_40_mph.ov2
ren pocketgps_uk_specs_50.ov2    ~specs!_50_mph.ov2
ren pocketgps_uk_specs_60.ov2    ~specs!_60_mph.ov2
ren pocketgps_uk_specs_70.ov2    ~specs!_70_mph.ov2
ren pocketgps_uk_specs_tba.ov2   ~specs!_unknown_limit!.ov2
ren pocketgps_uk_specs_var.ov2   ~specs!_variable!.ov2

ren pocketgps_uk_specs_20.bmp    ~specs!_20_mph.bmp
ren pocketgps_uk_specs_30.bmp    ~specs!_30_mph.bmp
ren pocketgps_uk_specs_40.bmp    ~specs!_40_mph.bmp
ren pocketgps_uk_specs_50.bmp    ~specs!_50_mph.bmp
ren pocketgps_uk_specs_60.bmp    ~specs!_60_mph.bmp
ren pocketgps_uk_specs_70.bmp    ~specs!_70_mph.bmp
ren pocketgps_uk_specs_tba.bmp   ~specs!_unknown_limit!.bmp
ren pocketgps_uk_specs_var.bmp   ~specs!_variable!.bmp

ren pocketgps_uk_specs_20_X2.bmp    ~specs!_20_mph_X2.bmp
ren pocketgps_uk_specs_30_X2.bmp    ~specs!_30_mph_X2.bmp
ren pocketgps_uk_specs_40_X2.bmp    ~specs!_40_mph_X2.bmp
ren pocketgps_uk_specs_50_X2.bmp    ~specs!_50_mph_X2.bmp
ren pocketgps_uk_specs_60_X2.bmp    ~specs!_60_mph_X2.bmp
ren pocketgps_uk_specs_70_X2.bmp    ~specs!_70_mph_X2.bmp
ren pocketgps_uk_specs_tba_X2.bmp   ~specs!_unknown_limit!_X2.bmp
ren pocketgps_uk_specs_var_X2.bmp   ~specs!_variable!_X2.bmp

ren pocketgps_uk_redlight.ov2    ~redlight_camera!.ov2
ren pocketgps_uk_redlight.bmp    ~redlight_camera!.bmp
ren pocketgps_uk_redlight_X2.bmp  ~redlight_camera!_X2.bmp

Save the above as a text file (using Notepad or similar), then rename it as "Rename.bat".
Unzip the camera files as usual, copy the batch file into the same folder and double-click it. The names of all the files magically change in front of you ready to copy across onto the TomTom.
(Don't worry if there are any lines for files you don't have, it will ignore any extras).


Other notes:
Using the 'brief' warning settingon the TomTom, you get "Camera! 20 miles per hour, 200 yards" etc.

The "~" just shoves them to the bottom of the POI list on the TT (though first on the PC).

We've used "camera" instead of "Gatso", as the speech system recognises the word better than "Gatso", but feel free to experiment with your own version of the text if you feel confident.

Remember you only need to copy the .bmp icon files to the TomTom ONCE. Just replace the .ov2 data files each week when you want to update.

"Settling in nicely" ;-)

Click here to view more comments...
Reply to topic

CamerAlert Apps

iOS QR Code

Android QR Code

Terms & Privacy

GPS Shopping