Thread: iGO Speedcam (DISCUSSION)

Of course, with the EUR+ encoding of the previous post, this is not the full story.

In December 2022, Radalerte closed. And I opened a special topic on the French Forum -06.01.2023.

OpenSpeedCam (OSC) Pour la France et les autres pays européens original

This topic is closed now.
I was trying to replace a database that had ceased to exist. In 2023, there were still users for this encoding. Right now, I see only one thing, EUR+ files are being downloaded. and they are used in standard encoding. It is difficult for me to control all the technical forums so that the files are used correctly. But there were such cases yesterday, this is the second case since the beginning of this year, this is something that can be seen on the forums, oh, I can't see all kinds of telegram channels that are published there. Why did I turn to artificial intelligence, it can read the entire forum and even closed sections and find answers. This is an interesting story about who created the non-standard encoding and for what purpose.

I totally agree with this, I added these codes, and they eventually became 32 types.. Under the name EUR+ Mod AF

=20:20:Dangerous turn
=21:21:Tunnel
=22:22:Point of interest
=23:23:Police checkpoint
=24:24:Dangerous road
=25:25:Highway Exit
=26:26:Educational Speed Camera
=27:27:End of Zone 30
=28:28:Weight Control
=29:29:Pedestrian crossing
=30:30:SC camera
=31:31:Dangerous zone

Spoiler: EUR+ Mod AF

EUR+ Mod AF , beginning
January 8, 2021

Up to this point, there were 24 types in the pongo skin. And there are still 24 types in the pongo Mod m.LOLO skin.

Spoiler: EUR+ Original

I found this information, EUR+ Mod AF , the beginning
8 January 2021, so the artificial intelligence mentioned my name while reading the forum. The idea of extending the coding to 32 types belongs to Batiskaf.

Code:

Please Login or Register to see the links

Ah, I agree with you there. The modification of the EUR+ Mod AF encoding did not produce any results or innovations. This was because the radar database did not match these codes, and there was nothing to fill them with. Additionally, no one intended to modify the old skins, and they remained at 24 types. Currently, there is no radar database even for 24 types, and it is fortunate if French bakeries and agricultural farmers use the EUR+ encoding. And the cars for which the EUR+ skins were created will be scrapped sooner or later. There is no radar database, and there is no encoding. It makes no sense to use the EUR+ encoding with five codes. Any encoding, including VB in the pongo skin, can alert five types, and this will be a more interesting version with cameras in the back. Therefore, I do not claim a history page in the EUR+ encoding, In his own name, Mod AF.
And maybe now the users of the gpspower forum will understand the meaning of the EUR+ speedcam txt encoding and that it should not be placed in the standard iGO navigator. And the EUR+ encoding should not be on the gpspower forum, as it confuses users when using files.

Coding.
iGO alert codes are usually compiled based on an information collection database. The database is the basis of any encoding. Stationary databases for collecting information are based on websites with a user-friendly and intuitive interface. Updating data and storing data, as well as exporting data. There are also local groups that exchange information with each other, usually data exchange is carried out using speedcam.txt. The alert code exists as long as the database provides data updates. The code cannot continue to work if the information collection database has been closed and the code was created based on this database.
And so, the situation is the closure of the base, the information collection base is closed. You can no longer receive updates to alert codes that were only on this information collection database. To use the code, you can still use codes that you can get from other information collection databases for some time. But the very meaning of creating the original code has already been lost, with the loss of the database.
Radalerte - had specific codes that were used in encoding EUR+. Any other information collection database can only replace traditional alert codes.
Using traditional codes in a specific encoding, such as EUR+, is possible, but traditional codes have other types of alerts and need to be constantly adapted (converted) to the specific encoding of EUR+. Since the traditional iGO codes have been changed to EUR+ encoding.
The Lufop data collection database has only traditional codes and only converts its data into EUR+ encoding and will not replace the lost specific data from Radalerte.
The EUR+ encoding will continue to be used for some time, as long as the previously created skins in this encoding are relevant for use and there will be nothing to replace them, in a different, more standard encoding.
The OSC database has provided a partial replacement option for the specific EUR+ encoding. As the moderator of the OSC database, I have adapted some specific types of alerts for the EUR+ code. I also adapted the EUR+ code itself into EUR+ Mod AF, changing the number of EUR+ codes from 24 types to 32 types. The OSC database can also provide traditional codes that can be converted to the EUR+ code.
Practically, I have revived the specific EUR+ code and introduced new alert types for France in the OSC database. Radar monitoring in France is ongoing.
And in the end, it turned out to be a waste of time for me. Since many users believe that the contribution is something more than drawing 2 icons for the EUR+ code. And they prefer the Lufop base, despite the fact that 10 percent of the base there is only on paper, without notification. And no one fixes anything at Lufop, I wrote about it back in 2023, and there these azimuths looking at fields with agricultural products existed before.

Originally Posted by lunapark

It should be noted that this standard was not created overnight and has been refined over time in response to various demands. At one point in its history, this is what it represented.

Spoiler: EUR+

Code:

Please Login or Register to see the links

This encoding is EUR+ Mod AF (beginning January 8, 2021), as it preserves the EUR+ codes and supplements them with other codes from the OSC database.

And this new EUR+ standard was created instantly, after the request of the Bathyscaphe to unify this code consisting of 24 types. At the same time, the Radalerte database had not yet been deleted.

Users of the EUR+ code can continue to use the OSC information collection database. To get a speedcam.txt needs to use a converter - [Only registered and activated users can see links. ]. The received conversion files are for personal use or for publishing files outside the gpspower forum. I consider it impossible to distribute further files on the gpspower forum with the EUR+ encoding, so as not to mislead iGO users.

POI Base,
The database is populated by users of the mobile application. All points are added to the map while the vehicle is moving, and the accuracy of the installed radars is usually constantly changing due to the last confirmation click. But usually the driver's reaction to pressing a button is quite slow, and the radars in the information collection database are geographically poorly connected. There is also a problem with radars installed on turns of the road, the azimuth can reach a critical maximum deviation from the road. You can fix it by adding an entry to sys:

[warning]
Speedcam_max_angle=30

But not all iGO navigators have this feature.
An example of a situation where notification may be difficult in iGO navigators.

[Only registered and activated users can see links. ]

This is also solved by changing the critical alert points to a 100% option.

[Only registered and activated users can see links. ]

Such changes are made and published marked Mod AF.
Original:

X,Y,TYPE,SPEED,DIRTYPE,DIRECTION
-8.183165,43.167392,1,80,1,5
-8.183165,43.167392,1,80,1,228

Mod AF:

X,Y,TYPE,SPEED,DIRTYPE,DIRECTION
-8.183166,43.167393,1,80,0,0

All entries inside a text file:

X,Y,TYPE,SPEED,DIRTYPE,DIRECTION, // 17.03.2026 iGO POIBase code 1,2,3,4 Western Europe no GBR Mod Andrey Form
-0.006628,43.242897,1,90,2,277
-0.008868,48.418453,1,70,2,280

FAQ Radars installed on turns.

The problem is not that the radar is not visually visible around the bend. The problem is that there is no ideal database for collecting data with a targeted notification. Usually, the maximum deviation angle from the road is exceeded. Let me remind you that iGO can notify a maximum deviation of 20 degrees by default.

Using the example of the POI Base:

-8.183165,43.167392,1,80,1,228

[Only registered and activated users can see links. ]
38 degrees deviation from the road, the road has an azimuth of 190 degrees in the direction of the car, 228-190=38.

Since we are considering a Radar in Spain, let's pay attention to the BBS database:

-8.18326,43.16732,1,80,1,229

[Only registered and activated users can see links. ]
39 degrees deviation from the road.

40 degrees will provide notification of such maximum deviations. With an entry from sys

Code:

Please Login or Register to see the links

The real test is in motion, with a change in azimuth.

In a previous post, we discussed the theory of alerts, the maximum deviation angle from the road can be no more than 20 degrees for alerts in iGO with default settings. However, we cannot always accurately determine the azimuth of the road, especially in places where the road is rounded. On OSM maps, the azimuth of the road was 10=190 degrees. Based on this, we can deflect the azimuth of the radar by a maximum of 20 degrees, which will be 30 =210. But a real test showed that OSM and TomTom maps are different, and the road graphs are different. And the test azimuth of the road was 4=184 - TomTom data. For iGO, the maximum deviation from the road is 20 degrees, but this is the limit. For stable and guaranteed alerts, you need to have as few as 20 degrees as possible (this information is for those who create iGO radar databases) since we cannot accurately determine the azimuth of the road. The azimuth of the road may be different when using maps from HERE or TomTom.

And so the test is in motion. The coordinates of the installed radar are taken from the BBS database:

-8.18326,43.16732,1,80,1,204

Spoiler: 204

[Only registered and activated users can see links. ]

There is no notification from the radar, and even more so there is no notification if you use the BBS database specifically for this entry, the original BBS database:

-8.18326,43.16732,1,80,1,229

Now the corner is working:

-8.18326,43.16732,1,80,1,203

Spoiler: 203

[Only registered and activated users can see links. ]

What it looks like on the OSM map, 23=203 degrees, black ray.

Spoiler: +

[Only registered and activated users can see links. ]

Based on recent tests, I would recommend that iGO users have an entry in sys for the BBS database.

Code:

Please Login or Register to see the links