Skin iGO nextgen by pongo (DISCUSSION)

**srbabeg** · 31st December 2017, 11:00 AM

Originally Posted by quartzo

...New picture from pongo, for the sake of understanding
...
L.E.

Pongo UX plug-in for Measurement Average Speed, for now, is not good !

I noticed problems in using the Camera for Average Speed. In short :

1) If only slightly changes the route, stopping at the gas station, the Average Speed Camera stops to be measured.
2) If a GPS signal disappears for a moment, which happens in ordinary driving, and in the tunnel it is mandatory, the camera stops measuring again.

However, with special respect for @Pongo, I did a little more careful testing, so as not to make a mistake. With the @Pongo Add-on, a third problem appeared:

3) Measurement The average speed is interrupted for no apparent reason.

This is an illustration of the measurement problem in the area of New Belgrade:

Spoiler: Link

Of course, @Pongo deserves gratitude for the effort, but his addition is not nearly as reliable as the UX plug-in of @Frontzosd for Measurement The Average Speed. UX frontzosd add-ons are used toll booth as a trigger and work excellent in iGO AvicSync navigation with a frontzost skin.

Spoiler: Link

If someone wants to look at the testing of the @frontzosd method of Measurement The Average Speed, it can see at topic

Spoiler: Link

**WOB** · 31st December 2017, 12:43 PM

Based on users feedbacks, UX from Frontzosd is working partially ONLY with AvicSync, and ONLY with Frontzosd skin, and only in Serbia, and only with specific speedcam file. Pongo's UX is working same with all versions of iGO, only with Pongo skin, everywhere...
How can you even compare this two utilities and make conclusions on Pongo's ux based on virtual testing?!?

**BIRBANTE** · 31st December 2017, 02:32 PM

Sorry for my ignorance on the subject, but the math is not an opinion.....

The speed, and also the average speed, they are the result of the division of a section between a point A and a point B with the time taken to travel it.

The software knows the point A, there are the coordinates in the speedcam file, but does not know point B, there are no coordinates of point B in the speedcam file, and in any case, how do it give me the average speed even before getting to point B?
It can only give the instantaneous speed detected by the satellite......

In Italy we know the coordinates of points B in our txt files, and I created the category "average speed end", I know the beginning of the stretch, I know the end, and in that stretch I have to be careful with my speed........ but I should do the same with the skin of Pongo or Frontzosd ......

**WOB** · 31st December 2017, 03:23 PM

Point A is only trigger for start of calculation (Av. speed zone start)... Software knows only actual speed, "measured" from satellites... It takes, for example, actual speed every 1 second, and calculate average ... So simple... Sum of 10 speed values, devided with 10 is Average speed, right? No Point A, no Point B...

There is also a second way of calculation. Point A is again trigger ... Then software saves time. Afterwards, software knows in every point your Avg. Speed. For example, you have driven 10 minutes and you passed 10 km, so Avg. speed is ... ?

I don't know how Pongo calculate Avg. Speed in his UX, but Point B is really unimportant for calculation. It triggers only End of "measuring"!

My question is, what's the difference between these two Av. Speeds?!?

Spoiler: screen

**Midnight Blues** · 31st December 2017, 03:50 PM

Point A is starting point (must be known), point B is actual position (at present moment), no matter where exit point will (or will not) be in future.
B = Exit point, will be at moment when you reach that point.
Rest is math.

"Driving Avg. Speed" is average in last short period, another is for complete section (from A to B).

**WOB** · 31st December 2017, 05:10 PM

Originally Posted by Midnight Blues

Point A is starting point (must be known), point B is actual position (at present moment), no matter where exit point will (or will not) be in future.
B = Exit point, will be at moment when you reach that point.
Rest is math.

I have already said that

Originally Posted by Midnight Blues

"Driving Avg. Speed" is average in last short period, another is for complete section (from A to B).

What is "last short period"?!?

**BIRBANTE** · 31st December 2017, 05:58 PM

Originally Posted by WOB

What is "last short period"?!?

There is a point A, and after 5 km there is point B. You have passed point A from 500 meters, let's call it point A1, from A to A1 is "last short period", with this example I answer also to your post#650, if point A1 is close to point A, the average speed and the actual speed are the same.

I made a check and maybe I understood where is point B. It's virtual, and it's on the data.zip, in the speedcam.zip file and in some sys.

section_beep_distance=150
section_beep_spoken_type=speech
section_beep_speech="Average speed camera."

these three strings are only for the "Average speed camera" category, the number should be the seconds after which the stretch ends......

A safer answer can only be given by Arimi, Pongo & C.

**vasile1955** · 31st December 2017, 07:09 PM

I continue the
Cameras of medium speed
changed the warning logic
for the zone, two cameras should be created
first (the beginning of the zone) with the limiting limit limit. The
second (zone end) with a speed limit of 5 or 0 km / h
can be deleted by clicking on it

Spoiler: Link

Thanks to pongo

Spoiler: Image

**WOB** · 31st December 2017, 07:14 PM

@BIRBANTE If that's true (and I think it is not), what is "the rule" for point A1? Is it 10%? Half way? 5 minutes before? ... Then I would like to know, what is a purpose of this? Why I want to know, what was my Avg. Speed in past?
And of course, why is then called "Driving Avg. Speed"?