Author Topic: Two bugs: route page % clinched by segment  (Read 772 times)

0 Members and 1 Guest are viewing this topic.

Offline mapcat

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 828
  • Last Login:Today at 05:17:46 am
Two bugs: route page % clinched by segment
« on: June 10, 2018, 02:46:50 pm »
KY 560 is a route driven by five users and clinched by no one, where all users have driven the segment concurrent with KY 165 (and only that segment).

Bug #1: the waypoint table shows that 100% of users have been on the concurrent segment, and 20% have been on the other two segments, even though no one has traveled the other two segments.

Bug #2: the route stats table shows that I've traveled .22 mi of the route (3.68%), and that all five travelers have also traveled .22 mi of it (3.60%). Why the discrepancy in % traveled?

BTW the KY52 waypoint name will be corrected in my next pull request.
Clinched:

Offline Jim

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1486
  • Last Login:Today at 08:11:13 am

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 568
  • Last Login:Today at 07:08:30 am
Re: Two bugs: route page % clinched by segment
« Reply #2 on: April 20, 2019, 09:28:36 am »
I am unsure if this is included with this issue, but I noticed when looking at PA 347 this morning that 14.29% of the travelers had traveled between GreRidSt and DriSt (the segment I added last night).

I could not find any record in Github showing that someone had added GreRidSt to their list files yet.

Online yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2040
  • Last Login:Today at 08:59:34 am
Re: Two bugs: route page % clinched by segment
« Reply #3 on: April 20, 2019, 11:53:28 am »
Don't think it's strictly related to this issue.
I've noticed that table can be a bit janky at times, especially in the first/last entries.
According to PA-region-traveled.tmg, there are no travelers on PA PA347 GreRidSt DriSt.