Low-resolution images can come from a variety of sources, but the most common source is probably screen capture. Screen capture images are usually 96 DPI on Windows. (This can vary depending on the user settings). Additionally, image representations of incoming faxes may also be considered low-res and fall under the resolution threshold acceptable for OCR. Typically, OCR engines require images of 200 or 300 DPI in order to achieve acceptable results.
Change Image Resolution
One easy solution for images that do not have noise or have complex structures is to change the resolution of the image before OCRing the image. This C# sample shows you how, then it gets the text from the image and outputs it to the console.
Right around the corner is one of our favorite industry conferences, RSNA. The annual event for the Radiological Society of North America will be held, once again, in the McCormick Center in Chicago, IL the week after Thanksgiving. If you are attending the conference or will be in the area between November 27 – December 2, 2016, stop by Hall B, Booth # 7707 to see the latest features and solutions LEADTOOLS has for the medical imaging industry.
Even today there are many organizations that rely on fax as a required form of communications. Because of this, receiving faxes is a requirement that much still be met. To do this, many organizations utilize fax services either hosted locally or by a third-party. Many of these services will email received faxes to users as a PDF file.
In a normal facsimile transmission, every other scan-line is skipped. This reduces the amount of data that needs to be sent over the relatively slow connection used to send faxes. To account for the missing scan-lines, the aspect ratio of the pixels is 2:1. It is important to recognize this when displaying the image else you will end up displaying the image incorrectly, making it looked squashed.
We are proud to announce that LEAD Technologies and its flagship SDK products, LEADTOOLS, are the recipients of several awards from ComponentSource. This global distributor has been one of our mainstays since 1995, serving thousands LEADTOOLS customers throughout Europe, Asia, Latin America, Africa, and Australia (if someone in Antarctica needs LEADTOOLS, I bet ComponentSource could do that too!). Continue reading
LEAD is continuously updating and adding new features to LEADTOOLS. One feature that was rolled into Version 19 after the initial release includes enhanced SVG support. This enhancement allows users to load document and vector formats as SVG, which can then be handed off to other parts of LEADTOOLS such as the Document Writers. In other words, you can convert from formats such as DOC, PDF, DWG, DXF, etc. to other document formats such as PDF/A, HTML, and SVG without rasterization or OCR.
In Convert a Word Document to PDF (C#), I pushed a project on GitHub to show how to do the conversion in .NET. Now I have pushed a C/C++ version of the project that will convert vector and document formats to PDF.
Last month we published a white paper on eDiscovery, which gave a brief overview on the Electronic Discovery Reference Model (EDRM). Today, we want to dive into more details about the EDRM and how it pertains to imaging and LEADTOOLS in particular.
Posted in Document Imaging
Tagged Document Converter, Document Imaging, Document Viewer, eDiscovery, EDRM, Forms Processing, Forms Recognition, OCR, PDF, Scanning, TWAIN
The cause of a
System.BadImageFormatException is a common question received by our developer support department. At first glance, some LEADTOOLS users think the
BadImageFormatException is a LEADTOOLS specific exception because LEADTOOLS is an imaging SDK and “Image” is in the name of the exception. However, the exception has nothing to do with LEADTOOLS being an imaging SDK.
This exception is thrown when a process tries to load an assembly that is built for an incompatible architecture. The MSDN description of the exception is: