Thread: iGO Speedcam (DISCUSSION)

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.