Overlay map color schemes

[jtstill]

For what it’s worth, it’s possible at the moment for an average user like me to see unhighlighted untraveled sections and keep what I have travelled in view, if I’m willing to dig a little: I just go to Inspect > Sources > updateConnectionColors() and update the opacity variable in that function to “1*highlight” instead of the default “0.3 + 0.55*highlight”, and then it applies the new opacity variable once I toggle the highlight options dropdown. Of course, I’d also love to see a front end way to do this, since I have to reapply those changes every time I reload the page or change the region (and the site still loads ALL segments, even the unhighlighted ones, so I can’t really do something like get the entire USA in view and then change the opacity settings, since it’ll never load. It’d be great to find a way to not even load untraveled segments so I can see the full extent of my personal travels)

[michih]

I have noticed that the blue lines tend to have less contrast between segments that are highlighted and those that aren't than the other colors do, especially when zoomed out.  In fact, If I show my travels on usai to people who aren't roadgeeks, they'll assume that I've clinched the whole system because the contrast is low enough they can't tell the difference.

Yep, I think it's just an issue with TMblue. Maybe one can suggest a better setting?

https://github.com/TravelMapping/Web/blob/master/lib/tmjsfuncs.js#L113

Code: [Select]

colorCodes[0] = { name: "TMblue", unclinched: "rgb(100,100,255)", clinched: "rgb(0,0,220)" };

And https://github.com/TravelMapping/Web/issues/581 is now implemented and on the main site.

For the colors= QS param, you can still specify a pair of CSS colors for clinched and unclinched (even the same one and rely on the opacity difference to indicate clinched vs. unclinched), but also now can specify a single TM predefined color (ones used in systems.csv, now with a "TM" prefix).

QS param for usai in NY with TMblue--> https://travelmapping.net/user/mapview.php?rg=ny&colors=usai:rgb(100,100,255):rgb(0,0,220)

[Nagamasa]

I think the unhighlighted salmon color is too light: I'm staring at it and I can't see it.

[michih]

I think the unhighlighted salmon color is too light

That's the current color: https://travelmapping.net/user/mapview.php?rg=jpn&colors=jpnh:rgb(224,162,162):rgb(240,150,115)
Feel free to change the rgb settings by editing the url (first = unclinched, second = clinched). Once you have good settings, you can suggest it for discussion here.

[pderocco]

That's the current color: https://travelmapping.net/user/mapview.php?rg=jpn&colors=jpnh:rgb(224,162,162):rgb(240,150,115)
Feel free to change the rgb settings by editing the url (first = unclinched, second = clinched). Once you have good settings, you can suggest it for discussion here.

It looks like the first is the unhighlighted and the second is the highlighted.

Also, it appears to support rgba as well as rgb, but the unhighlighted alpha is still scaled down by the default value. At least this gives us a way of turning the unlighted ones off completely.

It would be even nicer if you could use #rrggbb or #rrggbbaa hex colors, since they're a lot more compact.

[Nagamasa]

I think the unhighlighted salmon color is too light

That's the current color: https://travelmapping.net/user/mapview.php?rg=jpn&colors=jpnh:rgb(224,162,162):rgb(240,150,115)
Feel free to change the rgb settings by editing the url (first = unclinched, second = clinched). Once you have good settings, you can suggest it for discussion here.

Actually that color looks fine to me (TMlightsalmon), looks like jpnlex* were all set to TMblack. I'll just switch them all over? In the original photo, the color in question is the NW/SE rail line, which I don't think anyone even noticed.

[michih]

ah, got it! Standard colors like "salmon" had bad contrast. Thus, we set up TM colors like "TMlightsalmon".
https://github.com/TravelMapping/Web/blob/master/lib/tmjsfuncs.js#L113

[Nagamasa]

Looks like it used a nonexistent color "TMblack". Changed in my branch.

[Jim]

Changing color schemes will never gather unanimous support.  In some of our discussions over the winter, I believe we came up with a nice alternative, which I have just put onto the main site.  New shades of green and purple are now the default TMgreen and TMpurple, and I have changed all state highway systems in the US to use this new purple.  This will distinguish them other systems like usanp and usaush that continue to use (and make more sense using) TMbrown.

[mapcat]

Purple is a great choice, but the traveled purple doesn't contrast all that well with traveled magenta. Untraveled seems to contrast better. What do you think about making the traveled purple color a little darker?

[vdeane]

Is that a different purple?  It seems "bolder" than what I remember us testing.  The unclinched color might be a little too visible.

Yep, it is.  This is the last one I remember suggesting.  Also looks like the changes to the green color were not made.

[mapcat]

Yeah, that would definitely work.

[jtstill]

I imagine some people will scream bloody murder at this, but to my taste, I'd rather not have the translucent "unhighlighted" lines at all. All we'd need is two checkboxes, for Traveled and Untraveled. Since checkboxes can be manipulated much more quickly than a pull-down, it would be really easy to momentary enable the other one if you need to see those lines too.

Again, I know my pull is minimal, but since the topic’s come alive again it would be really nice to have an option to turn off translucent lines altogether — even if it’s just another choice in the drop down rather than a new spot for checkboxes (although I think the latter is ideal). Would it be any more complicated than a toggle influencing the opacity variable in the updateConnectionColors() function? I could be missing something.

Translucent On (default) —> “opacity = 0.3 + 0.55 * highlight”
Translucent Off (for users like pderocco and I) —> “opacity = highlight”

[Jim]

Fixing to install the last colors as they were on tmtest.  Looks like my install this morning did tmdevel instead of the production site.  You might need a force reload if your browser caches tmjsfuncs.js.

[mapcat]

How about changing the brown to purple in Canada too? There may be some equivalent of usatr or usanp there eventually. Yakra was working on cannss at one point.