You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But it's all handmade. I thought about a "simple" automatic solution.
I think an "Invers" button on the stats page could automatically replace the "Clinched Mileage" column by a "Not Clinched mileage" column and caluclate the % this way. Opening a map, the color parameters could be added and the color values could be inverted.
I think it has not an high priority but maybe the feature could be helpful.
The text was updated successfully, but these errors were encountered:
w.r.t. traveled vs not traveled colors, keep in mind that semi-transparent color represent sections not yet traveled. One can take the difference of traveled miles and total miles for the stats in web scripting in the not yet added feature though. I suspect this may be a bit overboard though.
I thought about how to figure out which sections of a system or region I have not yet traveled.
I can sort the stats table by % but I miss a "Not clinched mileage" column to see which are the longest routes I've not traveled.
In addition, how can I highlight the not yet traveled sections on the map?
It's possible by adding color parameters to the url (red = traveled, white = not traveled)
http://tm.teresco.org/hbtest/mapview.php?sys=luxa&u=michih&colors=tier1:rgb(255,255,255):rgb(255,69,0)
and inverting them (white = traveled, red = not traveled):
http://tm.teresco.org/hbtest/mapview.php?sys=luxa&u=michih&colors=tier1:rgb%28255,69,0%29:rgb%28255,255,255%29
But it's all handmade. I thought about a "simple" automatic solution.
I think an "Invers" button on the stats page could automatically replace the "Clinched Mileage" column by a "Not Clinched mileage" column and caluclate the % this way. Opening a map, the color parameters could be added and the color values could be inverted.
I think it has not an high priority but maybe the feature could be helpful.
The text was updated successfully, but these errors were encountered: