Get a color name from any RGB combination(gauth.fr)
gauth.fr
Get a color name from any RGB combination
http://gauth.fr/2011/09/get-a-color-name-from-any-rgb-combination/
11 comments
I also noticed the problem with darker colors. I introduced several ideas in the article: using a different metric or a different colorspace. This could help, but if we really have a lower points density in the darker zones, the good solution might be to find even more colors on the internet.
Your proposed solution looks to be a mix of changing the color space and the metric. Maybe we could use HSL/HSV with a metric that reduces the weight of some component. It could therefore consider less the fact that the three components are high/low, but focus on the "real" color side.
Your proposed solution looks to be a mix of changing the color space and the metric. Maybe we could use HSL/HSV with a metric that reduces the weight of some component. It could therefore consider less the fact that the three components are high/low, but focus on the "real" color side.
Increasing the dataset of color names doesn't really work as well to address this problem in my opinion. I looked at a pretty large set of colors of 5000+ and I discarded it because it just introduced too many exotic sounding names only a color expert can tell apart - it wasn't an UI improvement and it still doesn't give consistent results for the darkest and lightest colors.
I think working with HSL values works better in principle. Just adjusting the lightness value can be used to arrive at a more sensible color description. The most common lightness values for color names hover around 50% (at least in the 3000+ dataset I compiled). One solution is to have a simple formula that takes in account how accurate the nearest color name match is and if it is too inaccurate, to find the color name for the color's HSL with the L adjusted to 50%. I guess you could call it staying true to the hue. I think that would make the color naming script even more useful though.
I think working with HSL values works better in principle. Just adjusting the lightness value can be used to arrive at a more sensible color description. The most common lightness values for color names hover around 50% (at least in the 3000+ dataset I compiled). One solution is to have a simple formula that takes in account how accurate the nearest color name match is and if it is too inaccurate, to find the color name for the color's HSL with the L adjusted to 50%. I guess you could call it staying true to the hue. I think that would make the color naming script even more useful though.
One solution could be to use several points for each label (color name). For instance, we could use a limited set of color names (red, green, blue, etc) but have a lot of points associated to this labels. For example, different points like #07250b (that is, in my opinion, missclassified) and #51f665 could share a same label: green. The main problem is that I'm not sure It is possible to find such a dataset on the internet. Maybe we can build one from sites like http://cloford.com/resources/colours/500col.htm, removing the numbers from each color name.
With several points for each label, It will give us the possibility of using a 3NN, for example, instead of a 1NN classifier. It should impact also on the results, but I'm not sure it will really improve the results.
With several points for each label, It will give us the possibility of using a 3NN, for example, instead of a 1NN classifier. It should impact also on the results, but I'm not sure it will really improve the results.
The trouble with these names is that you have things like #7a937d comes up as Xanadu. And there are other weird names in there like "Blanched Almond" and "Bubble gum" which are fine if everyone knows you're talking about a colour, but if you're trying to build, say, an image tagging script you don't really want "bubble gum" being put as the tag instead of "pink".
As explained in the article, you need to choose the dataset that fits your needs. And you're right, a smaller dataset with more common names will be more useful in some cases.
You may want to try using the colr.org API:
http://www.colr.org/api.html
The entire colr.org dataset isn't available, but you can make ajax requests for individual hex values, typically in less than 100ms.
The dataset should also include the standard CSS and HTML color names. This was part of the initial buildout several years ago.
http://www.colr.org/api.html
The entire colr.org dataset isn't available, but you can make ajax requests for individual hex values, typically in less than 100ms.
The dataset should also include the standard CSS and HTML color names. This was part of the initial buildout several years ago.
You should try it with the xkcd color dataset.
http://blog.xkcd.com/2010/05/03/color-survey-results/
http://blog.xkcd.com/2010/05/03/color-survey-results/
EasyRGB is nice for matching them to actual paint colors and names: http://easyrgb.com/index.php?X=SEEK
I was wondering what to do with darker colors as they are less represented in terms of color names. So, when you pick a random darkish color the accuracy reduces because there are less names to choose from.
I was thinking perhaps the best solution would be in these cases to extrapolate a lighter variation of the picked color and display that color with a measure of its darkness (30% darker purple). Right now, if you pick a color like #291c36 you'll get dark jungle green when it's a dark purple. Any thoughts on tackling that problem?