User Discussions > Other Discussion

Two bugs: route page % clinched by segment

(1/7) > >>

mapcat:
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.

Jim:
https://github.com/TravelMapping/Web/issues/272

Markkos1992:
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.

yakra:
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.

Jim:
Both situations described in this thread have changed, so I can't test them directly.  I have poked around looking for similar examples and behavior for showroute seems correct in all cases I've tried.  I'm going to close the corresponding GitHub Issue.  Please reply here if it looks like I have done that too soon and the problems described still exist.

Navigation

[0] Message Index

[#] Next page