Thread: iGO Speedcam (DISCUSSION)

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.

Hi all

If SCDB was a good deal, it is not the case for OSC bases...

I use a tool that can easily extract STD speedcams from a global SCDB base to separate countries. But now we cannot find anymore standard base for all Europe (with codes 1-2-3-4-5) as before... Why ? Perhaps they need to be paid ?

NB : Yes, in France must of us are using EUR+ codification, because it is the more adequate for our country

If we are talking about this forum, then I do not publish files in the iGO 1,2,3,4,5 standard
but only 32,34,36,35,33. Of course spudigo is configured for 1,2,3,4,5, with the exception of spudigo [Only registered and activated users can see links. ]

I saw...