HSV colorspace clarification [closed]
I read that OpenCV uses 0-179° of Hue. In this link the best voted answer is that docs state that OpenCV uses 0-360°. But I did not find that paragraph stating that. What is thruth? I guess the fist. But main reason why I create this question, is it save to use this namespace or can I lose information. I often use Photoshop where the range is 360° or RGB o CMYK image. So if read the image savee using iRGB ICC profile, and then read it by OpenCV and then convert it to HSL, work with it, convert it back to RGB and save it, did I lost the information? And if I measure color ranges in Photoshop and then use color ranges for HSV image (converted from RGB) do I loose information. And what if I want to work with 360° degrees, is there any way how to convert to some different data type or namespace which will contain all the data and not lose it? I am used to work with HSV colorspace because this is the most "user friendly" colorspace, it is quite simple to change lightness or hue or saturation in this colorspace so this is why I am worried about inaccuracies.
You're guessing wrong: http://docs.opencv.org/master/de/d25/...
all hsv colorspace calculations work on the 0-360 range, H ist just stored in 0-180 range, to fit into a byte.
clarification to @berak's: 0-180 range modification is only performed when using 8-bits images. Otherwise, H is stored in 0-360 range
Thanks for explanation! So what image type RGB should I use exactly, not to lose it? CV_8U1, CV_8U3 will cause data lost. Do I need to use floats? So basicly I can use HSV but I need to use wider data type. But which one?
@LorenaGdL: It should be possible to force range 256 based on this expression:
int hrange = depth == CV_32F ? 360 : code == CV_BGR2HSV || code == CV_RGB2HSV || code == CV_BGR2HLS || code == CV_RGB2HLS ? 180 : 256;It is the 3rd parameter of function cvtColor