-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid bounding polygon computed exception during segmentation #632
Comments
Does it actually fail or does it just print this message and ignore the
line? The latter is expected, the former not.
What could cause this?
Usually polygonization fails for broken lines, e.g. short line
fragments, very high curvature, things like that.
|
Yes it fails and stops processing other images.
That's weird because I have much worse images that kraken processes fine. If I attach the image, will it help you to understand why this could happen? EDIT: Now that I think a bit more about it, I remember that the previous dev version worked fine, that is it skipped unsuccessful images and continued the work on other images. |
Hi, did you manage to reproduce the error? Do you think it should be easy to fix? |
Getting a new exception now, and the
|
Any news on fixing this? |
Sorry, it's vacation time in France so as a good assimilating foreigner I've been off all of August. Could you give me the image it happens on? And try the latest main branch as a bug in the polygonizer got fixed that caused weird bounding polygons (which are prone to triggering these kinds of shapely errors). |
Oh, sorry that I got on you, hope you had a good rest :) I use the latest dev version (I guess?) 5.2.9.dev6, get the exception:
|
Hi, just checking if you had time to find out what can cause the TopologyException during the segmentation?
|
I'm trying to segment a bunch of images, however the
segment
command fails at one of the images with the following error message:What could cause this?
Thanks in advance.
Traceback:
The text was updated successfully, but these errors were encountered: