Thread: FAQ iGO encodings and speedcam.txt [compatibility]

What does "artificial intelligence" think about this?

FAQ Ai - iGO OEM, iGO OEM Primo

Speedcam.txt files in iGO OEM (often corresponding to earlier versions such as iGO 8) and iGO Primo OEM have the same basic format and are generally interchangeable.

Basic Principles and Format
The basic principle of working with the speedcam.txt file in both versions is to use a simple text format with delimiters (usually the pipe symbol |). Each line in the file describes one point of interest (POI) or camera and contains a set of parameters:
X|Y|TYPE|SPEED|DIRECTION|...
Where:
X and Y are the geographic coordinates (longitude and latitude).
TYPE is the type of camera or warning (e.g., fixed camera, dangerous spot, railway crossing).
SPEED is the speed limit for the given point.
DIRECTION is the camera's direction of action (optional).
Differences
The key difference lies not in the file format itself, but in the functionality of the iGO Primo OEM software, which supports a wider range of alert types (categories) compared to older versions of iGO OEM.
iGO OEM (older versions): Supports basic camera and hazard types (e.g., fixed radars).
iGO Primo OEM: Adds support for additional POI categories, such as railway crossings, fire stations, school zones, etc.
Therefore, the speedcam.txt file for iGO Primo OEM may contain lines with new TYPE values ​​that will not be recognized or used in older versions of iGO OEM. However, basic camera types will work in both versions.
It is important for users to ensure that the database they are using is compatible with their region and software versions.