Feature request: Invert a ColorScheme (inverse of `get`) about colorschemes.jl

[NHDaly]

Actually, after thinking about this a bit more, there are two separate parts to what I'm asking for...

1. The first is simply the ability to invert a linspace. That is, given a simple continuous scale, find the value in the domain at which the scale's range equals my value. That is what I did in the javascript above, and it is a completely independent question from this package. I should perhaps bring this question somewhere else.

2. The second request is to be able to find out that same thing (which value in the domain produces my range value, or color) but for a not-obviously-continuous value -- one that can't be represented by a linspace. This second class of problem is the problem space that this package works in: it provides a way to describe all colors used in an image on a single continuous scale. So for my initial use case (reading the values off an a heatmap image), this package seems like the correct place. :)

But if there already exists the ability to invert a linspace as I described in 1, above, then maybe we could implement the behavior I described in 2 as another method of that function. This would mirror the way this package provides another method for get.

Thanks! :)

[cormullion]

Hi! If you want to add your code to this package (via a PR if you like), I’d be delighted to help/assist in any way. This package could do with some more skilled contributors, I don’t understand what the code does myself sometimes ... :)

[NHDaly]

:) Hi @cormullion! :) Thanks, I've opened a PR.

Yeah, I'm looking forward to working together! I'm not sure if this is better discussed over there in the PR or here, but hopefully the README.ipynb demonstrates a bit about what I had in mind! :)

And haha okay sure. I'm not sure if I'll be a great long-term maintainer; I don't spend too much time working in this space either, mostly i was just playing. But yeah I'm happy to help out if needed!

[cormullion]

Looks pretty good to me. The package will need an overhaul in a few months when everything breaks on the road to v0.7/v1.0, so I think we should merge this and see how it works/what needs revising.