Thread: iGO Speedcam (DISCUSSION)

FAQ Summary of using speedcam.spc

Spc does not work in new 64 bit versions:

- 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

Spc works, but in countries where miles are used they do not work correctly, the iGO program reduces the values (in the UK instead of 30 mph it will be reported as 19 mph):

- iGO_Luna_9.35.2.153810

All versions NextGen 9.18.27 аnd Primo spc work

This is not entirely true, if there is a corresponding * .lyc, all 64-bit iGOs see * spc files...

Spoiler: *.spc

[Only registered and activated users can see links. ]

[Only registered and activated users can see links. ]

[Only registered and activated users can see links. ]

The question of why the AF blog is closed to the public is increasingly arising.
I also sometimes wonder why the blog should work. The blog was created in 2019 as an alternative to technical forums. In 2019, many technical forums reacted aggressively to my innovations in iGO encoding, as well as the promotion of the OSC database as an alternative to already known databases, which in turn is able to combine all known data with the ability to edit data on the map, with a fairly simple registration on the site. And in the end, gpspower turned out to be more far-sighted than others, which allowed many ideas and authors to be grouped here.
Returning to access to the AF blog, it seems pointless to me to duplicate files on the blog, while there is gpspower. You can get all the information by visiting the gpspower forum.

I apologize if this question is not appropriate
Where can I find speedcam Cat16 In a single updated txt file?

Additions!!!
FAQ - kmh / mph - For average speed control zones

PS
[Only registered and activated users can see links. ]

All this will affect the OSC base, with the next update speedcam.txt ready assemblies will be changed. Also it will affect HERE and TomTom conversion speedcam.spc - speedcam.txt

And you think that has something to do with this topic?
What skin are you using? What speedcam ux files? Which lang and voice files?

Browse relevant themes.

Hello

Hello, how far away (when the road is not straight) I should calculate the DIRECTION using DIR TYPE=1 ?

The maximum azimuth deviation from the road can be no more than 19 degrees, if the deviation is higher, it is better to use a circular alert.

Do you think Andrey Form didn't think about how he could earn a few pennies? Why do you think he changed everything in speedcam? Especially for comfortable or non-tech-savvy people. Contact him because for a small fee, he gives you the entire speedcam archive, saving you 30-40 minutes of your life.

About changing the encoding, why 32 when everyone is used to 1. For various programs that are adapted to 1 code, this is important, but for the content/speedcam folder, it does not matter. Since iGO reads all codes with period 32, there is a table of periods at the beginning [Only registered and activated users can see links. ] Therefore, for iGO, it does not matter which period is used in speedcam.txt, 1 or 32, as this substitution is built into all iGO navigation programs. We assume that the 32 code works on iGO Primo, iGO nextGen, and iGO Luna. It does not work on ?iGO8 v8.3?, and I do not have the opportunity to verify this.
Another question is about iGO8 v8.3 and the use of speedcam.spc files. The fact is that spc is a primo encoding, and there can be any alert types from 1 to 15 + 31, which are incompatible with iGO8 v8.3

This is what he writes @Andron66 in 2011 year - 21.04.2011

Let me explain...
Initially, iGo8 had five types (from the top, in order: 192, 193, 194, 227, 68). Then, as the program evolved, it became possible to increase their number to... We settled on 15, adding cameras 197 through 206 (these aren't really speedcams, but rather warnings), calling them "Extended" or DA (Driver Alerts), by analogy with the Driver Alerts signs that appeared in the program much later (files with the .fda extension). As it turned out, the introduction of these types was more than successful. Firstly, it became possible to add and edit these warnings ourselves, and secondly, it allowed for more extensive warning settings (voice-sounds-distance-direction). This is the format of the databases for the 8 and Primo, with modifications for the 8 speedcam databases. With the release of Primo, the developer introduced an additional 27 types (in addition to the first 5), bringing the total to 32 (types 197-223). As a result, we had a conflict between types 197-206 (the extended type in iGo8). This is where our "experts" began their shenanigans, swapping speedcam lines. Although, as you can easily see, types 208-222 are unused in Primo itself. WertVRV's skin left the Primo types alone, instead adding an extended type for the empty 208-215 (Danger Zone coincided with Primo's type 223). Now it's clear why only 24 types are used in skins? Types 197, 216-222 are "dummy" types, i.e., "reserve" :D (32-8 = 24).

Here's the thing, even back in 2011 the encoding for iGO was 3 digits, the first 5 types - 192, 193, 194, 227, 68.

_ID0 = 1_or_64_or__96_or_128_or_160_or_192_or_224 - 32
_ID1 = 5_or_65_or__97_or_129_or_161_or_193_or_225 - 33
_ID2 = 2_or_66_or__98_or_130_or_162_or_194_or_226 - 34
_ID3 = 4_or_67_or__99_or_131_or_163_or_195_or_227 - 35
_ID4 = 3_or_68_or_100_or_132_or_164_or_196_or_228 - 36

@Stanislavovoch 29.10.2008

Basic - standard (common to ALL versions of iGO, Primo, Amigo, etc.); are new codes for txt database files, although iGO still accepts old codes (1....5) from txt databases.
ID0 = 1 /192 CD "Static" "Stationary camera"
ID1 = 5 /193 CD "Mobile" "Mobile ambush" (no speed recording)
ID2 = 2 /194 CD "Redlight" "Camera built into a traffic light"
ID3 = 4 /227 CD "Section" "Speed ​​measurement on a section"
ID4 = 3 /68 CD "Redlight Only" "Red light monitoring" (no speed recording)

Here's what we were able to expand in iGO 8.3: @Stanislavovoch 29.10.2008

Extended - non-standard
ID5 = 5 / 197 DI "Railroad" "Crossing" (no speed limit, always in both directions)
ID6 = 6 / 198 DI "Give Way" "Give Way" (no speed limit) (corresponds to sign 2.4 "Give Way") voiceover: "Give Way"
ID7 = 7 /199 CD "FixMobil" "Mobile Ambush" (with speed limit, essentially an alternative to CD 05 "Mobile")
ID8 = 8 /200 DI "Speed ​​Breaker" "Speed ​​Bump" (corresponds to sign 1.17 "Speed ​​Bump") voiceover: "Speed ​​Bump Ahead"
ID9 = 9 /201 DI "Children" "Children" (no direction or speed limit), indicates areas where pedestrians, children, and other living creatures congregate
ID10 = 10 / 202 DI "Dangerous Turn" "Dangerous Turn" (no speed limit) (corresponds to sign 1.12.1 "Dangerous Curves" voiceover: "Dangerous curve ahead"
ID11 = 11 / 203 DI "Tunnel"
ID12 = 12 / 204 DI "Dangerous Way" (corresponds to sign 1.33 "Other hazards") voiceover: "Dangerous section ahead." Used to warn of potholes, poor road conditions, and repair work.)
ID13 = 13 / 205 DI "POI" (no speed or direction) voiceover: "POI of interest ahead"
ID14 = 14 / 206 CD "RPS Post" voiceover: "Traffic police post ahead"

Now let's talk about how iGO Primo has expanded: @Stanislavovoch 31.12.2014

Extended - standard Primo
ID5 = ----------------------------
ID6 = 6 / 198 Railway crossing
ID7 = 7 / 199 Bus Lane Camera
ID8 = 8 / 200 High Accident Zone
ID9 = 9 / 201 School Zone
ID10 = 10 / 202 Town Entry Point
ID11 = 11 / 203 Red Light and Speed ​​Camera
ID12 = 12 / 204 Toll Booth
ID13 = 13 / 205 Hospital, Ambulance
ID14 = 14 / 206 Fire Station
ID15 = 15 / 207 Congestion Charge Zone
ID31 = 31 / 223 Dangerous way

speedcam.spс correctly notifies starting with Primo versions:
Primo 1.0 (exe version - 8.5.9.x)
Primo 1.1 (exe version - 8.5.11.x)
Primo 1.2 (exe version - 9.2.1.x)
Primo 2.0 (exe version - 9.6.x)
Primo 2.4 (exe version - 9.6.13)

FAQ new Primo 18w
Starting with version 9.35.2, the new Primo standard comes with 18 default notification types from the manufacturer.

ID0 = 1 / 32 "StaticCamera",
ID1 = 5 / 33 "MobileCamera",
ID2 = 2 / 34 "CameraInTrafficLight",
ID3 = 4 / 35 "SectionCamera",
ID4 = 3 / 36 "RedLight",
ID6 = 6 / 38 "RailwayCrossing",
ID7 = 7 / 39 "BusLane",
ID8 = 8 / 40 "BlackSpot",
ID9 = 9 / 41 "SchoolZone",
ID10 = 10 / 42 "UrbanArea",
ID11 = 11 / 43 "RedLightTrap",
ID12 = 12 / 44 "TollBooth",
ID13 = 13 / 45 "Hospital",
ID14 = 14 / 46 "FireStation",
ID15 = 15 / 47 "ChargeZone",
ID22 = 22 / 54 "SpeedBump",
ID23 = 23 / 55 "NoParkingZone",
ID31 = 31 / 63 "DangerousArea"

This encoding is for all versions starting with 9.35.2. Unless there are changes, there will be extensions to 32 types in UX speedcam.

Primo standard has changed from 16 to 18 types, with all the ensuing implications. This may be reflected in the future when using speedcam.spc.