Run OCR for remote file
Process a remote file given via URL with the OCR API.Language used for OCR. If no language is specified, English eng
is taken as default.
IMPORTANT: The language code has always 3-letters (not 2). So it is eng
and not en
.
Engine2 has automatic Western language detection, so this value will be ignored. Any Western language can be processed.
Engine3 supports additional writing systems/languages. More can be added on request.
ara
bul
chs
cht
hrv
cze
dan
dut
eng
fin
fre
ger
gre
hun
kor
ita
jpn
pol
por
rus
slv
spa
swe
tur
Engine3 also supports:
hin
kan
per
tel
tam
tai
vie
true
, returns the coordinates of the bounding boxes for each word. If false, the OCR'ed text
is returned only as a text block (this makes the JSON reponse smaller). Overlay data can be used,
for example, to show text over the image.Specify how the response should be mapped to the table output. The following formats are available:
Raw Response: Returns the raw response in a single row with the following columns:
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
To use this node in KNIME, install the extension OCR Space from the below update site following our NodePit Product and Node Installation Guide:
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com, follow @NodePit on Twitter or botsin.space/@nodepit on Mastodon.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.