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
A DFG requirement when scanning is to show a part of the opposite page. On some pages this tends to be a problem, since anybaseocr-crop does not crop the text and later tools detect text/characters where they shouldn't.
Here are two examples.
What would be a strategy to tackle this?
The text was updated successfully, but these errors were encountered:
AFAICT this processor tries to avoid textual noise via separator line detection. There are a couple of (crappy and badly documented) parameters for this (rular...), but IMHO your best shot here would be trying to increase the contrast so the binarized image shows a distinct, contiguous vertical line where the gutter/spine is.
Besides binarization settings, there is a second workflow detail that might help: If you deskew before cropping, these lines should be easier to detect.
A DFG requirement when scanning is to show a part of the opposite page. On some pages this tends to be a problem, since
anybaseocr-crop
does not crop the text and later tools detect text/characters where they shouldn't.Here are two examples.
What would be a strategy to tackle this?
The text was updated successfully, but these errors were encountered: