Thread: FAQ iGO encodings and speedcam.txt [compatibility]

iGO Primo w16

Primo 16 is the iGO Primo standard used when no skin is applied. It can also be used with a skin, but in that case, only default warnings will be displayed. Additionally, it is used in factory car navigation systems; when using it in Renault R-Link 2, remember to use the correct filenames — usually, these are country names following the standard.
(for example, France or Italy) to provide a replacement for the spedcam file.txt in the car navigator.
w16



OSC base

iGO Primo w16 Full
(32 Speed Camera), (34 Built-in Camera), (36 Red Light), (43 Red Light and Speed Camera), (35 Average Speed Camera), (35 Average Speed Camera - Finish 5 km h), (39 Bus Lane Camera), (33 Mobile Speed Camera), (38 Railway crossing), (42 Town Entry Point), (41 School Zone), (40 High Accident Zone), (44 Toll Booth), (63 Dangerous Area), (47 Congestion Charge Zone)

iGO Primo w16 Pro
(32 Speed Camera), (34 Built-in Camera), (36 Red Light), (43 Red Light and Speed Camera), (35 Average Speed Camera), (35 Average Speed Camera - Finish 5 km h), (39 Bus Lane Camera), (33 Mobile Speed Camera), (47 Congestion Charge Zone)

iGO 5w speedcam - code 1,2,3,4,5
1 - (32 Speed Camera),
2 - (34 Built-in Camera),
3 - (36 Red Light),
4 - (35 Average Speed Camera + Finish 5 km h)
5 - (33 Mobile Speed Camera)

iGO 4w speedcam - code 1,2,3,4 NOMob
1 - (32 Speed Camera),
2 - (34 Built-in Camera),
3 - (36 Red Light),
4 - (35 Average Speed Camera + Finish 5 km h)

SCDB base NOMob
1 - (32 Speed Camera),
2 - (34 Built-in Camera),
3 - (36 Red Light),
4 - (35 Average Speed Camera)

SCDB base Code 5
5 - (33 Mobile Speed Camera)

POI base NOMob
1 - (32 Speed Camera),
2 - (34 Built-in Camera),
3 - (36 Red Light),
4 - (35 Average Speed Camera)

POI base Code 5
5 - (33 Mobile Speed Camera)

OSC base OEM, POI base OEM, SCDB base OEM (maximum radar azimuth adaptation is relatively expensive)
1 - (32 Speed Camera),
2 - (34 Built-in Camera),
3 - (36 Red Light),
4 - (35 Average Speed Camera)

radar warning system in the PONGO skin

Currently, the alert scenario from Pongo Igo Luna is based on the alert distance. It is the distance in plugin.ini that determines the priority of alerts of one type or another. Thus, important alerts are displayed first, even if they are further away on the route map. This ensures that all types of alerts are displayed in a timely manner. This is not the default behavior of Igo. The only requirement is to follow the recommendations from Pongo, including speedcam.txt. It is important to close the section with a speed of 5 km/h.
This alert scenario, the beginning of Luna 32 bit. And further implemented in all pongo skins, 64 bit. (Luna, Basar, World). It is important when you edit the alert distance in the plugin.ini. Apply longer distances for radars, and shorter distances for road signs. Radars will be alerted even if they are the second ones in the direction of movement.

Pongo skin update and speedcam activation (May 2026)

since the "auto_road" plugin has a disabled=0 speedcam entry constantly pending.

To activate temporarily:
-Cameras can be turned on via "drag mode" long tap on the rightmost "favorites" button

To activate permanently:

Code:

Please Login or Register to see the links

Go to the menu and turn on the alerts. Skin settings/ Warnings/ Cameras/ Report cameras - on.

For Luna 64 bit - add to plugin

Code:

Please Login or Register to see the links

iGO NextGen 32 bit - Skin by WANDEL™

On April 14, 2022, a master, a well-known skin for iGO nextGen, joined us - Skin from @Wandel.

speedcam_mod VB, NC, BG, FR, Eur+, GR, SP, IT
speedcam_mod_AF
[Only registered and activated users can see links. ]

How speedcam_mod.zip for Wandel skin works:
Any speedcam_mod.zip needs to be moved to the UX folder, speedcam.zip should also be in the UX.
If you need to replace speedcam_mod.zip (encoding or icons) you need to remove the replacement file.
In the UX folder may be speedcam.zip, or set speedcam.zip, speedcam_mod.zip

Working Average Speed Camera in the Wandel skin.
In more detail about the Average Speed Camera
for the correct warning "Average Speed zone" there must be two cameras:
- the first (the beginning of the zone) with a measurable limit limit, for example 70 km / h
- second (end of zone) with a speed limit of 5 km / h,
on the navigator screen, both cameras are directed against the traffic ( in speedcam.txt in the direction of travel );
in those areas where the speed is controlled by both directions, there must be four cameras (two opposite ones)

Expert Warning: Why iGO Misses Speedcams and How to Choose the Right Database

The iGO navigation engine is extremely sensitive to the structure and geometry of data inside the speedcam.txt file. Using an incompatible or "raw" database can lead to massive camera misses on the road and unexpected fines.Below are the critical technical details that every iGO user must consider when choosing a data source.

⚠️ Main Technical Pitfalls for iGO

• Strict Direction Filter (±20°): iGO uses a rigid heading control algorithm. If the camera's direction vector in the file deviates from the actual road axis by more than ±20 degrees, the navigation software simply ignores the speedcam.
  Blindness on Winding Roads: Speedcams that work perfectly on straight highways can become invisible on serpentines, exits, junctions, and 90-degree intersections. This happens because their angles are not mathematically adapted to iGO's movement tracking algorithms.

Differences in Data Collection Methods by Databases When choosing a database, it is vital to understand the mathematical method used to generate its direction angles:

Spoiler: 1. POIBase

Angle Generation Method: Direct ray method. The vector points diagonally from the camera to an abstract warning start point.
This completely breaks the geometry of winding roads.
Behavior in iGO Navigation: Critical failure (up to 10% of "blind" cameras). On complex interchanges and road bends,
the angles guaranteed to exceed the ±20° tolerance, causing iGO to skip the speedcams entirely.

Spoiler: 2. Local Forum Databases (Without Auto-Filtering)

Angle Generation Method: Manual method. Moderators or users set the camera directions in editors
"by eye" based on visual estimation.
Behavior in iGO Navigation: High risk of human error. Single and oncoming cameras often contain input errors,
leading to missed alerts or annoying false alarms.

Spoiler: 3. Professional Databases (OpenSpeedcam / OSC with Adaptation)

Angle Generation Method: Algorithmic method. Raw geodata passes through specialized filters to adapt it specifically
for the iGO engine.
Behavior in iGO Navigation: Maximum accuracy. The filter automatically combines paired speedcams or activates
a safe omnidirectional (360°) mode at complex junctions.

Recommendations for Choosing an iGO Database
Avoid "Direct Imports": Do not use databases exported directly from universal international projects (such as POIBase) without pre-processing.Look for Modified Files: Choose modified sources (e.g., Mod AF), where the data has been optimized as much as possible for iGO.
Check the Header Structure: Before copying the database into your navigation device, make sure the first line of the speedcam.txt file is strictly standardized and does not contain stray punctuation marks (especially semicolons ;), which can completely break the software's parser.

Recommendations for Extending the Detection Angle in iGO
You can manually expand the camera deviation angle from the road centerline to (±40°):

[warning]Speedcam_max_angle=40

Note: This is for users who have access to editing the hidden settings (sys.txt) of the iGO navigation software.