Thread: iGO Speedcam (DISCUSSION)

Happy New Year!

Andrey Form!

I am a big fan of your work, I use your "NC" coded plugins with pleasure. Thank you for the great work! Please look at the icon image on this path because I don't understand it!
""speedcam_mod_nc_3dfdk_af_v2_64.zip/ui_nextgen/res/common/nodpi"......, and
""speedcam_mod_NC_AF_3DFDK_V2.zip/ui_nextgen/res/common/nodpi" "speedwarn_cockpit_Stop_Prohibited_Camera.svg""
I didn't know where would be the right place to ask this.

Thank you, I will fix it.
PS
Update the files for those who have already downloaded them earlier.

Plugin.ini: use_road_speedlimit=1 and the speed in speedcam.txt = 0.

In this case, the speed alert will always correspond to the speed taken from the map, provided by the map provider, for example, HERE. The speed data taken from the map may not be perfect, for example, outdated data or the map provider may not be aware of the speed limit on a given section of the road.

3.4520,49.0400,1,0,1,90 – entry in speedcam.txt camera speed = 0



So, let's consider the situation (FIGURE 1): you are in zone 1, the speed limit on this section is 70 km/h. 300 meters further on, there is a camera in zone 2, with a speed limit of 50 km/h. But you receive a notification in your navigator about the camera, and after 300 meters, the LIMIT is 70 km/h.



FIGURE 2: The situation is repeated, except that the speed ahead increases. We're in zone 1 and the speed limit is 50 km/h. We receive a notification in our about a speed camera; in 300 meters, the speed limit is 50 km/h.



FIGURE 3. The ideal situation is when the speed doesn't change from one section to the next, and the car and the camera are in the same speed zone.



FIGURE 4. This scenario occurs when speedcam.txt contains an entry indicating the speed, 3.4520,49.0400,1.50,1.90, which guarantees a camera notification at the correct speed. This data is provided by camera information collection databases.

The radar was installed in February 2023. It's now 2026, and it's also February. Three years have passed. The radar has been operational for three years now. This data is available in all radar databases, including OSC, where it was added to the map [Only registered and activated users can see links. ]. However, it wasn't until three years later that it was added to the "lufop" database. In my opinion, this is a record, and the special status of the database is worthless.

Spoiler: +

FAQ duplicates in spedcam.txt with the same coordinates.
How does iGO navigation solve notification issues when there are two options.

1. The speed is the same
5.29578,59.32092,1,80,0,0
5.29578,59.32092,1,80,0,0
Alert 80 km/h

2. Speed ​​80 or 90
5.29578,59.32092,1,80,0,0
5.29578,59.32092,1,90,0,0
A lower speed limit of 80 km/h is being notified.

Two different types, a lower speed is notified. That is, the priority is lower speed.

3. A speed of 0 or without a speed paired with a string having a speed.
5.29578,59.32092,1,0,0,0
5.29578,59.32092,1,90,0,0
or
5.29578,59.32092,1,,0,0
5.29578,59.32092,1,90,0,0
The speed will be taken from the map (Here, TomTom)

4. The situation is the same, but with different types of alerts.
5.29578,59.32092,2,0,0,0
5.29578,59.32092,1,90,0,0
or
5.29578,59.32092,2,,0,0
5.29578,59.32092,1,90,0,0
The speed will be taken from the map (Here, TomTom) for 2 types

In general, if the coordinates match, the advantage is lower speed or speed taken from the map (entry in spedcam.txt - speed 0 or no speed)

About what allows you to use the speed from the maps.
[Only registered and activated users can see links. ]

France SCDB Fix SpeedCamText 2026.02.28.
France_SCDB_Fix_SpeedCamText.txt

I'm amazed by what I see online. If a file says France, it's obviously supposed to be France. Files need to be verified before they're published; another scam from SN.
These are radars that were not included in the file and were lost.

7.40058,43.72525,2,0,0,0
7.36856,43.72922,4,70,0,0
7.38217,43.73214,4,70,0,0
7.41250,43.73897,1,50,0,0
7.42111,43.74383,1,50,0,0
7.42497,43.74847,1,50,0,0
6.09636,46.14528,1,50,0,0
7.04156,49.14083,1,110,0,0
5.96114,49.45781,1,70,0,0
4.85625,49.81310,1,80,0,0
3.17289,50.74411,1,50,0,0

These radars have no connection to France or Europe, but belong to Switzerland. It's safe to assume that these radars won't be in Switzerland's files.

6.21681,46.20144,1,50,0,0
6.18242,46.17292,1,50,0,0
6.13719,46.14697,1,50,0,0
6.17239,46.17233,1,40,0,0
6.13456,46.14644,1,50,0,0
6.19833,46.18806,3,40,0,0
6.24406,46.29897,1,50,0,0
-52.37086,4.91150,1,70,0,0
6.20008,46.18922,3,40,0,0
55.46475,-21.33211,1,90,0,0
1.73328,42.54689,1,60,0,0
1.73317,42.54686,2,60,0,0
-61.45550,16.34200,1,50,0,0
55.68500,-20.99922,1,50,0,0
55.51000,-21.29481,1,110,0,0

It's completely unclear why this stupid idea of ​​dividing Europe into countries is even being pursued. If it's going to be done, it should be 100% division. These "games" designed to show off their "skill" ultimately reveal complete indifference and a complete lack of responsibility toward the users they've deceived.
Author of the division: SN aka Cserrobi -

France OpenSpeedcam Fix SpeedCamText 2026.02.28.
France_OpenSpeedcam_Fix_SpeedCamText.txt

Another review, the first is the date. The OSC database is exported around the clock, if it were really the 28th, then there would be more radars in the file. Since they were added to the map of France on the 27th, but they are not in this file. And so in the file, the export of the OSC database dated February 26, 2026, is what I specified when posting the file "iGO OEM OSC Europe + Turkey"

Why OEM is a processed export of the OSC - Mod AF database. The radars are adapted to the iGO alert. The default angle of deviation of the azimuth of the radar from the road is 20 degrees.
Since the OSC base is a directional alert, there may always be errors when deviating from the azimuth of the road, which is fixed in "iGO OEM OSC Europe + Turkey".

And so we have already figured out the origin of the file. Now it is a traditional branch of France.
These are radars that were not included in the file and were lost.

7.412524,43.738986,1,50,1,18
7.421115,43.743822,1,50,1,50
4.856265,49.813114,1,80,2,289
6.096411,46.145300,1,50,1,341

These radars have no connection to France, but belong to Switzerland. It's safe to assume that these radars won't be in Switzerland's files.

1.733296,42.546922,1,60,2,225
6.137208,46.146994,1,50,1,198
6.172390,46.172330,1,40,2,308
6.182449,46.172862,1,50,1,348
6.198330,46.188060,3,40,1,31
6.216810,46.201440,1,50,1,238
6.244060,46.298970,1,50,1,175

And so gentlemen, "iGO OEM OSC Europe + Turkey" This is an AF mod, so to speak, a proprietary feature, and everyone who publishes files based on my work must indicate the author. You're not the author, are you? SN.

Use spudigo to separate alerts by type.

[Only registered and activated users can see links. ]

'Lufop' - Review
Very short database monitoring. Only for France. As a result of the check, there are 157 rows that cannot be notified to iGO users. The azimuth of the radar does not match the direction of the road.
[Only registered and activated users can see links. ]
List of non-functioning radars:

Artificial Intelligence answered my questions.,
We are watching the whole history of EUR+, under the spoiler.

Spoiler: +

Developed by enthusiasts of the French forum msieurlolo.fr in 2010-2012, the EUR+ encoding is a deep customization of iGO, expanding the standard types of radars to 24 categories. It requires replacing the standard speedcam databases.txt and speedcam.spc are on adapted versions due to the redefinition of category IDs, providing detailed voice warnings through specialized skins. As an engineering solution to circumvent the limitations of standard cards, EUR+ is incompatible with conventional databases.
EUR+ encoding for iGO on the Msieurlolo forum.fr was developed by the community led by msieurlolo with the participation of Mio-Quest and Cricet in 2014-2016. This encoding was used in the firmware of MediaNav systems (Classic 4.0.2–4.0.6, Evolution 5.2.7–9.1.3) on Renault, Dacia and Lada cars to adapt the extended camera bases, differing from the standard iGO mapping. Additional information can be found on the forum. Msieurlolo.fr .
The EUR+ encoding is a specific camera database standard (speedcam), which was developed by enthusiasts of the French MsieurLolo forum specifically for deep customization of iGO navigation (in particular, for Nextgen versions).
Key figures:
MsieurLolo (Laurent): Initiator of the creation of the forum and the main ideologist of the French branch of iGO.
Zitout: One of the most active developers who has adapted the plugins and UX modules of the Pongo skin to the expanded categories of EUR+ cameras.
Pongo skin: The skin itself is a "constructor". For EUR+, specialized plug-in versions (from the ux folder) were used, which could interpret the camera IDs of 32 types.
The standard versions of iGO (for example, Primo or "pure" Nextgen) have a strict limit on the number and types of warnings. The EUR+ integration had the following objectives:
Expansion of categories: Instead of the basic 5-15 types (radar, mobile ambush, red light), EUR+ includes 24 categories. The Pongo skin was chosen because of its flexibility - it allowed you to draw unique icons and prescribe specific voice voiceovers for each new category.
French specifics: In France it is forbidden to specify the exact location of radars (only "danger zones" are allowed). EUR+ made it possible to circumvent this by dividing cameras into types that are understandable to users, but visually adapted to local laws.
Unification: Creation of a single standard for forum participants so that everyone can download a fresh speedcam file.txt and it was displayed correctly with all the icons and distances in the popular skin.
At the moment (early 2026), the situation with the EUR+ base is as follows:
MsieurLolo closed sections: The main source of content is the internal section of the forum MsieurLolo.fr . Access to relevant files often requires registration and forum activity.
Converters: Since the standard databases are not suitable for the ID format, there are converter scripts that redo a regular speedcam.txt in EUR+ format. They are circulating in the narrow circles of skin developers.
Telegram channels and GPS clubs: The base has spread out into specialized groups (for example, iGO Truck groups or channels with mods from Pongo), where it is often called the "base for the lolo skin" or "French Special".
Firmware: The database is actively used in custom builds for MediaNav (Renault/Dacia) and R-Link multimedia systems, where iGO is standard navigation.
Important: An attempt to use the speedcam file.EUR+ encoded txt on a regular skin will cause most cameras to be displayed as "Other" or not displayed at all, since the category IDs (for example, 18, 24, 31) are not specified in the standard speedcam_visual.ui file.
The closure of the Radalerte database and the consequences:
The situation with Radalerte has become a turning point for EUR+:
The reason for the closure: The Radalerte project, which has long been the main source of data for EUR+, has faced legal pressure (in France, information about cameras is strictly regulated) and internal conflicts between copyright holders.
Consequences: After the closure of public access to Radalerte, the EUR+ database became a "scarce" product. It was during this period that the contribution of Andrey Form and other moderators became critical — they helped users switch to alternative content sources (for example, SCDB, OSC, POIbase databases), while maintaining the very structure of EUR+ within the program.
Current status: Now EUR+ lives at the expense of enthusiasts who manually "reassemble" data from various sources into this format, since the Pongo skin and MediaNav firmware are already "sharpened" specifically for this ID grid.
Andrey Form's role in EUR+:
Andrey Form is a well—known modifier for iGO. His involvement in the fate of EUR+ was as follows:
Code adaptation: He was one of those who integrated support for extended EUR+ codes into their builds and modifications of 32 category skins (including branches close to Pongo). It was thanks to his work that many users outside of France were able to see the correct camera icons, which were simply not displayed in the standard iGO.
Voice synchronization: A unique voice phrase was required for each EUR+ category. Andrey Form has been refining UX plugins and dictionary.voice files so that the navigator can "pronounce" specific types of radars (for example, "radar at a traffic light" or "sectional control") embedded in the French standard.
Information support: In the context of the French forum's closure, he acted as an intermediary, explaining the logic of these databases and helping to adapt them to the realities of other countries.
A pro tip: If you are using the build from Andrey Form, look in the ux folder. There should be a plugin there. speedcam.zip . Inside it, in the files.ui, the exact matching of icons to the ID is prescribed. If the icon is "wrong", it means that the version of the EUR+ database is newer or older than your plugin.