What Resolution image is good for OMR

Aspose.OCR Product Family
1

Hi There,


I am using Aspose.OCR to process my OMR sheet, in my case the OMR images can be any(either scanned images, camera photos or webcam images) so what is the best resolution i should set to get correct result all the time.

I did set to 300 and editor behave in strange
- Show very small image when 300DPI image is loaded into editor
- and OMR element have fixed height, can’t reduce this to my bubble size(other elements too)

So currently i am using 96DPI, this works fine, but some time chances of not getting correct result.

Please find an attachment of image for more info, 1st image shows size of image uploaded, and 2nd shown height of OMR element is overlapping. it is not allowed to reduce height less than this.

Please suggest me something in this

Thanks, Veeresh
2
Hi Veeresh,

Thank you for your inquiry and providing sample files.

For showing very small image when 300 DPI image is loaded into OMR template editor, the issue has been logged into our issue tracking system with ID OCR-34343. Our product team will further look into it. We will update you accordingly via this thread.

For OMR template element fixed height and width issue, you can adjust the height and width of the element from properties in the property sheet panel on left hand side of the OMR template editor. A screenshot has been attached for your reference. In the screenshot, you can see a Choice Box element with height and width adjusted to accommodate your bubble size.

Hope the above information helps. Feel free to reach us in case you have further query or comments.

3
Hi Veeresh,

For the issue Show very small image when 300DPI image is loaded into editor, this is to update you that the template editor displays images close to print size of the image. For example if an image is small and its DPI value is high (e.g. 300 DPI), the editor will display the image even smaller because that is how the image will look like if printed.

Hope the above information helps. Feel free to reach us in case of any query or comments.

4

The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for JasperReports 18.3 update.