You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 6, 2025. It is now read-only.
When you say that lattice should work perfectly - I sort of wish to create a generic way to detect and extract tables without having to know which detection method (lattice / stream) is best for a given document - I want to decouple them as much as possible.
vinayak-mehta:
I get your use-case and it is not possible currently through the library itself. But I see two possibilities which can be implemented (both heuristics):
As far as I can tell from NurminenDetectionAlgorithm.java, Tabula first filters out all Lattice-type tables from the document and then looks for Stream-type tables, till it cannot find any more tables. Similarly, we can "couple" both flavors into a single one inside Camelot.
We can create a flavor called guess which automatically chooses between Lattice and Stream.
The text was updated successfully, but these errors were encountered:
Could you please let me know how i can auto detect when to use lattice and stream. I dont want to check manually rather need an automated way to identify
Thanks in advance
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Continuing the conversation from #102.
imri:
vinayak-mehta:
The text was updated successfully, but these errors were encountered: