Florent Tomi's profile - activity

Hello !

One of my algorithms constructs points which should represent a contour. My problem with these points is the order. There is no reason these points have the correct connection order in order to be able to build a contour (for example, passing these to cv::drawContours will result in a mess...).

How should I order these points to satisfy the contour definition of OpenCV ? Is it even possible ?

Thanks !

I can't post any code (I am not allowed to...), but I'll try to give you an example. Let's say you have found a contour

I can't post any code (I am not allowed to...), but I'll try to give you an example. Let's say you have found a contour

Building contours from points Hello ! One of my algorithms constructs points which should represent a contour. My probl

Thanks for the quick answer. I assume OpenCV is also meant to be memory efficient so a straightforward change from int

Hello !

I'm working on large images (~65000x40000 on average). I've experienced multiple issues with some functions (ie. cv::threshold and cv::medianBlur) that I don't have if I downscale these images.

After some code digging, I think the issue comes from the use of "int" types in most functions which, obviously, can't fit my size.

For example, in functions cv::threshold with Triangle method, operations like this are done:

size.width *= size.height

Is there any "easy" solution to use "int64" instead of "int" in OpenCV ? I've tried to change cv::Size alias from Size2i to Size2l but it isn't enough as most of OpenCV functions uses "int" as input/output type...

Thanks :)

Very (very) large image causes issues with function (int type related) Hello ! I'm working on large images (~65000x4000