HB: traveler mileage and percent

[Jim]

Code addressing the main feature requested in

https://github.com/TravelMapping/Web/issues/218

is now in the HB on tmtest.  Please give it a try.  I think it's pretty straightforward, but I'd like to get a little feedback before going live with it on the production site.

(Grades went in for the semester, and I felt I should knock off at least one item from the TM backlog before taking care of a bunch of other work-related items I have been putting off.)

[mapcat]

Found a bug:

http://tmtest.teresco.org/hb/?units=miles&u=mapcat&r=ca.ca163

(I just selected the route at random)

Even though I'm listed among those who have clinched the route, and my length traveled (10.87 mi) equals the total length (also 10.87 mi), my percent traveled is 99.97%.

Similar situation on two more short clinched routes:

http://tmtest.teresco.org/hb/?units=miles&u=mapcat&r=ca.ca056
http://tmtest.teresco.org/hb/?units=miles&u=mapcat&r=ca.ca282

Note that, for CA282, a route clinched by everyone who's driven it, the average traveled is 100.00% even though users are credited with 100.6%.

Longer routes don't have the problem:

http://tmtest.teresco.org/hb/?units=miles&u=mapcat&r=ca.i005
http://tmtest.teresco.org/hb/?units=miles&u=mapcat&r=ca.i010
http://tmtest.teresco.org/hb/?units=miles&u=mapcat&r=ca.i040

[Jim]

Ah, a rounding problem.  Thanks for finding it.  I think I've fixed it.

[mapcat]

Looks good!

[yakra]

Straightforward, and cleanly presented. As @mapcat noted on GitHub, we can compare our percent travelled to the average. I like.

[Jim]

This first improvement is now on the main site.  I'll see if I can implement the highlighting of segments in the waypoint table next.

[Jim]

Highlighting in the waypoint table for segments traveled by the selected user is now on tmtest.  Give it a look if you have a chance.

[mapcat]

Looks good to me. It's already helped me identify a short unclinched segment that's almost impossible to see on the map.

[michih]

It's already helped me identify a short unclinched segment that's almost impossible to see on the map.

There could be a "Goto first unclinched segment" button. On clicking, the marker box on the map could appear...

The last row should automatically get the same color like the second to last row.

[mapmikey]

Looks good to me. It's already helped me identify a short unclinched segment that's almost impossible to see on the map.

No idea how hard this would be...

How about an 'inverse' button that switches the bolded lines on the map to the unclinched segments...?

[Jim]

It's already helped me identify a short unclinched segment that's almost impossible to see on the map.

There could be a "Goto first unclinched segment" button. On clicking, the marker box on the map could appear...

A couple reasons not to do it at least not right away.  I hesitate to add more UI elements for something like that, and the page doesn't really store that kind of information for dynamic behavior.  At this point, the colors in the tables and on the map are set on creation and there's no information stored to allow such a search.

The last row should automatically get the same color like the second to last row.

My hesitation on this is because I think it would somehow imply two clinched segments at the end when one really exists.  The way to think about the table's colors is to see the segments that start at each point that are clinched or not.  It would be impossible to clinch a segment starting at the end.

[Jim]

No idea how hard this would be...

How about an 'inverse' button that switches the bolded lines on the map to the unclinched segments...?

Something to think about.  With the current code structure, I think this would require a page reload.  I'd like to put that off pending a better way to select colors overall.

[michih]

The last row should automatically get the same color like the second to last row.

My hesitation on this is because I think it would somehow imply two clinched segments at the end when one really exists.

As it is today. If you have clinched the entire route, the last segment is still indicated unclinched.... That's why I suggested to use the color of the previous segment. Who really cares about the number of segments traveled?

[Jim]

I don't know how hard it would be, but here's something I think would make some sense. 

[Jim]

Related to this, I'd like to replace the light pink to dark pink scale currently used to map percentages with something nicer.  One possibility is a scheme like CHM's, where high percentages are blue (or close) and low percentages are orange.  I never liked that a whole lot but I am also not sure what a better scale should look like.  I'd like to come up with a scheme and apply it in maps and tables throughout TM. 

Suggestions?