I think I might have found a bug in the codebase. I am using version 0.9.0 of camelot-py and the following line uses a strange order for the bounding box definition:
The docstring in text_in_bbox specifies that a Tuple (x1, y1, x2, y2) should be passed. (x1, y1) is the lower left corner of the box and x2, y2 is the upper right corner.
Could somebody please check whether this is in fact a bug? I believe it might be causing the ZeroDivisionError problem when using table_regions, since the text_in_bbox fails to return any text...
I think I might have found a bug in the codebase. I am using version 0.9.0 of
camelot-py
and the following line uses a strange order for the bounding box definition:https://github.com/atlanhq/camelot/blob/cd8ac7979fe3631866fe439f07e9d6aaa5b1e5c6/camelot/parsers/stream.py#L305
The docstring in
text_in_bbox
specifies that aTuple (x1, y1, x2, y2)
should be passed.(x1, y1)
is the lower left corner of the box andx2, y2
is the upper right corner.Could somebody please check whether this is in fact a bug? I believe it might be causing the
ZeroDivisionError
problem when usingtable_regions
, since thetext_in_bbox
fails to return any text...