Thread: iGO Speedcam (DISCUSSION)

"New Automatic Speed ​​Cameras Coming in 2025"

New automatic speed cameras in 2025, but cameras installed in 2024, namely in May, were added to the lufop database in January 2025.
For example: Latitude : 43.28411 Longitude : 5.49088 Azimuth : 100 23-01-2025 The radar turret was installed in May 2024.
Latitude : 45.4032 Longitude : 4.3644 Azimuth : 70 23-01-2025 The radar turret was installed in 20 May 2024.
Latitude : 44.23797 Longitude : 0.44565 Azimuth : 75 21-01-2025 The radar turret was installed in December 2023.
Latitude : 43.41726 Longitude : 6.68316 Azimuth : 155 19-01-2025 The radar turret was installed in May 2024.
Latitude : 44.83674 Longitude : -0.14578 Azimuth : 330 19-01-2025 The radar turret was installed in February 2024.
Latitude : 44.6228 Longitude : -0.06023 Azimuth : 345 19-01-2025 The radar turret was installed in March 2024.

Code:

Please Login or Register to see the links

Added points to the database 6-9 months after installation, but this is not the main thing. The problem is in azimuths, not all users responsibly added azimuths to the map, deviation from the main direction of the road is allowed maximum 19 degrees for iGO navigation.

Spoiler: ++++

[Only registered and activated users can see links. ]

+ This is the same place on the OSC map

[Only registered and activated users can see links. ]

After analysis, conclusions and recommendations.
The fact is that the procedure for adding a point to the map is not thought out and is not controlled by moderators. As a result, 500 points on the map need to be edited, this is data for France. The best option for this base would be to abandon the targeted notification and continue to maintain the base for France as it is done for other countries, circular notification. The missing information on radars installed earlier is a solvable issue, the more participants, the more reliable the information. I do not recommend using the lufop base in iGO navigators , an alternative to SCDB.

and so on

Spoiler: ++++++

[Only registered and activated users can see links. ]

[Only registered and activated users can see links. ]

[Only registered and activated users can see links. ]

I think this is the last review, because the distributor of the content eventually saw what he was spreading on various forums. Here are his revelations on the French forum. The key word is, "We just didn't notice it until now."

Spoiler: screenshot

[Only registered and activated users can see links. ]

Translation into English:
"Hello, everyone who downloaded the file from 23.01.2025, you should not use it.
My program incorrectly converted negative coordinates,
I will change it. We just did not notice it until now.
We apologize for the inconvenience caused."

Of course they didn't notice, despite the fact that I wrote about it on the French forum of Mr. LOLO, on the German forum (digital-eliteboard). The problem is that a regular user cannot know and cannot verify the veracity of the information. The forum administration also does not control the files posted. Advice for everyone, use verified sources.

A small excursion into the history of the creation of the EUR+ encoding (only what I know, some deviations from the chronology are possible, but in general this story is from my side). The masters of the forum, Mr. LOLO, changed the standard iGO encoding by rewriting it at their discretion and called it EUR+. This encoding was implemented in all possible skins that were in 2015-2017, including skins for car multimedia, actually for this reason there is now a demand for speedcam.txt in the EUR+ encoding. The LOLO mod for the pongo skin from 2017 can still be downloaded on the French forum, it is a bestseller, it turns out that the LOLO 2017 mod is so good for the French user that it can be compared equally with the pongo skin from 2024? The EUR+ encoding is a serious bid for success, as well as a cruel joke, since no standard speedcam file can be used in navigation without changing it, and it is also impossible to use *spc files - they are also in standard encoding.
Next, I spent a lot of time restoring the basics of the EUR+ encoding. Because without the speedcam database, this encoding should have been thrown in the trash 2 years ago, since radalerte.fr closed down and lufop.net is simply not able to keep the database up and running.
There is a possibility to support the base for France now, as all the remains of radalerte.fr were placed on the OSC website. These data were analyzed and edited. Now these data can be downloaded from the website using export and the export name - iGO skin PONGO, which corresponds to the encoding in the Pongo skin in all versions under the VB encoding.

Code:

Please Login or Register to see the links

Which in turn gives users the opportunity to travel from Lisbon to Vladivostok without any changes to the navigation. You just need to use the pongo skin and put the speedcam files in the content/speedcam path. Actually, they are already in the pongo skin if you downloaded it, still in the content/speedcam folder.

Why is everything so detailed and with a short excursion into history. I often see how the EUR+ encoding is used incorrectly, for example, by placing files in a standard skin, of course such a story creates false alerts. And I think that this EUR+ encoding should not have been placed on the gpspower forum, but left for the m. LOLO forum in the place where it was created, this is their history.

We will address this issue in the survey topic here:

[Only registered and activated users can see links. ]

The most recent spc from TomTom could have been from 06.2024 (Q2) when the maps were released. My opinion about spc is that it's always outdated data, for example, you want to use the spc from June 2024 in your navigator, it's February 2025. There are also tips for users to put spc and txt files in the speedcam folder. But in this case, you will receive a lot of static alerts, as well as double alerts, since the coordinates on the map may differ from the actual location of the camera installation. Approximately 50% of the alerts will match in type and location in aisles of 20-50 meters. Another argument is that the speed in the bases may also not match, in one base 90 in another 120 or even 50, if at the time of the base's exit, the roadbed was being repaired or the road as a whole was being reconstructed, which allowed for an increase in speed. In general, there is no ideal data, and spc is also a 100% guarantee, but only data from the database according to a certain date
Use more recent publications and databases that combine data from different sources. For example, OSC, this database collects and combines data from different sources and does not contain duplicates with different types of alerts, as well as has direct access to editing the database. I plan to update the OSC files today.

I confirm that TT *.spc are very old and inaccurate. I personally stick to SCDB, which has always been sufficient 👍

@tata
For iGO prima without skin, everything that has up to 16 types
OSC_iGO_5w
OSC_iGO_5w_iTruck or OSC_iGO_4w_iTruck_NOMob
OSC_iGO_Primo_16w_Full or OSC_iGO_Primo_16w_Pro

POI Base has a mobile radar export filter.

Spoiler: +++

[Only registered and activated users can see links. ]

Mobile Speed ​​Camera Locations: Install only if active last
-12 months (max current data)
-2 years
-3 years
-5 years
-Install ALL (max safety)

The mobile radar export filter sorts by the dates of confirmation by users of a mobile ambush actually located on the road. Thus, we can see different options for exporting the POI Base, some with a full one, others after a filter of 12 months of confirmed ambushes.
So what is 12-month data, it means that all other data is not included in the export file. Here everything depends on the number of users and the quality of traffic on all European roads with a length of about 8,500,000 km. And also the driver's desire to confirm in the application the status of the notified object on the road.