Thread: iGO Speedcam (DISCUSSION)

FAQ The notification for the average speed camera does not work.

I found the following file on a friendly site, it created a solution for notifying sections of average speed, alas, it does not work because there is no connection to the map, all points have 270 degrees for opening a section and 70 for closing at a speed of 5 km/h

Spoiler: +++

[Only registered and activated users can see links. ]

[Only registered and activated users can see links. ]

Do not use in your navigator

Code:

Please Login or Register to see the links

FAQ
The fact that the speedcam.txt file cannot be used in the form of advertising, with the exception of using a comma after DIRECTION,
[Only registered and activated users can see links. ]

As a result, not a big test with the base laradiobbs.
First test, speedcam.txt records do not contain any records other than iGO:

Code:

Please Login or Register to see the links

Radar coordinates and their direction:

Spoiler: +

Car movement 1-2 turn 3-4, Based on the direction of the cameras, they should only trigger at points 1 and 2
17:35 - 1, 17:38 - 3, 17:39 - 3, 17:43 - 4, Photos 1 and 2 show warnings, 3 and 4 do not.

Spoiler: Test 1

Second test, original files from the database laradiobbs.

Code:

Please Login or Register to see the links

17:57 - 1, 18:00 - 3, 18:01 - 3, 18:05 - 4

Spoiler: Test 1

- Point 4 did not work because it is too far away, but it shows that it works in a circular notification.

FAQ creation of a new type for iGO cameras, when this has been implemented for a long time, errors in the notification strategy.
An attempt to create a new type of camera aimed in one direction.
Its characteristics are recording violations in two directions of movement, but within the camera’s coverage area, and the detection range of the violator is 500 meters. When using the pongo skin with the ability to notify that the camera has the ability to measure your speed after crossing. But since we have an alert in two directions, one direction remains false, as shown in the figure.

8.055361,44.811310,1,70,2,334



The only way to notify these types of cameras is only using VB encoding:


8.055361,44.811310,59,70,1,334 --------------------------------- 8.055309,44.811317,32,70,1,154

@BIRBANTE
Hi,
The fact is that I do not modify the POI base, I only publish data from it. So you see what the base does, of course it is better to have one point and 2 directions than 2 points and 2 directions, there is no need to carry out tests, the only question is the number of lines in the speedcam.txt file, this does not affect anything else.

Code:

Please Login or Register to see the links

Originally Posted by BIRBANTE

Just do some tests....... but do it seriously and completely...

If you know how notification of alarm points in iGO works, then you don’t need to do any tests with the program, just look at the contents of speedcam.txt. Any options work, since they have the same type of alert, in this case it is radar.

It will not warn you only in one case, if the angle of deviation from the direction of the road is more than 19 degrees - this is azimuth. And yes, there can be a lot of such points in Italy, this is when the radars are located on the bends of the roads. But this has nothing to do with the direction of the alert.
There is a simple solution for those who use radar databases where the points have a directional effect, this is an entry in sys:

Code:

Please Login or Register to see the links

For mountain serpentines

Code:

Please Login or Register to see the links