Running in a tunnel caused issues in the total distance computation

[Dimitrios Kanellopoulos]

@sky-runner we have fixed this issue quite some fw before.

[tuxella]

This “double counting” theory could explain the results I get.

I analysed the data in the Suunto fit file from the 30/03/2021 :

The first time in the tunnel (difference between the first and the last point without coordinates):

• Distance: 0.87 km
• Time: 4:15
• Speed: 12.28 km/h

On the way back (in the same tunnel):

• Distance: 0.88 km
• Time: 4:19
• Speed 12.23 km/h

If I add these distances to the distance calculated from GPS coordinates of each point:

7.74 + 0.87 + 0.88 = 9.49km

Where the total distance in the fit file (and reported in Suunto App, QS, Runalyze, Strava…) is 9.58 km

[Dimitrios Kanellopoulos]

@tuxella can you make the links of qs public ? You can easily see if it’s that bug which was fixed

Currently I cannot open those links

[tuxella]

@dimitrios-kanellopoulos They should be public now

[Dimitrios Kanellopoulos]

@tuxella are you using a pod ?

[tuxella]

@dimitrios-kanellopoulos No, this activity was done with just a Suunto S9 and the HR belt

[Dimitrios Kanellopoulos]

@tuxella I’ll take a better look when I am on my pc.

I do see the issue.

[tuxella]

@dimitrios-kanellopoulos Cool

Have a nice week-end

[ddausw]

@tuxella
I have the same problem with the s9b after the last FW update. The tunnel length is counted twice. I tested with Glonass as well as Galileo.

Dieter

[MiniForklift]

Nice pace! Just gave you kudos

[tuxella]

@miniforklift Thanks

[tuxella]

@dimitrios-kanellopoulos Hello

did you have the opportunity to check on this?

[Dimitrios Kanellopoulos]

@tuxella I reported a bug or the watch guys.I think this new FW re introduced the issue

[Dimitrios Kanellopoulos]

@tuxella I would like some suunto app links

[tuxella]

@dimitrios-kanellopoulos

For the 30/03/2021: https://www.suunto.com/fr-fr/move/thomas430851/606310cf949ba71fa290dc8a

For the 09/03/2021: https://www.suunto.com/fr-fr/move/thomas430851/60476ac697a7b66e0c4c5d8a

[tuxella]

@dimitrios-kanellopoulos I had this issue twice: on the 30/03 and on the 09/03.

On the 09/03 I wasn’t using the “new firmware” (which was released on the 30/03 AFAIK)

[Dimitrios Kanellopoulos]

@tuxella I did open a bug report in any case… Something is wrong here.

Strangely while I tested this I didn’t get this issue. so lets let the watch guys figure this out.

[tuxella]

@dimitrios-kanellopoulos Thank you

[Likarnik]

@Dimitrios-Kanellopoulos I had same issue two days ago, but I think never before (I ran quite a lot under that tunnel). I thought it was just a glitch before I saw this topic Will it help with my link too?

[tuxella]

@dimitrios-kanellopoulos Did you have any news on this topic?