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

R_LINK-2 speedcam.txt for skin patch v1.2-1.5

OSC base

VB Full

Spoiler: VB Full

R_Link_2_VB Full speedcam.txt
(32 Speed Camera - Speed Camera in the back), (33 Mobile Speed Camera),
(34 Built-in Camera), (37 Speed ​​multi control - Speed ​​multi control in the back),
(36 Red Light), (43 Red Light and Speed Camera),
(54 Average Speed Camera), (46 Average Speed Camera - Finish),
(47 Congestion Charge Zone), (39 Bus Lane Camera - Bus Lane in the back),
(49 Fixed Mobile Camera - Fixed Mobile in the back),
(55 Post police), (56 Stop Control Camera), (62 SC camera and fake),

(38 Railway crossing),
(40 High Accident Zone), (41 School Zone), (42 Town Entry Point),
(44 Toll Booth), (45 Town End), (48 Give way), (50 Speed Breaker),
(51 Bad road), (52 Dangerous turn), (53 Tunnel),
(57 Overtaking is prohibited), (58 Speed limit),
(61 Pedestrian crossing), (63 Dangerous Area),

______________
VB Pro

Spoiler: VB Pro

R_Link_2_VB Pro speedcam.txt
(32 Speed Camera - Speed Camera in the back), (33 Mobile Speed Camera),
(34 Built-in Camera), (37 Speed ​​multi control - Speed ​​multi control in the back),
(36 Red Light), (43 Red Light and Speed Camera),
(54 Average Speed Camera), (46 Average Speed Camera - Finish),
(47 Congestion Charge Zone), (39 Bus Lane Camera - Bus Lane in the back),
(49 Fixed Mobile Camera - Fixed Mobile in the back),
(55 Post police), (56 Stop Control Camera), (62 SC camera and fake),
______________
Full

Spoiler: Full

R_Link_2_Full speedcam.txt (without notifications in the back)
(32 Speed Camera ), (33 Mobile Speed Camera),
(34 Built-in Camera), (37 Speed ​​multi control),
(36 Red Light), (43 Red Light and Speed Camera),
(54 Average Speed Camera), (46 Average Speed Camera - Finish),
(47 Congestion Charge Zone), (39 Bus Lane Camera),
(49 Fixed Mobile Camera),
(55 Post police), (56 Stop Control Camera), (62 SC camera and fake),

(38 Railway crossing),
(40 High Accident Zone), (41 School Zone), (42 Town Entry Point),
(44 Toll Booth), (45 Town End), (48 Give way), (50 Speed Breaker),
(51 Bad road), (52 Dangerous turn), (53 Tunnel),
(57 Overtaking is prohibited), (58 Speed limit),
(61 Pedestrian crossing), (63 Dangerous Area),


[Only registered and activated users can see links. ]

НUN Truck - UX speedcam

Spoiler: НUN Truck

iTruck

OSC base

iGO 5w iTruck speedcam - code 1,2,3,4,5
1 - (32 Speed Camera),
2 - (34 Built-in Camera),
3 - (36 Red Light),
4 - (35 Average Speed Camera + Finish 5 km h)
5 - (33 Mobile Speed Camera)

iGO 4w iTruck speedcam - code 1,2,3,4 NOMob
1 - (32 Speed Camera),
2 - (34 Built-in Camera),
3 - (36 Red Light),
4 - (35 Average Speed Camera + Finish 5 km h)

SCDB base iTruck NO Mob
1 - (32 Speed Camera),
2 - (34 Built-in Camera),
3 - (36 Red Light),
4 - (35 Average Speed Camera)

SCDB base iTruck Code 5
5 - (33 Mobile Speed Camera)

POI base iTruck NO Mob
1 - (32 Speed Camera),
2 - (34 Built-in Camera),
3 - (36 Red Light),
4 - (35 Average Speed Camera)

POI base iTruck Code 5
5 - (33 Mobile Speed Camera)

Updated data due to changes in the composition of speedcam.txt published on the gpspower forum
09.08.2025

FAQ speedcam for Trucks

This topic is from 26th March 2024 had to decide on the use speedcam.txt, for each UX - speedcam corresponds speedcam.txt (classification by coding), that's why the topic is called

FAQ iGO encodings and speedcam.txt [compatibility]

The main point is that the pongo skin in all versions comes with encoding VB this is a post #2, if you downloaded the assembly iGO, on the forum, in social networks with the note assembly with skin pongo, the question must always arise, what kit does the author of the assembly offer?, Let's look at a more common type, with a note: "For Truck".

Look in the folder UX and content/speedcam.

UX speedcam encoding VB skin pongo:
speedcam_mod_vb.zip или speedcam_mod_vb_64.zip

Corresponds to encodingVB
content/speedcam:
Skin32w_Full_VB_HRV.txt

NO corresponds to the encoding VB
content/speedcam:
Skin32w_Truck_NOMob_HRV.txt, Skin32w_iTruck_NOMob_HRV.txt, Skin32w_Truck_HRV.txt, Skin32w_iTruck_HRV.txt


For speedcam Truck or iTruck corresponds to the encoding UX speedcam with abbreviation NC - #4, 5
speedcam_mod_nc.zip или speedcam_mod_nc_64.zip

For all assemblies published on the Internet, Assembly authors, please pay attention to the contents of the folders UX и content/speedcam, files must comply with encoding.

Where to download UX speedcam in encoding NC:
[Only registered and activated users can see links. ] - for nextgen
[Only registered and activated users can see links. ] - for nextgen 64bit

Attention!!! set speedcam.zip - speedcam_mod.zip must be of the same version Mod AF.

FAQ explanation for the application for iGO nextgen - iGO nextgen Luna

For all countries:
-Learn more about the medium speed cameras
for the correct warning "medium speed control zone" there must be two cameras.:
- the first one (the beginning of the zone) with a measurable limit, for example 70 km/h
- second (end of the zone) with a speed limit of 5 km/h,
both cameras are directed against traffic; in those areas where speed is controlled by both directions, there should be four cameras (two opposite ones);

1. For the UK and other countries with miles iGO nextgen including the version iGO_Israel_9.18.27.955559
-Learn more about the medium speed cameras
for the correct warning "medium speed control zone" there must be two cameras.:
- the first one (the beginning of the zone) with a measurable limit limit, for example 30 mph
- second (end of the zone) with a speed limit of 3 mph,
both cameras are directed against traffic; in areas where speed is controlled by both directions, there should be four cameras (two opposite ones);

Speed speedcam.txt It should be miles away

2. For the UK and other countries with miles iGO nextgen:
iGO_Luna_9.35.2.153810
iGO_Israel(Luna)_9.35.2.263562
iGO_Avic_v9.35.2.227616
iGO_Basar_9.35.2.262743
iGO World v9.35.2.252374
-Learn more about the medium speed cameras
for the correct warning "medium speed control zone" there must be two cameras.:
- the first one (the beginning of the zone) with a measurable speed limit, for example 64 km/h
- second (end of the zone) with a speed limit of 5 km/h,
both cameras are directed against traffic; in those areas where speed is controlled by both directions, there should be four cameras (two opposite ones);

Speed speedcam.txt It should be in kilometers (The program iGO converts it into miles by itself.)

For the UK by по spc:
United_Kingdom_HERE_In_MPH.spc speed in miles (MPH), this means that this file should be used for iGO nextgen including the version iGO_Israel_9.18.27.955559

United_Kingdom_TomTom.spc speed in kilometers, this means that this file should be used for
iGO nextgen:
iGO_Luna_9.35.2.153810
iGO_Israel(Luna)_9.35.2.263562
iGO_Avic_v9.35.2.227616
iGO_Basar_9.35.2.262743
iGO World v9.35.2.252374
(The program iGO converts it into miles by itself.)

[Only registered and activated users can see links. ]

FAQ iGO OEM

I'm trying to understand the situation with the first five iGO codes. Let's say the 1.2.3.4.5 encoding is the default for all iGOs since the program's inception. Let's call this phenomenon "iGO OEM." This also applies to all iGO-based programs, such as Becker and other iGO-based ones. If you don't have iGO Primo, which was released in 2010, but an older version of iGO, such as iGO8 or iGO8.3, then your speedcam.txt is iGO OEM. Also, if you iGO OEM, you can't use spc files from HERE or TomTom. Because spc is iGO Primo's encoding, you'll get unreliable notifications.
Now, regarding usage, how many users are still using older hardware? I estimate their number is approximately 0.1% of the total iGO user base, as those using iGO Primo since 2010, newer Android devices, and iGO Primo Nextgen.
Now let's talk about OEM for iGO Primo. So, iGO Primo is a workaround for iGO's bugs, a different approach to route building, and a different coding principle. All radar coding to this day is based on iGO Primo. You can safely use spc, as this is iGO Primo's encoding.
"OEM iGO Primo" has a coding system with a 32-bit repetition rate. [Only registered and activated users can see links. ] and so on up to 992.
Now about my publications: Mod AF, speedcam.txt. All files are created for iGO Primo users. Let's call this OEM iGO Primo. We've covered two concepts: OEM iGO and OEM iGO Primo. If you're an iGO Primo user, you don't need to look for special speedcam.txt files for OEM iGO with encoding 1.2.3.4.5.
Your navigator supports at least 16 notification types, and up to 32 notification types when using a skin. Older iGO Primo skins 24, 25, or 27 notification types, depending on the skin author's efforts. Mod AF - 32 types as in iGO Primo Nextgen.

History of iGO

Spoiler: +++++

iGO My Way 2006 Plus is a navigation program for personal navigators (running Windows CE) and PDAs/communicators (running Windows Mobile). Released in 2005, it was discontinued in 2009.

iGO 8 is the next version of iGO, released in 2008. Its key feature is realistic 3D navigation with terrain display, road junctions, buildings, and other landmarks.

iGO Amigo is a version of iGO with a simplified user interface, released in 2009. It retains the core features of iGO 8 required for GPS navigation, although its capabilities are limited compared to the previous version to achieve maximum simplicity and ease of use. Features of iGO Amigo:

• a built-in presentation that teaches the user how to use the program;
• low-maintenance RAM usage, allowing the program to run quickly on any device;
• Comparison of multiple route options (fast, short, economical, easy);
• The "Where am I?" function determines your current GPS coordinates and displays nearby points of interest, such as a police station, emergency room, auto repair shop, etc.;
• The route is displayed as dots, allowing you to see your direction even at very low speeds;
• The cursor shape can be selected—a standard "arrow" or a cursor representing various vehicle models.
• The app is preinstalled on personal navigators from several brands, including Navon, Prestigio, and others.

iGO My Way 2009 is a version of iGO for iPhone. Currently, the app is available in the Apple App Store with maps of North America and Europe. Features of iGO My Way 2009:

• Realistic 3D display of the map, road junctions, and buildings;
• TTS Pro (Text-to-Speech) support, which provides voice prompts for street and city names, as well as traffic information and information about road conditions within a country after crossing its border.
• Google Local Search – search for businesses, landmarks, and other points of interest near the user's current location;
• purchase of additional content through the App Store;
• realistic display of interchanges;
• calculation of an "eco-friendly" route with the lowest fuel consumption and CO2 emissions in addition to the standard quick, short, and easy route options;
• search for POIs along the route;
• select iPhone contacts, GPS coordinates, and photos as the destination;
• route calculation with multiple waypoints;
• the ability to call a POI directly from the navigation app;
• the "Where am I?" function determines the current GPS coordinates and displays the nearest necessary points of interest, such as a police station, emergency room, car service, etc.;
• Automatic device orientation detection (portrait/landscape orientation);
• Display of traffic lanes and realistic signs during navigation;
• Selectable cursor shape—standard "arrow" or models of various vehicles;
• Automatic return to navigation mode after an incoming call.

iGO Primo is the latest version of the program, released in 2010. Like iGO Amigo, it has a simple user interface, but also includes a wide variety of features and customization options.

iGO Primo features:

• High-resolution 3D terrain display;
• Point Addressing—navigate through driveways and search for houses with fractional numbers, multiple buildings, etc.;
• Realistic display of road signs in the country;
• An improved program core significantly accelerates the calculation of complex routes;
• Additional navigation tips—information about the next two maneuvers, warnings about road safety cameras, speeding alerts, etc.;
• The "Back to Car" function automatically remembers the car's position when the device is disconnected from the power supply;
• Simultaneous calculation of multiple route options, including an "eco-friendly" route;
• Accounting for traffic restrictions that depend on the time of day or day of the week (e.g., streets closed to traffic on weekends);
• Display of traffic lanes and realistic signs during navigation;
• The user can customize the quick menu and map screen;
• The cursor shape can be selected—a standard "arrow" or models of various vehicles;
• The route is displayed as dots, allowing you to see the direction of travel even at very low speeds;
• The "Where am I?" function determines your current GPS coordinates and displays the nearest necessary points of interest, such as a police station, emergency room, auto repair shop, etc.;
• The program takes into account and displays traffic regulations in different countries (maximum speed limits in and outside populated areas, permissible blood alcohol levels, etc.);
• Truck navigation (iGO Primo Truck version), taking into account the vehicle's dimensions and the nature of the cargo.

The program is pre-installed on personal navigation devices.

iGO Primo Nextgen was introduced in 2015.

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.