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

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.