News for hackers. Stuff that matters.
Re:Documents OCR: Improving Efficiency by Making PDFs Search... by catchmeifyoucan on Saturday October 13, 2018 @02:35AM (#18206757)
$3200 seems pretty expensive. In the startup I used to work at, I was tasked with building something similar. Except, the documents I had to index was around 1000 pages each almost - they were building plans and diagrams. We did all of our processing within an AWS Lambda pipeline and Elasticsearch. Elasticsearch was the only real cost.
Re:Documents OCR: Improving Efficiency by Making PDFs Search... by matwood on Saturday October 13, 2018 @08:54AM (#18207714)
For 98% accuracy that's pretty cheap for OCRing a large number of pages. It wasn't that long ago that you had to use something like abbyy - now that was expensive.
Re:Documents OCR: Improving Efficiency by Making PDFs Search... by catchmeifyoucan on Saturday October 13, 2018 @11:26AM (#18208387)
Wow I didn't know. But I'd highly recommend using a lambda function and try with a local OCR library. To see if it afffects cost. No need for Google to be reading your docs. I believed I used PYOCR. Not sure how they got the 98% figure
Re:Documents OCR: Improving Efficiency by Making PDFs Search... by tensor on Saturday October 13, 2018 @11:58AM (#18208558)
I'm curious why you think Amazon isn't reading your docs (lambda function) but Google is?