iGO Speedcam (DISCUSSION)

**Andrey Form** · 17th March 2026, 09:30 AM

POI Base,
The database is populated by users of the mobile application. All points are added to the map while the vehicle is moving, and the accuracy of the installed radars is usually constantly changing due to the last confirmation click. But usually the driver's reaction to pressing a button is quite slow, and the radars in the information collection database are geographically poorly connected. There is also a problem with radars installed on turns of the road, the azimuth can reach a critical maximum deviation from the road. You can fix it by adding an entry to sys:

[warning]
Speedcam_max_angle=30

But not all iGO navigators have this feature.
An example of a situation where notification may be difficult in iGO navigators.

[Only registered and activated users can see links. ]

This is also solved by changing the critical alert points to a 100% option.

[Only registered and activated users can see links. ]

Such changes are made and published marked Mod AF.
Original:

X,Y,TYPE,SPEED,DIRTYPE,DIRECTION
-8.183165,43.167392,1,80,1,5
-8.183165,43.167392,1,80,1,228

Mod AF:

X,Y,TYPE,SPEED,DIRTYPE,DIRECTION
-8.183166,43.167393,1,80,0,0

All entries inside a text file:

X,Y,TYPE,SPEED,DIRTYPE,DIRECTION, // 17.03.2026 iGO POIBase code 1,2,3,4 Western Europe no GBR Mod Andrey Form
-0.006628,43.242897,1,90,2,277
-0.008868,48.418453,1,70,2,280

**Andrey Form** · Yesterday, 06:14 PM

FAQ Radars installed on turns.

The problem is not that the radar is not visually visible around the bend. The problem is that there is no ideal database for collecting data with a targeted notification. Usually, the maximum deviation angle from the road is exceeded. Let me remind you that iGO can notify a maximum deviation of 20 degrees by default.

Using the example of the POI Base:

-8.183165,43.167392,1,80,1,228

[Only registered and activated users can see links. ]
38 degrees deviation from the road, the road has an azimuth of 190 degrees in the direction of the car, 228-190=38.

Since we are considering a Radar in Spain, let's pay attention to the BBS database:

-8.18326,43.16732,1,80,1,229

[Only registered and activated users can see links. ]
39 degrees deviation from the road.

40 degrees will provide notification of such maximum deviations. With an entry from sys

Code:

Please Login or Register to see the links

**Andrey Form** · Today, 09:36 AM

The real test is in motion, with a change in azimuth.

In a previous post, we discussed the theory of alerts, the maximum deviation angle from the road can be no more than 20 degrees for alerts in iGO with default settings. However, we cannot always accurately determine the azimuth of the road, especially in places where the road is rounded. On OSM maps, the azimuth of the road was 10=190 degrees. Based on this, we can deflect the azimuth of the radar by a maximum of 20 degrees, which will be 30 =210. But a real test showed that OSM and TomTom maps are different, and the road graphs are different. And the test azimuth of the road was 4=184 - TomTom data. For iGO, the maximum deviation from the road is 20 degrees, but this is the limit. For stable and guaranteed alerts, you need to have as few as 20 degrees as possible (this information is for those who create iGO radar databases) since we cannot accurately determine the azimuth of the road. The azimuth of the road may be different when using maps from HERE or TomTom.

And so the test is in motion. The coordinates of the installed radar are taken from the BBS database:

-8.18326,43.16732,1,80,1,204

Spoiler: 204

There is no notification from the radar, and even more so there is no notification if you use the BBS database specifically for this entry, the original BBS database:

-8.18326,43.16732,1,80,1,229

Now the corner is working:

-8.18326,43.16732,1,80,1,203

Spoiler: 203

What it looks like on the OSM map, 23=203 degrees, black ray.

Spoiler: +

Based on recent tests, I would recommend that iGO users have an entry in sys for the BBS database.

Code:

Please Login or Register to see the links

**Andrey Form** · Today, 11:27 AM

BBS' — Review
Very short database monitoring. Only for Spain, 1 code. As a result of the check, there are 60 lines requiring changes, including those looking into a field or forest, 5-6 radars.

Spoiler: +

**pacodelgps** · Today, 11:48 AM

Good morning, friend AF, is the entry you mention for the sys. file in the root of the igo program (Android or Wince)? Or is it for the speedcam.zip files that are in the UX folder?
Have you reported the errors found to 'laradiobbs'?

**Andrey Form** · Today, 11:57 AM

This entry is needed in sys, the program's root directory. For all iGO installations, if you have access to the sys file, this applies if you use targeted notification databases, not circular ones.

[Only registered and activated users can see links. ]

This recording will not help if the azimuth is directed towards the forest. And it has a 90-degree deviation from the road.

Code:

Please Login or Register to see the links

Spoiler: ++

**pacodelgps** · Today, 12:18 PM

Thank you very much, my friend, for your help. Have you reported those problems to "laradiobbs"?

**Andrey Form** · Today, 12:24 PM

This is a problem, deal with it yourself. I can only point out the problems. My first comma question took almost a year.

Code:

Please Login or Register to see the links

It was a very long time.

Code:

Please Login or Register to see the links

Thread: iGO Speedcam (DISCUSSION)

Thread Tools

Display

Advertissements

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions