Skip to content
This repository has been archived by the owner on Jan 6, 2025. It is now read-only.

While using "stream" mode, I tried passing table_regions = ['10,710,604,72'](which I found using plot), it worked and gave me an output df. But, I also tried table_regions = ['170,370,560,270'](which I found in camelot documentation). This also gave me the same output. The coordinates are not even close, but how is camelot able to detect the table in pdf? #501

Open
Jashwanthreddy14 opened this issue Dec 13, 2023 · 0 comments

Comments

@Jashwanthreddy14
Copy link

Jashwanthreddy14 commented Dec 13, 2023

I have also tried manually finding coordinates and passing it in table_regions. In few cases, camelot is detecting 1 table as 2 tables. The 2nd table detected by camelot is having duplicate data which is already in table 1.

And the most weird thing is table_regions = ['170,370,560,270'](which I found in camelot documentation) is working for almost all my pdfs'.

@Jashwanthreddy14 Jashwanthreddy14 changed the title While using "stream" mode, I tried passing table_regions = ['10,710,604,72'](which I found using plot), it worked and gave me an output df. But, I also tried table_regions = ['170,370,560,270'](which I found in camelot documentation). This also gave me the same output. While using "stream" mode, I tried passing table_regions = ['10,710,604,72'](which I found using plot), it worked and gave me an output df. But, I also tried table_regions = ['170,370,560,270'](which I found in camelot documentation). This also gave me the same output. The coordinates are not even close, but how is camelot able to detect the table in pdf? Dec 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant