Printable View
Even in the tests the Type is always the same, but the fact remains that if they are not "diluted" they are toxic and iGO would not alert them, including those with Dirtype = 2.Quote:
Originally Posted by Andrey Form [Only registered and activated users can see links. Click Here To Register...]
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:[warning]
Speedcam_max_angle=30
For mountain serpentines
Code:[warning]
Speedcam_max_angle=45
I was careful about this and placed the points only on straight stretches of road and to be more sure I tried several different stitches.
If it depended on the angle they should never work, but when they are "diluted" they work.
In order for the next point after the notification to work. if two points are intended for notification in the same direction, the program needs 3 seconds to notify the second point, if the point is located closer than 3 seconds, then this is not a point, but a duplicate that needs to be deleted, and not tested what will happen to the notification.
You need to have a radar database where all road conditions are taken into account, it’s like a song where every word has meaning. Usually they put everything called speedcam.txt in the content/speedcam folder, but no one understands what is involved.
What you describe is not my case, three points in 10 kilometers, about one warning every 3 minutes.
I repeat once again, alone the txt files with the double direction only work as a warning for the first one I encounter, however if they are together with other txt files from Fixed Speedcam or other categories they all work normally.
I just want to make it clear that as long as the number of points with the double direction is small nothing happens but if it exceeds a certain percentage there could be problems with their reporting by iGO, in Italy it is a very remote circumstance, out of over 7000 fixed speed cameras only around a hundred are bidirectional.
@BIRBANTE
Of course you can describe the situation, your words: "double direction only work as a warning for the first one I encounter",
But how to understand all this, apply it and what needs to be done. If it works like this:
[Only registered and activated users can see links. Click Here To Register...]
and in spc files the same thing, 1 direction, 2 directions, circular alert.
And it all works because these are the principles of the iGO program.
There are 7,000 cameras in Italy, but you don’t categorize them according to directions, but use a database that simply records the installation location. 100 cameras have 2 directions, and the speed is reduced in 7000 cases.
So, maybe it would have been more correct to write "There are 7,000 type code 1 cameras in Italy"?
:damnpc:
Is there any database editor or sth where I can FILTER OUT cameras I do not want to have in my speedcam.txt file?
Simply if I choose any speedcam file here on forum and decide to filter out cameras I do not want...is there any way or sql editor it sth that can simplify that task?
Thx
Notepad ++, texas :smile:
Boki my friend...can u give me some more hints...since I have notepad ++ and I am not versatile in it..I cannot find a way to do it...do I need some kind of plugin or...can u give me some hints xdd
Cause n+ does not differentiate 2, from coordinates...
Spoiler: CLICK TO SEE